Zero recorded defaults is a gap in the record, not a clean bill of health.

Zero recorded defaultsand that is not the same as nothing failing. 2,324 of 2,415 redemptions recorded a settlement, and none recorded a default — but a default only appears on chain when somebody calls for it. 91 obligations are past their deadline with nothing recorded either way. See §2.2.

Why the executor number decides everything: redemptionPaymentDefault is permissioned — only the redeemer, the agent, or the executor appointed at redeem() time may call it. An unaffiliated relay cannot claim a stranger's default however good its proof. At 85.92%, naming an executor is already the norm, so the role does not need to be invented, only served better.

We asked. They paid.Every one of these was put to the Flare Data Connector: did the agent make this payment? The verifier found the payment on XRPL in all 91 cases and refused to attest absence (INVALID: REFERENCED TRANSACTION EXISTS). There are no defaults here. The agents paid and never submitted the proof that records RedemptionPerformed on Flare — unresolved bookkeeping, not theft.

A correctionAn earlier run of this tool reported 93 proven defaults, 935 XRP. That was wrong and is retracted. The request asked about valueUBA; the agent pays valueUBA − feeUBA, retaining its fee. A request for an amount nobody ever paid can never match, so the verifier truthfully attested absence for every redemption — settled or not — and produced a clean sweep of false accusations. A clean sweep is not a strong result; it is a symptom. The control that caught it takes redemptions the chain says were settled and requires the verifier to refuse them.

FDC proofs of a missed payment can only be minted for 14 days after the deadline. After that the question is permanently unanswerable — which is why the record's completeness is a running clock and not a backlog anyone can catch up on later.