45ae3c39-b80a-47ba-9502-285cbb6a8603

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

Transaction

TypeANALYSIS_RECORDED

Subjectgenetic_analysis · cay011.SG

Actoradna-ingest-pipeline

Institution—

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

Effective at—

Domain moduleancient-dna

Schema version1

Input entitiescay011.SG

Output entitiesnone

Revision ofno earlier revision on record

Payload

assessment{"Known":"Pass"}

coverage_autosomal_targets{"Known":"0.04683832"}

family_relations{"Known":"1.0d:cay011:cay022"}

molecular_sex{"Known":"M"}

mtdna_haplogroup{"Known":"n/a (<2x)"}

y_haplogroup{"Known":"G"}

y_haplogroup_isogg{"Known":"G"}

y_haplogroup_manual{"Known":"G"}

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)0x231f…0ae6

↓

merkle root0x231f…0ae6

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: 0x4c30…e4e5
Signing key: authority-1
Signature: 0xdedf…e90a

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 hash0x4c30e14a3744ee0d5d4b6713a188b6f1ab83919622d4fd756b1f5137b14de4e5

Signature0xdedf5dba591d4f139da819e1d2266367d7562f38651625185277e5d8bc9896d451c0e91d99e458684e7063d6e9725503c95b6df6d322dd360a5473420c1ee90a