MFA and device verification
Not a code from an app — a signature-derived one-time value tied to your wallet and eSIM.
PTERI doesn't use traditional MFA — there's no authenticator app, no TOTP secret, no SMS code. If you're used to that model, here's the closest equivalent and how it actually works.
eSIM identity binding
A PTERI-linked account can be bound to a wallet address, which is bound to a device's eSIM. When step-up verification is needed, the device signs a message with the wallet's private key and derives a one-time value from that signature — not from a shared secret sitting on a server. The signed payload is sent to PTERI, which verifies the signature against the known wallet address and confirms the eSIM binding before marking the device "verified."
Moving to a new device
If you get a new phone, there's no MFA reset request to file. Install the PTERI Wallet app, restore your wallet from your recovery phrase or an encrypted cloud backup, sign an authentication message to prove control, and re-register the device. See recovering account access for the full steps — and back up your recovery phrase now, before you need it.
Why this instead of TOTP/SMS?
Shared TOTP secrets can be phished or leaked from a server-side database; SMS can be intercepted via SIM-swap. Deriving the one-time value from a device-held signature removes the shared secret entirely — there's nothing sitting on a server that, if breached, would let someone else generate valid codes.