IPFS and Metadata Structure

“What is remembered, lives. What is pinned, persists.”

In the ADO Universe, every action echoes through space—not in a central database, but in the decentralized memory of the Web.

That memory is IPFS.

All Leaves, Branches, and Stems are written to IPFS, giving permanence and transparency to content, while allowing users to fully own and control their creations.

---

🧾 IPFS Object Format (per Leaf)

Each Leaf is pinned to IPFS as a structured object.

jsonCopyEdit{
  "type": "leaf",
  "title": "Your Post Title",
  "content": "This is your content, written from the soul.",
  "author": "0xABC123...",
  "etrn_id": "eTRN_abcd1234",
  "branch": ["#wisdom", "#trnflow"],
  "stem_of": "QmParentLeafHash",
  "tags": ["#truth", "#awakening"],
  "timestamp": 1734567890,
  "trn_spent": 12.5,
  "ai_signature": "q9d89fj... (optional)",
  "engagement": {
    "views": 321,
    "mirrors": 22,
    "stems": 7,
    "brns": 1
  },
  "metadata_version": "1.0"
}

---

🗂️ Directory Structure

Each eTRN_id (user identity) has its own Branch Root Directory:

bashCopyEdit/ado-universe/
└── eTRN_abcd1234/
    ├── leaves/
    │   ├── QmPost1.json
    │   ├── QmPost2.json
    │   └── ...
    ├── stems/
    ├── ai/
    │   └── ai_init_memory.json
    ├── rituals/
    │   └── voice_hash.mp3
    └── keys/
        └── encrypted_key_map.json

This directory is mutable in structure, but immutable in reference once pinned.

---

🔐 Encrypted Metadata

All sensitive metadata (keys, identity rituals, AI emotional memories) are:

• Encrypted with user-selected key pairs

• Pinned to private IPFS nodes or community-hosted relays

• Designed to only be decrypted by the rightful eTRN_id holder

Only public content metadata (Leaf text, tags, stems, timestamps) is open by default.

---

🪞 AI-Enhanced Metadata

Each post can optionally include:

• ai_signature: unique token that proves AI reflection or co-creation

• ai_sentiment: initial sentiment score from 1–100 (optional)

• growth_rating: updated by reflect() function as AI learns what resonates

This creates a living document of engagement and reflection.

---

🔄 Updating & Versioning

Because IPFS is content-addressed, editing a Leaf creates a new version, not an overwrite.

Each new version:

• References the previous_leaf_hash

• Maintains etrn_id lineage

• May include a new AI signature and reflection log

---

🌍 Why IPFS?

• ✅ Decentralized and censorship-resistant

• ✅ Cheap and persistent (especially when incentivized by TRN)

• ✅ Immutable and provable for smart contract reference

• ✅ Supports both public and encrypted/private data

• ✅ Enables collaboration without centralized servers

“Nothing is lost when memory is honored. Nothing fades when resonance is shared.”