Rezva

Identifier registry

The registry owns protocol mappings, controller references, lifecycle state, payment destinations, and auditable events.

Registry lifecycle

availability → register → pending → active
                           ↓
                  update_pending → active
                           ↓
                 removed → cooldown → available
  1. Check availability for the exact typed value.
  2. Register with controller authorization and payment options.
  3. Activate after the configured safety period.
  4. Update metadata or destinations through authorized mutations.
  5. Remove, suspend, revoke, or reclaim only through the permitted workflow.

Uniqueness

Uniqueness is evaluated on the normalized value within its identifier type. Similar-looking values are not automatically conflicts, while an exact normalized match cannot be registered twice.

External crypto names are resolved by their authoritative systems; raw blockchain addresses are destinations, not registry identifiers.

Use Register an identifier for the request sequence and Statuses before allowing a payment.