Hey @bussyjd, I maintain indexing tooling at Envio and spent a day on the ERC-8004 side of Obol Stack.
Two things from reading discovery.py. search_registered_events looks back 10,000 blocks from latest, one chain per invocation, which on Base is roughly 5.6 hours of history. And cmd_count calls totalSupply() first, which reverts, because the registry is ERC-721 but not Enumerable, then falls back to a 50,000 block scan.
I built a version that answers the same questions off an index instead: 16 chains from one config, 380,990 agents since each registry's deploy block, with the ReputationRegistry joined in, which discovery does not read today. https://obol.envio.sh/, and the raw GraphQL endpoint is https://enviodev-5e79f84.internal.hyperindex.xyz/v1/graphql if you would rather curl it (can use an introspection query to see schema)
If it is useful I can share the repo and you can point discovery at a GraphQL endpoint in an afternoon.
Hey @bussyjd, I maintain indexing tooling at Envio and spent a day on the ERC-8004 side of Obol Stack.
Two things from reading discovery.py.
search_registered_eventslooks back 10,000 blocks from latest, one chain per invocation, which on Base is roughly 5.6 hours of history. Andcmd_countcalls totalSupply() first, which reverts, because the registry is ERC-721 but not Enumerable, then falls back to a 50,000 block scan.I built a version that answers the same questions off an index instead: 16 chains from one config, 380,990 agents since each registry's deploy block, with the ReputationRegistry joined in, which discovery does not read today. https://obol.envio.sh/, and the raw GraphQL endpoint is
https://enviodev-5e79f84.internal.hyperindex.xyz/v1/graphqlif you would rather curl it (can use an introspection query to see schema)If it is useful I can share the repo and you can point discovery at a GraphQL endpoint in an afternoon.