Testnet only. Sei Atlantic-2, chain 1328.Not audited. Test funds only.

Concepts

Addresses and keys

The seed, the spend and view keys, batin1 addresses, passkeys and the backup file.

On this page
  1. One seed
  2. batin1 addresses
  3. Passkeys (PRF)
  4. The backup file
  5. The funding account (app-level)

One seed

A wallet is 32 random bytes generated on the device. Two keys come from it with HKDF-SHA256:

spendKey = OS2IP(HKDF(seed, salt="sei-private-pay/v1/keys", info="spend", L=48)) mod r
viewKey  = OS2IP(HKDF(seed, salt="sei-private-pay/v1/keys", info="view",  L=48)) mod l

The sei-private-pay/v1/… labels are frozen protocol identifiers from before the project was renamed. Changing them would change every key and the circuit constants.

Keys are never derived from a wallet signature or from a passkey assertion. A signature-derived key is only as private as every site you ever signed for.

batin1 addresses

A receiving address is ownerPub ‖ pack(viewPub) (64 bytes) plus a 4-byte keccak checksum, base64url-encoded behind the prefix batin1. It is one unit: a payer needs both halves to make a note you can find and spend. Sharing it reveals nothing about your balance.

Passkeys (PRF)

Where the browser supports the WebAuthn PRF extension, the app creates a platform passkey and asks it for a 32-byte secret bound to a fixed salt. That secret, through HKDF, becomes an AES-256-GCM key that seals the seed on the device. Unlocking asks the passkey for the same secret.

Support depends on the browser and the passkey provider. Recent Chrome on Android (Google Password Manager) and Safari on iOS 18+ return PRF results. When a browser doesn't, the app falls back to the passphrase and tells you.

The backup file

The backup file is JSON with the seed sealed twice: once under scrypt(passphrase, N=2^17, r=8, p=1) with AES-256-GCM, and once under the passkey key if there is one. The app saves it through the share sheet. The file alone is useless without the passphrase or the passkey.

The funding account (app-level)

The app also derives an ordinary Sei EVM account for deposits and refunds:

entryKey = HKDF-SHA256(seed, salt="batin/app/v1/entry", info="evm:0", L=32)

This is an app convenience, not part of the protocol. It is public by nature, and every deposit from it is linked to it. Withdrawing back to it links your deposit and your withdrawal.

Source: apps/web/content/docs/addresses-and-keys.md