From persist v50.0.0 (CIRISPersist#928 / #925 review). src/blob_swarm/revocation.rs:506 re-derives already-stored withdraws at READ time through check_withdraws_admission, the WRITE gate, which now walks CC 4.1.1's 5-hop default. A withdraws validly admitted through a 6–16-hop chain (pre-v50, or under an explicit opt-in) would then read as not admitted and the blob would un-retire — the retroactive change persist ruled out.
Persist v50 records each withdraws row's admitting depth (migration V157; pre-V157 rows read as 16) and exports check_withdraws_admission_as_admitted(dir, row), re-deriving at the ROW's depth; the capsule forwards withdraws_admission_depth (an appended op). Ask: switch that read-time call (and any sibling) to the helper. Part of the v33 checklist (CIRISEdge#702).
From persist v50.0.0 (CIRISPersist#928 / #925 review).
src/blob_swarm/revocation.rs:506re-derives already-stored withdraws at READ time throughcheck_withdraws_admission, the WRITE gate, which now walks CC 4.1.1's 5-hop default. A withdraws validly admitted through a 6–16-hop chain (pre-v50, or under an explicit opt-in) would then read as not admitted and the blob would un-retire — the retroactive change persist ruled out.Persist v50 records each withdraws row's admitting depth (migration V157; pre-V157 rows read as 16) and exports
check_withdraws_admission_as_admitted(dir, row), re-deriving at the ROW's depth; the capsule forwardswithdraws_admission_depth(an appended op). Ask: switch that read-time call (and any sibling) to the helper. Part of the v33 checklist (CIRISEdge#702).