Skip to main content

Content model

All quest content follows Project → Campaign → Quest. Studio workflows map directly to this hierarchy.

Project​

FieldDescription
Name, slug, logo, coverBranding; cover drives OG images
Description, website, socialsPublic project page
Project categorye.g. DEX, Layer-1, Validator (admin-managed)
Subscription planDynamic tier from admin pricing
Project moderatorsSeat count limited by plan
Verification APIOptional REST endpoint for custom tasks
SEO profileTitle, description, keywords, OG overrides
StatusDraft · Pending approval · Live · Suspended

Campaign​

FieldDescription
Name, description, coverOptional campaign-specific OG
Start / end datetimeScheduling
StatusDraft · Scheduled · Active · Paused · Ended
Reward poolDP plus optional on-chain escrow
Eligibility rulesReputation floor, regions, wallet age, etc.
Quest countAuto and manual breakdown

Quest​

FieldDescription
Title, description, instructionsUser-facing copy
Task typeFrom global catalog (admin can disable types)
Quest categoryFilter tag (On-chain, Social, Developer, etc.)
Verification methodIndexer · Platform API · Project REST · Manual · AI verify
RewardDP, XP, optional token amount
Input schemaDynamic fields for manual or custom submissions
LimitsMax completions, per-user cap, cooldown
StatusDraft · Live · Paused · Archived

Task type catalog​

Task types are stored globally. Super admin can enable or disable types platform-wide. Disabled types are hidden from Studio but existing quests remain until archived.

Each task type defines default verification, required integrations, default input schema, and compatible quest categories.

Examples:

Task typeCategoryVerification
Twitter FollowSocialPlatform API
GitHub StarDeveloperPlatform API
DEX SwapOn-chainOn-chain indexer
Tutorial submitContentManual review
Custom logicAnyProject REST API

See Verification for how submissions are validated.