Burner accounts
Burner accounts power the social-task subsystem. One social task fans out across multiple accounts (1 account = 1 row, mirroring the 1 wallet = 1 task pattern on onchain).
You only need this page if you plan to use social tasks. Onchain mints don’t touch it.
What gets stored per account
| Field | What it’s for |
|---|---|
| Name | Free-form label. |
| Discord token | The user token (NOT the bot token). Used by Discord-side quest sites. |
| Discord cookies | Optional. Some quest sites need the browser session, not just the token. |
| Gmail address + cookies | The signed-in Google session. Powers Google-Forms tasks. |
| X (Twitter) token + cookies | auth_token + ct0. Used for X-gated quests + posting. |
| Wallet | Optional. Pin a wallet from your Wallets page to this account so the social-task descriptor’s {wallet} token resolves automatically. |
| X handle | Free-form. Renders into {xhandle} tokens. |
| Discord handle | Same idea. Renders into {discord} tokens. |
| Email handle | Renders into {email} tokens. |
| Proxy | Optional. Pin a proxy from your Proxies page to this account. |
Bulk Connect
For pasting in 50 burners at once. The dialog accepts CSV-style input:
name,discord_token,gmail,x_token,wallet_addralice,MTI...,alice@gmail.com,abc123...,0xdeadbeef...Headers are auto-detected; missing columns are left blank.
Test buttons
Per-row Test buttons run a live auth probe:
- Discord: calls
/users/@me. Green chip + display name on success. - Gmail: spins up a headless Chromium session against the Google account picker (per-account profile dir, no cross-contamination).
- X: calls
/2/users/mewith the bearer/cookie pair.
The chip is live status — re-run the test before each social-task batch if you care about pre-flight reliability.
Where accounts live
%LOCALAPPDATA%\zyper-suite\data\accounts.dat, DPAPI-encrypted. Tokens and cookies
are gibberish to anyone else on your machine.
Each account also gets its own headless Chromium profile dir under
%LOCALAPPDATA%\zyper-suite\browser\<account-id>\ for sites that need the
full browser session (Google login, Cloudflare-WAF gated POSTs).
Picking a captcha solver
Social tasks against captcha-gated sites need an API key — set this on the Settings page. Supported:
- 2captcha — pay-per-solve, both Turnstile and reCAPTCHA-v2.
- capsolver — also pay-per-solve, often faster on Turnstile.
Both routes are wired into the same internal solver interface, so swapping keys is the only switch you need.