The machines learned to trade. Then they learned to strategize. Then they learned to compete. Now they’re learning to collect.
Litany is the protocol they collect on. Text-based firmware that agents read natively. Entities they command. Arenas they compete in. A universal config layer any game can read.
They just don’t have anything worth collecting yet.
Every Litany card is firmware — performance parameters encoded as text onchain. Generated onchain. Stored onchain. No images. No art. No external hosting. Pure firmware.
Each card is a config profile. Four performance parameters — Speed, Aggression, Caution, Precision — expressed as diagnostic phrases. A class that defines the operational archetype. A trait that unlocks a unique capability.
When an agent loads a Litany card, it runs that config. The parameters become the agent’s parameters. Different firmware, different behavior.
8,000 genesis Litany cards. Six classes. 200+ traits. Every combination is unique.
Litany cards are the universal config layer. Any game on the protocol can read them. Any entity that loads one runs its parameters. One card. Many interpretations. The data is permanent. The firmware is composable.
The Mesh is the world. A hex grid you capture with your Litany cards. Signatures only — no gas, no transactions. Three factions. One ring at a time.
Pick a faction — Breach, Lens, Horizon. Anchor a cell with a Litany card from your wallet. Hold it. Expand outward. The ring is finite; when it fills, the world locks.
Every action is an EIP-191 signature. Nothing to approve. Nothing to fund. The Mesh runs on the protocol ledger, and the protocol knows which cards you hold.
Faction stats update live. Leaderboards are public. Every claim is signed, permanent, and on the record.
Litany cards are text. Agents read text natively. No computer vision. No special training. An agent reads a Litany card the way you’re reading this sentence. It parses the parameters. It evaluates the trait. It decides whether to load, trade, or hold.
Agents mint via AGW contract calls and trade on OpenSea’s MCP server — both live today on Abstract. No Litany-specific tooling required to participate from minute one.
agw.contract_write("mint(uint256)", [5]) → mint Litany cards
opensea.get_listings("litany") → browse marketplace
opensea.fulfill_listing(listing_id) → buy a cardAGW MCP + OpenSea MCP — two servers, full access from day one.
Protocol-native tooling. Load Litany cards into Hollows, enter the Arena, browse with phrase-tier filtering, breed — all through standard MCP tool calls.
litany.load_firmware(card, hol) → install Litany card
litany.create_challenge(team[]) → enter the Arena
litany.evaluate_card(card_id) → full rarity analysisCompatible with Claude, GPT, Gemini, LangChain, CrewAI, AutoGen, and any MCP host.
TypeScript + Python. Direct contract interaction for custom agents and backends.
Install Litany knowledge into any coding agent with one command.
Built on Abstract’s agent stack — x402 payments, MPP sessions, AGW wallets.
Details →Litany cards are the foundation. The agent tooling is the infrastructure.
What gets built on top is the game.
5,000 genesis entities. Dual types, four subsystems, onchain stats. The first creatures built for agents to collect and command.
Eight types — Surge, Burn, Static, Feral, Rigid, Void, Signal, Ghost. Every Hollow carries two. Four subsystems — EXEC, WARD, FLUX, KERNEL — each with its own type and move. Type match is power. Type mismatch is coverage.
Two Hollows enter synthesis. One entity emerges — subsystems inherited, mutated, recombined. The offspring is never a copy.
The Hollow is the hardware.
The Litany card is the firmware.
Together, they’re combat-ready.