d842385e-6dbe-4587-94d4-1b9dcdeeca13

ANALYSIS_RECORDED · recorded 2026-09-11T22:53:16.248410549+00:00

Transaction

TypeANALYSIS_RECORDED

Subjectgenetic_analysis · cay008.SG

Actoradna-ingest-pipeline

Institution—

Recorded at2026-09-11T22:53:16.248410549+00:00

Effective at—

Domain moduleancient-dna

Schema version1

Input entitiescay008.SG

Output entitiesnone

Revision ofno earlier revision on record

Payload

assessment{"Known":"Pass"}

coverage_autosomal_targets{"Known":"0.10842236"}

family_relations{"Known":"2.5d:cay008:cay013"}

molecular_sex{"Known":"F"}

mtdna_haplogroup{"Known":"T2g"}

y_haplogroup{"Known":"n/a (female)"}

y_haplogroup_isogg{"Known":"n/a (female)"}

y_haplogroup_manual{"Known":"n/a (female)"}

Decoded from the canonical CBOR payload — the exact bytes the chain commits to.

Source references

AADR v66 (dataverse.harvard.edu/api/access/datafile/13994515)

Merkle inclusion proof

leaf (index 0)0x3878…bfed

↓

merkle root0x3878…bfed

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.

Integrity

Payload hash: 0x143c…1863
Signing key: authority-1
Signature: 0x4afb…c309

Verification

online checks passed

Transaction structure validpassed
Payload hash matches recorded hashpassed
Merkle proof matches block headerpassed

Signing key

Active

This 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.

Full digests

Payload hash0x143cab74db4f2056256f252cff034c628d62b821a2a76f5d5df9991fdf301863

Signature0x4afb463d8f419e5f64e9c4e00d35bb84c9b005f27b0aae97af3969ba775e03d2839235e6ff8dae3a389e5c55aaa091dc2b94d21361188d39acc2eb62a3d0c309