Transactions & authority
Use ENTITY, AUTHORITY, RIGHT, EVENT and VALUE to build governed actions with explicit delegation, provenance and value state.
Universal Transaction Fabric →ENTITY v3.4.3 exposes persistent identity, delegated authority, rights, evidence, a universal transaction fabric, a rights-based exchange engine, economic participation, BTDU information state and provider-independent recovery. Start with the surface closest to your problem.
Use ENTITY, AUTHORITY, RIGHT, EVENT and VALUE to build governed actions with explicit delegation, provenance and value state.
Universal Transaction Fabric →Create rights instruments, listings, orders, RFQs, auctions, trades, settlement evidence, positions and recoverable economic state.
Exchange API →Use BTDU/continuous ingestion for governed objects, exact content, source/controller/right-holder distinctions and durable causal/economic lineage.
Ingestion & BTDU →Order book, call auction and RFQ.
Spot licence, subscription, compute-to-data, procurement, contribution and secondary licence.
Treasuries, reserves, primary/secondary/derivative participation, service revenue and obligations without an automatic protocol tax.
Logical recovery of venues, balances, orders, trades, entitlements, usage, revenue rules, payment attestations and participation state.
Vector #26501 / PR #26504 and Memnox #46 / PR #86 are merged upstream and recorded by ENTITY as accepted external contribution histories. Both remain correctly marked pro bono with USD 0 realized cash. They demonstrate durable external problem → contribution → review/CI → acceptance → rights/economic-state lineage.
The six BTG-controlled language repositories exist for portability and reproducibility. External reproduction is useful evidence; an unrelated implementation remains a higher and separate bar.
Complete API, schema, architecture, conformance, SDK and release documentation.
Open docs →Market engine, participation, settlement and recovery documentation.
Open economy docs →Keys, revocation, evidence threats, backup and provider-capture boundaries.
Security docs →