Introduction
Starknet Wallet is a desktop wallet built for secure Starknet workflows. It helps users manage STRK, review Cairo calls, inspect smart-account permissions, and approve transactions with clearer signing context.
Built for Starknet
Mainnet and Sepolia, smart accounts, Cairo calls, and STRK as first-class primitives.
Desktop-first workflow
Native builds for macOS, Windows, and Linux with a focused signing surface.
Local-first account control
Keys are generated and stored on your device — nothing is custodied for you.
Clear signing review
Every approval shows dApp, network, contract, fee, and decoded calldata.
Installation
System requirements
- Windows 10 or later, x64
- macOS 12 Monterey or later, Apple Silicon and Intel
- Linux: Ubuntu 22.04+, Fedora 38+, or equivalent modern distribution
- Internet connection for Starknet Mainnet and Sepolia access
Download options
- Windows (.exe installer, x64)
- macOS (.dmg Universal — Apple Silicon and Intel)
- Linux (.AppImage / .deb)
Verification-first install
Before installing, verify the package source, checksum, and build signature. The download section provides the SHA256 and PGP verification details for every maintained build.
First Setup
Launch Starknet Wallet and walk through the onboarding flow. The product is designed so each decision is explicit and reversible.
- 1Choose your network: Starknet Mainnet or Sepolia. The active network is always visible.
- 2Create a new Starknet account or import an existing one.
- 3Review where local key material is stored on your device.
- 4Set your wallet password and confirm device-level security settings.
- 5The website product interface explains the signing workflow without submitting wallet transactions.
Managing Accounts
Account overview
See STRK balance, recent activity, and the active Starknet account at a glance.
Multi-account workflows
Create or import multiple Starknet accounts and switch between them cleanly.
Network switching
Move between Starknet Mainnet and Sepolia explicitly, with the network labeled on every signing surface.
Local-first control
Account material stays on your device — Starknet Wallet does not custody keys.
Transaction Review
Starknet Wallet focuses on showing clearer transaction context before approval. Review before signing. Approve only when the transaction context is clear.
- dApp name and origin
- Active Starknet network (Mainnet or Sepolia)
- Target contract address
- Estimated fee
- Cairo call preview with the function name
- Decoded calldata details
- Token and spending-approval context
- Final approve or reject action
Smart-Account Permissions
Starknet is built around smart accounts. Starknet Wallet helps users review permissions, session keys, spending approvals, and signer context before they apply.
Session keys
Review scope, expiry, and which contracts a session key is allowed to call.
Spending limits
See spending caps and per-token approval contexts before they are granted.
Signer visibility
Inspect the signer set tied to a smart account and any pending changes.
Approval paths
Understand which approvals a transaction depends on inside an account-abstraction flow.
Security Practices
Starknet Wallet is designed around local-first key control, verification-first installation, and clear signing context. The practices below help you get the full benefit of that model.
- Keep key material local — never paste account material into web forms.
- No telemetry by default; opt in only if you want to share diagnostics.
- Verify every download before installing.
- Check the published SHA256 checksum for your build.
- Verify the build signature supplied for your package.
- Review transaction details on every approval, including network and contract.
- Keep your operating system and wallet updated.
- Use hardware-wallet workflows for higher-value accounts when appropriate.
Hardware Wallet Workflows
Starknet Wallet supports compatible external signing workflows, so you can keep signing material on a dedicated device.
Ledger-compatible workflows
Use a Ledger-compatible signing workflow where supported by your account and firmware.
Trezor-compatible workflows
Use a Trezor-compatible external signing workflow where supported.
Smart-account signing
Pair a hardware signer with a Starknet smart account to keep approvals on a separate device.
External signer review
Inspect what is being sent to the external signer before you confirm on the device.
Hardware-wallet architecture
The signing surface integrates external signers cleanly into the review flow.
dApp & Developer Workflows
For Cairo builders and Starknet developers, Starknet Wallet provides clearer transaction context before signing, making it easier to debug integrations end-to-end.
- Cairo call preview with the resolved function name
- Contract call review with decoded calldata
- Explicit Mainnet and Sepolia switching, surfaced on every signing screen
- Developer-friendly transaction context for QA and integration review
Troubleshooting
Wallet does not open after install
Likely cause: Installer was blocked by the OS or the file did not finish downloading.
Recommended fix: Re-download the build for your platform and verify the SHA256 before opening.
Wrong network selected
Likely cause: The active network was Sepolia (or Mainnet) when you expected the other.
Recommended fix: Switch network from the account header — the active network is shown on every signing surface.
Transaction details look different than expected
Likely cause: The dApp may be requesting a different contract, calldata, or approval than you thought.
Recommended fix: Reject the transaction, re-trigger it from the dApp, and re-review the decoded Cairo call.
Download verification failed
Likely cause: Checksum or signature does not match the published values.
Recommended fix: Do not run the file. Re-download from the official source and verify again.
Account import issue
Likely cause: Source material was incomplete or copied from an untrusted location.
Recommended fix: Re-check the source of your account material before pasting and try the import again.
Hardware signer not detected
Likely cause: Cable, firmware, or device app not in the expected state.
Recommended fix: Reconnect the device, update its firmware, and re-launch Starknet Wallet.
dApp connection issue
Likely cause: The dApp may not support the active Starknet network or account type.
Recommended fix: Confirm the dApp supports your network, refresh the page, and re-initiate the connection.
Advanced Tools
Cairo calldata viewer
Inspect decoded calldata for the Cairo call you are about to sign.
Permission viewer
Walk through session keys, signer changes, and spending approvals tied to your smart account.
Account activity inspector
Browse account activity with network, contract, and fee context.
Build verification panel
Reference the SHA256 checksum and signature published for your build.
Multi-network context
Move between Starknet Mainnet and Sepolia with the active network clearly labeled.
Hardware signer workflow status
See whether an external signer is connected and ready for the next approval.
Frequently Asked Questions
Does Starknet Wallet store keys online?+
No. Keys are generated and stored on your device. They are not transmitted to any server.
Which operating systems are supported?+
macOS 12 or later (Apple Silicon and Intel), Windows 10 or later (x64), and modern Linux distributions such as Ubuntu 22.04+ and Fedora 38+.
Can I use Starknet Mainnet and Sepolia?+
Yes. You can switch between Starknet Mainnet and Sepolia, and the active network is shown on every signing surface.
Does it support STRK?+
Yes. Starknet Wallet treats STRK as a first-class asset with balance, activity, and signing context.
Can I review Cairo calls before signing?+
Yes. Every approval shows the dApp, network, contract, fee, function name, and decoded calldata before you sign.
Does it support hardware wallets?+
Yes. Starknet Wallet supports compatible external signing workflows, including Ledger- and Trezor-compatible flows.
How do I verify downloads?+
Compare the SHA256 of your downloaded file with the published checksum, and verify the build signature with the published key.
Does the website submit wallet transactions?+
No. The website product interface explains the signing surface; wallet and network actions are performed in the desktop application.
Resources & Support
GitHub
Source, releases, and verification material.
Developer guides
Deeper guides for installing, verifying, and integrating.
Security
Security model, verification flow, and disclosure.
Download
Get the maintained build for your operating system.
Contact & support
Reach the maintainers for product or security questions.