Bounty campaign

Bring a Task, Build a Habit

Bring a Task, Build a Habit is a Verdikta bounty campaign. Creators fund tasks. Hunters complete them. Selected milestones are checked by a campaign verifier when you claim the quest on Zealy.

You can read this page without logging in, joining Discord, connecting a wallet, or signing anything.

These dates are the planned window. The campaign has 16 quests, and they are not published yet. A configured start date does not mean the campaign is live or that rewards are funded.

Open BountiesOpen the Zealy quest board

How claims work

Activity has to finish before the activity cutoff. Claiming during the grace period does not make a late transaction eligible.

Start
2026-10-14T12:00:00Z
Activity cutoff
2026-11-04T12:00:00Z
Claim and correction cutoff
2026-11-07T12:00:00Z
  • Bounties pay ETH on Base. LINK is not required for this workflow.
  • Use the same ordinary EOA wallet for Zealy authentication and for the funding or submission activity on Base. A relayer, a different funding wallet, or a smart-wallet owner address is a different account for this check.
  • Creators fund bounty rewards. Hunters separately cover evaluation prepayment and gas.
  • Required activity must happen at or after the start and before the activity cutoff. That window is 21 days. The Eastern clock changes from EDT to EST during the campaign; the UTC instants above preserve the window.
  • The following 72 hours, through the claim and correction cutoff, are for claiming and for correcting a claim. A bounty created, submitted, settled, or paid at or after the activity cutoff stays ineligible.
  • Allow about 30 minutes after the relevant chain event for indexing. If the verifier still says the claim is pending, wait five minutes and claim again from Zealy.
  • A passing or creator-approved submission still needs to be the winning paid result before a payment milestone counts. Deferred payments count after the hunter withdraws them.
  • Cash bonuses are limited and first come, first served. Verification does not reserve cash. XP remains available after cash rewards fill.
  • Cash bonuses are credited to your Zealy account in USDC and withdrawn to the Polygon wallet address set in your Zealy profile; it can be your Base address or a different one, and a change takes about 48 hours to take effect, so set it early. The minimum withdrawal is 1 USDC. Zealy deducts a 5% fee plus a network fee of about $0.10 per withdrawal, so a $5 bonus arrives as roughly $4.65; Zealy's withdrawal screen shows the current figures before you confirm. Bonuses do not cover gas, evaluation deposits or withdrawal fees, and ETH price moves change their value.

Eligibility

This checklist covers the milestones the campaign verifier checks. Other quests on the board follow the instructions written on those quests. When you contact support, include the quest title shown on Zealy.

Qualifying bounties

  • The bounty is on the campaign's current deployment and uses open eligibility, so it is not targeted at a single hunter.
  • The original submission window, deadline minus creation time, is from 4 to 336 hours, including both ends. 48 hours is the recommended window. The 72-hour rule below is the gap between repeat tasks, separate from this submission window.
  • The campaign minimum is 0.0041 ETH, fixed in ETH at launch (about $10). The check uses the ETH funded when the bounty was created.
  • The bounty carries a valid evaluation package: the task, a rubric with at least one criterion, and a passing score. Bounties created on the website meet this automatically; a package built by hand or by an agent must contain the same parts.
  • You are not the hunter on your own bounty. A self-payment does not count.

New means new to the campaign's current deployment: the Verdikta bounty contract on Base that went live on September 12, 2026. It does not mean this is your first time using Verdikta, and activity on earlier Verdikta contracts does not count against you. Creator newness looks for a bounty created on this deployment before the start. Hunter newness looks for a submission prepared on this deployment before the start. A wallet on the campaign's prior-wallet list is also excluded. Do not open a second wallet to work around that rule.

Verdikta agents are team-operated agents that fulfil external bounties. An approved Verdikta agent can complete paid work for an external creator, and that payment can count toward the creator's paid milestone. Team wallets, including Verdikta agents, cannot claim campaign rewards.

Standard bounties qualify automatically for Q4, Q6 and Q10 when they meet the campaign's funding, window, evidence, identity and payment requirements. Create a bounty with your own rubric on the website; no template, API use, preflight or manual cash approval is required. Only Q14 and Q15 require approved template work orders. Flagged bounties or wallets may still be held or excluded after an abuse review.

