Bitroots Certificate Schema

Schema version 1.0. Issued by Bitroots Technology Ltd.

MenuIntroduction How to verify a certificate Document variants Header Certified output Origin Energy Compliance, at issuance Certificate disclosure Verification Scope statement The verification record Reissued certificates Worked example Schema versioning

This page defines every field that appears on a Bitroots Certificate of Provenance and on its verification record. A certificate attests the provenance, origin attributes, energy attribution where applicable, and compliance screening results of a single Bitcoin output, as at the issue date. Certificates are documents issued and hosted by Bitroots. Nothing is written to the Bitcoin blockchain; chain facts stated on a certificate are independently verifiable against public blockchain data.

How to verify a certificate

Every certificate carries a Certificate ID and an issuer seal. To verify, enter the Certificate ID at bitroots.io/certificates. The register returns the canonical record, its current status, and its seal. Confirm that the seal printed on your document matches the seal on the record, and that the field values match. A document whose seal or fields disagree with the register has been altered and should not be relied upon.

The verification record may show fields that are not printed on the document. The printed certificate is a summary rendering; the sealed record is the complete attestation.

Document variants

Certificates are issued in a public or private variant, stated on the face as Certificate disclosure.

Public. The certificate may be verified by Certificate ID or by outpoint. The holder has elected public verifiability.

Private. The certificate may be verified by Certificate ID only. The Certificate ID functions as a credential: it is disclosed by the holder to parties entitled to verify. Lookup by outpoint is not available for private certificates, and the register does not confirm or deny certification status for arbitrary outputs.

A certificate naming its operator does so at the operator's election. Where no operator is named, the line is absent. Absence of any optional line is by design and carries no adverse meaning.

Field reference

Header

Certificate ID: Unique identifier and verification credential. Format: BR.CERT, the issuance year, then sixteen characters of Crockford base32 in four groups. Example: BR.CERT.2026.7Q4M.X2KD.9RTF.W3NH. The character set excludes I, L, O, and U to prevent misreading. IDs are randomly generated and carry no sequence or meaning.
Issued: Date and time of issuance, UTC.
Asset: The asset class of the certified output. Permitted value in schema 1.0: BTC. The field is reserved for future asset classes under later schema versions.
Tier: The certification tier. Permitted values:
Provenance. Origin, chain of custody, and compliance screening.
Provenance + Energy. Provenance plus attested energy attributes of the mining facility. The Energy section appears only on this tier.
Status: The certificate's state in the register. The printed value is the status at document generation; the verification record shows the live status, which is authoritative. Permitted values:
Active. In force.
Superseded. The certified output has been spent in a settlement registered with Bitroots, and successor certificates have been issued for the resulting outputs. The historical attestation remains true.
Revoked. Withdrawn by the issuer. A revoked certificate should not be relied upon.
Suspended. A post issuance event concerning a certified party or attribute is under review. The historical attestation as at the issue date stands; verify before relying.

Certified output

Outpoint: The certified unspent transaction output, as transaction ID and output index, printed in full. One certificate attests exactly one output.
Amount: The output value in BTC, to eight decimal places.
Block height: The height of the block containing the output.
Script type: The output's script form. Permitted values: P2PKH, P2SH, P2WPKH, P2WSH, P2TR.

Origin

Operator: The mining operator's name, where the operator has elected to be named. Optional; absent on unnamed certificates.
Jurisdiction of mining: The country in which the certified facility operates, stated at country level. Values follow ISO 3166. Bitroots does not issue certificates for facilities in comprehensively sanctioned jurisdictions.
Facility: Bitroots facility reference, format BR.FAC followed by a random identifier. Facility identity and location beyond country level are held in the Bitroots register and are not stated on the certificate.
Facility audit: Month and year of the most recent Bitroots facility audit current at issuance. The audit verifies the facility's existence, identity, operations, and, for Energy tier certificates, its energy sourcing.
Source: How the certified output relates to mining origin. Permitted values:
Direct coinbase payout. The output is a block reward output paid directly to the certified operator's address through the operator's pool arrangement.
Solo mined coinbase. The output is a block reward output mined by the operator without a pool.
Certified descent. The output was created by a settlement transaction spending only certified outputs, registered with Bitroots. See Reissued certificates below.
Hops from coinbase: The number of transaction steps between the certified output and block reward issuance. 0 means the output is itself a block reward output and has never moved. For certified descent, the value is the maximum over all lineage paths, the conservative measure where a settlement combined inputs of different depths.

