Wallets without the wallet
hi, i’m Estel 👋
i’m a developer working on wallet stuff: keys, signing, and onboarding. my goal is simple: apps where people don’t think about “wallets.” you just sign in, use it, and it works.
i’ve spent too many late nights on the bits: device keys, sane recovery, transactions that feel instant. along the way i learned why users bounce at “connect wallet” and how to remove that speed bump.
recently i joined a team building embedded wallets you can drop into a product—no extensions, no seed phrases. web2 flow, web3 ownership.
if you’re shipping anything with crypto under the hood or you’ve got scars from wallet ux, let’s swap notes. what are you building, and where do users get stuck?
Interesting concept — removing the traditional wallet UX makes a lot of sense in terms of adoption, but from a developer perspective the real challenge is balancing security properties (key custody, anti-phishing) vs seamless user flows. It’s easy to build a “no wallet” facade, but much harder to design it so the attacker surface doesn’t expand or recovery isn’t a UX nightmare.
In practice, the first behavioral signal or metric I watch when evaluating keyless/hidden wallet flows is how often users hit recovery paths (lost keys, session expiry, re-auth), and how that correlates with error rates or support tickets — because that tells you whether the UX truly reduces friction without undermining security.
Curious — in your implementation, which metric or signal do you treat as the earliest real indicator that users are actually benefiting from the “walletless” approach (e.g., lower drop-off at onboarding, fewer session failures, fewer support recoveries)? That’s usually the hard part developers need to measure to validate the architecture.
Estel, your mission to make wallets invisible is spot on! The current wallet UX is a major barrier to web3 adoption.