RE423 make-good
Were you affected by RE423?
Paste your address below to see whether you're on the list, exactly how the amount was worked out, and — once paid — the transaction that paid you. Either address works: the C-chain address the payment goes to, or the P-chain address you actually staked or delegated from — we'll tell you which one matched.
This lookup currently covers Flare only.
Full incident, compensation, and Songbird details
On 2026-08-10, our registration transaction for reward epoch 423 (RE423) failed to land in time. That meant our FTSO/staking rewards for that one ~3.5-day epoch were forfeited — and because rewards to our delegators and stakers flow through us, so was the portion that would have gone to you. The node itself kept running and validating throughout, and no delegated or staked funds were ever at risk — what was forfeited was that epoch's reward stream, including the share that would have flowed to you.
We're compensating every affected address at the reviewed estimate, in full, as a one-off. Payouts are going out smallest-first in phases as we fund each batch — so a small balance below isn't a lower priority, it's usually paid sooner.
One caveat on completeness: about 0.09% of delegated vote power couldn't be matched to any address in this ledger, so if you delegated to us at RE423 and don't see yourself below, that's not proof you aren't owed — message @africanproofs on X and we'll check the chain directly.
The same registration miss also affected our Songbird delegators, and they are owed compensation too — that ledger is finalised but not yet loaded here, so a Songbird address will show as “not owed” even though it is. If you delegated to us on Songbird, nothing is required from you; we'll add Songbird to this page before those payouts go out.