Published verdictRanking snapshot 3 November 2026
Rabby Wallet leads by 6 points
Rabby Wallet scores 6 points above Solflare, led by clear signing and incident record.
RBRabby Wallet #1 of 1181
Solflare #5 of 1175Why, term by termRabby Wallet leads on 2 of 4 published criteria; Solflare on 2. The terms sum to the gap.
TermRabby WalletSolflareWeightPoints
Clear signing8/107/107.2+1.9for Rabby Wallet+1.0 of 32
Key export9/1010/106.7−1.7for Solflare−0.9 of 32
Incident record7/102/105.8+7.5for Rabby Wallet+3.8 of 32
Account recovery8/109/104.3−1.1for Solflare−0.6 of 32
Net of the terms+6.5
Reproduced gap+6.5
Published gapAfter score rounding and bounds — see the note below8175+6.0
Weight is in points of the 86-point weighted total. Points are score points of the gap between the two.
Rabby WalletScore 81The reference implementation of pre-signature transparency in this pool, and the product that proves the signing axis actually separates. Rabby is a self-custodial EVM wallet from OPCODE LABS PTE. LTD. (the DeBank team), shipping as an MIT-licensed browser extension, a desktop app and iOS/Android apps. Where most wallets show a confirm button, Rabby's help centre documents an entire pre-signature apparatus: a simulation that previews the exact balance change, a decode that turns calldata into a readable action, a named Security Engine whose heuristics are published rather than hand-waved, and — uniquely in this pool — a hard lockout, "If a risk is detected, the Sign button will be disabled." Key custody is equally plain: one vendor page documents both Backup Seed Phrase and Backup Private Key on both platforms, with no email or account anywhere in the flow. The paperwork is better than it first appears: fourteen dated third-party audit reports across two repositories, from SlowMist, Least Authority and Cure53, spanning 2021-2025 and covering the extension, iOS and Android separately, joined by SlowMist reports dated 2026-08-24 for all three. What is genuinely missing is the disclosure machinery — no bug bounty, no security policy, no advisory archive — and the help centre remains silent on the October 2022 Rabby Swap contract exploit that cost users roughly $194,000, an event the vendor did in fact disclose on the day, on X, but never on its own website.Strength: Key export — 9/10Watch-out: Read the incident record before the feature list. Rabby is the strongest pre-signature product in this pool and among the weakest at maintaining a place to tell you when it has failed. There is no bug bounty (zero occurrences of "bount" anywhere in the homepage bundle or the help centre), no SECURITY.md (GitHub states outright "No security policy detected"), no security.txt, no advisory archive, no security@ contact and no postmortem page anywhere on rabby.io or support.rabby.io — so a researcher has no published private channel to report a vulnerability. On 2022-10-11 the Rabby Swap contract was drained of roughly $194,000 of user funds via approvals granted to it. In fairness the vendor did disclose it the same day on X, with a list of affected addresses, the four exploited contract addresses and revoke instructions — but that thread is now the ONLY disclosure that exists, and nearly four years on Rabby's own website and help centre still contain no mention of the event, nor any confirmation that the promised "satisfying solution for users within 1 week" was ever delivered. Weigh that against what IS published, which is more than it first appears: fourteen dated third-party audit reports across two repositories, from SlowMist, Least Authority and Cure53, spanning 2021-2025, with iOS and Android audited separately, and the extension set linked from a "Security & Transparency" section on Rabby's own homepage. Better than most of this pool, and newly refreshed: since August, SlowMist reports dated 2026-08-24 for the extension, iOS and Android have been added to the two repositories' audits/2026 folders. Three narrower things before committing. First, the protection you are buying is documented and sold for the EXTENSION: the Chrome Web Store listing advertises "pre-transaction potential risk scanning" and "upcoming balance change before you sign", while Rabby's own App Store and Google Play descriptions claim neither, so do not assume the mobile app is the same object. Second, no Rabby page ever prints "BIP-39" or a derivation path — verified zero hits across every vendor surface — so if you later want to restore your phrase into a different wallet you will be cycling HD-path options by trial and error. Third, the open-source guarantee is uneven: the extension's code is under an MIT grant (its LICENSE adds that "Brand name and logo of Rabby is copyright reserved", and GitHub reports the licence as NOASSERTION), but the mobile repository carries no licence file at all, so its published source grants no formal right to rebuild it if the vendor disappears.SolflareScore 75Solana-only self-custody wallet that documents seed AND per-account private-key export on both extension and mobile in printed steps, and whose named in-house scanner is described only in prose — no audit, no bug bounty, no advisory archive exists on any Solflare surface.Strength: Key export — 10/10Watch-out: Solflare tells you what its protection does, never what your screen shows, and publishes nothing a security engineer can check. Its scanner is named and described in prose — "Every time you go to sign a transaction, Solflare Guards step in to" … "They simulate the transaction behind the scenes" (solflare.com/crypto-101/crypto-wallet-security-101-how-solflare-protects-your-assets/) — but no Solflare page renders a balance-change diff or a decoded human-readable action, so "What You See Is What You Sign" is a claim about a screen the vendor has never documented. Behind it: solflare.com/security/ names no audit, no auditor and no bug-bounty programme; /.well-known/security.txt is HTTP 404; none of the eight sitemaps (page 94, blog 31, crypto-101 54, glossary 120, guide 18, ecosystem 5, job 6, blog-author 12) contains an advisory or disclosure page; there is no SECURITY.md and no GitHub advisory; and the client is closed source. The sharpest tell is the vendor's own FAQ telling Ledger users to "make sure that Blind Signing is enabled in Ledger Live" — that turns the paired device's screen into a hash and leaves the undocumented Solflare screen as the only human-readable view of what you are signing. Where Solflare is genuinely strong is the exit: seed and per-account private key both export in printed steps on extension and mobile, no login exists, and "Any Solana recovery phrase works, regardless of which wallet it was created in." Buy the custody model, not the security assurance.