Knowing what onchain tasks can be verified on Galxe Quest

You now understand that task verification on Galxe works by matching two data points — one consisting of the user id data bound to Galxe, and the other consisting of data Galxe pulls from external sources. In this part of the course, you’ll learn what kinds of data for each point are available for onchain task setup on Galxe, and therefore what kinds of onchain tasks can be verified. Scroll down to have a look.

<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/046d56bb-337c-428c-ba45-93717675a29f/44746536-e16d-4400-be7a-0e61592d1c40/Round_Gradient_Background_(1).png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/046d56bb-337c-428c-ba45-93717675a29f/44746536-e16d-4400-be7a-0e61592d1c40/Round_Gradient_Background_(1).png" width="40px" />

Course Navigation

  1. Course Introduction
  2. Task verification on Galxe: How does it work?
  3. What kinds of onchain tasks can be verified on Galxe Quest? - Current Page
  4. Onchain task types on Galxe Quest
    1. NFT Holder tasks
    2. Snapshot Vote tasks
    3. Wallet Balance tasks
    4. Contract Query tasks
    5. Import Your Own Data tasks
      1. Import Your Own Data task set up requirements
      2. Setting up Import Your Own Data Tasks
  5. Strategy considerations for onchain tasks
  6. Troubleshooting and resolving common issues with onchain tasks
  7. Course Completion and Certification </aside>

What are the limits of onchain task verification on Galxe Quest?

Given our knowledge of how task verification works on Galxe Quest, it’s fair to say that the types of onchain tasks able to be verified are only limited by two factors: the user id data able to be bound to users’ Galxe Accounts, and the availability of external data for who has performed a given onchain task. As always, Galxe will look for a match between these two data points in order to perform its task verification process. Let’s take a look at each data point individually to determine what kinds of tasks can be verified on Galxe Quest.

Data Point 1: User id data available on a user’s Galxe Account

Task setup showing address type options on Galxe Quest

Task setup showing address type options on Galxe Quest

The first data point that Galxe will use to verify an onchain task is the id data bound to a user’s Galxe Account. For onchain task verification, this bound data is typically the user’s wallet address for a particular network type. Given this, the type of address available for onchain task verification on Galxe Quest is limited by what address types are currently supported for user wallet address binding on Galxe, of which 16 address types are currently supported. The list of supported types follows: