Accounts, connections and signing
Keep four capabilities separate
| Capability | Meaning | Does not mean |
|---|---|---|
| Application login | An application user session exists | Private keys are available or every wallet is recoverable |
| Wallet connection | The user exposes a selected account and network | Arbitrary signatures or automatic payments are authorized |
| Private-state access | The application has scoped decryption or recovery material | Pure read-only access; complete Note material can carry financial capabilities |
| Transaction signing | The user authorizes a particular transaction or terms | Other sites, accounts or future payments are authorized |
Design application-login recovery separately from wallet recovery. A cloud record containing an address or account label does not prove that the device can sign for it. Watch-only accounts can query public information but cannot perform financial actions without control of the required keys.
Isolate DApp sessions by site
Connection confirmation should identify the site origin, requested account and network. Bind a session to at least a trusted origin and the selected account. Changing an account on one site must not silently grant another site access to a different account.
- Disconnecting revokes the connection session and further automatic access; it does not revoke on-chain token allowances.
- Re-evaluate outstanding requests, balances and recipients when accounts or networks change.
- Block before signing if the source, network or unlocked account does not match.
- Cancellation and rejected signatures must not create successful-payment records.
Show the actual authorization
Distinguish message signing, structured authorization, token allowance and asset transfer. Display the site, network, account, contract or recipient, amount and fees. Combining steps into one business action must not obscure these different permissions.
The signing payload's chain ID, target and amount must match confirmation. Rebuild and revalidate terms after changes to the amount, recipient, input Notes or submission route; do not reuse stale confirmation. Keep private keys and proof witnesses out of browser logs and support tickets.
Recovery and removal
Disconnecting a site, logging out, resetting a device, removing a wallet and revoking on-chain authorization are different actions. Explain which local capabilities are removed and which on-chain states remain. Restore against the original account and deployment rather than merging another account's inventory.
Read DApp discovery and connections, security and trust boundaries and session recovery.