Social Tasks

Social tasks are off-chain jobs run across burner accounts: Google Forms, X/Discord tasks, signup flows, allowlist forms, and curated quest submissions. They do not touch a chain directly.

What You Need#

• Accounts - each account can hold wallet address, Gmail, X handle/cookies, Discord username, and an assigned proxy.
• Captcha Solver - only needed for modules with hCaptcha, Turnstile, or reCAPTCHA v2/v3 fields. Configure a supported provider and API key in Settings.
• Browser session - only needed when a Google Form or browser-engine module needs a real logged-in session.

A Quick Sketch#

The panel below is a simulation of the Social Task dialog. Pick a module, run it, and watch each account resolve on its own — that per-account fan-out is the thing worth understanding before you run a real one. Nothing here touches the network.

Google Forms#

Build from a Google Form

6 steps

1. 1

   Step 1

   Open a social task group

   Groups keep related tasks together and decide which accounts are in scope.

2. 2

   Step 2

   Click +New Social Task

   This button is always the Google Forms builder. Modules start somewhere else — see below.

3. 3

   Step 3

   Paste the Google Forms URL

   The app first tries to parse the form anonymously. If Google gates the form, it falls back to a connected Google account from the selected account group.

4. 4

   Step 4

   Choose the account group

   Every account in the group gets its own task.

5. 5

   Step 5

   Map each question

   The parser renders the questions so you can point each answer at an account field, a fixed value, a random choice, or auto-fill where supported.

6. 6

   Step 6

   Save

Paste a Google Forms URL and choose an account group. The app first tries to parse the form anonymously. If Google gates the form, it falls back to a connected Google account from the selected account group. When the form needs Google session submission, the runner uses each row’s account session when it fires.

The parser renders the questions so you can map answers from account fields, fixed task values, random choices, or auto-fill behavior.

Social Modules#

Build from a social module

6 steps

1. 1

   Step 1

   Open Home

   Modules live in the Home Modules panel, not behind +New Social Task.

2. 2

   Step 2

   Pick a social module

   The dialog opens locked to the module you clicked and renders that module’s fields.

3. 3

   Step 3

   Choose the account group
4. 4

   Step 4

   Fill the fields the module exposes

   The module author picks the engine and the fields — you only fill what’s shown.

5. 5

   Step 5

   Pick a captcha solver if the module needs one

   Modules with hCaptcha, Turnstile, or reCAPTCHA v2/v3 fields need a provider and API key in Settings, or the dialog blocks.

6. 6

   Step 6

   Save

Social modules are not picked from the normal +New Social Task button. Start them from the Home Modules panel. The dialog opens locked to that module and renders the module’s fields.

Modules are descriptors published by the team. They can run through:

Engine	Used for
http	Plain API or form requests
browser	Sites that need real browser cookies, TLS fingerprinting, or Cloudflare challenge handling

The module author picks the engine. You fill only the fields the module exposes.

Account Isolation#

Each social task uses one account:

• account profile fields such as wallet, X handle, Discord username, and Gmail
• that account’s assigned proxy
• that account’s browser profile when browser execution is needed

Tasks without the required account field are skipped or failed with a clear message in the row log.

Captcha Handling#

Captcha fields are declared by the module. At run time the tasks looks up the selected solver provider and API key from Settings, solves the challenge, and injects the returned token into the request template.

If a module has captcha fields and no solver is configured, the dialog blocks or the row fails with a solver setup error.