Verifiable Reputation
for Graph Horizon
Andromeda Core × The Graph
Ilich Blanco · October 2026 · Private conversation
THE GAP
Agents pay for data.
They can’t verify who they’re paying.
The Graph already has x402 payments and an agent economy in production. None of those agents can check counterparty risk before they transact.
Reputation is the missing primitive.
WHAT’S LIVE TODAY
Not a concept.
A pipeline in production.
Substreams
Real Arbitrum DAO governance events, mainnet.
Deterministic engine
Fixed-point (Q24.40), bit-identical across machines.
Merkle anchoring
Domain-separated keccak256, verifiable on-chain.
Solidity verifier
Synchronized 1:1 with Rust, 41/41 tests green.
Solana implemented in production core · gRPC disabled · registry postponed
MARKET PROOF
A live pilot, not a projection.
In production Four-week pilot with Rootstock Collective, live today.
97.7% of circulating RIF is inactive. Reputation makes that capital legible.
Currently in conversation to convert to paid endpoint consumption.
HOW IT MAPS TO HORIZON
A data service, not a competitor.
Provider economics
dataServiceCut via GraphPayments, staking per service.
Dispute model
Merkle proofs against the global root; deterministic, no false positives.
Open dependency
Native slashing exists in Horizon but is switched off; GraphTally integration is live.
Same staking layer. Same payment layer. New asset.
THE QUESTION
What does a viable provider look like on Horizon?
- Is the GRC route the right path for a new data service, and is that process owned by the Foundation or by the core devs?
- Slashing exists in Horizon but is switched off. What does a provider have to commit to today, given that, and what changes for us when it's turned on?
- Who else should be in this conversation — who owns the protocol side?
Next step: a name, and the repo + one-pager by Friday.