Phase 1 specification and invariants #24

Closed
opened 2026-01-31 17:05:35 +01:00 by erikinkinen · 0 comments
Owner

Goal
Formally define Phase 1 assumptions and success criteria before implementing revocation logic.

Steps

  • Write docs/phase1.md describing full-knowledge assumptions
  • Define revocation correctness (soundness, completeness)
  • Define revocation cost counters
  • Define what does not count as revocation failure in Phase 1
**Goal** Formally define Phase 1 assumptions and success criteria before implementing revocation logic. **Steps** * [ ] Write `docs/phase1.md` describing full-knowledge assumptions * [ ] Define revocation correctness (soundness, completeness) * [ ] Define revocation cost counters * [ ] Define what *does not* count as revocation failure in Phase 1
erikinkinen added this to the Phase 1 milestone 2026-01-31 17:05:35 +01:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
erikinkinen/AES#24
No description provided.