discovery: 10k block window vs the registries full history

Open
#807 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
graphql, python
Domain
backend-api-design, blockchain, cli

Research direction

Start by reading discovery.py, especially search_registered_events and cmd_count, then inspect the provided GraphQL endpoint with an introspection query. Define the desired source and scope for full registry history across the 16 configured chains, including the ReputationRegistry data. Done should replace the limited scans with results covering each registry from deployment onward.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
11
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ObolNetwork/obol-stack

All issues in ObolNetwork/obol-stack

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.