Creator Studio — Create a Quest

The Creator Studio is the self-serve home for building and running quests. You register an identity, build a quest with the Campaign Builder, fund its rewards, ship it through approval, and then manage and promote it — all from one place.

This page is the hands-on walkthrough. For the conceptual model (providers, escrow, anti-fraud, the analytics funnel), read For Sponsors & Creators alongside it.

Where the Studio lives

The Studio is available on both clients, backed by the same live endpoints:

You must be signed in. Signed-out (or non-Telegram) sessions see a prompt to authenticate first.

Step 0 — Become a sponsor or creator

There are two ways to run a quest, and you choose simply by whether you attach a sponsor profile:

• Creator quest — run directly under your own account, with no sponsor profile. Low-risk, auto-approvable quest types can publish without review.
• Sponsor quest — run under a registered Sponsor identity. Sponsor-funded campaigns always route through admin approval.

Registering a sponsor

In the Studio’s Sponsor profiles panel, choose Register and provide:

• Slug — your unique handle (lowercase letters, numbers, and dashes; e.g. acme-protocol).
• Name — the display name shown on the quest card.
• Kind — one of Brand, Protocol, Creator, or Partner.
• Website, Logo URL, and Description — all optional.

New sponsors start in a pending state until an admin approves them. Once a profile exists, its row has a New quest → link that launches the builder pre-attached to that sponsor.

The five-step Campaign Builder

Creating a quest walks through five steps, each gated by exactly the validation the API enforces — you cannot advance a step until its inputs are valid, and a misconfigured quest can never reach players.

Provider → Configure → Details → Budget → Review

Step 1 — Provider

Pick the quest type. Each provider defines its own steps, verification, and which rewards it can grant. The first-party providers are:

Each card is badged Auto (auto-approvable) or Review (always reviewed). The provider is locked once the quest is created — it can’t be changed later, so pick the archetype that fits your goal.

Step 2 — Configure

Supply the provider’s configuration. The fields differ per provider (see Provider configuration below), plus a couple of shared inputs:

• Banner asset key — optional artwork reference for the quest card.
• Rewards — one or more reward lines built with the reward editor (see Reward types). Each provider declares which reward kinds it allows.
• For learn.quiz, a quiz answer key — one correct answer per question, order-sensitive. Only a non-reversible hash of the answers is ever stored; when editing later, you leave the fields blank to keep the existing key or re-enter every answer to replace it.

Step 3 — Details

How the quest reads in discovery:

• Title and Description (each at least 3 characters).
• Category, Tier, and Difficulty — pre-filled from the provider’s defaults, editable here.
• Estimated minutes — how long the quest takes.

Step 4 — Budget & targeting

All amounts are in base units (whole-number, wei-scale integers).

• Total budget and Daily budget — the spend caps for the campaign.
• Max completions — optional hard cap on how many players can finish (blank = unlimited).
• Country allowlist — optional, comma-separated 2-letter codes (e.g. US, GB, DE).
• Start date / End date — optional; the end date must be after the start date.

Step 5 — Review

The review step renders the quest exactly as players will see it: the card preview (tier, difficulty, reward pills), the step plan (each step’s title, description, verification method, and any per-step reward), and a summary (provider, category, budget, and whether it auto-publishes or routes to approval).

From here you choose:

• Save as draft — store it in DRAFT without submitting.
• Submit & publish (auto-approvable creator quests) or Submit for approval (everything else).

Provider configuration

Each provider verifies a specific real action and needs a specific config.

social.telegram-join — Join Telegram

A single-step Social quest, auto-approvable.

• Needs: the target chat id (e.g. -1001234567890), a display chat title, and a public invite link.
• Verifies: Telegram membership — the player is actually in the group/channel.
• Reward kinds: XP, Battle Pass XP, QUEST (TOKEN), in-game items, badges.

onchain.swap — Swap on-chain

A two-step DeFi quest, always reviewed.

