zolfa
/
tendermint
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 221 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
167 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: 4a9bcebe2a
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '4a9bcebe2a'
${ noResults }
tendermint/rfc
Callum Waters b39af911ae
RFC: ReverseSync - fetching historical data (#224) 		4 years ago
..
images ABCI++ RFC (#254) 4 years ago
001-block-retention.md ci: add markdown linter (#146) 4 years ago
002-nonzero-genesis.md ci: add markdown linter (#146) 4 years ago
003-ed25519-verification.md RFC: adopt zip 215 (#144) 4 years ago
004-abci++.md ABCI++ RFC (#254) 4 years ago
005-reverse-sync.md RFC: ReverseSync - fetching historical data (#224) 4 years ago
README.md RFC: ReverseSync - fetching historical data (#224) 4 years ago
rfc_template.md This PR is to create signed commits to be able to merge (#50) 5 years ago

README.md

Request for Comments (RFC)

RFC stands for Request for Comments. It is a social device use to float and polish an idea prior to the inclusion into an existing or new spec/paper/research topic.

An RFC should not be used for bug reports or trivial discussions - the overhead of compiling an RFC does not justify it.

An RFC should not consist only of a problem statement (use a standard issue for that).

A RFC should consist of:

  • Changelog
  • Context on the relevant goals and the current state
  • Proposed Solution
  • Summary of pros and cons
  • References

If recorded decisions turned out to be lacking, convene a discussion, record the new decisions here, and then modify the code to match.

Note the context/background should be written in the present tense.

Some RFC's will be presented at a Tendermint Dev Session. If you are an outside contributor and have submitted a RFC, you may be invited to present your RFC at one of these calls.

Table of Contents