The original Sollet (SPL Token Wallet), carefully community-packaged for Windows, macOS, and Linux. Non-custodial, open source, and straightforward to verify.
Prefer proof? Check the checksums or build from source — then connect to Solana dApps with a lightweight, predictable client.
Choose your operating system. The download opens the upstream Releases page (project-serum/spl-token-wallet).
If no binaries are available, use Build from source. Always verify before installing.
Standard installer for Windows 10/11. Verify hash and (if available) Authenticode before running.
SolletWallet-Setup.exef1a8c4b0d7e9b1240c6e99f57b2e31d6f7e8a9b3a2c4d5e6f0ab12cd34ef5678 Get-FileHash .\SolletWallet-Setup.exe -Algorithm SHA256Get-AuthenticodeSignature .\SolletWallet-Setup.exeGet-FileHash .\SolletWallet-Setup.exe -Algorithm SHA256
Get-AuthenticodeSignature .\SolletWallet-Setup.exe | Format-List *Signed .dmg for macOS 12+. Gatekeeper may require allowing the app in Privacy & Security.
SolletWallet.dmgSollet.app.dmg, drag to Applications.a0ee1d3b99f6c2de448c0e57b1a223cd930a4c11dfc0ba772e0b1d2a3f4c5679 shasum -a 256 SolletWallet.dmgcodesign -dv --verbose=4 Sollet.app · spctl -a -vv Sollet.appshasum -a 256 SolletWallet.dmg
codesign -dv --verbose=4 /Applications/Sollet.app
spctl -a -vv /Applications/Sollet.appxattr -dr com.apple.quarantine Sollet.app (only if trusted).Portable AppImage for major distros. Make executable, then run. FUSE may be required.
SolletWallet.AppImageb97a2c4d5e6f0ab12cd34ef5678f1a8c4b0d7e9b1240c6e99f57b2e31d6f7e8 shasum -a 256 SolletWallet.AppImageshasum -a 256 SolletWallet.AppImage
chmod +x SolletWallet.AppImage
./SolletWallet.AppImagechmod +x SolletWallet.AppImage./SolletWallet.AppImageHashes shown on this site are examples. Always compare against the hash published alongside the specific upstream release you downloaded. Never import a recovery phrase into software you haven’t verified. Prefer a throwaway VM to test new builds.
Focused on clarity and control — for users who prefer to verify.
Your wallet, your rules — keys never leave your device, recovery is entirely under your control.
Back up your seed with an offline method (paper/steel/air-gapped). Sollet avoids remote custody assumptions: no hosted accounts, no “sign in with seed” web flows. You decide RPC endpoints, segmentation of funds, and the operational envelope.
Trust through transparency — rebuild and compare outputs to ensure integrity.
Pin a commit SHA, lock dependencies, compile in a clean VM/container, and compare hashes with community artifacts. Hash equality proves integrity; signatures attest authorship. Combine both for defense-in-depth across your toolchain.
Connect to the Solana dApp ecosystem using standard wallet adapters.
Ecosystem support evolves; some projects may prioritize newer adapters. Start with tiny amounts, verify transaction previews, and confirm state changes chain-side before scaling up — especially for swaps and program interactions.
Familiar web tooling and a straightforward codebase make audits practical.
Clone, run, instrument. Swap RPC providers, add logging, layer stricter sign policies, or wire custom UIs for advanced flows. If you need hardware-only signing, choose a wallet that explicitly guarantees it.
Simple habits reduce risk dramatically in day-to-day use.
Never type a recovery phrase into a website. Evaluate new builds in a VM; keep hot and cold keys separate; use allowlists; prefer watch-only views when inspecting balances from untrusted networks.
Minimal UI and predictable behavior make it easier to reason about what the app is doing.
No flashy surfaces or surprise background flows. Performance and clarity come first — the application stays out of your way while you execute the task at hand.
Integrity first. Follow the steps, then paste your local SHA-256 to check it against the example for the active OS tab.
Open the upstream Releases page and download the file for your OS — avoid mirrors and re-hosted binaries that might silently change over time.
# Windows
Get-FileHash .\SolletWallet-Setup.exe -Algorithm SHA256
# macOS / Linux
shasum -a 256 SolletWallet.dmg
shasum -a 256 SolletWallet.AppImageMatch your local result with the expected hash from the specific release notes. Hashes prove integrity, not authorship — add signature checks where available.
Signatures establish developer identity; Gatekeeper enforces policy on launch. If anything looks suspicious, stop and rebuild from source.
codesign -dv --verbose=4 /Applications/Sollet.app
spctl -a -vv /Applications/Sollet.appAuthenticode integrates with the Windows trust store and SmartScreen. Inspect signer, timestamp, and chain.
Get-AuthenticodeSignature .\SolletWallet-Setup.exe | Format-List *Prefer maximum assurance? Build locally and review diffs yourself.
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” is deprecated; see Resources. If you publish builds, publish hashes and signatures alongside artifacts.
Primary references and historical context. Some items are deprecated but kept here for completeness.
Open-source SPL Token Wallet (Sollet). Review issues, PRs, and commit history to understand current status.
Sollet adapter used by some dApps. Ecosystem support may shift toward newer adapters over time.
Official rationale and background. Treat legacy bridging flows as unsafe today.
Historical package for the Sollet adapter. Check advisories before use in modern stacks.
Archived Serum ecosystem help pages and links for historical context.
Context for evaluating Sollet in your setup.
No. This is a community-packaged distribution that references upstream code. It is intended for advanced users who are comfortable verifying software integrity and provenance. There is no warranty or support commitment.
Maintenance varies over time. Some branches or releases may be dormant, others may receive occasional fixes. If Releases do not include binaries, build locally from source using locked dependencies.
Sollet Bridge has been deprecated. Do not use legacy bridging flows today.
Many wallets share BIP39 seeds and Solana derivation, but some differ in path conventions or account discovery. Test with a throwaway seed first.
It depends on adapters a dApp supports. Validate connection and signing prompts before committing funds.
Use a VM with snapshots, create a disposable wallet, and confirm chain state via an independent explorer.
Use reputable endpoints or host your own node. Prefer HTTPS and avoid public networks for sensitive sessions.
Open issues on the upstream repository. Include OS version, steps to reproduce, and exact commit or release.
Yes. If you publish builds, provide signed artifacts and SHA-256 hashes. Document changes clearly.