Identity / Names·Multi-chain
Galxe
Onchain quest and credential platform. Distribute campaigns, mint OAT/NFT rewards, and verify sybil-resistant identities via Galxe Passport.
- 01user acquisition campaigns
- 02onchain quests with NFT/OAT rewards
- 03loyalty programs
- 04sybil-resistant verification (Passport)
- 05multi-chain credential issuance
- pnpm add @galxe-identity-protocol/sdk
| Variable | Scope | Description |
|---|---|---|
| GALXE_ACCESS_TOKEN | Server | Galxe v2 GraphQL API access token (Basic Auth bearer). |
| NEXT_PUBLIC_GALXE_CAMPAIGN_ID | Client | Campaign ID for the deployed Galxe quest. |
Use Galxe to power quests and credentials. Query the v2 GraphQL API at `https://graphigo.prd.galaxy.eco/query` with `Authorization: Basic <GALXE_ACCESS_TOKEN>` — typical operations: `campaign(id)`, `addressInfo(address)`, and the `prepareParticipateMutation` / `participate` flow for credit issuance. Wire credential checks (Galxe Passport SBT) via the Identity Protocol SDK (`@galxe-identity-protocol/sdk`) to build ZK-credential proofs for sybil resistance. For lightweight integrations, embed a Galxe quest iframe and listen for completion via a webhook configured in the campaign builder.
- ⚑v2 GraphQL API is rate-limited per access token — batch queries (`addressInfos` plural) instead of looping single calls.
- ⚑Some Galxe campaigns are jurisdiction-blocked (US, OFAC list, sanctioned regions); EU/UK users may need GDPR consent flows.
- ⚑Galxe Passport is an SBT minted on BNB Chain — verifying holders cross-chain requires reading the registry, not the user's primary wallet.
- ⚑Credential issuance has a curation review step ("under review" until approved); plan for 24–72h delay before public launch.
- ⚑Free tier caps OATs and credit storage; high-volume campaigns require the paid Growth tier.
- ⚑Avoid trusting client-supplied `participate` results — always re-query `credentialItems` server-side before granting offchain rewards.