Overview
This article explains what “ancestral DNA” means for the Xolo, why a blockchain registry matters, and how our open, privacy-respecting protocol works on the eCash (XEC) network with the $RMZ eToken.
The story written in the Xolo’s genome
Modern genetic testing can confirm key aspects of breed identity and lineage continuity. For the Xolo, markers associated with:
- Coat phenotype (notably the FOXI3 variant—often informally called “FOX-13”) tied to hairlessness,
- Population structure and diversity, and
- Lineage relationships across kennels and generations,
…help document a dog’s place within a uniquely Mexican bloodline that spans centuries of culture and art. While DNA doesn’t “prove” history on its own, genetic signatures plus archival records (pedigrees, show results, photos, and breeder attestations) create a robust, multi-source evidence trail.
Why register DNA evidence on a blockchain?
Traditional databases are useful—but centralized systems can be altered, lost, or siloed. By anchoring proofs to the blockchain, we gain:
- Immutability: A timestamped, tamper-evident record for certificates and pedigree events.
- Portability: Owners can prove a claim without relying on a single website or authority.
- Composability: On-chain proofs link to NFTs, tokens, and future dApps (e.g., exhibition passports, health-record wallets).
- Community governance: Open standards encourage multi-breeder participation and third-party verification.
The XolosArmy “Proof-of-Pedigree” protocol (v1)
1) Evidence collection (off-chain)
- DNA certificate from a recognized lab (PDF or paper scan).
- Key fields extracted: Dog Name, Sex, Microchip (if any), Lab Sample ID, Issue Date, Lab Name/Contact, and relevant genotype notes.
- Context media: Pedigree PDF, kennel letter, and provenance photos (owner handover, show certificates, etc.).
- Owner consent: Permission to publish hashes and minimal metadata.
2) Hashing & packaging
file_hash
: SHA-256 of the DNA certificate file.summary_hash
: SHA-256 of a canonical JSON summary (ordered keys) with key fields only.- Optional content-addressed pointers (e.g., IPFS CIDs) for redacted PDFs/photos stored off-chain.
3) On-chain anchoring (eCash)
We write a compact, human-readable OP_RETURN note in a transaction controlled by the XolosArmy registry wallet. Example (UTF-8 payload):
XOLODNA|v1|sha256:7b6c…d3a2|summary:9f41…2b07|cert:cid:bafy…kq|ped:cid:bafy…9n|id:XR-2025-001|owner:ecash:qq…9x
sha256
= hash of the full certificate filesummary
= hash of the JSON summarycert
/ped
= optional content-addressed locations for redacted documentsid
= canonical XolosArmy Registry IDowner
= current owner’s eCash address (for signed updates)
4) Token-bound identity (optional)
Link the registry entry to a non-transferable NFT “Pedigree Badge” or a transferable collector NFT that includes the dog’s media (respecting privacy). This enables:
- Exhibition “passes” for galleries and cultural events
- Proof-of-ownership updates
- Community perks for $RMZ holders
5) Ownership & status updates
Changes (owner transfer, corrections, vet updates) are published as new on-chain notes referencing the original id
. The newest valid note is current state; all history remains auditable.
Minimal, open metadata schema
For interoperability, we publish a small, vendor-neutral JSON. Only non-sensitive fields are included; raw genotype is never on-chain.
{
"schema": "xolosarmy.xoloDNA.v1",
"registry_id": "XR-2025-001",
"dog": {
"name": "Yoalli Ramírez",
"breed": "Xoloitzcuintli",
"variety": "Hairless / Standard",
"sex": "F",
"microchip": "9851-...-1234"
},
"lab": {
"name": "Example Genetics",
"sample_id": "EG-2025-7781",
"issued": "2025-08-30"
},
"genotype_notes": ["FOXI3 variant present"],
"hashes": {
"certificate_sha256": "7b6c...d3a2",
"summary_sha256": "9f41...2b07"
},
"media": {
"certificate_cid": "bafy...kq",
"pedigree_cid": "bafy...9n",
"photos_cid": "bafy...xy"
},
"chain": {
"network": "eCash",
"txid": "…",
"op_return": "XOLODNA|v1|..."
}
}
Privacy, consent, and revocation
- Privacy by design: Only hashes and minimal descriptors go on-chain. Certificates remain off-chain; sharing is voluntary.
- Owner control: Owners decide which media to reveal (e.g., redacted PDFs).
- Corrections: If a certificate is superseded, we anchor a new hash and mark the old hash as retired via a follow-up on-chain note.
- Right to be forgotten vs. immutability: We cannot delete a past hash, but we can publish a revocation/update instructing verifiers to ignore prior entries for that
registry_id
.
Benefits for the Xolo community
- For families & collectors: Transparent provenance with a simple QR or txid lookup.
- For breeders: Credible proof-of-pedigree without exposing private client data; a neutral, multi-party standard.
- For culture carriers: Museums, curators, and researchers gain durable references that connect living dogs to Mexico’s artistic and archaeological record—respectfully and verifiably.
- For developers: An open schema to build explorers, verification bots, and gallery apps.
Verifying a claim (how it works)
- Download the owner-shared certificate file (or a redacted version).
- Compute its SHA-256 locally.
- Compare with the
certificate_sha256
anchored on-chain (via the tx’s OP_RETURN). - Confirm the
registry_id
lineage (initial record + latest update note). - (Optional) Check media CIDs and summary JSON hash for additional assurance.
If the hash matches, the certificate existed in that exact form at the time of the transaction—a powerful guarantee against tampering.
Roadmap
- v1 (live): OP_RETURN anchoring, open JSON schema, basic explorer views.
- v1.1: Non-transferable “Pedigree Badge” NFTs + QR verification cards.
- v2: Multi-lab attestations, zk-proofs for selective disclosure (prove a trait without revealing the whole report).
- v3: Cross-chain mirrors and museum-grade exhibit passports.
TL;DR
The Xolo’s DNA carries a unique, living heritage. By anchoring DNA evidence and pedigree proofs on the eCash blockchain, XolosArmy Network gives every guardian, breeder, and curator a durable, verifiable way to protect identity, prove provenance, and celebrate culture—without exposing private data.