Source register and authority
APPROVED · IMPLEMENTATION SPECIFICATION · London 0.1.0
Current source
The pinned source manifest contains exact SHA-256 hashes and repository revisions for the canonical Porto sources reviewed. Those sources describe existing product/protocol intent, not evidence of this MVP running. Source authority: whitepaper for company/product intent; PIPs for their specified mechanisms; this approved directory for London-specific implementation departures.
| Source | Relevant exact sections | Use |
|---|---|---|
| Whitepaper | §§3.2 System overview, 3.3 Revenue split, 4.2 chain, 6.2-6.5 streaming, 7.2 user-centric model, 8 Governance, 9 Phased Rollout | Intent, trust transition and economic context |
| PIP-2 | System overview, Revenue split, Node roles, Phased rollout | Original network model |
| PIP-3 | §§1-7 token identity through staking interplay | Explicitly excluded token mechanics |
| PIP-4 | §§1-8 streaming architecture through migration | Eligibility and central trust context; London changes documented |
| PIP-5 | §§1-5 listener accrual through cost bounding; Security Considerations | Listener attribution and rights split context |
| PIP-6 | §§1-5 node modes through Beta exemption | Distinguish delivery, attestation and validators |
| PIP-7 | §§1-4 governed parameters through migration | Governance contrasts |
| RFC 8785 | §3 canonicalisation, Appendix D large integers | Canonical signed and hashed bytes |
| Aptos transaction management | Sequence, submission and recovery guidance | Implementation must pin and test actual SDK/framework semantics |
External technical references inform implementation review; they are not provider agreements or proof of a deployed Porto integration. Pin actual framework/SDK/issuer asset references in L07 before Mainnet. Do not copy a native-USDC address from an example or assume any token named USDC is the approved asset.
Storage-engine references
RocksDB Transactions documents TransactionDB and explicit read/write conflict protection. Basic Operations documents synchronous writes and process ownership. Backup guidance documents engine backup facilities. Porto's deterministic command protocol, single-owner policy, journal and migration boundary are approved design decisions specified in chapter 27, not capabilities supplied automatically by RocksDB.
Approval and supersession evidence
On 22 September 2026 the product owner approved the reduced MVP after agreeing that it must retain artist/third-party-owned infrastructure and real peer participation. The owner requested this complete specification and status APPROVED. The new baseline supersedes the broader London draft, while preserving its navigable documentation structure. No supplied roadmap PDF was available in this authoring task, so none is cited as read or used.
This source register establishes where decisions came from. It does not establish implementation, regulatory status, licences, audits, deployment, real payments or observed demand. Those are captured separately in the release/pilot evidence record.