BTG / PUBLIC RECORDS

Public records, provenance and ledgers

Understand the difference between openly published source records, asset and instrument information, authorization history and an actual settled financial transaction ledger.

Blackmore Technology Group corporate emblem

Four distinct public records

Technology and research records contain reviewed summaries of test methods, results, limitations and source hashes. Asset records describe an identified dataset, algorithm or component and its provenance. Instrument records describe proposed rights, issuer, disclosures and legal eligibility. Transaction-ledger records would describe actual authorized issuance, clearing or settlement with appropriate privacy controls.

Publishing a page or hash on GitHub does not by itself prove an authorized instrument, legal ownership, a trade or bank settlement.

Public GitHub material and private exchange source

BTG uses a deliberate public/private separation. For example, the public ENTITY repository contains publicly visible protocol work. That is not the proprietary Bit Trade Global Exchange execution repository or a ledger of settled trades.

Public-facing issuer and instrument pages may be delivered through a standalone read-only portal or approved GitHub Pages publication. The private algorithms, signing secrets, user information, account credentials and settlement records must not be placed in the public source repository.

What is presently recorded

Records dated 20 October 2026 distinguish two proposed robotics DCO assets from four actual source-linked sector research artifacts in forestry, agriculture, hydrology and historical emergency alerts. Six staged commercial-use, IP-assignment and investment candidate profiles remain unissued. Source-linked research evidence does not establish exclusive ownership of underlying government datasets or a public security. The same records report zero legal-rights assignments complete, zero authorized issuer offerings, zero issued investment units and zero settled public trades.

BTG will not display fictional market prices, apparent live order books or simulated settlements as real market activity. Public instrument directories can remain useful before trading by showing description, development status, rights classes, provenance and missing approvals.

What a verifiable ledger needs

A future public checkpoint will require a documented signing authority, chain of previous record identifiers, verifiable inclusion proofs, issuance and revocation status, source-rights passport, issuer authorization and a publicly readable verifier. A signed ledger proves a record under its key infrastructure; it does not replace a bank receipt, statutory record or financial-market approval.

See candidate asset and instrument records and readiness register. A public repository or GitHub Pages URL should be linked only after the exact publishing destination has been verified and approved, rather than guessed.

Engage as a prospective issuer or evaluator

BTG invites appropriately authorized researchers, organizations, data-rights holders, developers and reviewers to discuss evidence-based pilots. The process starts with legitimate source authority, scoped test data, a defined outcome and an assessment of privacy and rights. It does not require opening confidential data or buying an unissued investment.

Contact Blackmore Technology Group Limited to start a professional discussion.

Verified public GitHub documentation

These destinations were checked on 21 October 2026. They provide public technical and economic-lineage information but do not certify live Bit Trade Global Exchange securities trading.

Related public documentation

Public Bit Trade Global documentation portal ↗ is the live public GitHub documentation destination. It presents research and market architecture; it must not be interpreted as proof of licensed exchange operation, live instrument issuance or completed cash settlement.