graphprotocol / graphprotocol/graph-node
Trigger caching
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Introduce the ability for Graph Node to store / cache raw events from the chain. This is an extension of https://github.com/graphprotocol/graph-node/issues/2581
Impact:
- Reduced duplicate work in the event of restarts
- Re-use of fetched triggers across deployments
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #2581 and the discussion here to understand the intended trigger-caching design. Trace how raw chain events are fetched and how restarts and deployments currently repeat that work. Done means the design supports reusing fetched triggers across deployments and reducing duplicate work after restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100