Connect Wallet
Spreadr uses Privy (opens in a new tab) for wallet authentication. Your wallet address IS your account — no email, no password, no separate signup flow.
Sign in
Visit the app
Open app.spreadr.xyz (opens in a new tab). If you don't have a session, you'll see the Privy login modal.
Connect your wallet
Privy supports MetaMask, WalletConnect, Coinbase Wallet, Rainbow, and most EVM wallets. Click the one you use.
Sign the message
Your wallet will prompt you to sign a Sign-In-With-Ethereum (SIWE) message. This is a free signature — no on-chain transaction, no gas.
Done
Spreadr verifies the signature and creates your session. You're in.
How your identity works
Your wallet is how you sign in — it isn't your account. Your account exists independently, which means you can link additional wallets (see below) or rotate your primary wallet without losing trades, history, or credentials.
Link additional wallets
Spreadr supports multiple wallets per account. Each must prove ownership cryptographically — you can't add a wallet you don't control.
Navigate to Settings → Wallets
The current primary wallet is marked. Click + Add Wallet.
Switch to the wallet you want to link
Spreadr links whichever account is currently active in your wallet extension — switch to the new address there first, then click Link Wallet.
Sign the linking message
You'll sign a short message proving you control the wallet. Once verified, the wallet is associated with your account.
Why multiple wallets? Common reasons: separate trading wallet per venue (especially helpful for rate-limit isolation), separate cold/hot wallets, delegated wallets for ops or partners.
Sign out
In the top-right corner of the terminal, click your wallet address → Disconnect. This ends the session on this device only; sessions on other devices are unaffected.
Privy connection issues
If sign-in fails or seems to loop:
- Clear site data — DevTools → Application → Clear site data → reload.
- Try a different wallet client — some wallet browser extensions don't handle SIWE cleanly.
- Network problems — Privy
auth.privy.iomust be reachable from your browser. Corporate networks sometimes block it.
If the problem persists, see Troubleshooting.