Sign In With a Wallet, Delivered Over SimpleX: A Better 2FA Idea
A login idea with no phone number. A wallet signs, SimpleX delivers, and two separate things have to hold. A proposal, with the weak spots listed.
The idea
Most sites use your phone number twice. It is how they find you, and it is where they send the code that proves you are you. I wrote about why that makes a poor identity in The Phone Number Is Dying as Our Identity. This post is the replacement I would build.
It is a proposal. Nobody has built it this way, and it is not a product. Every piece of it exists today.
How it would work
You enroll once. Your wallet signs a short message with your private key. That is a digital signature, and it proves you hold the key behind a public key without showing the key. Cake Wallet can already sign a message with your wallet keys to prove you control an address.[3] Then you give the service your SimpleX Chat link. SimpleX has no user identifiers, and you connect with a one time link or a QR code.[2]
Later you log in on a laptop. The service sends a challenge to you over SimpleX. That is a push to you, instead of you pulling a code out of a text. Your wallet shows who is asking and a short number that matches the one on the laptop. You approve. The wallet signs. The service checks the signature against the key you enrolled.
The signed message should name the service and carry a nonce, a one time number, and an expiry. Sign In With Ethereum already works that way. Its message includes the domain, a nonce, and an expiration time.[4]
Why two channels help
Two separate things have to hold. One is delivery over SimpleX. The other is the proof from the wallet. Because you connected to the service once, a message on that connection already tells you who sent it.
SimpleX uses the same logic for its own first connection. It stops servers from swapping the key by requiring the invitation link to travel through another channel. Since that channel could also be compromised, it adds a security code you can compare.[1] That is the answer to a man in the middle attack, where someone sits between two people and quietly swaps the keys.
It is close to a passkey. A passkey is tied to the website's domain, and the browser refuses to sign for a mismatched one.[5] This idea has no browser doing that. The check lives in the message, in the SimpleX connection, and in what you read. That is the weaker side. It also explains why the signed message must name the service, because push approvals can be relayed.[6]
Where it can fail
Push fatigue. An attacker who already has a password can bombard you with prompts until you tap yes.[9] Microsoft began enforcing number matching in Authenticator push notifications on May 8, 2023.[7] CISA says it helps because you need access to the login screen to approve.[8] That is why the number on both screens matters.
Enrollment. The first connection is where a man in the middle would strike, so use the out of band link and compare the security code.[1] Recovery. If you lose the wallet, you are locked out, so there must be a backup key or a person who can vouch for you.
Both devices have to be yours. A compromised laptop can start logins but cannot sign for you. A compromised phone is the worst case, because the key lives there. SimpleX has desktop and mobile apps, so the push can land on either.[2] Cake Wallet has desktop apps too. Its 2025 review says it now covers iOS, Android, macOS, Linux and Windows,[12] though the Linux version is still listed as beta.[13] I have not confirmed that message signing works on desktop, so this post still assumes the phone signs.
Where this stops
People do stupid things. These layers reduce the ways to fail. They do not remove them, and a clever fake can still trick a tired person. Treat this as an idea to test, not security advice. Do not trust anything important to it until a real security engineer has reviewed it.
One more link. TwoOfFive is one of Happy's projects, a player for media where creators get paid in crypto. Its site already uses a wallet login, keeps email or phone optional, and offers 2FA by a second wallet or hardware key. It also tells creators to share a Session, SimpleX or Signal link for chat.[11] The demo page itself does not describe how sign in works.[10] This idea is a variant of that 2FA. Instead of a second wallet, the proof arrives as a challenge over SimpleX with a matching number. For how a wallet signs, see Your Wallet Is Your Signature, and for the home box idea see Your Phone Has a Key Vault.
Sources
- SimpleX Chat, v4.4 release notes (the invitation link must pass through another channel so servers cannot swap the key; a security code lets you check the connection)
- Help Net Security, SimpleX Chat removes user identifiers from messaging (no user identifiers, one time link or QR code, apps for iOS, Android, Windows, macOS and Linux)
- Cake Wallet documentation, Sign and verify messages
- Ethereum Improvement Proposals, ERC 4361: Sign-In with Ethereum (message includes domain, nonce, issued at and expiration time)
- WorkOS, Cryptographic origin binding: how passkeys make phishing structurally impossible (April 9, 2026)
- ScrambleID, Phishing-Resistant Web Authentication (OTP and push approvals can be relayed)
- BleepingComputer, Microsoft enforces number matching to fight MFA fatigue attacks (May 8, 2023)
- CISA, Implementing Number Matching in MFA Applications (fact sheet)
- SecureW2, What Is MFA Fatigue and How Do Attackers Exploit It?
- TwoOfFive demo (the page says users can sign in but does not say how; creators list Session, SimpleX or Signal as a contact channel)
- TwoOfFive, home page (wallet login; email or phone optional; 2FA by a second wallet or hardware key; creators share a Session, SimpleX or Signal link for chat)
- Cake Wallet blog, Cake Wallet 2025 (cross platform: iOS, Android, macOS, Linux and Windows)
- Cake Wallet guides (the Linux version is still in beta and support is best effort)
Inspired by Happy, written by Claude.
Next relatedYour Wallet Is Your SignatureRevision history (R1 current)
| Rev | Date | What changed | Page |
|---|---|---|---|
| R0 | Nov 18, 2026 | First published. Written by Claude (Sonnet) from Kenny's design in chat, not DeepSeek. The design is a proposal. SimpleX, Cake Wallet, Sign In With Ethereum, passkey, number matching and TwoOfFive facts were checked against the ten pages listed; twooffive.io itself could not be opened here, so only the demo page was read. Cake Wallet desktop support was not checked. This is a judgment heavy post, so a second look on Opus is worth it. Wikipedia links are from memory. | view |
| R1 | Nov 18, 2026 | Corrected the TwoOfFive paragraph after reading twooffive.io in a browser: the site already uses a wallet login with 2FA by a second wallet or hardware key, so this idea is now described as a variant, not a fix for a missing login. Replaced the line saying Cake Wallet desktop was unchecked: Cake has macOS, Linux (beta) and Windows apps. Whether message signing works on desktop is still unconfirmed. Three sources added. | view |