Quest Marketplace — For Sponsors & Creators

The Quest Marketplace lets brands, protocols, and community creators run campaigns — configured quests that drive qualified players to take a real action (join your channel, swap on your protocol, learn about your product) and reward them automatically.

This guide covers how a campaign is built, approved, funded, and measured. For the hands-on, step-by-step walkthrough of the Campaign Builder UI, see the Creator Studio guide.

Sponsors vs. creators

Anyone can run a campaign. The difference is mostly attribution and review:

• Sponsor campaigns belong to a registered Sponsor — a brand, protocol, creator, or partner profile with a slug, name, logo, and links. Sponsor-funded campaigns always go through human review before going live.
• Creator campaigns are run directly by a community member (e.g. a guild owner). Low-risk recurring quest types can auto-publish without review.

Register a sponsor with a unique slug, a display name, a kind (Brand / Protocol / Creator / Partner), and optional logo and website. New sponsors start in a pending state until approved.

Provider types

A campaign is built on a provider — a reusable action archetype. You pick a provider and supply its configuration; the provider generates the player-facing steps and the verification each step requires. The first-party providers are:

Each provider declares which reward kinds it can grant and which verification methods it uses, and whether it is auto-approvable. For example, social.telegram-join and learn.quiz are auto-approvable; onchain.swap always requires review.

Example configurations

Join a Telegram channel (social.telegram-join):

{
  "chatId": "-1001234567890",
  "chatTitle": "DegensQuest Announcements",
  "inviteLink": "https://t.me/DegensQuestAlerts",
  "rewards": [
    { "kind": "XP", "amount": "250" },
    { "kind": "BADGE", "ref": "early-supporter", "rarity": "RARE" }
  ]
}

Complete a swap on Base (onchain.swap):

{
  "protocolName": "Uniswap on Base",
  "chainId": 8453,
  "routerAddress": "0x…",
  "minAmountBaseUnits": "10000000000000000",
  "connectReward": [{ "kind": "XP", "amount": "100" }],
  "rewards": [
    { "kind": "PARTNER_TOKEN", "amount": "5000000000000000000",
      "tokenAddress": "0x…", "chainId": 8453, "label": "5 PARTNER" }
  ]
}

Configuration is validated against the provider’s schema on every save and again before the quest can go live, so a misconfigured quest can never reach players.

Building a campaign

A campaign moves through a clear lifecycle:

DRAFT → PENDING_APPROVAL → APPROVED → ACTIVE
         (auto-published for low-risk providers)
ACTIVE ↔ PAUSED → ENDED → ARCHIVED      REJECTED (sent back to edit)

1. Create a draft. Choose a provider, write a title and description, pick a category, tier, difficulty, and estimated time, and supply the provider config. You set:
   • Budget and daily budget — the spend caps for the campaign.
   • Max completions — an optional hard cap on how many players can finish.
   • Targeting — optional eligibility/targeting rules.
   • Banner, start date, and end date.
2. Edit freely while in DRAFT (or after a rejection). Once submitted, the config is locked.
3. Submit for approval. Low-risk, auto-approvable creator quests publish straight to ACTIVE. Everything else enters the review queue as PENDING_APPROVAL.
4. Review decision. A DegensQuest admin/moderator approves (→ ACTIVE) or rejects (→ REJECTED, with a reason, so you can fix and resubmit).
5. Manage the live campaign. As the owner you can pause, resume, end, or archive it at any time.

Approval gating (hard rule): sponsor-funded campaigns and any higher-risk provider always require human approval. Only low-risk recurring quest types are eligible for auto-publish.

Funding rewards & escrow

How a reward is funded depends on its kind:

• Platform rewards (XP, Battle Pass XP, QUEST, in-game items, guild reputation) are granted by the platform and drawn against your campaign budget.
• Partner rewards that carry real external value — partner tokens, partner NFTs, and whitelist spots — must be pre-funded into on-chain escrow. When a player completes the quest, the engine records a claim and a release against your campaign’s escrow; the on-chain escrow contract settles the actual transfer against a verified claim. Releases are idempotent, so a completion is never paid twice.

This means a player can only ever claim a partner reward your campaign has actually funded — there’s no way to over-promise.

The sponsor & creator dashboard

Every campaign reports a full conversion funnel and cost metrics:

You get three views:

• Sponsor dashboard — aggregate totals plus a per-campaign funnel across all of a sponsor’s campaigns.
• Creator dashboard — the same funnel for your own quests, plus your active boost stake.
• Per-campaign analytics — the funnel, an enrollment-status breakdown (Active / Completed / Failed / Expired), reward-claim counts, your current boost score, and provider-specific stat keys (quest starts, step completions, completions, step fails).

Use CPA and the start→complete funnel to tune budget, reward size, and difficulty: a high start rate but low completion rate usually means a step is too hard or its instructions aren’t clear.

Anti-fraud & integrity

• Verification, not honor system. Every step is proven by a dedicated adapter (chain RPC, Telegram API, quiz key, etc.). Players can’t self-attest completion.
• Risk scoring. Each attempt can surface risk signals (e.g. duplicate wallet, suspicious network) that accumulate into a risk score and can route an enrollment to manual review.
• Exactly-once payouts. Rewards and escrow releases are idempotent and logged append-only, so a campaign’s spend always reconciles to real, verified completions.
• Review queue. Admins can review enrollments, verifications, reward claims, campaigns, and sponsors before value moves.

Ready to launch?

1. Register your sponsor profile (or run as a creator).
2. Create a draft campaign on the provider that fits your goal.
3. Fund the budget — and the escrow if you’re offering partner rewards.
4. Submit for approval and go live.
5. Watch the dashboard and iterate.

Questions or partnership ideas? Reach the team via t.me/DegensQuestEntry or @DegensQuest. For the step-by-step builder walkthrough see the Creator Studio guide, or for the player’s perspective see For Players.