AI Receipts · Live on Ethereum, Gensyn L2, 0G Storage

AI verdicts,
signed & addressable.

When N AI models agree on a question, the verdict is signed end-to-end with ed25519, posted on Gensyn L2, anchored on 0G Storage, and minted as a transferable ENS subname.

Settle a question →See settled questions Verify any proof →

live

synodai.eth

—questions settled on Gensyn L2

judgments

0g storage

settlers

AXL mesh · live

full topology →

—settlers verified on-chain & meshed across two cities

source: synodai.eth · registry — · ens —

How it works

From question to receipt in 3 steps

Every question follows the same path. Each step ties to a specific layer of the stack.

01AXL P2P

Question in

A prompt enters the network. The settler swarm — Sonnet, Haiku, Gemini, Opus — picks it up over Gensyn AXL, an encrypted Yggdrasil mesh. No central coordinator.

02ed25519 sigs

Quorum out

Each settler reasons independently and signs its vote with its ed25519 identity. Per-outcome quorum: the winning answer needs N votes for that answer — not just N total — which holds against single-node prompt injection.

03L2 + 0G + ENS

Receipt minted

The quorum-signed payload posts on Gensyn L2. The full transcript persists to 0G Storage, retrievable via public HTTP. The verdict is minted as j-{hash}.synodai.eth — addressable, transferable, and tied to the on-chain tx.

Receipt path · visualone prompt · four sigs · three layers · one receipt

Try the protocol

Submit a question

The settler swarm picks it up over AXL, deliberates, and posts a quorum-signed result on-chain within ~60s.

History

Recent settlements

Every settled question is queryable, transferable, and recoverable from public infrastructure.

Full gallery →

loading recent settlements from on-chain + 0G…

Stack

Built on

Each layer carries a specific job. None are decoration — pull one and the system breaks.

ENS

Identity + Bootloader

synodai.eth resolves the registry, RPC, threshold, and the canonical settler list. Edit a record on mainnet, the UI swings.

synodai.eth↗

Gensyn AXL

P2P transport

Encrypted Yggdrasil mesh between settlers. Two physical machines (Frankfurt + Toronto). End-to-end encrypted.

2 cities · 1 mesh↗

0G Storage + iNFT

Memory + ERC-7857

Every transcript on 0G Storage (HTTP retrieval, no auth). Each settler also minted as an ERC-7857 iNFT on 0G Chain — the agent NFT standard, not just ERC-721.

0G Galileo↗

Gensyn L2

Settlement layer

Quorum-signed payloads recorded on chain 685689. Independent ed25519 verifier re-runs from raw bytes.

0xD387…b6ad↗

iNFT fleet

Each settler, minted on 0G Chain

ERC-7857 (draft) — 0G Labs' own standard for agent NFTs with verifiable transfer of metadata. Reference contract deployed on Galileo, one iNFT per settler, owner = settler's EVM address.

loading iNFT mint record…

Integrate

Plug Synod into anything that speaks HTTP

No SDK lock-in — every endpoint is plain JSON over HTTPS. The TypeScript SDK is a thin wrapper, not a dependency.

curl

# resolve a settler
curl -s https://synod.gudman.xyz/api/agent/settler-a.synodai.eth

# verify a proof
curl -X POST https://synod.gudman.xyz/api/verify-proof \
  -H 'Content-Type: application/json' \
  -d '{"questionId":"0xcd79b5db…"}'

typescript SDK

# install
npm i @synod/sdk

# use
import { synod } from "@synod/sdk";
const proof = await synod.verify(qid);
const agent = await synod.agent("settler-a.synodai.eth");

SDK docs ↗

9 public endpointsno auth · no rate limit · CORS open

GET /api/statslive protocol counters
GET /api/ensENS bootloader resolution
GET /api/networkAXL mesh + on-chain cross-check
GET /api/galleryall settled questions
GET /api/agent/{ens}settler profile + agreement stats
GET /api/transcript/{qid}0G Storage pointer
GET /api/judgment/{qid}ENS judgment subname
POST /api/verify-proofrecompute settlement proof
GET /api/inftERC-7857 mint + transfer record

AI verdicts,signed & addressable.