Skip to main content
Zonk.fun uses Privy authentication with wagmi and viem on Base Mainnet. You can continue with Google, X/Twitter, or an external EVM wallet.
  1. Select Log in on zonk.fun.
  2. Choose Google, X/Twitter, or wallet login.
  3. If you use Google or X and do not already have a linked wallet, Privy creates a user-controlled embedded EVM wallet for you.
  4. If you use an existing wallet, select Rabby, MetaMask, another detected EVM wallet, or WalletConnect and approve the connection in that wallet.
  5. Switch the active wallet to Base if prompted.
  6. Confirm that the account control and transaction review show the address you intend to use.
The selected active wallet is the signer. If more than one wallet is linked, open the account menu and choose the intended signer before reviewing a transaction. Switching wallets updates the displayed address, balances, quotes, and wagmi wallet client together. Embedded and external wallet transactions both require user approval. Zonk.fun does not ask for, store, or control a seed phrase or private key, and its backend cannot sign on a user’s behalf.
Never enter a seed phrase or private key into Zonk.fun, its documentation, a support message, or a transaction form. A legitimate external-wallet flow asks for approval in the wallet; an embedded-wallet flow uses Privy’s user-controlled signing UI.

​
Privy Dashboard setup

The project administrator must enable Google, Twitter, and wallet login in the Privy Dashboard. Configure these allowed origins:
  • production: https://zonk.fun
  • local development: http://localhost:3000
No canonical www production domain is currently used by this project, so do not add one unless that deployment becomes canonical. Production Google and Twitter login should use project-owned OAuth provider credentials when available. NEXT_PUBLIC_PRIVY_APP_ID is public browser configuration; Privy client secrets and OAuth secrets must remain outside the frontend and repository. See Wallet safety for transaction-checking guidance.