All Collections
Credentials & Rewards
Credentials 101 🍎
Credential Types 🧰
Galxe Plugin: Empowering Community Engagement and Rewards on Snapshot.org
Galxe Plugin: Empowering Community Engagement and Rewards on Snapshot.org

Unlock community engagement and rewards with Galxe Plugin. Incentivize participation in Snapshot.org proposals through OATs.

Operation Team avatar
Written by Operation Team
Updated over a week ago

The Galxe Plugin empowers Snapshot.org by incentivizing community engagement in proposal voting through On-Chain Achievement Tokens (OATs). Seamlessly integrate Galxe Plugin in your Snapshot space for a rewarding environment. Maximize Snapshot proposals with active participation and OAT rewards!


Here's a step-by-step guide on how to make the most of the Galxe Plugin:

  • Preparation

    • Create a proposal on Snapshot.

    • Generate a Snapshot Credential using the proposal ID from the previous step on Galxe.

    • Set up an OAT campaign exclusively for this proposal using the credential obtained in the previous step on Galxe.

  • Add Galxe Plugin to Your Space

    • Access Snapshot space settings.

    • Find and add Galxe Plugin in the plugins section.

  • Configure the JSON Settings

    • Open the Galxe Plugin editor.

    • Customize the JSON settings as needed.


    Example JSON format (supporting multiple OATs):

    {
    "oats": {
    "<proposal ID 1>": "<Space Name>/campaign/<Campaign ID>",
    "<proposal ID 2>": "<Space Name>/campaign/<Campaign ID>",
    "<proposal ID 3>": "<Space Name>/campaign/<Campaign ID>"
    }
    }

    By default, the API section doesn't require modifications unless specific preferences exist.

    Example API and OAT configuration:

    {
    "api": "https://graphigo.stg.galaxy.eco/query",
    "oats": {
    "0x554ca2bd7d979e8b72c6ae6415946a7bb470da9f60a9cf931205f083c03632a3": "jokey/campaign/GCixQUUqfE"
    }
    }

    Fill in proposal ID and campaign information to link campaigns with proposals. Add multiple proposal ID-campaign pairs for OAT distribution. Deleting pairs hides OAT information, even if the proposal ended or OATs were distributed.

    Demo JSON configuration:

    {   "oats": {      "0x554ca2bd7d979e8b72c6ae6415946a7bb470da9f60a9cf931205f083c03632a3": "galaxy/campaign/GCcqvUtDaM"   }}

    Adjust proposal ID and campaign info accordingly.


Did this answer your question?