Open infrastructure for sovereign digital authority, verifiable claims, data rights, continuous provenance and economic state that survives providers.
Run it. Verify it. Break it. Implement it independently.
ENTITY is Blackmore Technology Group's open-source protocol and reference implementation for persistent identity, delegated authority, provenance, evidence, rights, trusted state transitions, portable recovery and data-economic infrastructure.
15-minute first-run audit · ENTITY v3.4.3 Release · External Qualification · ERQ Campaign · Documentation · Conformance Kit · Interoperability Challenge
ENTITY v3.4.3 is the current supported ENTITY runtime. It is a bounded remediation release based on the immutable v3.4.2 release. The BTDU component remains version 3.4.2 unchanged. v3.4.2 remains immutable historical evidence and is superseded for current deployment.
v3.4.3 remediates two reproduced Issue #28 defects:
- derivative-revenue evidence substitution could create a second economic event and obligation for the same occurrence;
- a zero-edge causal graph could return a positive self-trace for missing or empty endpoints and label an empty path evidence-bound.
The remediation keeps authoritative occurrence identity separate from evidence identity, rejects exact replay, records additional evidence without creating a duplicate obligation, and validates causal-trace endpoints before traversal.
| Evidence | Result |
|---|---|
| Issue #28 remediation module | 76/76 PASS |
| Full repository source suite | 279/279 PASS |
| Full source-suite exit code | 0 |
| Compiled Rust qualification | PASS — inherited unchanged scope |
| Real-world BTDU training qualification | PASS — inherited unchanged scope |
Release merge commit: 528b70aabd05b1e930b77e4933f157731e47274f
Immutable predecessor commit: 6dfa3d6cc738d9369cf092d2782676bf4f2a46e4
The v3.4.3 release does not rewrite the active 30-day wall-clock evidence campaign or immutable v3.4.2 evidence.
Canonical ENTITY origin remains:
Shawn Blackmore → Blackmore Technology Group → ENTITY
Protocol origin is separate from downstream asset ownership, custody and economic entitlement.
UPSTREAM OWNERSHIP
≠
BTG FORK CUSTODY
≠
BTG ENTITY METADATA OWNERSHIP
≠
ENTITY PROTOCOL ORIGIN
≠
AUTOMATIC ECONOMIC RIGHTS
ENTITY may record provenance, authorship, copyright, licence, custody, rights metadata and governed relationships. Registration, mirroring, ingestion, verification or custody do not themselves transfer upstream ownership or create automatic economic entitlement.
BTDU remains component version 3.4.2 in ENTITY v3.4.3. It provides an atomic/bonded information architecture in which reusable atoms, bonds and compounds can be connected to ENTITY provenance, authority, rights and economic state.
Atoms → Bonds → Compounds → Governed Objects → Provenance / Rights / Economic Lineage
BTDU is not presented as generic raw-file compression. It is a representation model for structured, semantic and relational information with explicit provenance and rights boundaries.
Historical v3.4.2 + BTDU documentation remains available at the v3.4.2 documentation archive.
ENTITY models explicit rights around data rather than requiring artificial scarcity in the bytes themselves.
DCO
↓
Instrument
↓
Listing
↓
Disclosure
↓
Order / RFQ / Auction
↓
Price Discovery
↓
Trade
↓
Clearing
↓
Settlement
↓
Entitlement
↓
Usage
↓
Derived Output
↓
Economic Consequence
Originator participation may be expressed through explicit terms such as issuance participation, retained rights, secondary participation or derivative participation. ENTITY does not require a cryptocurrency, gas token or automatic BTG tax.
Python 3.11+ is recommended for the reference implementation.
git clone https://github.com/blackmore-technology-group/ENTITY.git
cd ENTITY
git checkout v3.4.3
python -m pip install -r requirements.txt
python -m compileall -q src sdk protocol
python -m unittest discover -s tests -vThen choose a narrow path:
- 15-minute first-run audit — stop at the first broken, stale, ambiguous or platform-specific step and report exactly what happened.
- External Verification Challenge
- External Repository Qualification campaign
- Reproduce the published Rust baseline
- Attempt an independent implementation
- Read the Protocol 1.0 Conformance Kit
A reproducible failure, ambiguity, counterexample or portability problem is useful evidence.
BTG publishes controlled reproducibility baselines in:
Some of these repositories deliberately reproduce sealed v3.4.2 campaigns. Those version labels are historical test-target identifiers and should not be read as statements that v3.4.2 remains the current runtime.
These repositories are BTG-controlled reproducibility baselines, not independent third-party implementations. External reproduction of a baseline is meaningful portability/reproducibility evidence, but the stronger milestone remains an implementation independently authored and controlled by an unrelated engineer or organization from the public protocol/specification material.
ENTITY separates BTG-controlled qualification from evidence that should come from unrelated participants.
Current entry points:
- #80 — 15-minute first-run audit
- #55 — External Verification Challenge
- #78 — External Repository Qualification campaign
Historical issues #58–#62 were created against the frozen v3.4.2 target. Their evidence scope remains v3.4.2 unless an issue explicitly states that it has been retargeted to v3.4.3. Historical hashes, tags and receipts are not rewritten simply because the supported runtime advanced.
The active 30-day wall-clock qualification remains time-dependent and was not reset or modified by v3.4.3.
The same ENTITY sovereignty model is packaged for:
The packages configure one ENTITY sovereignty model; they do not create separate sovereignty systems or redefine external standards.
- Identity is not an account.
- Registration is not ownership.
- Provenance is not truth.
- A valid signature is not proof that an external-world assertion is correct.
- Possession, hosting, routing, custody and storage do not create sovereign authority.
- Applications and agents act only through explicit, scoped, revocable authority.
- Data bytes do not require artificial scarcity; scarcity can exist in rights, entitlements, capacity, duration, jurisdiction, usage quantity, derivation and participation.
- Usage does not become realized economic value without the required evidence.
- Historical signed semantics are superseded, not silently rewritten.
- An ENTITY identity is intended to survive replacement of a device, host, provider or BTG infrastructure subject to the applicable recovery/qualification evidence.
Never commit operational sovereignty state to this repository.
Do not commit private signing/recovery keys, live credentials, principal/device/application binding instances, .entitybackup files, runtime databases, production state directories or unredacted user/business data.
See SECURITY.md.
- ENTITY v3.4.3 release
- 15-minute first-run audit
- Documentation portal
- Historical v3.4.2 + BTDU documentation
- External Verification Challenge
- ERQ campaign
- Engineering evidence
- Interoperability challenge
- Governance
- Contributing
- Security
- Citation metadata
- CodeMeta
- All releases
ENTITY is published under the Apache License 2.0.