Energy

Present on Provenance + Energy tier certificates only.

Energy source: The facility's attested energy source. Permitted values: Hydroelectric, Wind, Solar, Geothermal, Nuclear, Stranded natural gas flare mitigation, Grid mix, Other attested. Grid mix is accompanied by a source breakdown on the verification record.
Attributed share: The share of facility consumption attributed to the stated source, 0 to 100 percent, as verified at facility audit.
Supply basis: The basis on which the source claim rests, stated in descending order of directness. Permitted values:
On site generation. The facility generates the stated energy on site.
Direct utility supply. The facility draws the stated energy under its physical supply arrangement.
PPA backed. The claim rests on a power purchase agreement.
Certificate backed. The claim rests on retired energy attribute certificates.

Energy sourcing is verified against metered consumption and utility supply records at facility audit. Supporting evidence is held in the Bitroots register.

Compliance, at issuance

All results are produced at issuance and are fixed as at the issue date. They are statements of what was screened and found on that date; they are not predictions and do not update. The live status of the certificate reflects any post issuance events.

Jurisdiction screening: The jurisdiction of mining screened against comprehensive sanctions programs and FATF listings. Value on an issued certificate: Clear.
Sanctions screening: The operator, its directors, and its beneficial owners screened against the designation lists stated in Lists applied. Value on an issued certificate: Clear. Bitroots does not issue certificates where screening is not clear.
Prior transaction history: Permitted values:
None. The output is a block reward output with no transaction history.
Certified lineage only. Every transaction between this output and block reward issuance was a settlement registered with Bitroots spending only certified outputs.
Mixer exposure: Exposure to mixing or obfuscation services. Value on an issued certificate: None, which is structural: an output with no history, or a fully certified lineage, has no exposure by construction.
Lists applied: The screening sources: OFAC SDN, UK OFSI, EU, UN, FATF, at the versions current at the time of issuance. Exact list version identifiers are recorded in the register and shown on the verification record.

Certificate disclosure

The document's verification mode: Public or Private, as defined under Document variants above. The verification record shows the current setting, which the holder may change.

Verification

Issuer seal: A SHA256 hash of the certificate's canonical field data, computed at issuance and registered by Bitroots. Any alteration to the certified fields produces a different hash, so a document whose printed seal matches the registered seal is byte for byte the record Bitroots issued. The seal is computed over the data, not over the document file, so the hosted record and the PDF rendering carry the same seal.
Certificate schema: This page. The schema version stated on the record governs the certificate's field definitions.

Scope statement

Every certificate carries the following scope. The certificate attests the provenance, origin attributes, energy attribution where applicable, and compliance screening results of the output listed, as at the issue date. It does not attest current control, title, value, or the legality of any transaction. Current control of an output is demonstrable by the holder by signed message and is not asserted by the document.

The verification record

Verifying a Certificate ID at bitroots.io/certificates returns the canonical record. In addition to every printed field, the record shows:

Live status and, where relevant, the succeeding Certificate IDs of a superseded certificate.
Block hash of the containing block, pinning the attestation to a specific chain history.
Confirmations at issuance. Coinbase outputs are certified at or after maturity, 100 confirmations.
Lineage, for certified descent: parent Certificate IDs and the settlement transaction ID through which provenance descended.
Applied list versions, the exact identifiers and dates of the screening lists used at issuance.
Evidence and method references, identifying the audit evidence and screening procedure held in the register.

Reissued certificates

