feat(indexer): fetch v3.5.0 and v1.4.0 events from their upgrade blocks

[rvagg]

Duplicate contract addresses but for the new versions so we can start from their upgrade blocks rather than from the complete START.

[Copilot]

🟢 Approval recommended

The configuration, handler retargeting, and added tests are consistent and verify the intended start-block behavior for the upgraded event ranges.

Pull request overview

This PR updates the indexer configuration and event handlers to start indexing newly introduced events (PDPVerifier v3.5.0 and FWSS v1.4.0) from their respective upgrade blocks, while keeping the proxy addresses unchanged.

Changes:

• Added per-network “upgrade block” constants for PDPVerifier v3.5.0 and FWSS v1.4.0.
• Split Ponder contract entries (same address, later startBlock) and retargeted the relevant event handlers to those new entries.
• Added a test to assert the upgrade entries share the parent address and start after the parent (and in the expected order).

File summaries

File	Description
indexer/ponder.config.ts	Adds PDPVerifierV35 and FWSSV14 contract entries that start at upgrade blocks while sharing the parent addresses.
indexer/src/networks.ts	Introduces PDP_VERIFIER_V3_5_BLOCK and FWSS_V1_4_BLOCK in the network type and per-network constants.
indexer/src/pdp-verifier.ts	Retargets v3.5.0-only events (PiecesAddedV2, PiecesScheduledForRemoval) to PDPVerifierV35.
indexer/src/fwss.ts	Retargets the v1.4.0-only event (DataSetAuthorizerSet) to FWSSV14.
indexer/test/networks.test.ts	Updates expected network registry objects to include the new upgrade block constants.
indexer/test/upgrade-entries.test.ts	Adds coverage ensuring upgrade entries share addresses but start later than their parent entries.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.