This document is inteded to help people understand the various ways one can mint a badge using the Otterspace protocol.

There are 4 ways to mint an otterspace badge using our protocol

1. Mintlist flow (with single issuance)
2. Mintlist flow with bulk issuance (via Merkle Trees)
3. Request flow
   1. 2 party consented model
   2. Single party consented model
4. Airdrop flow

In order to help you decide what flow to use for your app, the following questionnaire should help

• Do you plan to issue consented badges?
  • If No, then you should use the airdrop flow. We generally recommend establishing consent with the account before sending them a non-transferable token
  • If Yes, then you either need to use the Mintlist flow or Request flow. See questions below.
• Do you want to allowlist account(s) before they can claim it?
  • If Yes, you should implement it the Mintlist flow. You can allow 1 or many accounts at once. Allowlisting many accounts at once use the merkle tree approach, see below sections for details
• Do you want users to request a badge that you already created?
  • If Yes, then the Request flow is the right approach
  • Depending on your use case, please see the sections below to determine if a single or 2-party consented model is right for you
• Do you want to just airdrop badge(s) to accounts?
  • Use the airdrop flow

Recommended reading

Firstly, familiarize yourself with the quickstart

Quick start on using our protocol

As a pre-requisite, it is important to understand how Otterspace uses an NFT called RAFT tokens, in otder to represent orgs and capture administrative authorization over their Otterspace account.

Raft Tokens – How communities are represented within Otterspace