Start with the command deck
Arbitrum Wallet is arranged around the actions users repeat most often: checking balances, moving assets through trusted routes, opening ecosystem destinations and reviewing recent activity.
- Use the Assets view to confirm the selected account, network and available balances before taking action.
- Keep Bridge, Apps and Activity close together so a route, destination and result can be checked from the same surface.
- Review network, token, amount, recipient and fee details before approving a transaction in a connected signer.
Install and verify
Download the build for your operating system, then compare the published SHA-256 checksum before opening it. Checksums help confirm that the file you received matches the release file that was published.
- Use the macOS, Windows or Linux release link from the download section.
- Open the matching checksum file and compare it with a local SHA-256 hash of the downloaded installer.
- Keep the application updated, especially after network, signer or bridge changes are released.
Networks
The wallet keeps Arbitrum networks explicit so every balance, route and approval has clear context. Always check the active network before signing or moving assets.
- Arbitrum One is the primary rollup network for broad ecosystem activity.
- Arbitrum Nova is useful for high-volume, low-cost flows and apps that support Nova.
- Arbitrum Sepolia is for testing and development, not production funds.
Bridge flows
Bridge actions should keep the source chain, destination chain, token, amount, route and expected status visible before the next step. When an external bridge page opens, compare the domain and route details before connecting a wallet.
- Prefer the official Arbitrum Bridge for standard Ethereum and Arbitrum movement.
- Check withdrawal timing carefully, since exits back to Ethereum can involve a waiting period.
- Keep the transaction hash or bridge status link until the move is complete.
Apps
The Apps area is a curated launchpad for Arbitrum ecosystem destinations. It should help users find the right official destination without turning the wallet into a noisy directory.
- Use Arbitrum Portal to browse ecosystem applications by category.
- Keep Docs, Bridge, Status and community destinations near product flows that depend on them.
- Open external apps in the browser and confirm the domain before connecting or approving anything.
Transaction review
Before a transaction reaches a signer or the chain, the wallet should explain what is about to happen in plain terms. Raw data can stay available, but the primary review should be readable at a glance.
- Show the active network, account, recipient, token, amount and estimated network fee.
- Separate normal route details from warnings, unknown contracts and unusual approval requests.
- Keep final confirmation visually distinct so it is clear when the user is committing to an onchain action.
Security basics
Wallet safety depends on habits as much as interface design. Treat every transaction approval as a real asset movement and every external destination as something to verify.
- Never share a recovery phrase, private key or signing code in chat, email, support forms or websites.
- Use checksum files, trusted domains and official community links when installing or troubleshooting.
- For larger balances, prefer a hardware wallet or another signer that keeps keys isolated from the desktop app.
Troubleshooting
If balances or routes look wrong, start with the simple checks first. Most issues come from the wrong network, stale cached data, an external app connection or a bridge transaction that is still settling.
- Confirm the selected account and network, then refresh balances or reconnect the signer.
- Check Arbitrum Status if RPC responses, bridge status or app loading feels delayed.
- Use the transaction hash in an explorer or the bridge status page when a move is pending.
Useful links
Official ecosystem resources are kept as external routes. Bookmark the domains you trust and compare them before connecting a wallet.
