Internals

Keys

Networking keys for an Azimuth point. The on-chain values are two public keys: encryption (CryptKey, curve25519) and authentication (ed25519). Bridge calls them network keys. Commands never print KEY.

Rederive

Rederives the private keys Bridge set, then checks them against the on-chain public key. Does not write to Azimuth. Fail closed if neither derivation matches.

SIWE with Frame (or --browser), then Bridge-style derivation. If that misses on-chain keys, one extra personal_sign of “Bridge Authentication Token” (MetaMask / Bridge-set keys).

Set

Same as Bridge “Set network keys.” Derives the next-revision network keys, then configureKeys (L1 Ecliptic / L2 roller). Stores KEY in the keyring after a successful receipt (L1) or roller pending (L2).

--discontinuous increments continuity (rift). --yes skips the confirm.

Life and rift

Azimuth stores two counters on the point:

• Life (keyRevisionNumber) — how many times the networking keys have actually changed. Unset is 0. First write is 1. A no-op set does not increment.
• Rift (continuityNumber) — how many times continuity has been broken. Starts at 0. --discontinuous increments it.

Login on a miss confirms reset. Reset increments life. Matching keys rederive with no chain write. Never-set keys write with no extra confirm.

Import

If you decline the reset, import with az bind POINT KEY. The same command accepts a dojo 0w from a running ship. Login. --output json cannot prompt; pass --yes to reset, or import.