Certification follows the coins. When certified outputs are spent in a settlement registered with Bitroots, the spent outputs' certificates become Superseded and fresh certificates are issued for the resulting outputs, with Source: Certified descent, an incremented hops value, and lineage recorded on the verification record. A settlement is registrable only if every input is a certified output; certified and uncertified value are never combined. Origin attributes, including a named operator where naming persists, carry through the lineage. Prior holders are never identified on any certificate.

Worked example

A public, Energy tier, genesis issuance certificate:

Certificate ID:   BR.CERT.2026.7Q4M.X2KD.9RTF.W3NH
Issued:           16 Jul 2026, 11:04 UTC
Asset:            BTC
Tier:             Provenance + Energy
Status:           Active

CERTIFIED OUTPUT
Outpoint:         c47e02ab6d91f38d4a507e2b9c13ff08d21e6a4b70c5839fd1642eb08a97d35c:0
Amount:           3.14066105 BTC
Block height:     907,731
Script type:      P2WPKH

ORIGIN
Operator:         GreenHash Mining USA
Jurisdiction of mining: US
Facility:         BR.FAC.9K3W
Facility audit:   Jun 2026
Source:           Direct coinbase payout
Hops from coinbase: 0

ENERGY
Energy source:    Hydroelectric
Attributed share: 100%
Supply basis:     Direct utility supply

COMPLIANCE, AT ISSUANCE
Jurisdiction screening:     Clear
Sanctions screening:        Clear
Prior transaction history:  None
Mixer exposure:              None
Lists applied: OFAC SDN, UK OFSI, EU, UN, FATF, versions at time of issuance.
Results are fixed as at the issue date.

CERTIFICATE DISCLOSURE: PUBLIC

VERIFICATION
Issuer seal, sha256:
f30a61dc275b98e4c01d8f2a5be7409c33d16a80f4b2c7591ee08d4a6c1b7b26

The same certificate as structured data, as returned by the verification record:

{
  "certificate_id": "BR.CERT.2026.7Q4M.X2KD.9RTF.W3NH",
  "schema_version": "1.0",
  "issuer": "Bitroots Technology Ltd",
  "issued_at": "2026-07-16T11:04:00Z",
  "asset": "BTC",
  "tier": "provenance_energy",
  "status": "active",
  "output": {
    "outpoint": "c47e02ab6d91f38d4a507e2b9c13ff08d21e6a4b70c5839fd1642eb08a97d35c:0",
    "amount_sats": 314066105,
    "block_height": 907731,
    "block_hash": "000000000000000000018a3c47b0f2ce91d4a4e88f03b651de24c7a109b58d3a",
    "script_type": "P2WPKH",
    "confirmations_at_issuance": 112
  },
  "origin": {
    "operator": "GreenHash Mining USA",
    "jurisdiction_of_mining": "US",
    "facility_ref": "BR.FAC.9K3W",
    "facility_audit": "2026-06",
    "source": "direct_coinbase_payout",
    "hops_from_coinbase": 0
  },
  "energy": {
    "energy_source": "hydroelectric",
    "attributed_share": 100,
    "supply_basis": "direct_utility_supply"
  },
  "compliance": {
    "jurisdiction_screening": "clear",
    "sanctions_screening": "clear",
    "prior_transaction_history": "none",
    "mixer_exposure": "none",
    "lists_applied": ["OFAC_SDN", "UK_OFSI", "EU", "UN", "FATF"]
  },
  "disclosure": "public",
  "seal": {
    "algorithm": "sha256",
    "value": "f30a61dc275b98e4c01d8f2a5be7409c33d16a80f4b2c7591ee08d4a6c1b7b26"
  },
  "scope_version": "1.0"
}

A private variant of the same instrument omits the operator line entirely and states Certificate disclosure: Private. A reissued certificate shows Source: Certified descent, a hops value of 1 or greater, Prior transaction history: Certified lineage only, and lineage on the verification record.

Schema versioning

Field definitions and permitted values are fixed per schema version. New values or fields are introduced only under a new schema version; a certificate is always interpreted under the version stated on its record. This page documents schema version 1.0.

Bitroots Technology Ltd, D S Burge And Co Ltd, The Courtyard, 7 Francis Grove, London, SW19 4DW, United Kingdom.