Topo POC V2 Documentation
Topo Proof of Contribution (POC) V2 is a validator-driven distributed computation protocol. It converts mature DApp contribution, confirmed through a trusted on-chain path, into verifiable, governed, and composable on-chain Power.
Documentation Map
| Document | Core question |
|---|---|
| POC V2 Whitepaper | How trusted contribution becomes Activated Power through independent Validator computation, weighted QC, and atomic activation |
| System Architecture and Component Boundaries | How the L5–L0 architecture separates authority, computation, persistence, communication, and delivery |
| Distributed Settlement Protocol | How periods, snapshots, deterministic computation, Artifact, Vote/QC, Candidate, and automatic catch-up work |
| DApp Integration Reference Case | How a DApp defines contribution maturity, uses trusted issuance, and handles settlement, refunds, and disputes |
| Security, Verification, and Production Readiness | Threat model, key separation, data availability, recovery, tests, and launch gates |
Recommended Reading Paths
| Reader | Recommended order |
|---|---|
| Ecosystem partners and governance participants | Whitepaper → DApp Integration Reference Case |
| Protocol and security reviewers | Whitepaper → Distributed Settlement Protocol → Security and Production Readiness |
| Validator and infrastructure teams | System Architecture → Distributed Settlement Protocol → Security and Production Readiness |
| DApp development teams | Whitepaper → DApp Integration Reference Case → System Architecture |
| Test and operations teams | Security and Production Readiness → Distributed Settlement Protocol |
Protocol Model
POC V2 consists of five consecutive trust boundaries:
| Boundary | Authoritative result |
|---|---|
| Contribution formation | The DApp state machine confirms a mature business fact |
| Trusted issuance | poc_contribution, constrained by Registry, produces a finalized ContributionEvent |
| Deterministic computation | Validators derive the same Commitment independently from the same Active cursor and finalized inputs |
| Result attestation | Strictly more than two-thirds of full Committee voting power signs the same result, forming a QC |
| Atomic activation | A complete Candidate atomically updates the Active root, version, and cursor |
Downstream Staking, Voting, and other modules read Activated Power only. They do not read local databases, Artifacts, provisional Validator outputs, or an unactivated Candidate.
Core Terms
| Term | Definition |
|---|---|
| ContributionEvent | A finalized contribution event produced through the trusted POC path |
| DApp equity token | The on-chain token that carries contribution entitlement and establishes a price identity |
| Registry | The governance module for App identity, equity token, custody, admission state, and weight |
| Latest Stable Price | The latest price formed by a closed Topo DEX period and recoverable at a specified finalized fence |
| Active cursor | last_power_update_period, the greatest source period fully included in current Active Power |
| Context | The computation context binding chain, Active base, covered range, input roots, price snapshot, and Committee |
| Artifact | Content-addressed evidence for replaying inputs, proofs, Patch, and Batches |
| Commitment | The result commitment over Context, Affected users, Patch, post-state, Batch set, and Artifact digest |
| QC | A strictly-greater-than-two-thirds weighted attestation to the same Context and Commitment |
| Candidate | A QC-bound result that is not yet consumable on-chain Power |
| Activated Power | The only authoritative Power exposed to downstream modules after atomic activation |
Normative Language
In this documentation, must denotes a protocol or security requirement, should denotes a recommended production practice, and may denotes an implementation choice that does not change the core security properties.