Asp

Staking Requests

loading…
#TypeAccountAmount (ACME)DestinationSubmittedStatusDistributionDetail
This page shows the complete request history of acc://staking.acme/requests, decoded from the locally held chain records — every registration, withdrawal, and note ever written, not just recently captured entries. Executed means the request provably ran: a withdrawal paired with an on-chain token movement, or a registration whose account appears in the staking.acme/registered history. Every open request is judged by the decision tables: valid or not with the reason, and when it executes. A valid withdrawal out of staking is held (yellow) until its release instant — requested in period A, held through A+1, distributed when A+2 opens — and then due (green), work for the signer fleet; a withdrawal into another staking account is due immediately, since the tokens never leave staking. Each signer recomputes the judgment from the chain and its own clock and acts only when the two agree; a disagreement is shown beside the request. Unjudged means an input the tables need is not yet in the database. A withdraw request expires 4 weeks after submission — an expired request has failed and must be resubmitted. Undetermined means the classification depends on data before 2025-07-13 (the chain genesis reset), which is not necessarily accessible. Informational entries are not actionable requests: delegate announcements, payout-change notes, unparseable data. Click any row for the full record and its validity findings; invalid marks a request failing at least one check against local chain data. Invalid requests are hidden by default — use All requests or Invalid only to see them.