56e41d86-f730-4f24-bf71-39a2a3b150ae

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

Transaction

TypeANALYSIS_RECORDED

Subjectgenetic_analysis · cay004.SG

Actoradna-ingest-pipeline

Institution—

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

Effective at—

Domain moduleancient-dna

Schema version1

Input entitiescay004.SG

Output entitiesnone

Revision ofno earlier revision on record

Payload

assessment{"Known":"Pass"}

coverage_autosomal_targets{"Known":"0.09875904"}

family_relations{"Known":"1.0d:cay004:cay027"}

molecular_sex{"Known":"F"}

mtdna_haplogroup{"Known":"K1a"}

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)0xf6e1…aa73

↓

merkle root0xf6e1…aa73

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: 0x1a7e…b59f
Signing key: authority-1
Signature: 0xa7a7…7206

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 hash0x1a7e9b5eaa78e79a2a285a30ad5e568e1e0a5389eeef80ca10beb838c02eb59f

Signature0xa7a7e8db55b377861e718af25ce541d1027a200b1bdf5a1d96a6f7915a67745baae4cf815a951bd081c0ffe7db5ddcf7645149180409b3a24aafeac4c6697206