19 days ago I started building Moirai using @shinzonetwork Generator client that ranks Polymarket traders by how much money they've actually made I figured the hard part would be the ranking maths. It wasn't. The hard part was getting the data out of the chain at all. Here's the thing nobody mentions when you start. A blockchain answers exactly one question: give me block N. That's it. There's no "show me this wallet's trades", no "add these up". And what comes back is a blob of hex you need the exact recipe the contract used to pack it, or it's meaningless. So before you write a single line of your actual product, you're fetching every block, unpacking each one, working out what it meant, and putting it somewhere you can query. Then doing that forever, because the chain doesn't stop. 93,730,850 trades later, that's what's sitting behind this thing. The app is four small programs, and they never talk to each other everything goes through Postgres. 1. ingester - pulls the logs, decodes them, works out each trader's profit 2. enricher - the chain only ever gives you a token ID, so this one asks Polymarket what the market is actually called api reads Postgres, hands out JSON web the site The bit I'd actually suggest copying is how the ingester talks to its data source. It goes through one interface, and that interface only ever asks four things: are you alive, how far along are you, describe block N, give me the logs between here and here. That's the whole contract. Shinzo answers those four. So does a plain RPC node. Nothing downstream knows or cares which one is plugged in. I wrote that on day one, before I needed it. Turned out to matter. Now the honest bit about Shinzo, because I've seen people get this wrong: I built the adapter and ran it against a preview host. Polygon isn't live on Shinzo yet Ethereum's the only live chain, Polygon's sitting on 3 votes. So Moirai runs on a plain RPC today. I ran their generator client locally to read its schema, not as part of the pipeline. Two things cost me real time that aren't written down anywhere: Collections are chain-prefixed. It's Polygon__Mainnet__Log, not Log. I spent a while convinced there was just no data. And DefraDB stores addresses checksummed, with a case-sensitive filter. Pass a lowercase address, you get zero rows and no error. Nothing to debug. Just silence. If you're pointing an agent at onchain data rather than a dashboard, three things I'd think about: An agent can't tell when a number looks wrong. I look at my own leaderboard, something feels off, I go and check. An agent doesn't do that it acts on whatever you handed it, straight away. Shinzo keeps a count of how many separate machines independently signed the same piece of data, so you can say "don't act unless three of them agree". There's no equivalent on a subgraph. Put the age of your data in the response. Mine's days behind right now my ingester can't keep up on a free RPC and the app says so on the page. Without that, an agent trades on three-day-old prices and has no way of knowing. And don't hand an agent a firehose. No model holds 93 million trades. Both of these give you events turning events into "who's winning" is still on you. On cost, since people assume: The Graph is 100k queries free a month, then $2 per 100k. An agent polling every ten seconds runs about $3/month. It's cheap. Don't pick on price. Choosing today- The Graph is the mature one. More chains, more people who've already hit whatever you're about to hit. Shinzo's early, but it's the one actually thinking about whether you can verify what you're given. Polygon's on 3 votes. Which is exactly why I'm on RPC. If you want it → shinzo.network/chains