Get started

Login

First-run onboarding. Stores KEY and starts the node. The command never prints KEY.

az login talks to a wallet, lists Azimuth points for that address, then rederives or sets networking keys. A master ticket or a key from a running ship stores the same key.

Wallet

az login

Connect a web3 wallet. Default is Frame on localhost. Pass --browser for a browser wallet like MetaMask or Rabby.
Pick a ~name you own. --point skips the picker. --address when the wallet returns more than one account.
Keys:
- Never set — writes networking keys on-chain (L1 Ecliptic / L2 roller). No extra prompt.
- Match — Bridge-style keys rederive from the wallet. No chain write.
- Miss — Prompts for a reset. Reset increments life. --yes skips the confirm. Decline the reset, or --output json (no prompt): az bind POINT KEY to import.
Node starts. --no-start stores KEY only.

--reset sets new keys even if rederive might work.

Master ticket

az login --ticket

az login --point ~sampel-palnet --ticket-file ./ticket.txt

Use --ticket or --ticket-file. The prompt asks for the point, the master ticket, and a BIP39 passphrase. Leave the passphrase empty when there is none. --point skips the point prompt. --output json needs --point.

The ticket rebuilds the Bridge networking keys already on the point, stores the magicsock key, and starts the node. The ticket is not stored. Unset keys stop before the ticket prompt and store nothing. A mismatch stores nothing. A key already in the keyring stays. --dry-run writes nothing. --no-start stores the key and prints az bind ~sampel-palnet to start.

Key from a running ship

In the dojo:

.^(@uw %j /=vile=)

Copy the printed 0w into:

az bind ~sampel-palnet KEY

az bind ~sampel-palnet --key-file ./key.txt

The paste matches the on-chain keys. A 32-byte hex key is stored as given. --dry-run checks a paste and writes nothing. Replacing a key already stored uses --force.

In az

Run az with no command. On the Nodes tab, a adds a point: f Frame, b a browser wallet, t a master ticket, k a key from a running ship.

Up and down

az up connects a node you already configured. az down disconnects it and leaves the daemon running. az start and az stop start and stop the daemon. Install registers it.