Erik GrinakerandGitHub
3ab6026ad7
* Added RFC for truncated block history coordination * Clarified minimum block retention * Added hard checks on block retention and snapshot interval, and made some minor tweaks * Genesis parameters are immutable * Use local config for snapshot interval * Reordered parameter descriptions * Clarified local config option for snapshot-interval * rewrite for ABCI commit response * Renamed RFC * add block retention diagram * Removed retain_blocks table * fix image numbers * resolved open questions * image quality
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.