Open infrastructure for sovereign digital authority, verifiable provenance, data rights and interoperable economic state.
Our primary open-source project is ENTITY — an Apache-2.0 protocol and reference implementation for persistent identity, delegated authority, evidence, rights, portable recovery and data-economic infrastructure.
Build it. Verify it. Break it. Implement it independently.
ENTITY v3.4.3 · 5-minute developer paths · Good first issues · Discussions · Documentation · Protocol 1.0 Conformance Kit
You do not need to understand the entire ENTITY architecture before contributing.
Choose one path:
- Create and verify an ENTITY provenance receipt.
- Build a tiny TypeScript or Python verifier.
- Turn a JSON event into an ENTITY evidence object.
- Add a GitHub Action that verifies an ENTITY receipt.
- Visualize a small lineage chain.
Start here: open buildable good-first issues
ENTITY is being exercised against real open-source engineering work. BTG contributions have already been merged upstream in projects including:
- Memnox PR #86 — policy/time-window validation hardening.
- Vector PR #26504 — ambiguous test-output failures converted from a panic into a normal configuration error.
The purpose is not to claim ownership of third-party code. The purpose is to make authorship, evidence, lineage, rights boundaries and later economic state reproducible.
- 15-minute first-run audit
- External Verification Challenge
- External Repository Qualification campaign
- Interoperability Challenge
A reproducible failure, ambiguity, counterexample or portability problem is useful evidence.
IDENTITY → AUTHORITY → RIGHT → EVENT → EVIDENCE → VALUE
ENTITY keeps several relationships separate that are often collapsed together:
- identity vs account;
- provenance vs truth;
- custody vs ownership;
- a valid signature vs an externally true claim;
- protocol origin vs ownership of downstream assets;
- usage vs realized economic value.
The current supported runtime is ENTITY v3.4.3. The Blackmore Technology Data Universe (BTDU) component remains version 3.4.2 unchanged inside that release.
BTG publishes controlled reproducibility baselines in:
Rust · TypeScript · C# / .NET · Go · Swift · Java
These are BTG-controlled reproducibility baselines, not independent third-party implementations. The stronger interoperability milestone is an implementation independently authored and controlled by an unrelated engineer or organization from the public protocol and sealed conformance material.
Use GitHub Discussions for design questions, implementation ideas, evaluation results and show-and-tell work. Use Issues for reproducible defects and bounded tasks. Use Pull Requests for reviewable changes.
Blackmore Technology Group Limited
Primary project: ENTITY
Current runtime: ENTITY v3.4.3
License: Apache License 2.0