ArbitrumOne place for Arbitrum movement
Desktop Wallet
for Arbitrum
Track balances, open ecosystem apps, follow official bridge routes, and keep Arbitrum activity readable from one desktop surface.
Built for Arbitrum One, Arbitrum Nova and the wider Arbitrum ecosystem.
Desktop releases
Arbitrum is where daily onchain activity already happens. The wallet should feel just as mature.
Command deck
Balances, routes, apps, activity
Assets
Balances and token activity in a clear view.
Bridge
Official routes between Ethereum and Arbitrum.
Apps
Entry points into the ecosystem, without tab hunting.
Networks
Arbitrum environments placed where you need them.
Activity
A compact record of what changed.
Review
Transaction details before the next step.
Arbitrum-native
Arbitrum first,
from the first screen
Arbitrum One
The primary rollup network stays close to the first actions.
Arbitrum Nova
High-volume activity sits in the same desktop route.
Bridge routes
Official movement paths stay visible when funds move.
Ecosystem apps
Useful destinations are arranged by intent, not by noise.
Network status
The environment stays in view before the next action.
What is Arbitrum Wallet?
A desktop wallet arranged around Arbitrum activity: balances, official bridge routes, ecosystem apps, networks and transaction review.
Which networks does it focus on?
The interface is built around Arbitrum One, Arbitrum Nova and useful Arbitrum routes, with room for additional supported environments as the product evolves.
Does it support bridge flows?
Yes. Bridge actions should follow official Arbitrum routes and keep source, destination, token, amount and route context readable before the next step.
Can I open Arbitrum apps from the wallet?
The product is designed to keep useful ecosystem entry points close, so users can move between balances, apps and activity without treating every action as a separate tab.
How are transactions reviewed?
Transaction review should make the network, address, fee, token and route visible before the action continues. The goal is to make activity readable, not hidden behind raw data.
How should release files be verified?
Each desktop release should be paired with a matching SHA-256 checksum. Download the installer, compare the checksum locally, and only open the build when the values match.
Why include SHA-256 checksums?
Checksums give users a way to verify downloaded release files. Keep checksum links next to the release links and update them every time a new build is published.
Where can users find official Arbitrum resources?
Keep links to the official Bridge, Portal, Docs, Network Status and community channels available in the header and footer.