BCCS answers a point-in-time question: what is the verified state of this biological asset? The BCCS Global Registry answers a different question: has the clearing obligation on this territorial asset reached finality?
One protocol. Two layers. One records truth. The other records settlement. Together they form the complete data stack for territorial bio-capital — from individual verification queries on Base L2 to sovereign-grade clearing infrastructure across 175 jurisdictions.
The BCCS protocol is not a single system. It is a vertical stack where each layer produces data consumed by the next. Verification produces state. Registry records the state progression. Clearing marks the progression as final. Each layer is independently operable, collectively indispensable.
Records clearing-state progression of every registered Territorial Bio-Asset Record. Seven-state irreversible ratchet. Tri-jurisdiction hosting (HK · UAE · SG). Institutional-grade tamper evidence via Merkle trees. The settlement layer.
The Territorial Bio-Asset Record object: GeoJSON boundary, measurement dataset, verification records, legal vehicle, exclusions, capital_eligibility flag. BAIN ID as primary key across all layers. Append-only, Merkle-anchored.
ERC-20 verification unit ($BCCS), soulbound ERC-721 Node Licenses, three-tier oracle consensus (satellite, IoT, inspection), Proof-of-Physical-State attestations, on-chain query API. The trust-machine for biological state.
A verification query on BCCS returns the current verified state of a biological asset at a moment in time. A registry query on BioClearing returns the clearing history of that asset across all time. The difference is not semantic. It is the difference between knowing a fact and having a record of the fact.
The 21-character Bio-Asset Identification Number is the primary key of the entire protocol. It is issued on BCCS at initial observation, persists through all verification states, extends seamlessly into the clearing registry, and survives every transition — including reversal and re-entry. One identifier. Every layer. Forever.
Why this matters architecturally. When a node operator on BCCS submits a verification attestation, the BAIN ID in their payload is identical to the BAIN ID in the BioClearing registry. There is no translation layer, no lookup table, no identifier mapping. An auditor querying RU-KAR-PEG-001-7 on BCCS and the same string on BioClearing is querying the same asset through two different lenses — verification state and clearing state.
This is how institutional data infrastructure compounds. Every layer of the protocol stack addresses the same asset by the same name. The BAIN ID is the CUSIP of territorial bio-capital.
Every entry in the BCCS Global Registry conforms to the Territorial Bio-Asset Record schema. Nine canonical fields. Each field is either queryable by auditor, consumable by smart contract, or both. The schema is append-only — once written, a field’s value enters the state history but is never overwritten.
The TBAR schema deliberately excludes fields that would capture it. There is no price field. No market-maker reference. No tokenisation URI. No regulatory classification. The registry is infrastructure, not commentary. Market participants query TBAR fields and construct their own instruments. The registry records. It does not opine.
The BCCS Global Registry implements a strict finite state machine. Transitions are atomic — either all conditions are met and the state advances, or nothing changes. Partial transitions do not exist. Forward motion is irreversible; the only path backward runs through State R.
Territorial footprint declared. BAIN ID assigned. GeoJSON polygon submitted and validated for geometric correctness. No measurement claims yet, no verification, no legal vehicle. An observed TBAR is a reserved address — a slot in the registry awaiting content.
All declared asset layers measured using protocol-compliant instrumentation. Measurement dataset cryptographically hashed and submitted to registry. Hash anchored in state_history. Raw data remains with the measurement operator; only the hash and methodology reference are registry-public.
Three or more accredited verifiers independently review the measurement dataset using published BCCS methodologies. Their convergence scores must fall within protocol tolerance. Convergence, not consensus — honest verifiers cannot collude on their errors. The verification_records array is populated.
Legal vehicle operational under its jurisdiction’s law. Exclusions declared. All TBAR fields populated and frozen against further edits (new values enter as new state_history entries). The registry record is structurally complete.
Continuous monitoring layer reports no degradation. All preceding states hold uncontested. capital_eligibility flag set to true. Institutional capital can now interact with the TBAR — through investment vehicles, insurance contracts, or sovereign balance-sheet integration — with clearing status as a settled fact.
Triggered by measurement failure, verifier disagreement surfaced post-registration, legal vehicle collapse, or physical degradation detected by continuous monitoring. Reversal is transparent and permanent in state_history. A reversed TBAR can re-enter the sequence only by restarting from State 1 — same BAIN ID, fresh progression.
The ratchet is not a design preference. It is the architectural enforcement of institutional trust. Forward-only motion with transparent reversal is the minimum condition under which sovereign-grade capital can rely on the record.
The bridge from on-chain verification (Base L2) to clearing registry (tri-jurisdiction) is a deterministic pipeline. No human judgement at transition points. The pipeline consumes oracle attestations and produces state transitions.
Node operator on BCCS submits Proof-of-Physical-State attestation for a specific BAIN ID with measurement evidence hash.
Registry waits for three-tier convergence from satellite, IoT, and inspection oracles. If achieved within protocol tolerance, proceeds.
Registry executes atomic state advance on the TBAR. New state_history entry with timestamp, oracle references, and Merkle-tree root.
Transition replicated synchronously to UAE and Singapore mirrors. Cross-jurisdiction finality achieved within seconds. Merkle root available for audit.
The registry operates from three independent jurisdictions with synchronous replication. No single government can compel unilateral data modification. Each jurisdiction is accessible to BRICS+ and Western institutional capital alike. Neutrality is not a policy — it is a physical property of the architecture.
Each node is functionally identical. A query to hk.registry.bioclearing.global returns the same TBAR state as sg.registry.bioclearing.global. Institutional clients route to whichever jurisdiction aligns with their compliance posture. The data is the same everywhere; the legal wrapper around querying it varies by preference.
The BCCS Global Registry is not an extraterritorial database. Every sovereign operates its own node within its own jurisdiction, registering only its own TBARs. The protocol connects nodes — it does not centralise data. This is the same architecture as the Internet: every autonomous system operates its own infrastructure, and the protocol is what makes interoperation possible.
The state (via its environment ministry, sovereign wealth fund, or designated statutory body) signs the Sovereign Operator Agreement with KRYONIS Registry Services. The SOA defines: node operating responsibilities, data-residency commitments, dispute resolution mechanism, and protocol compliance obligations.
The sovereign deploys the six-layer measurement stack on its own territory under its own jurisdiction. Satellite subscriptions, LiDAR flight schedules, IoT sensor networks, AI analytics compute, ground-truth verifier accreditation, continuous monitoring infrastructure. The sensors belong to the state. The standards belong to the protocol.
The sovereign selects a pilot territory. GeoJSON polygon submitted to the registry. BAIN ID assigned (e.g. RU-KAR-PEG-001-7). Clearing state initialised at 1 (Observed). First pilot typically: one territory, one bio-stock, twelve months from Observed to Final.
With one or more TBARs at State 5, the sovereign can expose clearing states to institutional capital. Investment vehicles, insurance contracts, balance-sheet integration, sovereign-to-sovereign clearing flows. The registry does not execute these — it provides the queryable record that makes them possible.
state_historyFirst TBAR becomes second, then tenth, then hundredth. The sovereign node stabilises into normal operation. At network scale, territorial bio-capital becomes a queryable asset class — not because any single state drove the adoption, but because each operated its own node under the same standard.
What the protocol requires of the sovereign: operate the node honestly, follow the measurement standards, accept the ratchet, tolerate reversal when integrity fails. What the protocol does not require: surrender data to any foreign entity, adopt any currency regime, integrate with any specific trading venue, or accept any geopolitical alignment. The registry is genuinely neutral — it records what is, not what anyone wishes to be true.
175 sovereign territories addressable. Every latitude, every jurisdiction, every biome. Explore the global registry, view the BAIN ID for your territory, and initiate sovereign deployment inquiry.