• Needs: a protocol name, the chain id (e.g. 8453 for Base), the router/contract address the qualifying tx must target, an optional token-in / token-out, and a minimum input amount (base units). An optional connect reward can be granted the moment wallet control is proven.
• Verifies: a wallet signature (gas-free proof of control), then a confirmed on-chain transaction matching the target and amount. The swap step caps attempts.
• Reward kinds: XP, Battle Pass XP, QUEST, partner tokens / partner NFTs / whitelist spots, badges.

learn.quiz — Learn & Quiz

A two-step Learn quest, auto-approvable.

• Needs: a lesson title and URL, a required read time (dwell seconds), the quiz answer key (hashed on save), and an optional read reward for finishing the reading step.
• Verifies: a time-elapsed dwell timer, then a quiz check against the stored answer hash. The quiz step caps attempts.
• Reward kinds: XP, Battle Pass XP, QUEST, in-game items, badges.

Reward types

The reward editor builds a list of rewards; the highest rarity in the set sets the card’s glow. Reward shapes fall into three families:

XP and $DEGEN are the free, platform-granted rewards. QUEST and partner rewards carry real external value and are settled through on-chain escrow (see Funding & payment). Providers can also attach a per-step reward (e.g. a small XP bonus for verifying a wallet or finishing a lesson); the main rewards land on full completion.

The approval lifecycle

A campaign moves through a clear, audit-ready lifecycle:

DRAFT → PENDING_APPROVAL → APPROVED → ACTIVE
         (auto-published for auto-approvable creator quests)
ACTIVE ↔ PAUSED → ENDED → ARCHIVED      REJECTED → back to edit

1. Submit. An auto-approvable creator quest (no sponsor attached) publishes straight to ACTIVE. Everything else — every sponsor quest, and any always-reviewed provider like onchain.swap — enters the review queue as PENDING_APPROVAL.
2. Review. An admin approves (→ ACTIVE) or rejects (→ REJECTED, with a reason so you can fix and resubmit).
3. Edit window. You can edit a quest only while it’s in DRAFT or REJECTED; the provider stays locked. Once submitted, the config is frozen.
4. Manage. As the owner you can pause, resume, end, or archive a live campaign at any time.

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

The Studio dashboard lists every campaign with its live conversion funnel — Views → Starts → Completions, plus Spend and CPA — and the lifecycle buttons appropriate to each status.

Promotion

Once a campaign is ACTIVE, you can Promote it from its dashboard row. A promote does two things:

1. Featured lane — flags the campaign so it surfaces in the marketplace’s highlighted Promoted lane.
2. Quest Board broadcast — fans the quest out to opted-in Telegram groups and the public Quest Board channel, @DegensQuestPromo, as a “Sponsored Quest” card with a Start Quest button.

Promotion is once-per-day, idempotent: repeated promotes within a day collapse to a single broadcast, so it can’t be used to spam. Only ACTIVE campaigns broadcast — promotion can never bypass review. You can Unpromote to remove a campaign from the featured lane.

Funding & payment

Rolling out. Real-reward funding is being introduced in stages. The details below are conceptual and may evolve — the Studio always shows the current funding step for your campaign.

How a reward is funded depends on what it grants:

• XP-only quests are free. XP, $DEGEN, Battle Pass XP, in-game items, and guild reputation are platform-granted and drawn against your campaign budget — no on-chain payment.
• Real-value rewards are funded on-chain. Campaigns that pay QUEST or native ETH (and partner tokens/NFTs/whitelist spots) are pre-funded into a per-campaign escrow on Base. Rewards are released against a verified completion, with a platform fee taken on release (so the protocol only ever takes a cut of rewards actually distributed). Any unspent balance is refundable to the sponsor after the campaign ends.

This means a player can only ever claim a real reward your campaign has actually funded — there’s no way to over-promise. For exact amounts, fees, and the funding flow, follow the in-product steps; this guide intentionally keeps the numbers out of the docs while the feature rolls out.

Ready to build?

1. Open the Studio on web or in the Telegram Mini App (/studio).
2. Register a sponsor (or run as a creator).
3. Create a quest and walk the five steps.
4. Submit — auto-publish or send to approval.
5. Promote the winners and watch the funnel.

See For Sponsors & Creators for the deeper model, or the Player guide for how the finished quest plays.