ENTITY Documentation
Architecture Guide

Data rights are not the same thing as ownership of bytes

Data is non-rival: copying a dataset does not necessarily deprive the original holder of the same bytes. A data-rights architecture therefore needs to govern authority, permissions, entitlements, usage and economic terms rather than pretending every transfer behaves like a physical asset transfer.

What becomes scarce?

The scarce object is often not the byte sequence itself. It can be a permission, licence, entitlement, exclusive use right, governed access window, verified origin claim, contractual participation rule, or another explicitly defined right associated with the data.

ENTITY's economic chain

DCO → Instrument → Listing → Disclosure → Order / RFQ / Auction → Price Discovery → Trade → Clearing → Settlement → Entitlement → Usage → Derived Output → Economic Consequence

A Digital Commodity Object (DCO) can connect an object to provenance, ownership assertions, rights, restrictions, licences, contribution history, usage events and settlement evidence. The protocol does not assume that creating the DCO makes those assertions objectively true; they remain subject to evidence and governing authority.

Rights remain explicit

ENTITY separates the protocol's canonical origin from downstream user assets. Canonical ENTITY ancestry does not transfer ownership of user assets to Blackmore Technology Group, and protocol origin does not automatically create a royalty. Economic participation requires explicit terms.

Primary, secondary and derivative participation

An originator participation profile can define retained rights, issuance terms, transfer rules, secondary participation or derivative participation where the parties explicitly agree to them. This permits a data economy without requiring a native token, mining, staking or an automatic protocol tax.

Why provenance still matters after a trade

The economic event does not erase origin. A transfer can preserve issuance and transfer lineage, while downstream usage can preserve the connection from the governed source to the process and resulting derivative. That makes later settlement or dispute analysis inspectable.

What ENTITY does not decide for you

Cryptographic verification is not a legal opinion. Market evidence is not automatically accounting fair value. Provenance is not automatic title. A deployment still needs its applicable contracts, laws, institutional authority and accounting policies.

Inspect the implementation

The current release is Apache-2.0 and publishes both economic documentation and bounded verification tasks. A useful external review is to identify any path where ownership or economic entitlement is inferred merely from protocol ancestry or topology.

Review the v3.4.2 boundaries →