Writing a task farmers can complete

A task is one action with one reward. The kind you choose decides how the platform confirms a farmer actually did it — and nothing waits for you to approve it.

📷 Screenshot placeholder — Tasks → New task, the Kind dropdown showing Social and Custom (app signup).

What a task is

A task is one action a farmer does for your project in exchange for points. Farmers see it under My Tasks, do the action, and the points land in their balance for the project's current season — the balance the leaderboard ranks and, on a token launch, the one that converts to tokens.

Tasks exist only on community projects and community-season token projects; an InstantLaunch project has no season, so the form will not create one there. Farmers can complete a task only while a season is open and once their email is verified.

Two kinds exist, and the kind cannot change after the task is created.

A social task asks for an action on a platform the farmer has connected: X, Telegram, Discord or LinkedIn. The actions depend on the platform:

X — follow, retweet, like
Telegram — join
Discord — join
LinkedIn — follow, repost, comment, like

The Verification control offers three modes; the server only accepts the ones that fit the action.

Auto (API) — the platform checks the provider before crediting. This exists for exactly three actions: a Telegram join, a Discord join and an X follow. Pick any other action and the server refuses automatic mode, because nothing can check it.
Self-attest — the farmer pastes a link as evidence: their profile link for a follow or a like, or the post link for a retweet, repost or comment. The link is checked for shape — the right site, a post link where a post is expected — and the completion is credited straight away. The proof is kept on the entry for you to look at later.
Manual review — despite the label, nothing is held for review. The farmer submits and is credited straight away, with no proof captured. Use it only for actions you take on trust.

📷 Screenshot placeholder — the Verification dropdown after choosing Auto (API) for an X like.

Custom tasks

A custom task — Custom (app signup) in the form — is anything you can confirm yourself: an app install, a sign-up, a purchase. The platform does not know what "done" means for your product, so it asks you.

You give the platform an https verification endpoint and choose the identifier it receives: the farmer's email address or wallet address.
On submit the platform POSTs a JSON body of taskId, identifier and identifierType, signed with your business unit's webhook secret: the header x-dappfactory-signature: t=<timestamp>,v1=<hex> is an HMAC-SHA256 of <timestamp>.<body>. Check it before you trust a call.
Reply within eight seconds with { "verified": true, "active": true } to credit the farmer. Anything less is "not yet": the platform retries with growing gaps for up to 48 hours (at most ten attempts) while the farmer sees the task as verifying, then credited or expired. A 4xx reply stops the retries.
The endpoint must be a public https address; redirects are not followed. A custom task cannot be paid, and its completion cap is set by the platform team.

The webhook secret is revealed and rotated from Settings, not the task form. Rotating it invalidates the old one at once, so update your endpoint first.

📷 Screenshot placeholder — the Custom step with the Verification endpoint and Identifier fields.

The target

The target is what the farmer opens: a handle, post or channel link for a social task; your app, store page or form for a custom one. It is also what the verifier checks against, so a wrong handle fails for every farmer at once. Open it yourself before you publish.

Reward and cap

Reward is the points a farmer earns per completion. Points are not drawn from a fixed budget — every completion issues new points. What is fixed is the season's token allocation: the end-of-season rate is the lower of the platform ceiling and allocation divided by total points, so the more points a season issues, the fewer tokens each is worth.

Completion cap limits the total number of times the task can pay across all farmers; leave it blank for unlimited. Each farmer can complete a task once whatever the cap says.

Paid tasks

Attach a commission and the task becomes paid: the farmer pays that commission's fee on-chain before the points are credited, and the commission's formula splits it between the platform, your affiliate network and you. Only an active commission for the task resource can be attached, and a custom task cannot be paid.

After it goes live

A live task is visible to every farmer immediately, and completions arrive straight away. Everything except the kind and the project can be edited later; deactivating hides a task without touching credited completions, and your tasks are never deleted. If the action cannot be verified automatically, decide whether self-attest or manual is the honest choice.