Blackmore Technology Group Limited corporate logo in metallic gold and electric blue
Blackmore Technology Group Limited · Canada

ENTITY

Verifiable DataChips, trusted authority and interoperable capability building.

ENTITY connects persistent identity, delegated authority, machine-readable rights, governed information, evidence, venues, rights instruments, positions, market execution, clearing, entitlements, usage, economic participation, settlement evidence and recovery without turning any application, cloud, exchange or AI model into the source of authority.

v3.4.3current ENTITY runtime
97.14% lowerLevel-3 vs 768-d float32 vector baseline
100% exactqualified destruction/cold recovery
2 acceptedVector + Memnox external lineage
Release and implementation status (12 October 2026): The protected ENTITY v3.4.3 tag is distinct from later BTDU formula storage and wallet work on main. Native mobile authority SDKs and independent security qualification remain open. View what is built, measured and still pending →
New engineering architecture | October 2026

Verifiable DataChips, typed Composer and native application hosts

ENTITY is evolving from a data-rights wallet into a capability-first DataChip platform. Formula-native EDCF v0.2 chips preserve exact portable content and can be assembled through typed interfaces, while the EDP and signed native hosts enforce independent compatibility and permissions. The Composer and wallet integration remain engineering candidates, not a qualified production release.

Explore DataChip architectureRead the actual qualification gates
What ENTITY actually implements

A governed authority and economic fabric.

The codebase contains the authority and information layers required to know who may do what, plus an implemented market engine and economic-participation system for what happens when those rights become usable, exchangeable, measurable or settleable.

Universal transaction fabric

Persistent objects, delegated authority, rights, events, causal provenance, value records, attestations, trust policies and resolution share one primitive model.

Transaction fabric →

Rights-based market engine

Venues, instruments, balances, listings, disclosures, order books, call auctions, RFQs/quotes, trades, clearing, entitlements, usage, surveillance, cancellations, revenue rules and payment attestations are first-class market state.

Market fabric →

Recoverable economic state

Exchange state and originator/treasury participation can be exported and restored as provider-independent logical state with semantic hashes and identity evidence.

Market recovery →
BTDU proof results

Storage efficiency and destruction recovery were tested as engineering properties.

97.14% lower in the reproduced Level-3 benchmark

The fresh 2026-10-01 qualification generated 250 million bonds for 50 million entities: 4.4 GB of compact bond-plus-index state versus a 153.6 GB 768-dimension float32 vector baseline, a 97.1354167% reduction. All 1,000 sampled lookups were correct and the regenerated bond/index hashes matched the historical qualification artifacts.

100% exact qualified recovery

The fresh 2026-10-01 Memnox cold-recovery rerun rebuilt the archive, manifest and acceptance receipt from sealed ADAM/BTDU state, then verified all 865/865 Git blobs with zero missing, extra or mismatched paths. Git, GitHub, network and the source clone were not used.

Why it matters: BTDU is not only a provenance index. It is designed as a compact governed information universe whose exact state and lineage can survive loss of the original working environment when the qualified recovery conditions are met.
Recorded testsFull Capability MapArchitecture & Evidence Boundaries
Economic lifecycle

From governed information to economic consequence.

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

Rights, not artificial byte scarcity

Economic scarcity can exist in access, entitlement, capacity, duration, jurisdiction, quantity, derivation, participation and transferability while the underlying information remains non-rival.

Participation without a token

Treasury reserves, primary participation, secondary terms, derivative participation and service revenue use explicitly established terms. ENTITY imposes no automatic protocol tax.

Economic wallet →

Settlement remains evidence-bound

A trade is not automatically external payment. Authorized settlement verifiers and payment attestations preserve that boundary instead of converting execution into fictional cash settlement.

Information, state and intelligence

ENTITY, BTDU, ADAM and NIKI have separate jobs.

ENTITY

Authority and economics. Identity, authority, rights, evidence, value, market and recovery relationships.

BTDU

Governed information universe. Exact objects, atoms, bonds, compounds, lineage, indexes, repository manifests and economic topology under ENTITY authorization.

