Identity & Authentication

ZDrive does not use accounts, passwords, or usernames. Your wallet is your identity. To start a session, you sign a message containing your address and a session UUID. The worker verifies the signature and grants access scoped to that session.

Auth message format

ZDriveX Auth
Address: 0x{your_address_lowercase}
Session: {uuid_v4}
This signature verifies wallet ownership and does not authorize any transactions.

The session UUID binds the signature to the current browser session only. If an attacker intercepts your signature, they can only replay it within that specific session — not across sessions. The UUID is discarded when you close the app.

Verification flow

ERC-1271 support

ZDrive uses viem's verifyMessage() which handles both standard EOA wallets (ECDSA signature recovery) and smart contract wallets (ERC-1271 isValidSignature on-chain call). This means Coinbase Smart Wallet, Safe, and other account abstraction wallets work out of the box — no separate code path needed.

Why not just ECDSA recovery? Smart contract wallets like Coinbase Smart Wallet do not have a private key that produces a recoverable ECDSA signature. They use ERC-1271 instead. Calling recoverMessageAddress on a smart wallet signature silently returns a wrong address, which would block all smart wallet users without ever surfacing an error.

Session lifecycle