Logótipo oficial do MASTR MASTR
Menu

Nomes, identidade e conteúdo web

Passkeys and crypto wallets: easier login, a new recovery map

The origin-bound credential, the account’s authority and the backup system need separate inspection.

Atualizado em 30 de setembro de 2026 · MASTR Labs

Os artigos e gráficos técnicos estão em inglês. A navegação está disponível em 7 idiomas.

Guias de referência
  1. What a passkey changes
  2. Login is not the same as spending authority
  3. Device-bound or synchronised?
  4. Questions worth answering before funding
  5. Exemplo concreto
  6. Fontes e originais

What a passkey changes

WebAuthn lets a relying party authenticate a user with a public-key credential scoped to that party. The authenticator signs a challenge; the server verifies it using the registered public key. The credential is not a shared password that a lookalike website can simply collect and reuse. Origin and relying-party checks are central to that protection. They do not validate the economic meaning of every action a signed-in application proposes. 1

Login is not the same as spending authority

A passkey might only log you into a portfolio service. In another product, it may authorise actions for a smart account or help unlock locally stored wallet material. Those architectures have different failure modes. Ask exactly which signature the chain accepts, which component translates the authentication result and which alternative keys or guardians can change account control.

Device-bound or synchronised?

Some credentials are tied to a device; others can be backed up and synchronised through a credential provider. The provider’s account recovery process then becomes relevant to regaining access. A wallet can also have its own recovery route independently of the passkey. ‘No seed phrase’ describes an interface choice, not the absence of a recovery dependency. WebAuthn exposes backup-related properties, but the complete product design still matters. 1

Questions worth answering before funding

Identify the relying-party domain, the device or sync provider, the smart-account address if applicable, and every route that can install a new signer. Confirm whether access survives a lost phone, a disabled cloud account and disappearance of the wallet website. Keep the distinction between authentication and authorisation visible: successfully proving who controls a credential does not establish that a requested transfer is sensible.

Map authentication to actual authority
Diagrama explicativo. Abrir em tamanho completo. Credits ↗ A convenient login does not describe the entire custody model.

Exemplo concreto

A passkey signs you into a dashboard, while a hardware wallet still signs transactions. Losing the passkey blocks the dashboard until account recovery; it does not automatically remove control of the hardware wallet. A passkey-controlled smart account can have a different outcome. The product architecture decides.

Fontes e originais

  1. W3C: Web Authentication Level 3
  2. ERC-4337: account abstraction

Continuar a leitura

Nomes, identidade e conteúdo web →

MASTR

Apoiar a investigação independente

As investigações, as provas originais e os guias são de acesso livre. Os donativos voluntários ajudam a financiar a investigação e a manter disponíveis as ferramentas MASTR.

Abrir carteira