Repository navigation
feat: index user rebate staking for explorer - #24
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explorer currently reads rebate staking and deposit fee waivers from the deprecated custom indexer, whose public endpoint is unavailable. The existing tBTC subgraph has operator staking but lacks the user RebateStaking entities needed to replace those reads.
Adds
RebateStaker,RebateStakingEvent, andRebateStakingStats, indexing the mainnet proxy from its actual deployment block (23,598,704). Stake remains in the balance while unstaking is pending; repeated requests replace the pending amount; transfers move the balance and pending request and record both participants. Rebate totals retain the previous API's lifetime award semantics, in satoshis, with cancellations recorded separately. Existing entities and consumers remain compatible.Consumer migration: tlabs-xyz/threshold-dapp#453, held in draft until the public proxy cutover.
Adds Matchstick regression tests to the reusable mainnet CI/deployment check and documents the coordinated Explorer cutover. Sepolia remains compile-only with the source disabled because no deployment is known.
Validation: Node 22.22.0; codegen; mainnet and Sepolia builds; all 5 mapping tests; all 58 existing cutover/toolchain tests passed locally.
Release order: deploy, fully sync, and publish this subgraph; update threshold-api's production
SUBGRAPH_GATEWAY_URL_MAINNETto the verified deployment-pinned gateway; verify the schema, deployment, chain head, and representative balances through the public proxy; then release the dependent Explorer frontend. Preserve the current published deployment throughout re-sync. Creating or merging this PR does not perform that cutover. The custom indexer stays deprecated.