The seed phrase is where most people quit. A passkey does the same job with the face scan you already use, and the trade-offs are worth knowing.
A passkey is a keypair your phone generates and stores in secure hardware. It signs with a different curve than Ethereum normally uses, so a small on-chain verifier contract checks the signature instead. You sign in with Face ID, so there is no seed phrase to type day to day. You save a single 12-word recovery key once, as a backup you never need to sign in.
Ask anyone who bounced off crypto why, and a striking number will describe the same moment: an app showed them twelve random words, told them that losing the words meant losing everything forever, and offered no way to undo that. Reasonable people close the tab.
The seed phrase is not there because it is good design. It is there because a normal blockchain account is a private key, and a key has to live somewhere a human can restore from.
Passkeys let that key live in the same hardware that already guards your banking app.
A passkey is a public and private keypair generated by your device. The private half is created inside a secure element, a dedicated chip designed so that keys inside it cannot be extracted, even by the operating system. Every iPhone, modern Android and most laptops have one.
You never see the private key. You cannot copy it, screenshot it, or be tricked into typing it into a website, because there is nothing to type. To use it, you prove you are present with a face scan or fingerprint, and the chip signs on your behalf.
The public half is not secret and is what identifies your account.
This is the same technology that has been quietly replacing passwords on major websites. The novel part here is using it to control money on a blockchain.
Here is the genuinely technical bit, kept short, because it explains why this took a while to become practical.
Ethereum accounts sign using an elliptic curve called secp256k1. Passkeys, standardised long before and used across the whole web, sign with a different curve, secp256r1, also called P-256. The maths is similar but the curves are not interchangeable. Ethereum's built-in signature check simply cannot verify a passkey signature.
For years the workaround was verifying P-256 in ordinary contract code, which worked but cost enough gas to be unattractive.
Base and several other chains now include a precompile for exactly this, a built-in function at a fixed address that verifies a P-256 signature natively and cheaply. That change is what makes passkey-controlled wallets practical rather than merely possible.
Three pieces, each doing one job:
So the chain of control runs from your face, to the chip, to the signature, to the signer contract, to your wallet. At no point does anyone else hold a key, and at no point is there a phrase to lose.
Creating the account takes three transactions: deploy the signer, deploy the Safe, and configure it. They are submitted back to back, and on Base they land in a single block. The waiting you experience is the biometric prompt, not the blockchain.
There is no phrase to lose. The failure mode that has cost people the most money simply does not exist here.
Phishing gets much harder. A passkey is bound to the website that created it. A convincing fake at a lookalike domain cannot request it, because the browser will not offer a passkey to the wrong origin. Compare that with a seed phrase, which a sufficiently convincing page can talk anyone into typing.
It syncs, safely. Passkeys sync through your platform's keychain, encrypted end to end, so a new phone restores your access without the key ever being readable by Apple, Google or anyone else.
No app, no extension, no gas. There is nothing to install and no need to acquire ETH before you can do anything, which removes the other place people commonly give up.
This is a genuine trade, not a free upgrade.
You are trusting the platform ecosystem, with a backup. Your passkey syncs through your platform account, so a new phone restores day-to-day access. And when you create your vault, Fonte sets up a 12-word recovery key as a second owner, so you can regain control even if you lose every device and your Apple or Google account. You save that key once. It is the same "keep this somewhere safe" as a seed phrase, with one difference that matters: you never need it to sign in, only to recover, so a bad day with your phone is not the moment you first go looking for it.
Moving between ecosystems is awkward. A passkey created in Apple's keychain does not simply move to Google's. Cross-platform support is improving and still rough.
It is newer. Seed phrases are ugly and extremely well understood. Passkey-controlled smart accounts are a younger pattern with a shorter track record, and the honest framing is that they trade a well-known sharp edge for a less-explored one.
The signer contract is a dependency. Your wallet's security now includes the correctness of that contract and of the precompile it calls. That is real code, and real code can have flaws.
No, and this is the part worth being precise about, because "easy signup" is exactly what a custodial product also offers.
A passkey account is self-custody. The signing key is yours, in your hardware, and the wallet is owned by a contract that only your passkey can authorise. A company operating this can be scoped so that it cannot move your funds regardless of how easy onboarding was.
Ease of signup and custody are independent. Plenty of products make signup easy by holding your keys. The check is the same one you should run on any of them: ask what the operator is technically capable of, not what the onboarding felt like. Our guide to what non-custodial actually means covers how to test that in a few minutes.