Desktop edition of Sollet (SPL token wallet), repackaged by the community for Windows, macOS and Linux. Non-custodial, open source and designed to be straightforward to audit.
Prefer to verify everything yourself? Compare checksums or compile the app locally, then connect to Solana dApps through a lightweight client you understand and control.
Select your platform. Each download button opens the upstream GitHub Releases page (project-serum/spl-token-wallet).
If your OS does not have prebuilt binaries, use Build from source. Always validate what you install.
| Platform | Package | Filename | Get it |
|---|---|---|---|
|
Windows 10/11 (x64)
|
Installer (.exe) |
|
Download |
|
macOS 12+ (Intel/Apple Silicon)
|
Disk image (.dmg) |
|
Download |
|
Linux (x86_64)
|
AppImage |
|
Download |
Use the commands below for your OS. The example hashes are placeholders; compare only with checksums published alongside the specific release you installed.
Get-FileHash .\Sollet-Wallet-1.7.0-windows.exe -Algorithm SHA256
Get-AuthenticodeSignature .\Sollet-Wallet-1.7.0-windows.exe | Format-List *shasum -a 256 Sollet-Wallet-1.7.0-mac.dmg
codesign -dv --verbose=4 /Applications/Sollet.app
spctl -a -vv /Applications/Sollet.appshasum -a 256 Sollet-Wallet-1.7.0-linux.AppImage
chmod +x Sollet-Wallet-1.7.0-linux.AppImage
./Sollet-Wallet-1.7.0-linux.AppImageThe hashes shown on this page correspond to the installer files linked above. If you download a different version or from another source, the checksum will be different. Always verify that the SHA-256 you compute on your own machine matches the value printed here before running any installer. Never enter a recovery phrase into software you have not reviewed, and for new builds consider testing first inside a disposable virtual machine with only small test funds.
Built for people who prefer clarity, control and the ability to verify what they run.
Your private keys stay on your machine; how you secure and recover them is fully in your hands.
Store your seed phrase using an offline method such as paper, metal or another air-gapped medium. Sollet avoids hosted accounts and “log in with seed phrase” flows in the browser. You control RPC endpoints, how you segment funds and which environments you trust for day-to-day operations.
Transparency over obscurity: rebuild the wallet and compare results with published artifacts.
Pin a commit, lock dependencies, compile inside a clean VM or container, then compare hashes with binaries you plan to use. Matching checksums confirm integrity, while signatures indicate authorship. Combining both gives stronger defense-in-depth across your toolchain.
Interact with the Solana dApp ecosystem through standard wallet adapter flows.
Ecosystem support changes over time and newer adapters may be preferred by some projects. Start with small test amounts, carefully review transaction previews and confirm state on-chain before increasing position sizes, especially when using swaps or complex program interactions.
Familiar web tooling and a straightforward codebase make audits and experimentation approachable.
Clone the repository, run it locally and instrument the code. Swap RPC providers, add logging, tighten signing policies or integrate custom interfaces for advanced workflows. If your setup requires hardware-only signing, choose and configure a wallet that explicitly guarantees that behavior.
Simple routines can significantly reduce day-to-day risk in real use.
Never type a recovery phrase into a website form. Evaluate new binaries inside a VM, separate hot and cold keys, use address allowlists where possible and prefer watch-only views when checking balances from untrusted networks or devices.
Deterministic swap flows with clear slippage settings across a wide range of SPL tokens.
No embedded browsers or opaque routing hops. Quotes account for price impact and, when applicable, priority fees upfront — you review once, approve a single transaction and the trade settles in seconds while the wallet stays in the background.
For maximum assurance, clone the upstream repository, review changes and produce binaries on your own machine.
git clone https://github.com/project-serum/spl-token-wallet.git
cd spl-token-wallet
npm install
npm run start
npm run build“Sollet Bridge” has been deprecated; see Resources for the original notice. If you distribute your own builds, publish both checksums and signatures next to the artifacts.
Primary reference material and historical context. Some items are legacy but kept for completeness.
Open-source SPL token wallet (Sollet). Inspect issues, pull requests and commit history to understand current project status.
Sollet wallet adapter used by some dApps. Over time, many projects have moved toward newer adapter stacks; always confirm compatibility.
Official explanation and background on sunsetting Sollet Bridge. Treat historical bridging flows as unsafe for current use.
Historical NPM package for the Sollet adapter. Review advisories and maintenance status before using it in new integrations.
Legacy Serum ecosystem help pages and links, useful primarily for historical reference.
Additional context to help you decide how Sollet fits into your setup.
No. This is a community-packaged distribution that references upstream code. It targets experienced users who are comfortable reviewing software provenance and verifying integrity on their own. There is no warranty, support obligation or official endorsement.
Maintenance status can change over time. Some branches or releases may be inactive while others receive occasional updates. If there are no current binaries for your platform, prefer building from source with pinned dependencies.
Sollet Bridge has been formally deprecated. Legacy bridging routes should be treated as unsafe for moving value today.
Many wallets use BIP39 seeds and Solana-style derivation paths, but there are differences in path conventions and account discovery. Always test behavior with a throwaway seed before importing any primary wallet.
Compatibility depends on which wallet adapters a dApp supports. Confirm that connections, transaction previews and signing flows behave as expected before you deploy significant capital.
Use a VM with snapshots, create a disposable wallet, fund it with a small amount and verify all results with an independent Solana block explorer before scaling up.
Choose reputable RPC providers or operate your own node where possible. Prefer HTTPS, avoid shared or public networks for sensitive sessions and be mindful that your RPC endpoint sees metadata about submitted transactions.
Open an issue on the upstream GitHub repository. Include your OS version, clear reproduction steps and the exact commit or release tag you are using so maintainers can investigate.
Yes. If you publish your own builds, accompany them with signed artifacts and SHA-256 hashes, and document your changes clearly so others can audit what differs from upstream.