fix: fall back to latest stake when L2 block lookup reverts

[rickstaa]

Summary

• When getL2BlockRangeForL1 reverts for an L1 block (no corresponding Arbitrum batches), the returned lastBlock: 0 was passed to getTotalStake(0), querying the subgraph at block 0 and producing near-zero total stake — potentially causing incorrect poll status (e.g. marking polls as passed when they should be quorum-not-met)
• Now falls back to querying latest total stake when the L2 block lookup fails, which is a much more reasonable approximation
• Downgrades noisy console.error (with full RPC error dump) to a clean console.warn

Test plan

• Load the voting page and confirm the L2 block revert no longer dumps a full error stack
• Verify finished polls still display correct status and vote percentages
• Confirm active polls are unaffected (they already used latest stake)

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
explorer-arbitrum-one	Ready	Preview, Comment	Mar 18, 2026 8:36am

[Copilot]

Pull request overview

This PR improves poll stake calculation robustness by falling back to querying the latest total stake when the L1→L2 block-range lookup fails, avoiding incorrect outcomes for finished polls when the Arbitrum NodeInterface call reverts.

Changes:

• Refactors getPollExtended to compute an optional l2BlockNumber and pass undefined to getTotalStake when an L2 end block can’t be resolved.
• Downgrades the L2 block-range lookup failure log from console.error to a cleaner console.warn.

Comments suppressed due to low confidence (1)

lib/api/polls.ts:220

• Using lastBlock: 0 as the failure sentinel is ambiguous because block 0 is a valid L2 block height. Returning undefined/null (or an ok flag) on failure would make the API unambiguous and avoid relying on lastBlock > 0 checks at call sites.

    return {
      lastBlock: 0,
      firstBlock: 0,
    };

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.