Hi,@amin,
Thank you for the clarification! That explains the discrepancy perfectly: Total Stake (Dashboard) = GSE Total Supply + Stake in Queue/Transit + Other.
To make our explorer accurate and aligned with the official dashboard, I have a few follow-up technical questions regarding the “Queue” and “Other” sequencers:
1. Tracking the “Queue” On-Chain
Since the GSE totalSupply() only reflects activated stake, what is the recommended way to track the “in-transit” stake?
-
Which contract/function should I query to see the current queue of sequencers waiting for activation?
-
Are there specific events that I should listen to for “Pending” stake that hasn’t hit the GSE yet?
2. Comprehensive Indexing of “Other”
Since sequencer registration is permissionless and “Other” won’t be normalized into providers, I need to ensure my explorer doesn’t miss them.
-
If a sequencer registers directly (bypassing the standard provider logic), they won’t trigger a
StakedWithProviderevent in theStakingRegistry. -
Which “canonical” event should I use as the primary trigger to catch every registration, regardless of whether it’s through a provider or a self-stake?
3. Calculating the Delta
To match the 889.8m figure exactly, should I be looking for a specific state variable in the contracts that tracks “Total Committed Stake,” or is the dashboard manually aggregating InitialDeposit events minus Exited events?
This detail is vital for us to build a reliable “Source of Truth” for the community via our explorer. Thanks again for your help!