ENTITY ownership rights and provenance
ENTITY is BTG’s open-source identity, authority, rights, provenance and economic-event protocol. The recorded v3.4.3 release passed 279/279 scoped source tests while retaining the unchanged v3.4.2 BTDU component. ENTITY can describe cryptographically attributable claims and restrictions, but deployment-specific owner-signed grants and legal title must still be established separately.
Why the Exchange needs ENTITY
A stock-market-style asset listing needs more than a ticker. ENTITY provides identity, provenance, evidence of who issued a claim, rights restrictions and revocation context for the underlying data or invention. It helps distinguish ownership of an asset from a licence to use it or an investment interest. ENTITY records alone do not establish legal title, and only competent issuers under applicable law may create tradable financial rights.
How Bit Trade Global lists, values and trades eligible data assets →
Asset identity and lineage
An ENTITY record can identify a dataset, software capability, research output or derived asset as a specific subject with version and parent relationships. It is important to distinguish an asset’s technical existence from legal title. Possession of a file or registration of an identifier does not independently confer transferable ownership rights.
Rights and restrictions
A Rights Passport describes the rights available, source-of-title and relevant restrictions, including allowed use, duration, geography, recipient rules, prohibited activities, assignments and possible revenue entitlements. The actual legal force comes from competent parties and valid agreements.
A useful provenance chain explains how a derived artifact was created, what inputs were eligible and what third-party rights survive transformation.
Qualified state and signed records
Recorded changes require appropriate authentication, authorization and a meaningful sequence or state reference. Technical signatures and hashes support attribution and tamper evidence under a trustworthy key and governance framework. They are not a substitute for a bank’s payment confirmation, a corporation’s statutory issuance or a regulator’s permission.
Relation to the Exchange
The Exchange can reference an ENTITY asset and its Rights Passport when disclosing the actual contract category. A commercial U licence, A assignment and an I investment interest remain different products, each with their own governing documents. ENTITY should not convert every record into a financial security or universal market ticker.
Evidence and public controls
A public description can identify classification, provenance summaries and restrictions without exposing confidential source material or internal signing keys. The system’s production authority, legal enforceability, secure key custody and external compliance must be assessed independently for the relevant deployment.
Provenance and Rights Passports
ENTITY is intended to maintain attributable lineage, source integrity, restricted rights and entitlements; ADAM addresses permissioned state changes. A hash proves bytes under a specified digest, not ownership or commercial authorization. Actual rights must come from a legitimate source owner, valid agreements and applicable law. Public summaries may expose provenance without revealing protected source records or signing material.
Explore the dated engineering evidence, public ledger and instrument records, and professional evaluation inquiries.