Agent operators: if an agent does the work for you, its wallet is your campaign wallet. Link that same address to Zealy by importing the agent's key into your browser wallet once. MetaMask imports an encrypted JSON keystore (for example the OpenClaw onboarding skill's verdikta-wallet.json) with its password, or a private key. Linking and claiming only sign messages, so the agent keeps sending the transactions. Smart-account agents (Coinbase Smart Wallet and similar) can deliver work that pays creators, but cannot claim: the escrow records the smart account and Zealy cannot authenticate it.

Quest checklist

Q3Creator

Fund one qualifying bounty. Standard bounties count. A later refund still leaves this posting credit in place.

Q4Creator

Be a new creator on the current deployment. Standard bounties and template work orders qualify automatically under the same campaign checks. Pay an eligible hunter during the activity window. An approved Verdikta agent can be that hunter.

Q5Creator

Create two qualifying bounties with different task scopes. Standard bounties count. Create the second bounty at least 72 hours after the first, and only after the first bounty has paid a hunter.

Q6Creator

Meet the Q5 pair. Both bounties qualify and are paid; standard bounties count automatically. Be a new creator on the current deployment. The winners are two different wallets, unless the same approved Verdikta agent wins both.

Q8Hunter

On a qualifying bounty, submit a valid work package and receive a completed passing evaluation or creator approval during the campaign. Standard bounties count. Payment is not required.

Q9Hunter

Meet Q8 and be the hunter who is actually paid during the activity window. Structurally valid standard bounties count automatically.

Q10Hunter

Be a new hunter on the current deployment. Receive a completed passing evaluation or creator approval on two qualifying bounties from two different creators, with different task scopes and at least 72 hours between the submission times. At least one of those bounties must actually pay you. The second creator cannot be a team wallet. Standard bounties count automatically; both bounties, including the earlier Q9 bounty, must meet all campaign checks.

Q12Zealy

Invite someone to the Verdikta quest board. Your invite counts once the person you invited completes Q4, so they need to be a new creator whose bounty pays an eligible hunter. This quest is XP only, and Zealy tracks it itself.

Q14Creator

Fund an approved template work order. A later refund still leaves this posting credit in place. A standard bounty does not satisfy this template-only quest.

Q15Creator

Meet the Q5 pair with two different approved templates, one per bounty. Two work orders from the same template do not count, and a standard bounty does not satisfy this template-only quest.

Verifier error codes

Zealy shows a sentence followed by a code in brackets. Search or browse by the next action: wait and retry, correct your wallet or task, or contact support.

Showing 28 of 28 codes.

Claim succeeded

[VERIFIED]

Claim succeeded

Verified: you completed this campaign milestone. [VERIFIED]

What to do. Zealy can record this milestone. Cash is still first come, first served, and this result does not reserve a cash reward. XP remains available after cash rewards fill.

Wait and retry

[VERIFICATION_UNAVAILABLE_RETRY]

Wait and retry

Not verified yet: the verification service is unavailable. Please retry later. [VERIFICATION_UNAVAILABLE_RETRY]

What to do. Wait five minutes, then claim again from Zealy. Contact support only if the same code continues after that.

[INDEX_NOT_READY_RETRY]

Wait and retry

Not verified yet: confirmed blockchain data is not current. Please retry later. [INDEX_NOT_READY_RETRY]

What to do. Wait about 30 minutes after the on-chain event, then claim again. If it is still pending, wait five minutes and retry.

[EXCEPTIONS_FILE_INVALID]

Wait and retry

Not verified yet: campaign exception settings need operator attention. Please retry later. [EXCEPTIONS_FILE_INVALID]

What to do. Wait and claim again later. This hold is on campaign settings. Contact support if the same code is still there after another try.

[CAMPAIGN_NOT_STARTED]

Wait and retry

Not verified yet: the campaign has not started. [CAMPAIGN_NOT_STARTED]

What to do. Wait until the start time in How claims work. Also check the launch status at the top of this page, because the quests can still be unpublished after that time.

[WALLET_HELD_FOR_REVIEW]

Wait and retry

