3e36b1d6-21ee-4a99-95cb-cdaef7922487
ANALYSIS_RECORDED · recorded 2026-09-11T22:53:16.656887669+00:00
Transaction
Payload
Decoded from the canonical CBOR payload — the exact bytes the chain commits to.
Source references
- doi:10.1126/science.aad2545
- ENA:ERP012908
Merkle inclusion proof
Recombining the leaf with each sibling hash in order should reproduce this root independently — this is the raw proof, not just a pass/fail check.
What this actually establishes
- IntegrityVerified
- Inclusion proof (Merkle)Verified
- Signing key statusActive
Trust not established in this browser context
Nothing above checks the signature against an independent authority, or links this record to a trusted checkpoint. That requires offline verification via biochain-cli with a separately, independently provisioned trust-anchor profile — a real, separate capability this browser session cannot perform on its own.
- Payload hash
- 0x46f4…fae9
- Signing key
- authority-1
- Signature
- 0xfcc4…840b
Verification
online checks passed- Transaction structure validpassed
- Payload hash matches recorded hashpassed
- Merkle proof matches block headerpassed
Signing key
ActiveThis key is currently registered and active.
- Actor
- authority-1
- Organisation
- adna
Reflects this key’s status as currently recorded on this chain — a self-referential check, not independent trust-anchor verification. Offline, trust-anchor-rooted verification is a separate CLI capability with its own explicitly supplied trust profile.