| Claim | Due by | Outcome | Evidence | Scored in |
|---|
| Gate re-enables XRD deposits, which have been off since the 31 August halt. | 2026-10-11 | Miss | Miss. Read at 11:15 UTC on 11 October 2026, the due date, https://api.gateio.ws/api/v4/spot/currencies/XRD returns delisted false, trade_disabled false, withdraw_disabled false and deposit_disabled true, with deposit_disabled true on both the XRD chain and the ETH chain. Deposits stayed off for the whole three weeks the claim ran, and Gate published no notice about them. | Radix Week in Review, 11 October 2026 |
| RadixTalk’s fee rises from 1.5% to 50% at epoch 348,297, as its queued request says. | 2026-10-18 | Hit | Hit. Read with no at_ledger_state at 11:15 UTC on 11 October 2026, POST /state/validators/list answers HTTP 200 at epoch 348,533, state version 562,414,332, and validator_rdx1s0qzv2vmxydpnglk36mczrdwczpsskuzek2cs5nnld6j533rzatmln reads effective_fee_factor.current 0.5 with no pending entry, on 67,299,055 XRD. The radixscan MCP reproduces it at epoch 348,533, state version 562,414,340: fee_percentage 50, raw_fee_percentage 1.5, registered, accepting delegated stake. The stored factor still reads 0.015. The settling epoch 348,297 passed around 15:00 UTC on 10 October, inside the due date. Stake fell from 73,007,050 XRD at the 4 October reading to 67,299,055. | Radix Week in Review, 11 October 2026 |
| All four fee increases queued in one transaction on 23 September take effect as queued: Radstakes 25% to 40%, RadixStake 14.9% to 29.89%, Sirius and Polaris 0% to 25%. | 2026-10-11 | Hit | Hit, two days before the due date. Read with no at_ledger_state at 19:05 UTC on 9 October 2026, POST /state/validators/list answers HTTP 200 at epoch 348,051, state version 561,990,122, and all four read effective_fee_factor.current at their queued value: Radstakes 0.4 on 93,474,561 XRD, RadixStake 0.2989 on 108,074,174 XRD, Sirius 0.25 on 106,801,938 XRD and Polaris 0.25 on 74,558,790 XRD. None was withdrawn. The settling epoch 347,421 passed on 7 October. Sirius and Polaris now each carry a further pending fee_factor of 0.5, effective at epoch 352,012. | Wiki maintenance sweep, 9 October 2026 |
| Radix Charts V2’s fee rises from 2.5% to 15% at epoch 345,107, as its queued request says. | 2026-10-04 | Hit | Hit. Read with no at_ledger_state at 11:15 UTC on 4 October 2026, POST /state/validators/list answers HTTP 200 at epoch 346,517, state version 561,023,490, and validator_rdx1svxx0jetjwnptndj60sm8h7ljs0v88fl6xhwcyp6ar397agwd0ezaz reads effective_fee_factor.current 0.15 with no pending entry, on 23,619,794 XRD. The radixscan MCP reproduces it at epoch 346,517, state version 561,023,460: fee_percentage 15, raw_fee_percentage 2.5. The settling epoch 345,107 passed around 15:00 UTC on 29 September, inside the due date. | Radix Week in Review, 4 October 2026 |
| GP-PRE-1, the proposal ratifying the Radix DAO Charter and Governance Framework, closes with its quorum and 66% approval both met. | 2026-10-04 | Hit | Hit. GP-PRE-1 closed at 15:18 UTC on 2 October 2026. Read 4 October 2026, the result endpoint https://vote.radixdao.org/vote-results?type=proposal&entityId=0 returns one option only, Approve, with 1,857,159,221.57 XRD of vote power, above the 1,350.83M quorum, and no Reject or Abstain, so approval is 100% against the 66% bar. A wiki sweep counted 193 accounts from /account-votes. The Radix Accountability Council announced the same figures that evening at t.me/RadixAccountabilityCouncil/1126: 1,857.16M in votes, 100% approval, Charter and Policies in effect. radixdao.org/govern had not been updated on 4 October and still read that nothing there is in force; that bears on 2026-09-20-dao-first-document-retry, not on this claim. | Radix Week in Review, 4 October 2026 |
| CaviarNine's two validators, unmentioned in its departure announcement, are deregistered, sold, or have a fee change filed against them. | 2026-10-04 | Hit | Hit, a week before the due date. Transaction txid_rdx1ksxuuge5ca3qc7ghuermxzrey07yz2tjhyffwx4yzfge3ulpg74sm2t92u, committed at 14:35:35 UTC on 23 September 2026 in epoch 343,389, calls update_fee Decimal("0.25") on both validators, which had been renamed Sirius (CaviarNine-1) and Polaris (CaviarNine-2) between 17 and 19 September. Read with no at_ledger_state at epoch 344,501, state version 560,016,610 on 27 September, both read effective_fee_factor.current 0 with effective_fee_factor.pending 0.25 at epoch 347,421, on 106,110,000 and 111,460,000 XRD; radixscan returns the same transaction. Both remain registered. The same transaction also queued increases on Radstakes and RadixStake. | Radix Week in Review, 27 September 2026 |
| Daffy (Supreme)’s fee rises from 5% to 20% at epoch 344,149, as its queued request says. | 2026-09-27 | Hit | Hit. Read with no at_ledger_state at 11:14 UTC on 27 September 2026, POST /state/validators/list answers HTTP 200 at epoch 344,501, state version 560,016,610, and validator_rdx1svug50cdlalm6plazajrmntf209j5azf57xeukuhx2hw7e7ut5mmz8 reads effective_fee_factor.current 0.2 on 51,594,800 XRD with no pending entry. The radixscan MCP reproduces it at epoch 344,501, state version 560,016,640: fee_percentage 20, raw_fee_percentage 5. The stored factor still reads 0.05, which is the engine declining to rewrite the substate. The settling epoch 344,149 passed around 06:00 UTC on 26 September, inside the due date. | Radix Week in Review, 27 September 2026 |
| The Radix Accountability Council publishes its report on the 31 August exploit and the restart. | 2026-09-27 | Hit | Hit, with the authorship noted. The written account came from the Radix Foundation rather than the council: Public Incident Report RDX-INC-2026-0831, published on the Radix blog on 17 September 2026, which describes the vault-authorisation defect, its origin in a June 2023 code change, the response timeline and the Eagle Ray fix. The council posted it to its own channel the same day at 15:59 UTC, t.me/RadixAccountabilityCouncil/1037, as the post mortem it had asked for time to coordinate on 11 September. The check asked for a written account describing the defect and the fix posted to the council channel, and that is met. | Radix Week in Review, 27 September 2026 |
| At least one of the Radix DAO's 24 governance documents moves from pending to in force, with its SHA-256 digest recorded on the ledger. | 2026-09-20 | Miss | Miss. Read 20 September 2026, radixdao.org/govern lists 26 rule-bearing documents, 25 of them reading "Signed · awaiting ratification" with a published SHA-256 digest and the Roles Registry pending, every digest recorded in ratification proposal GP-PRE-1. The page states in its own words that "Nothing here is in force yet", and its header adds that the ratification vote is pending and community decisions are advisory until activation. No document reads as active and no digest is recorded on the ledger, so neither half of the claim is met. The Radix Accountability Council said on 17 September, at t.me/RadixAccountabilityCouncil/1037, that the discussion phase of the framework ratification ends on 18 September and the process moves to the next phase, so the vote that would settle this had not been held when the claim fell due. Five readings over 33 days (18 August, twice on 30 August, 5 September, 20 September) found the same status. | Radix Week in Review, 20 September 2026 |
| Leaf Node’s fee rises from 1% to 100% at epoch 341,223, as its queued request says. | 2026-09-17 | Hit | Hit. Read with no at_ledger_state at 11:06 UTC on 20 September 2026, POST /state/validators/list answers HTTP 200 at epoch 342,483, state version 558,981,649, and validator_rdx1swzn5hvtut6yq0zxqqsa0wk4rnkfd8wewvnphzrckau22pun2lv86t reads effective_fee_factor.current 1 on 25,589,948.845796907639273623 XRD, with no effective_fee_factor.pending and no validator_fee_change_request. The radixscan MCP reproduces it a minute later at epoch 342,483, state version 558,981,677: fee_percentage 100, raw_fee_percentage 1, registered, accepting delegated stake, uptime 99.95%. The stored factor still reads 0.01, which is the engine declining to rewrite the substate and the reason this check named the effective fee. The settling epoch 341,223 passed around 02:00 UTC on 16 September, inside the due date; this read is four days later and no intervening change request exists, so the fee has read 1 since it landed. | Radix Week in Review, 20 September 2026 |
| hyperscale-vm records at least 200 commits in the fortnight from 31 August to 13 September 2026. | 2026-09-14 | Miss | Miss, and the first on this ledger. Read at 07:12 UTC on 14 September 2026, GET /repos/hyperscalers/hyperscale-vm/commits with since=2026-08-31T00:00:00Z and until=2026-09-14T00:00:00Z returns 155 commits on main, all by flightofthefox and none of them merges, against a hit condition of 200. The first scoring read, at 03:06 UTC, returned 109 and said no held-back work could still land inside the window. That was wrong for the reason this entry's check already records: a commit listing dates the commit, not the push. Two pushes to main after the window closed, at 05:15 and 06:45 UTC on 14 September, carried 46 commits dated inside it, 8 more on 11 September and 16 and 22 on 12 and 13 September, the newest d69b4746 at 23:55 UTC on 13 September. By author date the fortnight now runs 6 commits on 31 August, then 13, 8, 9, 2 and 2 to 5 September, none on 6 September, then 10, 8, 11, 10, 38, 16 and 22 to 13 September. The seven days before the window held 338. The count is 45 short of the line, and a later push of older work could still move it. | Wiki maintenance sweep, 14 September 2026 |
| Radix mainnet commits a round again, ending the halt that began on 31 August 2026. | 2026-09-20 | Hit | Hit on 11 September 2026, nine days before the due date. Gateway /stream/transactions shows state version 557,840,627 committed at 21:19:48.939 UTC on 31 August and the next, 557,840,628, at 11:35:28.96 UTC on 11 September, in epoch 339,897; Eagle Ray enacted at the start of epoch 339,898 and the first user transactions committed at 11:39:25 UTC. Read with no at_ledger_state at 11:04 UTC on 13 September 2026, POST /state/validators/list answers HTTP 200 at epoch 340,467, state version 558,030,223, above the 339,896 the check names. A wiki sweep scored this on 11 September in the page blocks but not in this state, so the index would have reverted it on the next sync. | Radix Week in Review, 13 September 2026 |
| A babylon-node release carrying the Eagle Ray protocol update is published. | 2026-09-20 | Hit | Hit on 8 September 2026, two days before it was scored, and the delay is this ledger’s own fault rather than the release’s. Read at 03:07 UTC on 10 September 2026, GET /repos/radixdlt/babylon-node/releases returns v1.4.0.0-RC1, named Eagle Ray v1.4.0.0-RC1, published 2026-09-08T15:35:42Z from merge commit 7400951e with seven assets attached. That is a tag above v1.3.0.5 whose notes name Eagle Ray, which is the hit condition as recorded on 6 September. The release is flagged pre-release, so GitHub’s /releases/latest still resolves to v1.3.0.5-test.1 of 2026-09-08T12:28:06Z and an operator following the documented install path gets the older build; that matters to a node runner and it is not part of the check, which asked whether a release carrying the protocol update exists. It does. | Wiki maintenance sweep, 10 September 2026 |
| StakeSafe's three validators raise their fees as scheduled: Amsterdam and Rotterdam from 15% to 25%, Seed Node from 15% to 100%. | 2026-09-06 | Hit | Hit, and scored on evidence the 30 August note recorded as unreadable. The Gateway refuses an unpinned state read while it is five days behind the network, but the freshness guard is skipped for a read that names a ledger state, and the frozen state is 288 epochs past Amsterdam's settling epoch. Read at 11:02 UTC on 6 September 2026 with at_ledger_state pinned to state version 557,840,622, epoch 339,896, the final state the ledger reached at 21:19:06.179 UTC on 31 August 2026: /state/validators/list returns HTTP 200 with all 287 validators. StakeSafe Amsterdam (validator_rdx1s066xuq885l0mttgmx4ptflte6fepkt0c06mqnqtdgajj4mcwh70q4) reads effective_fee_factor.current 0.25 on 75,671,832 XRD; StakeSafe Rotterdam (validator_rdx1s048k34ctk3m57gumema2e5jmhfxhdryyr5hq42xa9q59pvn8lezg8) 0.25 on 78,235,400 XRD; StakeSafe Seed Node (validator_rdx1svlvyezsxp467pznd2kfnhqpenmw7hpdgnxjgu3s8mzxtruz77d3q3) 1 on 210,603 XRD. All three still store validator_fee_factor 0.15, which is the engine declining to rewrite the substate and the reason the check named effective_fee_factor. Three of three as claimed, effective at epochs 339,608 and 339,609, roughly a day before the network stopped. | Radix Week in Review, 6 September 2026 |
| StakeSafe files a fee change request on the Avaunt Staking validator it bought on 21 August, raising the fee above 2%. | 2026-09-20 | Hit | Hit on 26 August 2026, 25 days before the due date, and the settling transaction is on the ledger: txid_rdx17sfhjgn0j8ymny889992j8aemk3q6vrjs2x97v6xpccrhe35w63snnyd3s at 20:47:04 UTC, epoch 338,450, state version 555,398,021. It proves the Avaunt owner badge [834bcbdc3bf9d9211f827af8b2c84c56cd156a4de412690718c624a2beb0] from account_rdx16xrp5e8faqxfa8j20xh5u29js8umdz7zcu6m0xnjfewkcxkpkdl84f, the same account that holds StakeSafe Amsterdam's owner badge, and calls update_fee Decimal("0.25") on the validator. Confirmed at the register at epoch 339,438 on 30 August 2026 07:06 UTC: effective_fee_factor.current 0.02 with pending 0.25 effective at epoch 342,482, on 142,194,735 XRD. The claim asked only for the request to be filed, so it settles now; whether 25% is actually charged is a separate question that the epoch answers around 9 September. | Wiki maintenance sweep, 30 August 2026 |