Search
What can I do on the public page?
You can search for a tracked IOTA address, open its public reward history, and submit a new address for qualification.
Qualification, background imports, validator-specific tracking, reward valuation, labels, and public visibility.
You can search for a tracked IOTA address, open its public reward history, and submit a new address for qualification.
Stakebook accepts valid IOTA addresses and resolvable IOTA Names ending in .iota. Names are resolved live to their current target address and are not stored as labels because name ownership and records can change.
Qualification and history backfill can take time. The public flow therefore returns immediately and lets the system continue in the background.
The recent lookback avoids unnecessary expensive full-history scans for random addresses. Stakebook first checks whether the address is currently staked or had recent staking activity within the last 30 days.
If the address qualifies, Stakebook does not stop at the lookback window. It queues the available staking history as far back as it can determine for that address.
A snapshot is Stakebook's epoch-level record for one tracked address. It stores the relevant staking state for that epoch, including rewards, delegated stake, epoch timing, and the price reference used for exports. One address can therefore have many snapshots, normally one per covered epoch.
For validator-mode addresses, Stakebook can show a reward breakdown. Commission reflects newly received validator commission stake for that epoch, while Own stake reflects the validator's own staking rewards for that same epoch.
Requests can be pending, processing, accepted, rejected, or failed. Accepted requests become tracked addresses. Rejected requests did not pass the qualification gate at that time.
No. Public users cannot assign labels, because open labeling quickly creates noisy data. Labels can only be managed manually by an admin.
Yes. Public address pages can report an existing snapshot for verification. Reports go into an in-memory low-priority queue and are only rechecked when regular reward and validator jobs are idle.
Yes. Public address pages provide CSV and PDF exports for the tracked activity ledger. You can export the full history or limit the download to a specific year or date range.
No. Public pages stay focused on available data. Missing epochs simply remain empty until data exists or another lookup succeeds. Internal failure details are for the admin area only.
Reward snapshots use a fiat price reference derived from the epoch end time. Price lookups are cached by reference timestamp so the same epoch price can be reused across many rewards.
Submission only places the address into the qualification flow. Depending on queue depth, qualification, network lookups, validator detection, and reward backfill, public snapshots may appear some time later.
Yes. If an address was previously rejected because it had no recent staking activity, it can be submitted again later when its status has changed.