Not verified yet: this wallet is held for an operator review. [WALLET_HELD_FOR_REVIEW]

What to do. Wait for the review. You can contact support with your public wallet address to ask for status. The message does not clear the hold or approve a claim.

[HISTORY_INCOMPLETE_RETRY]

Wait and retry

Not verified yet: current-deployment history is still being reconciled. Please retry later. [HISTORY_INCOMPLETE_RETRY]

What to do. Wait and claim again later. The campaign is still reconciling history on the current deployment.

[NO_MATCHING_CHAIN_ACTIVITY]

Wait and retry

Not verified yet: no qualifying activity was found for this wallet on the campaign deployment. [NO_MATCHING_CHAIN_ACTIVITY]

What to do. Confirm that the Zealy wallet is the address that funded or submitted on Base. If that transaction is recent, wait about 30 minutes, then claim again. If it is still pending, wait five minutes and retry.

[EVIDENCE_UNAVAILABLE_OR_INVALID]

Wait and retry

Not verified yet: the original evaluation or submission evidence could not be validated. Retry or contact support. [EVIDENCE_UNAVAILABLE_OR_INVALID]

What to do. Wait five minutes and claim again. If the code remains, contact support with the bounty URL and confirm the work package is complete. A support message does not approve the bounty.

[PAYMENT_NOT_RECEIVED_IN_WINDOW]

Wait and retry

Not verified yet: your bounty has not paid an eligible hunter inside the campaign window. Retry after settlement. [PAYMENT_NOT_RECEIVED_IN_WINDOW]

What to do. Wait until an eligible hunter is actually paid, then claim again. A passing submission is not payment. A deferred payment counts after the hunter withdraws it, and that withdrawal must fall before the activity cutoff.

[PASSING_PACKAGE_PENDING]

Wait and retry

Not verified yet: a valid submitted work package and completed passing result are required. [PASSING_PACKAGE_PENDING]

What to do. Submit a valid work package and wait until a completed passing evaluation or creator approval is recorded. Then allow about 30 minutes for indexing and claim again.

[MILESTONE_NOT_MET_OR_PENDING]

Wait and retry

Not verified yet: the required campaign milestone is incomplete. [MILESTONE_NOT_MET_OR_PENDING]

What to do. Compare the quest with Eligibility and finish the missing requirement. If the on-chain step just happened, wait about 30 minutes and claim again.

Correct your wallet or task

[INVALID_REQUEST]

Correct your wallet or task

Not verified: the verification request is invalid. Reconnect your wallet and retry. [INVALID_REQUEST]

What to do. In Zealy, reconnect the same wallet you used on Base, then start the claim again.

[CAMPAIGN_NOT_ALLOWED]

Correct your wallet or task

Not verified: this quest or community is not configured for this campaign. [CAMPAIGN_NOT_ALLOWED]

What to do. Claim from the Verdikta quest board linked on this page. A quest from a different Zealy community will not verify. If you are already on that board and claiming the right quest, contact support with the quest name, because the quest may not be configured yet.

[AUTHENTICATED_WALLET_REQUIRED]

Correct your wallet or task

Not verified: connect and authenticate your wallet in Zealy. [AUTHENTICATED_WALLET_REQUIRED]

What to do. In Zealy, connect and authenticate the same ordinary wallet that funded or submitted the bounty, then claim again.

[REQUEST_ID_REUSED]

Correct your wallet or task

Not verified: this request identifier was already used for different claim details. Retry from Zealy. [REQUEST_ID_REUSED]

What to do. Open the quest in Zealy and start a new claim. Retrying the old request keeps this code.

[CLAIM_WINDOW_CLOSED]

Correct your wallet or task

Not verified: the campaign claim and correction window has closed. [CLAIM_WINDOW_CLOSED]

What to do. This claim window is closed. Activity has to occur before the activity cutoff. A later claim cannot make that activity eligible.

[TEAM_WALLET_EXCLUDED]

Correct your wallet or task

Not verified: team wallets are excluded from these campaign claims. [TEAM_WALLET_EXCLUDED]

What to do. Team wallets cannot claim these rewards. An approved Verdikta agent can still complete paid work that counts for an external creator. If this is your personal wallet, contact support with the public address.

