Quest Protocol
  • Quest Protocol
    • Introduction to Quest Protocol
    • Mission & Principles
    • Ecosystem Challenges & Solutions
    • How it Works
  • Deploying Quests on Quest Terminal
    • Choosing an Action
    • Choosing Quest Participants
      • Allowlists
      • Our Philosophy on Sybil Resistance
    • Scheduling a Quest
    • Choosing a Reward
    • Deploying a Quest & Quest Fees
    • Monitoring a Quest
    • Withdrawing Tokens
    • FAQ
  • Protocol Rewards
    • Protocol Rewards Overview
    • Quest Referrals
  • RabbitHole
    • Completing Quests
    • Power Score
  • For Developers
    • Quest Protocol Contracts
    • How Contracts Work
    • Submitting Actions
    • Submitting Plugins
    • Submitting Tokens
    • Public API
    • Codearena Audit
Powered by GitBook
On this page

Was this helpful?

  1. For Developers

Quest Protocol Contracts

Quest Factory
0x52629961F71C1C2564C5aa22372CB1b9fa9EBA3E

RabbitHole Receipt

0xEC3a9c7d612E0E0326e70D97c9310A5f57f9Af9E

Quest Terminal Key

0x6Fd74033a717ebb3c60c08b37A94b6CF96DE54Ab

  • Quest Factory (code)

    • Creates new Quest instances of an ERC-20 reward Quest.

  • RabbitHole Receipt (code)

    • An ERC-721 contract that acts as a proof of on-chain activity. Claimed via usage of ECDSA sig/hash

  • ERC-20 Quest (code)

    • A Quest in which the reward is an ERC-20 token

PreviousPower ScoreNextHow Contracts Work

Last updated 1 year ago

Was this helpful?