What is trusted
The current checked witness ties the database proof anchor at height
948454 to the BHTM proof for chunk
mainnet-900000-954920. The same height, block hash, and
Core-display MuHash appear on both sides of the bridge.
Concrete witness
Database anchor
height948454
block hash 00000000000000000001ef683c02c383315db7e917c69d20f79e05985560a4e4
MuHash cf4fc1f1dd400622a5b6f39eca7f764a30570c30cc668e04f00e8a3356c2a2ee
Database super-roots
bucket e2ba2eee6788424309a95f771893d5401cc8e3ceec6188dc2708900e211a910a
onion f86baa3966a61cdcd70d8c0ad9bed233f591806eb351db2ae35ac0192a3fe997
BHTM leaf proof
chunkmainnet-900000-954920
leaf index48454
tree size54921
BHTM tree root babeea635812c3b1a2d5f352ab0a5d1ee8a4e9c668c43c05d6603ef3c3766ba6
leaf hash 0171a475dc43b97db594c7512039d12f5213d270b42e56babfa44d65359eeaaf
proof steps16
What a verifier checks
- Database answer Merkle path to the database super-root.
- Database proof super-root to the snapshot height, block hash, and MuHash.
- BHTM leaf proof from that same tuple to the BHTM tree root.
- BHTM attestation from tree root to SEV-SNP
REPORT_DATA. - AMD signature/VCEK chain and expected UKI measurement.
What it does not prove
The BHTM proof does not independently prove proof-of-work difficulty, script or witness validity, coinbase maturity, subsidy rules, absence of double spends, UTXO membership from first principles, duplicate-txid behavior, genesis handling, or unspendable-output filtering. Those rules remain the responsibility of the Bitcoin Core-side data source and extractor.