Tribechain RPC — PoT-O RFC Series
This section contains the PoT-O-related Tribechain RPC proposals. They define the design, architecture, and standards for the TribeWarez testnet RPC gateway and Proof of Tensor Optimizations (PoT-O) consensus.
RFC Overview
| RFC / Document | Scope | Implementations |
|---|---|---|
| PoT-O V1 | Conceptual introduction and base concepts | Docs only |
| PoT-O V2 / TW-RPC-001 | PoT-O core protocol, validator, Solana program | pot-o-validator, tribewarez-pot-o, API Reference |
| PoT-O V3 / TW-RPC-003 | Staking, reputation, yield | tribewarez-staking, DeFi staking UI |
| PoT-O V4 / TW-RPC-004 | Vault / treasury | tribewarez-vault, DeFi vault UI |
| PoT-O V5 / TW-RPC-005 | PQC, Tor/onion, mesh | pot-o-validator extensions, infra |
Expected users and implementers
These proposals are maintained as internal Tribechain RPC standards (project RFC-style). For IETF "who will use it?" alignment:
- Reference implementer: TribeWarez Project Team. Implementations are documented in Implementation Mapping and deployed on testnet (
testnet-solana.rpc.gateway.tribewarez.com,pot.rpc.gateway.tribewarez.com). - Code and services: Off-chain
pot-o-validator(Rust), on-chain Solana programs (tribewarez-pot-o,tribewarez-staking,tribewarez-vault), and Docker/infra in the TribeWarez ecosystem. - Adopters: External adopters will be listed here if and when they commit to implementing or deploying these specs.
IETF alignment and submission notes
These documents are not IETF Internet-Drafts. They use project-specific naming (TW-RPC-00x, PoT-O V1–V5) and do not include IETF boilerplate (Status of This Memo, Copyright, IPR). If submission to the IETF were pursued:
- Intended outcome: Informational RFC or Independent Submission Stream (project-specific consensus and tokenomics), unless an IETF WG charters work on a subset (e.g. Tor/PQC integration).
- Venue: DISPATCH (for technology-specific I-Ds) or Independent Submission; Working Group or BOF only if community and AD support develop.
- IPR: Standard IETF contributor rights and patent disclosure (BCP 78, BCP 79) would apply at submission time; no such grant or disclosure is made by the current project documentation.
See Bringing new work to the IETF for the full process.
IETF Internet-Drafts
IETF-relevant content (PQC hybrid signatures, Tor onion integration) is extracted into separate Internet-Draft sources for submission. See IETF Internet-Drafts for the draft list and source links; the .txt versions for IETF submission are generated from the .mkd sources using kramdown-rfc2629 and xml2rfc (build steps in that directory’s README).
Resources
- Implementation Mapping — RFC-to-code and service mapping.
- Hugging Face — Tribewarez models, datasets, and Spaces.
- Crates & API — Rust crates and validator API index.