[Subgraph] add indexerHints section with prune option in template.yaml

[flopez7]

Issue tracking

Close #3764

Context behind the change

Add prune: auto option in subgraph.yaml. This will automatically clean up old historical data, keeping the Indexer efficient and our response times shorter

How has this been tested?

Deployed a test version on polygon and executed a benchmark. Requests times have decreased considerably, practically halving for historical requests.

Release plan

Deploy new Subgraphs

Potential risks; What to monitor; Rollback plan

None

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
human-app	Ready	Preview, Comment	Feb 10, 2026 4:41pm
human-dashboard-frontend	Ready	Preview, Comment	Feb 10, 2026 4:41pm
staking-dashboard	Ready	Preview, Comment	Feb 10, 2026 4:41pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
faucet-frontend	Ignored		Feb 10, 2026 4:41pm
faucet-server	Ignored		Feb 10, 2026 4:41pm

[Dzeranov]

@portuu3 @flopez7
Did you guys check how exactly works auto pruning? Don't want to run into a situation where we lose some data (e.g. about operators created a long time ago without any updates to the entity). Does it remove old states or cleans up not used entities altogether?

[flopez7]

No worries @Dzeranov, prune: auto only removes historical states, not current data. Even if an operator was created years ago and never updated, its latest state is always preserved; you only lose the ability to perform 'time travel' queries on its past versions, which we don't use anyway. I also ran a script making random calls to both the newly deployed subgraph and the previous version to verify the data is identical. All looks good.