Reference
Conventions (TCCs)
Tenrai Calls for Conventions are voluntary standards that wallets, explorers and mining software share. What a TCC is and the conventions in use today.
On this page
A Tenrai Call for Conventions (TCC) describes a standard that software follows by choice. No consensus rule enforces it: a node treats a transaction or a block the same whether a convention was followed or not. Software that follows the same TCC works together. A wallet file opens in another wallet, every wallet reads the same payment link, and a miner talks to every pool.
Changes to the protocol itself are not conventions. They are improvement proposals (TIPs).
Conventions in use
| Number | Convention | Category | Status |
|---|---|---|---|
| TCC-0001 | Wallet derivation | Wallet | Final |
| TCC-0002 | Wallet file | Wallet | Final |
| TCC-0003 | Address verification words | Wallet | Final |
| TCC-0004 | Address ownership proof | Wallet | Final |
| TCC-0005 | Recipient payloads | Payments | Final |
| TCC-0006 | Payment requests | Payments | Final |
| TCC-0007 | Mining protocol V1, tenrai-mining-v1 | Mining | Final |
| TCC-0008 | Mining protocol V2, tenrai-mining-v2 | Mining | Final |
| TCC-0009 | Messenger: chats, long texts, voice messages, answers, forwards, reactions | Messaging | Final |
The Tenrai wallets, libraries and mining software follow these conventions. Tenrai has no tokens, NFTs or smart contracts, so there are no conventions for them.
New conventions
The tenrai-tcc repository holds every TCC as a document of its own, the definitions they share and a template. A TCC has a header like a TIP, with a category in place of the type and the identifier that tells its format apart, and goes through the same review stages. Its sections are the abstract, the motivation, the specification, the rationale, the security considerations, and the test vectors and implementations.
A new convention starts as tcc-draft-<short-name>.md in a pull request to that repository and gets its number when it moves to review.
