Read the wire before you sign.

A swap starts as a request: two mints, an amount in base units, a slippage window, and a cluster. A ticker is a label. Two tokens can share one, so Light Wire asks for the mint.

What comes back is an estimate with an expiry. It can move before you sign, and it can fail the price check after you do. A missing route is an error, not a zero we painted in to keep the screen calm.

Connecting a wallet is permission to ask for a signature. It is not permission to hold the coins. The unsigned transaction is built for your wallet to sign on your machine.

Light Wire does not ask for a seed phrase, does not store a private key, and does not sign on the server. Public pages stay readable before any wallet is connected.

A submitted signature means the network accepted a message. Confirmed, failed, expired, and unknown are different states. Confirmed means the cluster accepted the transaction.

The screen marks the swap finished when that confirmation arrives.

Token-2022 can store a Transfer Hook on a mint. When that extension is set, the token program calls another program as the token moves. That program may demand extra accounts a plain transfer does not.

Light Wire reads whether the mint is SPL Token or Token-2022, whether a hook is configured, and which program id is named. That read is the account at that moment. A safety review is a separate job.

Devnet is the working network. Mainnet writes stay off. Better features are on the way, and no date is promised. The lock is code.

Fee collection is off. A name and an image beside a mint are labels. They do not make the token safe, and they do not replace the address.