* Update docs references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update DOCS_README to reflect current reality Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update vuepress config with current versions and updated discussions link Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update generated docs versions Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update docs build to use temp folder instead of home Signed-off-by: Thane Thomson <connect@thanethomson.com> * Document build-docs Makefile target Signed-off-by: Thane Thomson <connect@thanethomson.com> * Add serve-docs Makefile target to serve local build of docs Signed-off-by: Thane Thomson <connect@thanethomson.com> * Ensure 404 page is copied during docs build Signed-off-by: Thane Thomson <connect@thanethomson.com> * Redirect /master/ to /main/ Signed-off-by: Thane Thomson <connect@thanethomson.com> * Attempt to resolve #7908 Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update OpenAPI references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update CHANGELOG references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update Docker readme references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update UPGRADING references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update package-specific documentation references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update spec references from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update all code comment references to docs site from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Build v0.34.x as "latest" Signed-off-by: Thane Thomson <connect@thanethomson.com> * Explicitly mark v0.34 docs as latest in version selector Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update all links from docs.tendermint.com/main to docs.tendermint.com/latest Signed-off-by: Thane Thomson <connect@thanethomson.com> * ci: Redeploy docs on pushes to v0.34.x Signed-off-by: Thane Thomson <connect@thanethomson.com> * Temporarily copy spec directory into docs while building Signed-off-by: Thane Thomson <connect@thanethomson.com> * Add nav link to main and clearly mark as unstable Signed-off-by: Thane Thomson <connect@thanethomson.com> * Revert to only publishing docs in nav for v0.34 and v0.33 with no latest Signed-off-by: Thane Thomson <connect@thanethomson.com> * Link to docs.tendermint.com/v0.34 from RFCs Signed-off-by: Thane Thomson <connect@thanethomson.com> * Rather just use main for all docs.tendermint.com references on main branch Signed-off-by: Thane Thomson <connect@thanethomson.com> * Rename GitHub tree links from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update link for ABCI Rust client Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update github links from master to main Signed-off-by: Thane Thomson <connect@thanethomson.com> * Update badges in root readme Signed-off-by: Thane Thomson <connect@thanethomson.com> * Remove codecov badge since we do not use it any more Signed-off-by: Thane Thomson <connect@thanethomson.com> * Remove Java and Kotlin tutorials Signed-off-by: Thane Thomson <connect@thanethomson.com> * Remove specs from docs build Signed-off-by: Thane Thomson <connect@thanethomson.com> * Migrate spec links to GitHub repo from docs site Signed-off-by: Thane Thomson <connect@thanethomson.com> * Remove references to non-existent PEX reactor spec Signed-off-by: Thane Thomson <connect@thanethomson.com> * Fix linting badge in README Signed-off-by: Thane Thomson <connect@thanethomson.com> Signed-off-by: Thane Thomson <connect@thanethomson.com>
order, parent
| order | parent | ||
|---|---|---|---|
| 1 |
|
Requests for Comments
A Request for Comments (RFC) is a record of discussion on an open-ended topic related to the design and implementation of Tendermint Core, for which no immediate decision is required.
The purpose of an RFC is to serve as a historical record of a high-level discussion that might otherwise only be recorded in an ad hoc way (for example, via gists or Google docs) that are difficult to discover for someone after the fact. An RFC may give rise to more specific architectural decisions for Tendermint, but those decisions must be recorded separately in Architecture Decision Records (ADR).
As a rule of thumb, if you can articulate a specific question that needs to be answered, write an ADR. If you need to explore the topic and get input from others to know what questions need to be answered, an RFC may be appropriate.
RFC Content
An RFC should provide:
- A changelog, documenting when and how the RFC has changed.
- An abstract, briefly summarizing the topic so the reader can quickly tell whether it is relevant to their interest.
- Any background a reader will need to understand and participate in the substance of the discussion (links to other documents are fine here).
- The discussion, the primary content of the document.
The rfc-template.md file includes placeholders for these sections.
Table of Contents
- RFC-000: P2P Roadmap
- RFC-001: Storage Engines
- RFC-002: Interprocess Communication
- RFC-003: Performance Taxonomy
- RFC-004: E2E Test Framework Enhancements
- RFC-005: Event System
- RFC-006: Event Subscription
- RFC-007: Deterministic Proto Byte Serialization
- RFC-008: Don't Panic
- RFC-009: Consensus Parameter Upgrades
- RFC-010: P2P Light Client
- RFC-011: Delete Gas
- RFC-012: Event Indexing Revisited
- RFC-013: ABCI++
- RFC-014: Semantic Versioning
- RFC-015: ABCI++ Tx Mutation
- RFC-016: Node Architecture
- RFC-017: ABCI++ Vote Extension Propagation
- RFC-018: BLS Signature Aggregation Exploration
- RFC-019: Configuration File Versioning
- RFC-020: Onboarding Projects
- RFC-021: The Future of the Socket Protocol
- RFC-023: Semi-permanent Testnet
- RFC-024: Block Structure Consolidation