github.com/KYVENetwork/cometbft/v38@v38.0.3/docs/rfc/README.md (about) 1 --- 2 order: 1 3 parent: 4 order: false 5 --- 6 7 # Requests for Comments 8 9 A Request for Comments (RFC) is a record of discussion on an open-ended topic 10 related to the design and implementation of CometBFT, for which no 11 immediate decision is required. 12 13 The purpose of an RFC is to serve as a historical record of a high-level 14 discussion that might otherwise only be recorded in an ad-hoc way (for example, 15 via gists or Google docs) that are difficult to discover for someone after the 16 fact. An RFC _may_ give rise to more specific architectural _decisions_ for 17 CometBFT, but those decisions must be recorded separately in 18 [Architecture Decision Records (ADR)](../architecture/). 19 20 As a rule of thumb, if you can articulate a specific question that needs to be 21 answered, write an ADR. If you need to explore the topic and get input from 22 others to know what questions need to be answered, an RFC may be appropriate. 23 24 ## RFC Content 25 26 An RFC should provide: 27 28 - A **changelog**, documenting when and how the RFC has changed. 29 - An **abstract**, briefly summarizing the topic so the reader can quickly tell 30 whether it is relevant to their interest. 31 - Any **background** a reader will need to understand and participate in the 32 substance of the discussion (links to other documents are fine here). 33 - The **discussion**, the primary content of the document. 34 35 The [rfc-template.md](./rfc-template.md) file includes placeholders for these 36 sections. 37 38 ## Table of Contents 39 40 The RFCs listed below are exclusively relevant to CometBFT. For historical RFCs 41 relating to Tendermint Core prior to forking, please see 42 [this list](./tendermint-core/). 43 44 <!-- - [RFC-NNN: Title](./rfc-NNN-title.md) --> 45 - [RFC-100: ABCI Vote Extension Propagation](./rfc-100-abci-vote-extension-propag.md)