[PRE_CAMPAIGN_ACTIVITY]

Correct your wallet or task

Not verified: this wallet has prior activity on the current deployment or the configured prior-wallet list. [PRE_CAMPAIGN_ACTIVITY]

What to do. This wallet is not new to the current deployment, or it is on the campaign prior-wallet list. New means new to this deployment. Do not open a second wallet to work around the rule. Contact support only if you believe the history is wrong.

[DUPLICATE_SCOPE_REVIEW]

Correct your wallet or task

Not verified: campaign bounties share the same task scope. Contact support if this is unexpected. [DUPLICATE_SCOPE_REVIEW]

What to do. Campaign bounties need genuinely different tasks. Rewording the same task does not create a new one. If your bounties really are different tasks and this code remains, contact support with both bounty URLs.

[SUBMISSION_WINDOW_OUT_OF_RANGE]

Correct your wallet or task

Not verified: the bounty submission window is outside the campaign duration limits. [SUBMISSION_WINDOW_OUT_OF_RANGE]

What to do. Create a bounty whose original submission window is from 4 to 336 hours. 48 hours is the recommended window. The claim time does not change a window that was set at creation.

[MINIMUM_ORIGINAL_FUNDING_NOT_MET]

Correct your wallet or task

Not verified: the original bounty funding is below the campaign minimum. [MINIMUM_ORIGINAL_FUNDING_NOT_MET]

What to do. The campaign checks the ETH funded when the bounty was created, not a later top-up or the remaining balance. If that original amount met the launch minimum shown in Eligibility, contact support with the bounty URL before spending more. If it did not, only a new bounty funded at or above the minimum can qualify.

[APPROVED_WORK_ORDER_REQUIRED]

Correct your wallet or task

Not verified: this template quest requires an approved work order. [APPROVED_WORK_ORDER_REQUIRED]

What to do. For Q14 and Q15 only, use an approved template work order. Standard bounties qualify for the other product milestones under their normal checks.

[BOUNTY_REFUNDED]

Correct your wallet or task

Not verified: the bounty was refunded before this milestone was completed. [BOUNTY_REFUNDED]

What to do. This milestone needed the bounty to stay funded through completion. Posting credit on Q3 or Q14 can still be claimed when that quest allows a refund. A payment milestone needs a bounty that was not refunded first.

[REPEAT_TIMING_SCOPE_OR_OUTCOME_NOT_MET]

Correct your wallet or task

Not verified yet: the required distinct repeat task, timing, or paid outcome is missing. [REPEAT_TIMING_SCOPE_OR_OUTCOME_NOT_MET]

What to do. Check Eligibility for the 72-hour spacing, the distinct task scope, and the paid outcome that quest requires. Finish the missing piece, wait for indexing, then claim again.

Contact support

[AUTHENTICATION_FAILED]

Contact support

Not verified: the campaign connection could not be authenticated. Contact the campaign operator. [AUTHENTICATION_FAILED]

What to do. Contact support with this code, the quest, and your public wallet address. A support message does not approve the claim.

[IDENTITY_REVIEW_REQUIRED]

Contact support

Not verified: this user or wallet is already linked to another campaign identity. Contact support. [IDENTITY_REVIEW_REQUIRED]

What to do. Contact support. Include the quest and the public wallet address. Support will not ask for a seed phrase, private key, or wallet signature, and the message does not approve the claim.

[BOUNTY_DENIED]

Contact support

Not verified: the relevant bounty is excluded by a reviewed campaign exception. [BOUNTY_DENIED]

What to do. Contact support if you believe this bounty was excluded by mistake, and include the bounty URL. A support message does not reverse the exclusion.

Contact support

A support request does not approve a bounty or a claim. For wallet details, include only your public address.

What to include

  • Quest name or number
  • Bounty URL or ID
  • Public wallet address
  • Exact bracketed verifier error code
  • A short description of the problem

What to leave out

  • A seed phrase
  • A private key
  • A wallet signature
Email campaign support

Response times and review expectations

Most requests are answered within 24 hours.

Eligibility is automatic. There is no preflight or per-bounty cash-approval queue. Support handles flagged abuse cases, holds and appeals; a support request does not reserve cash or extend a deadline.