Issues

persist v50: blob_swarm/revocation.rs re-derives stored withdraws through the WRITE-form check (5-hop default) — use check_withdraws_admission_as_admitted

#703

· emooreatx opened

on Sep 27, 2026

v33.0.0 adopt checklist — persist v50.0.0

#702

· emooreatx opened

on Sep 27, 2026

persist v50.0.0: DIRECTORY_ABI_VERSION 5→6 — ReachabilityVerdict gains beyond_depth_cap (CC 4.1.1 5-hop default); map it, don't book it as substrate_fault

#701

· emooreatx opened

on Sep 27, 2026

files: a file row's name and media type travel in cleartext in the signed envelope

#698

· emooreatx opened

on Sep 27, 2026

MLS state at rest on a TPM-less host must land on disk under the software-sealed seed, not in memory (#676 follow-up)

#694

· emooreatx opened

on Sep 26, 2026

First contact on the opaque plane: an unpeered device's request is dropped as UnknownKey, so a new phone cannot ask its owner's device to approve it (CIRISServer#678)

#683

· emooreatx opened

on Sep 25, 2026

Gate a node's own IdentityOccurrence/TransportDestination serve on its announce state — an unannounced device's row reaches every peer today

#682

· emooreatx opened

on Sep 25, 2026

Structural refusals never converge: senders re-offer rows whose attester the peer can't admit — refuse-with-reason, back off, and gate on the Key plane

#679

· emooreatx opened

on Sep 25, 2026

Per-plane cohort selectors: one CohortProvider drives Key, IdentityOccurrence and TransportDestination, so a host can't honour per-flow consent on relays

#678

· emooreatx opened

on Sep 25, 2026

heads-up: adopting CIRISVerify v17.0.0 makes edge's Ed25519 verification strict (edge is already DRY — no action beyond the adopt)

#677

· emooreatx opened

on Sep 25, 2026

Attribution requires Rooted, no production agent can root, and the self-attribution hole that hid it is closed: the trace plane has been dark since 2026-09-18

#659

· emooreatx opened

on Sep 23, 2026

CC 5.4 scope-native privacy WIRE profile (record_id + RaptorQ symbol envelopes + fixed-size cover framing) is not on any content path — chunks ride sha-addressed; FSD then implement

#651

· emooreatx opened

on Sep 22, 2026

Navigation Menu

All issues

persist v50: blob_swarm/revocation.rs re-derives stored withdraws through the WRITE-form check (5-hop default) — use check_withdraws_admission_as_admitted

v33.0.0 adopt checklist — persist v50.0.0

persist v50.0.0: DIRECTORY_ABI_VERSION 5→6 — ReachabilityVerdict gains beyond_depth_cap (CC 4.1.1 5-hop default); map it, don't book it as substrate_fault

files: a file row's name and media type travel in cleartext in the signed envelope

MLS state at rest on a TPM-less host must land on disk under the software-sealed seed, not in memory (#676 follow-up)

First contact on the opaque plane: an unpeered device's request is dropped as UnknownKey, so a new phone cannot ask its owner's device to approve it (CIRISServer#678)

Gate a node's own IdentityOccurrence/TransportDestination serve on its announce state — an unannounced device's row reaches every peer today

Structural refusals never converge: senders re-offer rows whose attester the peer can't admit — refuse-with-reason, back off, and gate on the Key plane

Per-plane cohort selectors: one CohortProvider drives Key, IdentityOccurrence and TransportDestination, so a host can't honour per-flow consent on relays

heads-up: adopting CIRISVerify v17.0.0 makes edge's Ed25519 verification strict (edge is already DRY — no action beyond the adopt)

Attribution requires Rooted, no production agent can root, and the self-attribution hole that hid it is closed: the trace plane has been dark since 2026-09-18

CC 5.4 scope-native privacy WIRE profile (record_id + RaptorQ symbol envelopes + fixed-size cover framing) is not on any content path — chunks ride sha-addressed; FSD then implement

Search results