ENTITY Documentation Portal
Current implementation status: The immutable v3.4.3 tag and later BTDU/wallet developments are distinct. See built capabilities, measurement scope and outstanding qualification gates.
ENTITY v3.4.3 · developer portal

Build the digital-economic fabric

ENTITY is built around five primitives—ENTITY, AUTHORITY, RIGHT, EVENT and VALUE—and composes them into governed information, market execution, economic participation, causal lineage and provider-independent recovery.

Current runtime: ENTITY v3.4.3. The BTDU component remains 3.4.2 unchanged. Sovereignty is a system invariant; developers should treat the authority, information, exchange, economics and recovery layers as the complete platform.
DataChip platform: The post-tag EDCF v0.2 DataChip, EDP and Universal Composer architecture provides bounded formula reconstruction, signed-bundle reference tooling, typed composition and native-host integration candidates. Do not infer production authorization, runtime execution or ownership from manifest content or checksum alone.

Start with the core implementation surfaces

Five primitives

PrimitiveDeveloper question
ENTITYWhat persistent actor, asset, dataset, software, model, device or financial object exists?
AUTHORITYWho may act, sign, access, execute, purchase, license, settle, publish, resolve, delegate or control?
RIGHTWhat may the holder inspect, read, copy, derive, train, infer, execute, modify, redistribute, commercialize, control or transfer?
EVENTWhat state transition, usage, provenance, market action or evidence event occurred?
VALUEWhat potential, offered, contracted, accrued, settled or realized consequence is actually supported?

Market & economic APIs

DCO → INSTRUMENT → LISTING → DISCLOSURE → ORDER / RFQ / AUCTION → PRICE DISCOVERY → TRADE → CLEARING → SETTLEMENT → ENTITLEMENT → USAGE → DERIVED OUTPUT → ECONOMIC CONSEQUENCE

The exchange implementation supports ORDER_BOOK, CALL_AUCTION and RFQ, with instrument classes SPOT_LICENSE, SUBSCRIPTION, COMPUTE_TO_DATA, PROCUREMENT, CONTRIBUTION and SECONDARY_LICENSE.

Information, execution and reasoning

SDKs, standards and packages

Determinism, conformance and independent implementation

Real-world developer proof

Vector and Memnox are now upstream-merged, ENTITY-recorded external contribution cases. The developer lesson is not “ENTITY can hash a patch.” It is that an external problem, contributor, exact change-set, review/CI, acceptance and economic state can remain reconstructable lineage that can later participate in a rights instrument or settlement workflow if valid terms are established.

Independent verification

BTG-controlled Rust, TypeScript, C#, Go, Swift and Java baselines remain reproducibility evidence, not unrelated implementations. Independent reproduction, independent implementation, security review and institutional use remain separate evidence classes.