[Identity Track: Testnet v0.2](TBD: anoncomms-pm milestone)
Track: Identity Track
FURPS: Identity FURPS
Estimated date of completion: 30 Jun 2026
Resources Required:
- 1 AnonComms researcher for spec review and cross-team coordination
- Messaging Chat team ownership of libchat-side deliverables (see below)
This milestone consolidates in-flight identity work into a tracked AnonComms protocol concern, establishes the cross-team specification scaffolding, locks in a future-proofed VLAD-compatible address format, and validates the LEZ-as-Registry approach via a spike.
Deliverables
[Specify basic λAccount protocol](TBD: anoncomms-pm issue)
Owner: Messaging Chat (primary), AnonComms Identity (review)
FURPS:
- U1. The basic identity protocol (accounts, address format, operation log, contact discovery flow) is published in a specification.
Checklist:
- Specs: link to specs and/or API definition
[Spike: LEZ-as-Registry feasibility](TBD: anoncomms-pm issue)
Owner: Messaging Chat
FURPS:
- P1. A registry lookup of an account’s current state completes within a bounded time under typical network conditions.
Checklist:
- Docs: links to README.md or other docs
[Implement key-based identity](TBD: anoncomms-pm issue)
Owner: Messaging Chat
FURPS:
- F1. An account is bound to at least one cryptographic key whose private part is controlled by the holder.
Checklist:
- Code: link to GitHub issues/PRs/Epic
- Dogfood: link to dogfooding session/artefact
- Docs: links to README.md or other docs