Revert "fix: temporarily show unbonding locks the subgraph has not indexed"

[rickstaa]

Reverts #748 when subgraph is done indexing (see livepeer/subgraph#247)).

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
explorer-arbitrum-one	Ready	Preview, Comment	Jul 21, 2026 7:38pm

[coderabbitai]

Warning

Review limit reached

@rickstaa, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 56c0accb-239c-49e2-9d2c-2d773e6d3246

📥 Commits

Reviewing files that changed from the base of the PR and between 081de4b and 3ec201a.

📒 Files selected for processing (4)

• components/StakeTransactions/index.tsx
• hooks/useSwr.tsx
• lib/api/types/get-unbonding-locks.ts
• pages/api/unbonding-locks/[address].tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch revert-748-fix/withdraw-without-subgraph

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Reverts the temporary “subgraph degraded” stopgap that fetched missing unbonding locks from chain via a custom API route, now that the subgraph has resumed indexing.

Changes:

• Removes the /api/unbonding-locks/[address] API route and its associated UnbondingLocks response type.
• Removes the useUnbondingLocksData SWR hook that called the removed API route.
• Simplifies StakeTransactions to rely solely on subgraph-provided delegator.unbondingLocks and the passed-in currentRound.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
pages/api/unbonding-locks/[address].tsx	Deletes the temporary API route that read unbonding locks directly from the chain.
lib/api/types/get-unbonding-locks.ts	Deletes the now-unused API response type for the removed route.
hooks/useSwr.tsx	Removes the SWR hook and type import that depended on the removed API route/type.
components/StakeTransactions/index.tsx	Removes degraded-subgraph merge logic and restores simple pending/completed lock filtering using currentRound.id.

---

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

[rickstaa]

Reverting as the new subgraph has been indexed.