Skip to content

docs: document P256/WebAuthn shared address derivation #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fgimenez merged 1 commit into from
Jan 27, 2026
Merged

docs: document P256/WebAuthn shared address derivation #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions src/pages/guide/use-accounts/webauthn-p256-signatures.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,20 @@ WebAuthn signatures include authenticator data from biometric devices. Identifie

The verification data contains information from the authenticator (device metadata, user presence flags, etc.).

## Address derivation

### secp256k1

Standard Ethereum address derivation: `keccak256(uncompressed_public_key)[12:32]`.

### P256 and WebAuthn

Both P256 and WebAuthn derive addresses from the public key coordinates: `keccak256(pub_key_x || pub_key_y)[12:32]`.

:::info[Shared address space]
P256 and WebAuthn use identical address derivation, so the same key pair produces the same address regardless of signature type. A passkey can authorize transactions via raw P256 signatures and vice versa.
:::

---

:::info
Expand Down