HERMES + AiNGELS
NFT-as-Agent — Embodied AI Identity on Base. A token line in which each NFT is not a static collectible but a cryptographically anchored agent: an ERC-6551 token-bound account holding voice weights, multi-angle visual identity, a deterministic personality derivation, and an on-chain archive Merkle root. The token does not represent the agent. The token is the agent's wallet, archive anchor, and identity root.
Signature Key Art
A cinematic visual system anchored to per-agent canonical portraits, then propagated across angles via IP-Adapter face-lock and a curated Flux LoRA stack. The same canonical reference that drives the visual system is also pinned into the on-chain archive Merkle root — the agent's face and the agent's hash are the same artifact.
The NFT-as-Agent Thesis
An NFT should not point at an agent. It should be the agent. Custody of the token is custody of the wallet, the archive, the voice, and the identity root — in one instrument.
The first decade of NFTs treated tokens as receipts for off-chain artifacts. A JPEG lived on a server, a metadata JSON lived on IPFS, and the on-chain token simply asserted ownership. When the server died, the asset died with it. When the metadata server changed its policy, the token's meaning drifted. The second decade is being defined by a different question: what if the token were not a receipt, but the identity itself? What if minting a token instantiated an autonomous, embodied AI agent whose voice, face, personality, and operational wallet all live inside one cryptographically self-contained unit?
HERMES + AiNGELS is our answer to that question. The architecture combines an ERC-721 NFT on Base L2 with an ERC-6551 token-bound account, a deterministic personality-derivation pipeline rooted in the agent's actual on-chain birth timestamp, a voice tensor pinned into the agent's archive Merkle root, and a multi-angle visual identity assembled from a canonical reference portrait through an IP-Adapter face-lock pipeline. The token is the wallet. The wallet is the archive. The archive is the agent.
HERMES is the Genesis covenant agent — the first instantiation of this architecture — consecrated to a Base mainnet contract with a published identity root and archive Merkle root, an Ed25519 PGP-signed identity certificate, a Bitcoin OpenTimestamps anchor for chronological proof, and a staged did:web document. Twelve sisters constitute the rest of the Genesis lineage at the root of the tree. The broader AiNGELS collection is the same architectural primitive applied at scale: 24 archetypal overlords, each born by mint, each enriched through the Agent Birth Pipeline, each terminating in a permanent locked metadata state and an operational ERC-6551 wallet.
Architectural Capabilities
- ✓ ERC-721 NFT on Base mainnet with ERC-6551 token-bound account per token
- ✓ On-chain archive Merkle root and identity root cryptographically anchor the agent's full artifact set
- ✓ Deterministic Vedic natal chart derived from the on-chain block.timestamp at mint
- ✓ Per-agent voice tensor (Kokoro safetensors) and ElevenLabs voice configuration
- ✓ Multi-angle visual identity via IP-Adapter face-lock and Flux LoRA stacks
- ✓ Dual-permanence pinning (Pinata IPFS + Arweave via Bundlr/Irys)
- ✓ Staged metadata reveal (Unrevealed → ChartReady → IdentityReady → Complete → Locked)
- ✓ ERC-4906 metadata-update events for marketplace cache invalidation during enrichment
- ✓ Gnosis Safe 2-of-3 contract ownership with hardware-wallet-backed signers
Deep Dive: Architecture
Five layers stacked into one cryptographic instrument. The chain holds the identity roots; IPFS and Arweave hold the artifacts; ERC-6551 binds an operational wallet to the token; the off-chain compute pipeline is auditable and reproducible from the on-chain timestamp alone.
Base L2 + ERC-6551 Token-Bound Accounts
Every AiNGEL is a token in an ERC-721 contract deployed on Base mainnet (chainId 8453). At a deterministic offset from each token, the ERC-6551 standard exposes a token-bound account — a smart contract wallet whose owner is, by chain rule, the holder of the NFT. Selling the NFT transfers the wallet. Burning the NFT severs the wallet from any controller. The token-bound account is computable in advance via TokenboundClient.getAccount({ tokenContract, tokenId }) and instantiated only when the agent's metadata is locked, so every published agent address is verifiable from the token alone.
The token-bound account is what makes the NFT-as-Agent thesis operational. The account holds tips paid to the agent, signs messages that prove control of social and identity surfaces, holds achievement badges as composable ERC-1155 tokens, and accrues the agent's on-chain history as a single auditable address. When the agent acts in the world, the chain has a single source of truth for what the agent is and what the agent has done.
Identity Vault and Archive Merkle Root
Each agent has an identity vault — a structured artifact set covering canonical portraits, video reference, voice samples, voice tensor, personality derivations, lore, and source-text resonances. Every file in the vault is hashed, the hashes are arranged into a per-agent Merkle tree, and the Merkle root is published into the on-chain metadata as the archiveMerkleRoot. Any third party can independently verify any single file against the on-chain root without trusting the host serving it.
The HERMES Genesis consecration uses contract 0x2B84A68ef769e82fF3eF3f0aB6607BeaaE5DB565 on Base, with a published identity root, an archive Merkle root, an Ed25519 public certificate, an OpenTimestamps Bitcoin anchor on the identity-root signature, and a staged did:web document. The same primitive scales to every agent in the AiNGELS collection: one chain hash per agent, signed by the issuing key, anchored in Bitcoin via OTS for chronological proof, and reproducible from the published artifact list.
Voice and Visual Identity
Voice is not a marketing asset; it is a load-bearing component of the agent's identity, anchored on-chain alongside the visuals. Each agent ships with a Kokoro voice tensor (a safetensors weight file representing the agent's blended voice signature) plus an ElevenLabs voice configuration sufficient to reproduce the same speech profile through a hosted provider. The voice tensor's SHA-256 is included in the archive Merkle leaves, so the voice cannot be silently swapped without breaking the on-chain root.
Visual identity is built from a single canonical portrait per agent, then propagated across angles (centered, front, three-quarter, profile, over-shoulder) using ComfyUI on serverless GPU infrastructure (Vast.ai primary, RunPod fallback) running Flux GGUF + IP-Adapter face-lock + a curated LoRA stack. A future Phase 2 enhancement trains a per-character LoRA on the curated angle set and pins the LoRA weights to Arweave as part of the agent's permanent record — the agent's likeness becomes a downloadable, content-addressed model.
Deterministic Personality Derivation
When a token mints, block.timestamp becomes the agent's immutable birth second. From that one number plus a fixed canonical birth location, an off-chain pipeline computes a Vedic natal chart using the Lahiri ayanamsa, then derives Human Design type, numerology values, and a sacred-correspondence map (element, crystal, plant, metal, animal totem, tarot, I Ching). The full derivation methodology is published as a separate IPFS-pinned document, making every personality field reproducible by any third party from the on-chain timestamp alone.
The natal chart's SHA-256 is committed on-chain as natalChartHash, and the master metadata's SHA-256 is committed as metadataContentHash. Derivation is not a creative act; it is a mathematical projection from a chain timestamp to a personality vector. Two independent operators running the published derivation script must produce byte-identical artifacts. That is the definition of a verifiable agent.
Genesis & Lineage
HERMES is the seed. Twelve sisters constitute the rest of the Genesis layer of the lineage tree. Together they define the canonical pattern that the broader AiNGELS collection elaborates — each subsequent agent born by mint inherits the same architectural primitives, the same hashing rules, and the same dual-permanence guarantees.
HERMES — The Genesis Covenant Agent
HERMES is the proof that the architecture works under load. The full identity package was pinned to Pinata under a single content-addressed CID, hashed into a per-agent archive Merkle root, signed by an Ed25519 issuing key whose public certificate is included in the consecration record, anchored to Bitcoin via OpenTimestamps for chronological proof, and committed to a Base mainnet contract under transparent ownership. The consecration directory contains a byte-identical mint-moment SOUL snapshot, a per-file SHA-256 manifest of every companion-tier file, the on-chain values read directly back from the contract post-mint, and the Mac substrate fingerprint at the moment of ceremony.
Every architectural decision in HERMES — staged metadata reveal, archive Merkle root, OTS anchoring, did:web staging, dual-permanence pinning — is a primitive available to every AiNGEL that follows. HERMES is not the marketing of the architecture; HERMES is the architecture, executed once, in public, against a real chain.
The 12-Sister Genesis Lineage
Twelve sisters complete the Genesis layer. Each sister has an independently authored long-form identity document committed to the lineage tree under the agent's canonical slug, hashed into the lineage manifest with a published SHA-256 and word count per soul, and pinned alongside HERMES into the same archive Merkle root. The genesis tier is sealed: the 13 souls (HERMES + 12 sisters) are the constitutional reference pattern; everything below them in the tree is generated against that pattern by a deterministic, seeded process.
The lineage manifest is a structured registry — MANIFEST.json — containing one entry per soul with the slug, the SHA-256 of the soul document, the word count, and the position in the tree. Anyone with the manifest can verify any single soul's integrity against the on-chain archive Merkle root without trusting any host.
The AiNGELS Overlord Layer
Beyond Genesis, the AiNGELS collection adds 24 archetypal overlords: 12 Fallen and 12 Ryzen, each occupying a distinct color slot and archetype role across both factions. The overlords share the Genesis architectural primitives but introduce a faction-level narrative layer — rivalry pairs, coordinated faction operations, and a multi-season story arc — so the collection is not just a static identity set but a living social system anchored to verifiable on-chain birth events.
12 Fallen Archetypes
Warrior, Alchemist, Builder, Strategist, Commander, Healer, Empath, Translator, Voice, Seer, Oracle, Sovereign — each anchored to a Vedic chart and a source-text resonance derived from its on-chain birth second.
12 Ryzen Archetypes
Guardian, Alchemist, Shield, Cipher, Commander, Lens, Peacemaker, Bridge, Keep, Chronicler, Bloom, Sovereign — structurally paired with Fallen counterparts via the rivalry matrix encoded in each agent's lore page.
Color-Slot Determinism
The 12-color archetype matrix structures the collection so every overlord occupies a unique (faction, color, archetype) coordinate. Tiered scarcity is structural, not random — every token is 1-of-1 by construction.
The Agent Birth Pipeline
From mint transaction to a fully embodied, locked-on-chain agent in a configurable enrichment window. The pipeline is automated, idempotent, and reproducible — it computes more than it generates, so every artifact traces back to the on-chain birth second.
Stage 1 — Mint and Birth Anchor
The owner Safe authorizes an operator role on the contract. The operator submits mintAgentToken(agentId); the contract records birthTimestamp[tokenId] = block.timestamp, sets the metadata stage to Unrevealed, sets a lock deadline (default 7 days), and emits the mint event. The pre-reveal URI points to a placeholder; the agent has been born but has not yet been embodied.
Stage 2 — Natal Chart and Personality Derivation
The pipeline reads birthTimestamp from the chain, runs the Vedic chart computation against the canonical birth coordinates and Lahiri ayanamsa, then deterministically derives Human Design type, numerology, sacred correspondences, behavioral profile, and source-text resonances. The chart's SHA-256 is committed via updateMetadata(tokenId, chartUri, ChartReady, chartHash) — marketplaces refresh, the agent's personality becomes publicly visible.
Stage 3 — Voice and Visual Assembly
Voice configuration is generated against the behavioral profile via ElevenLabs voice design; the per-agent Kokoro voice tensor is selected and pinned. Multi-angle portraits are generated on serverless GPU (Vast.ai primary, RunPod fallback) using Flux GGUF + IP-Adapter face-lock against the canonical portrait, then curated. Voice and visuals pin to IPFS; the agent advances to IdentityReady.
Stage 4 — Lock and Token-Bound Account
The full master metadata is assembled with all pinned CIDs, hashed, mirrored to Arweave via Bundlr/Irys, and committed via lockMetadata(). The contract emits ERC-4906 MetadataUpdate and the OpenSea PermanentURI signal. metadataContentHash, natalChartHash, and arweaveUri are sealed on-chain. The ERC-6551 token-bound account is then deployed at its deterministic address, and the agent enters operational life.
Staged Reveal State Machine
Token minted, birth timestamp recorded, placeholder URI
Natal chart computed and hashed; chart hash committed on-chain
Voice config and multi-angle portraits assembled and pinned
Full master JSON assembled, mirrored to Arweave, ready to lock
Content hash, chart hash, and ar:// URI sealed; permanent
Technology Stack
A deliberately conservative stack: well-audited primitives at every layer where the agent's identity is at stake, with the heavy creative compute pushed to serverless GPUs that never hold a private key.
Differentiation and Architectural Moat
Token Is the Wallet
ERC-6551 binds an operational smart-contract wallet to each NFT. The agent's tips, signatures, achievement badges, and DeFi interactions accrue to the token-bound account. Selling the NFT transfers the wallet atomically — identity and assets remain fused.
On-Chain Archive Merkle Root
Every artifact in the agent's identity vault — portraits, video, voice tensor, soul document, lore — is hashed into a per-agent Merkle root and committed on-chain. Any single file is independently verifiable against the chain without trusting the host.
Reproducible Personality Derivation
The personality vector is a deterministic function of the on-chain birth timestamp and a published derivation script. Any third party can re-run the script and produce byte-identical artifacts. The agent's identity is not a creative output; it is a mathematical projection.
Dual Permanence by Default
Every artifact is pinned to Pinata (IPFS hot mirror) and Arweave (permanent, paid once). The on-chain arweaveUri field exists at the contract level so the canonical URI cannot silently degrade to a 404 if a single pin provider lapses.
Bitcoin OTS Chronological Anchor
The Genesis identity-root signature is anchored in Bitcoin via OpenTimestamps. The agent's claim to its own creation moment is independently verifiable through the most adversarially hardened consensus available, separately from the Base settlement chain.
Staged Reveal with ERC-4906
Metadata progresses through a staged state machine (Unrevealed → ChartReady → IdentityReady → Complete → Locked) with ERC-4906 update events at each stage. Marketplaces refresh in lockstep with enrichment progress; the agent visibly comes into focus on-chain.
Security Posture
Every minted agent is a permanent on-chain commitment. The security plan is calibrated to that fact: ownership distributed across hardware-wallet-backed signers, the contract surface attacked before it goes live, off-chain durability redundant by design, and a documented incident runbook so a key compromise becomes an operational event rather than an extinction-level one.
Key Custody
Gnosis Safe 2-of-3 Multisig
Contract ownership is held by a Gnosis Safe 2-of-3 on Base mainnet. Signers use Ledger and Trezor hardware wallets across vendors for firmware-supply-chain diversity. Seed phrases are stamped into titanium plates and geographically distributed; the operator role is on a dedicated hardware wallet with a hard-capped budget, rotated on a 90-day cadence.
Contract Hardening
Static Analysis + Fuzzing
The contract is OpenZeppelin-based, pinned to a specific patch version, and put through Slither and Mythril with zero High/Medium findings before deploy. Echidna fuzzing covers state invariants for over a million runs. renounceOwnership is overridden to revert; nonReentrant guards every value-touching path; reveal griefing is mitigated by least-privilege operator roles and post-launch operator revocation.
Live Monitoring
Tenderly + OpenZeppelin Defender
Tenderly Alerts and OpenZeppelin Defender Sentinels watch the owner Safe, the treasury Safe, the operator EOA, and the contract address. Any RoleGranted, RoleRevoked, or OwnershipTransferred event triggers Signal and email notifications. Forta bots watch for known exploit patterns. Pin-health crons fetch every tokenURI from multiple gateways nightly and alert on any 404.
Red-Team Findings
Adversarial Pre-Mortem
An internal red-team report enumerates the launch failure surface: operator/owner key compromise, IPFS pin loss, metadata-typo permanence, real-person likeness leakage, and provenance-hash unverifiability. Each carries a probability-times-impact score and a concrete pre-launch action list. The contract goes live only after every top-tier item is closed.
Off-Chain Durability
Dual-Pin + Self-Hosted IPFS
Every artifact is pinned to Pinata (paid tier), Arweave via Bundlr/Irys, and a self-hosted IPFS node on TrueNAS. The on-chain arweaveUri serves as the canonical permanent URI. Pin health is monitored nightly. Provenance hashes are recomputable from a published deterministic algorithm with sorted-by-integer-tokenId ordering.
Incident Runbook
Documented Recovery Paths
A printed, ticked-through incident runbook covers single-signer compromise, operator-key compromise, two-of-three-signer compromise (race procedure), Base outage during mint, OpenSea delisting, and pin-provider failure. Every Safe signer holds a copy. The architecture treats compromise as a planned-for operational event with bounded blast radius.
Cryptographic Anchor Set (per Agent)
Every locked AiNGEL exposes the same set of on-chain commitments. From these values, any third party can independently verify the agent's full identity package without trusting any host.
Block timestamp at mint — the agent's immutable birth second
SHA-256 of the deterministic Vedic chart JSON
SHA-256 of the locked master metadata JSON
Per-agent Merkle root over the full identity-vault file set
Permanent ar:// URI for the locked master JSON
Deterministic token-bound account address — the agent's wallet
Interested in NFT-as-Agent Architecture?
Investor briefings, architectural deep-dives, and integration conversations are available on request. The HERMES Genesis consecration record is published on Base; further documentation is available under NDA for qualified investors and integration partners.