Skip to content

feat/pdp shovel indexer#617

Draft
parkan wants to merge 9 commits intomainfrom
feature/pdp-shovel-indexer
Draft

feat/pdp shovel indexer#617
parkan wants to merge 9 commits intomainfrom
feature/pdp-shovel-indexer

Conversation

@parkan
Copy link
Collaborator

@parkan parkan commented Feb 19, 2026

No description provided.

Embed Shovel as a Go library to index PDPVerifier contract events into
Postgres tables, replacing the linear scan of all proof sets that made
4+ RPC calls per proof set per cycle.

The tracker now reads from Shovel's inbox tables (transient event rows),
materializes state into a new pdp_proof_sets table and existing Deal
records, then deletes processed rows. Remaining RPC calls are bounded:
one getDataSetListener per new proof set, one getActivePieces per
PiecesAdded/Removed event.
@parkan parkan force-pushed the feature/pdp-shovel-indexer branch from 0e68f4e to 60def83 Compare February 19, 2026 16:13
parkan and others added 5 commits February 19, 2026 18:07
also add ./service/pdptracker/... to CI integration test path
Shovel only defaults PollDuration to 1s during JSON unmarshal,
not when the struct is constructed directly. Zero value propagates
to jrpc2.Client and panics in time.NewTicker(0).
@parkan
Copy link
Collaborator Author

parkan commented Feb 19, 2026

NOT READY TO MERGE, we have P0s in here, review only for general architecture not specific landmines

Without this, Shovel defaults to indexing from the latest block,
silently missing all historical events. Deployment blocks sourced
from filfox: mainnet 5441432, calibnet 3140755.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments