About the Tari RFC documents
1.
Proposed
❱
1.1.
TIP-PROC-1: Tari Improvement Proposals
1.2.
TIP-PROC-3: Community Forums
1.3.
TIP-RFC-O-8003: Tari Use Cases
2.
Accepted
❱
2.1.
TIP-RFC-MT-0241: XMR Atomic swap
3.
Implemented
❱
3.1.
TIP-PROC-2: The Tari Community Charter
3.2.
TIP-0005: Adjust Bridge Limits
3.3.
RFC
❱
3.3.1.
RFC-0001: An overview of the Tari network
3.3.2.
The Tari Base Layer
❱
3.3.2.1.
MT-0110: Base nodes
3.3.2.2.
MT-0111: Base node architecture
3.3.2.3.
MT-0120: Consensus rules
3.3.2.4.
MT-0131: Mining
3.3.2.5.
MT-0132: Merge Mining Monero
3.3.2.6.
MT-0140: Synchronizing the Blockchain: Archival and Pruned modes
3.3.2.7.
MT-0150: Wallets
3.3.2.8.
MT-0154: Deep Links
3.3.2.9.
MT-0155: TariAddress
3.3.2.10.
MT-0160: Block Binary Serialization
3.3.2.11.
MT-0170: Network Communication Protocol
❱
3.3.2.11.1.
MT-0171: Message Serialisation
3.3.2.11.2.
MT-0172: Peer to Peer Messaging Protocol
3.3.2.11.3.
MT-0173: Versioning
3.3.2.11.4.
MT-0174: Chat Metadata
3.3.2.12.
MT-0181: Bulletproofs+ range proving
3.3.2.13.
MT-0182: Commitment signatures
3.3.2.14.
MT-0190: Mempool
3.3.2.15.
Tari-specific extensions to Mimblewimble
❱
3.3.2.15.1.
MT-0201: TariScript
3.3.2.15.2.
MT-0202: TariScript Opcodes
3.3.2.15.3.
MT-0204: TariScript Examples
3.3.2.15.4.
MT-0203: Stealth Addresses
3.3.2.15.5.
MT-0205: Hardware Transactions
3.3.2.15.6.
MT-0250: Covenants
3.3.3.
Applications
❱
3.3.3.1.
MT-0123: Mitigating One-sided payment replay attacks
3.3.3.2.
MT-0153: Staged Wallet Security
3.3.3.3.
MT-0230: Hash time locked contracts
3.3.3.4.
MT-0240: Atomic swap
3.3.3.5.
MT-8001: Multi-party transactions
4.
Deprecated
❱
4.1.
RFC
❱
4.1.1.
MT-0010: Tari code structure and organization
4.1.2.
MT-0121: Consensus encoding
4.1.3.
MT-0130: Mining
4.1.4.
MT-0141: Sparse Merkle Tees
4.1.5.
MT-0152: Emoji ID
4.1.6.
MT-0180: Bulletproof range proof rewinding
4.1.7.
O-0300: The Digital Assets Network
4.1.8.
O-0301: Namespace Registration
4.1.9.
O-0302: Validator Nodes
4.1.10.
O-0304: Validator Node committee selection
4.1.11.
O-0306: DAN Template Registration
4.1.12.
O-0311: Digital Asset templates
4.1.13.
O-0312: High level Digital Asset Network Specification
4.1.14.
O-0322: Validator Node Registration
4.1.15.
O-0340: Validator Node Consensus
4.1.16.
O-0341: Asset registration
4.1.17.
O-0345: Asset Life cycle
4.1.18.
O-0360: NFT sale using MimbleWimble Invoice
4.1.19.
O-0500: Tari payment channels
4.1.20.
MT-8002: Transaction protocol
5.
Unknown status
❱
5.1.
RFC-0303: The Tari Digital Assets Network
5.2.
RFC-0313: Validator Node Registration
5.3.
RFC-0320: The turbine model
5.4.
RFC-0350: The Tari Virtual Machine
5.5.
RFC-0305: The Tari Network Consensus Layer
5.6.
RFC-0314: Validator node committee selection
5.7.
RFC-0321: Processing foreign proposals
5.8.
RFC-0325: Epochs and time management
5.9.
RFC-0330: The Cerberus-Hotstuff consensus algorithm
5.10.
RFC-0331: Indexers
5.11.
RFC-0310: Submarine swaps
5.12.
RFC-0388: Bearer tokens
5.13.
RFC-0385: Privacy-enabled Stablecoin contract design
5.14.
RFC-0323: Tari throttle exploratory analysis
6.
RFC template
7.
Glossary
Deprecated RFC
The following documents are either obsolete, or have been superseded by newer RFC documents.