ADAM

Deterministic state engine. Applies and replays governed atomic transitions without independently inventing rights or authority.

NIKI

Bounded causal intelligence. Reasons over approved models and governed evidence without minting ownership, permission or settlement.

Real external economic lineage

Accepted external lineage and active contribution work remain separate states.

Vector and Memnox are accepted external events recorded through ENTITY. AWS #934 / PR #935 is an active upstream contribution and remains below acceptance until maintainer-controlled gates complete.

Vector #26501 / PR #26504

Upstream merged and recorded as UPSTREAM_ACCEPTED_RECORDED. The contribution is pro bono with USD 0 realized cash and no payment settlement claimed.

Memnox #46 / PR #86

Maintainer-reviewed, CI/security-green, upstream merged and recorded as UPSTREAM_ACCEPTED_RECORDED. It is also pro bono with USD 0 realized cash.

AWS #934 / PR #935

Active upstream PR. The reviewer-requested ARN-scoped synthetic-root correction and collision regression are on the current head. Maintainer-controlled Build and OTel Conformance workflows remain action_required; ENTITY does not represent this case as upstream accepted or settled.

Capability vs evidence: ENTITY implements the complete market/economic fabric. Vector and Memnox prove accepted external contribution lineage and current economic state. AWS remains an active contribution until independent upstream acceptance evidence exists; none of these cases is represented as a paid settlement.
Understand the lineage modelOpen live ledgerAWS PR #935
Beyond one provider

Sovereignty protects the fabric; it is not the fabric.

Provider-independent identity, recovery and verification keep economic meaning from collapsing when infrastructure changes. That same architecture extends to encrypted vaults, purpose-bound access, retention/destruction controls, federated/offline nodes, causal partition recovery, crypto migration, rights/global passports, custody connectors and standards adapters.

Full architectureCanonical system mapSecurity boundaries
Public engineering activity

Blackmore Technology GitHub Footprint NEWS.

A source-linked engineering ledger for public repositories, forks, releases, ENTITY fixes, external pull requests and published ENTITY contribution evidence. It is generated from GitHub/evidence state rather than written as promotional news.

Releases and repository activity

Follow releases, public commits, repository creation events and the complete public owned/fork inventory.

Open NEWS →

External fixes

Track BTG-authored upstream pull requests independently from whether they have been accepted, merged or recorded by ENTITY.

External engineering →

ENTITY evidence state

See which external contribution records are actually present in the public ENTITY evidence ledger without inferring payment or independent validation.

Raw activity ledger →
Independent Node Program

Put ENTITY on another device and test the lineage.

Download the public test-node harness, run it on independently operated devices, and test A→B communication, multi-hop origin preservation, tamper rejection, restart persistence, offline handoff and cross-platform behavior.

DOWNLOAD ENTITY INDEPENDENT NODE ZIPInstall & test instructionsJoin the community test

Direct download: the ZIP above is the merged Independent Node Program on ENTITY main. It contains the node harness, Windows bootstrap, examples and test campaign materials.

Developer surface

Build against the economy itself.

Exchange API

Create/submit instruments, publish listings, submit signed orders, open RFQs, execute call auctions, settle trades and query positions/market data.

Exchange API →

Developer manual

Architecture, identity, rights/passports, evidence, continuous ingestion, schemas, SDKs, conformance, recovery and implementation packages.

Developer docs →

Source

Inspect the exchange protocol, economic participation, market recovery, causal economy, BTDU and adoption layers directly.

ENTITY repository →
Claim boundary: ENTITY does not equate signatures with objective truth, provenance with ownership, upstream acceptance with payment, modeled value with accounting fair value, or BTG-controlled tests with independent validation. The purpose is to keep each state explicit enough to verify.
Universal product design

Blackmore Aurora. A single recognizable engineering language.

ENTITY, Wallet, the DataChip Composer and Blackmore Nexus share the same precision controls, visual evidence, accessible interaction patterns and trusted boundaries—across desktop, applications and this public site.

Explore the Aurora design systemExplore DataChips