Each campaign in Absinthe supports multiple user identities, allowing participants to connect accounts across wallets, email, and social platforms. A single identity, however, must be designated as the Primary Identity.
The primary identity defines how users authenticate and log in to the campaign portal.
Supported identities
Users can connect the following identities to their campaign profile:
- X
- Email
- GitHub
- Discord
- EVM address
- Solana address
- Immutable Passport
These identities are linked to a single user profile once connected.
Primary identity behavior
Every campaign must have exactly one primary identity. This identity is:
- The required login method for the campaign portal.
- The canonical identifier used to create and resolve user profiles.
- The first identity a user must connect before accessing the campaign.
By default, the primary identity is set to EVM address, which is suitable for most onchain-first campaigns.
Customizing the primary identity
You can change the primary identity at the campaign level to any supported identity, depending on your audience and acquisition strategy. Common examples include:
- Using Email for web2-style onboarding and lower-friction entry.
- Using Discord or X for community-driven campaigns.
- Using Solana address or Immutable Passport for ecosystem-specific activations.
Once set, users must authenticate with the selected primary identity to enter the campaign. Other identities can be connected later to enrich the user profile and enable cross-channel attribution.
Choose the primary identity deliberately. It directly affects onboarding friction, conversion rates, and how users experience your campaign.