THE ANCIENT
BIOCHAIN

63c5e4bb-3e32-4fd6-83ec-07efc4ddfbd3

ENTITY_CREATED · recorded 2026-09-11T22:53:16.254192024+00:00

Transaction

TypeENTITY_CREATED
Subjectentity · cay011.SG
Actoradna-ingest-pipeline
Institution
Recorded at2026-09-11T22:53:16.254192024+00:00
Effective at
Domain moduleancient-dna
Schema version1
Input entitiesnone
Output entitiescay011.SG
Revision ofno earlier revision on record

Payload

age_at_deathUnknown
data_type{"Known":"Shotgun"}
date_full_info{"Known":"6475-6269 calBCE (7562±38 BP)"}
date_mean_bp{"Known":"8369"}
date_method{"Known":"Direct: IntCal20 (WARNING: MISSING LAB CODE)"}
date_sd{"Known":"40"}
group_id{"Known":"Turkey_PPN"}
individual_id{"Known":"cay011"}
latitude{"Known":38.2153}
locality{"Known":"\"Boncuklu (Konya, Karatay)\""}
longitude{"Known":39.7526}
master_id{"Known":"43"}
political_entity{"Known":"Turkey"}
skeletal_code{"Known":"cay011"}
skeletal_elementUnknown
unrecognized_columns{"\"mtDNA match to consensus if >10x (merged data) [estimates are typically off by (uncorrected + power(10,-0.271*LOG(mt-coverage)-1.120)]\"":"n/a (<10x)","Mean coverage on non-targeted autosomal SNPs for full bam - not yet computed if \"\"..\"\" and bam restricted to on-target SNPs if \"\"0\"\"":"0.04224026","No. Libraries":"2","Pulldown Strategy":"Native Pulldown on 3.2M snpset","SNPs hit on autosomal targets (Computed using easystats on 1240k snpset)":"23943","SNPs hit on autosomal targets (Computed using easystats on Compatibility snpset)":"27465","SNPs hit on autosomal targets (Computed using easystats on Compatibility_HO snpset)":"5702","SNPs hit on autosomal targets (Computed using easystats on HO snpset)":"12035","SNPs hit on autosomal targets (Computed using easystats on enhance 2M capture subset)":"41334","Suffices (indicating data types used for sources which can be a subset of that in bam)":"SG","Sum total of ROH segments >20cM":"n/a (<300K SNPs)","hapConX 95% CI truncated at 0 (only if male and >=2000 SNPs covered on X chromosome) [estimates are typically 0.005 too high]":"n/a (<2000 X SNPs)","mtDNA coverage (merged data)":"1.778"}

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)0x2f95…72bc
merkle root0x2f95…72bc

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
0xb655…7702
Signing key
authority-1
Signature
0xf882…8e0a

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 hash0xb655c0b2a19c5d0c7cd779e2bffbd92f46dcff4aaa36594958188a161d427702
Signature0xf88291a6bb595402f1a8f4f4fca607ad598ad3440a9aaafd9e91d4f6099dda5899856de4901cdfe92c1fb957ee5ddced8754827e972bc941277aa0ca7e948e0a