# AGENTS
Source: https://docs.flipsuite.xyz/AGENTS



# AGENTS.md

## Purpose

This file defines how to write and maintain product documentation inside `docs/`.

Use it when creating or updating Mintlify documentation pages for Flipsuite.

Primary goal:

* Keep new docs aligned with the strongest existing references, especially:
  * `docs/quests/introduction.mdx`
  * `docs/quests/setup.mdx`
  * `docs/points/introduction.mdx`
  * `docs/points/setup.mdx`
  * `docs/points/conversions.mdx`
  * `docs/points/discord-roles.mdx`

***

## What good docs look like here

The best docs in this repository are:

* Task-oriented
* Written for end users, not implementers
* Structured around real UI flows
* Dense with screenshots, but not screenshot-dependent
* Short on hype, long on clarity

Good pages in this docs set usually do the following:

* Start with minimal frontmatter: `title`, `description`, `icon`
* Open with a short orientation paragraph or blockquote
* Walk through the feature in the order a user encounters it
* Use `## Step N - ...` headings for setup guides
* Use screenshots inside `<Frame>` immediately after the text that introduces the UI
* Explain terms and options with tight bullet lists
* Link to the next relevant page with a `Card` or `CardGroup`
* Use `Tip`, `Note`, and `Warning` only for real exceptions, caveats, or constraints

Avoid:

* Marketing language
* Large theory dumps before showing the workflow
* Repeating UI labels in multiple ways
* Explaining implementation details users do not need
* Creating a brand new page structure when an existing pattern already fits

***

## Source references to mirror

Use these pages as canonical references before inventing a format:

* Overview/introduction pages:
  * `docs/quests/introduction.mdx`
  * `docs/points/introduction.mdx`
* Setup guides:
  * `docs/quests/setup.mdx`
  * `docs/points/setup.mdx`
* Focused feature pages:
  * `docs/points/conversions.mdx`
  * `docs/points/discord-roles.mdx`
* Repeated reference sections:
  * `docs/quests/tasks/points.mdx`
  * `docs/quests/tasks/twitter.mdx`
  * `docs/quests/tasks/input.mdx`

If a new page is similar to one of these, copy that structure and only change what is necessary.

***

## Page types and expected structure

### 1. Introduction pages

Use for landing pages like `quests/introduction` and `points/introduction`.

Preferred structure:

1. Frontmatter with `icon`, `title`, `description`
2. Hero image or embed
3. One short introduction paragraph
4. `##` section covering core concepts, capabilities, or key use cases
5. `## What's next?` section with a `Card` to the next action

Keep these pages high-level. They should explain what the feature is for and why someone would use it, then move them forward.

### 2. Setup guides

Use for pages that help users create or configure something in the dashboard.

Preferred structure:

1. Frontmatter
2. Short lead-in blockquote or intro paragraph
3. Sequential `## Step N - ...` sections
4. Screenshot `Frame` after each important UI transition
5. Bullets for field meanings, options, or behaviors
6. Small callouts for caveats
7. A closing `## Step N - What's next?` or `## What's next?`

This is the strongest pattern in the repo. Default to it whenever documenting a feature setup flow.

### 3. Focused feature pages

Use for narrower topics like conversions, imports, sharing, moderation, roles, notifications.

Preferred structure:

1. Frontmatter
2. Optional opening `Frame` if the page centers on one screen
3. Short explanation of what the feature does
4. `##` sections for how it works, how to configure it, and practical usage
5. One or two screenshots where they clarify the exact UI

These pages should stay compact. Avoid turning them into full setup guides unless the workflow actually needs it.

### 4. Reference collections

Use for grouped feature variants like quest task pages or command pages.

Preferred structure:

1. Frontmatter
2. Repeated per-item sections using:
   * `## <Icon ... /> Item name`
   * One-sentence description
   * Screenshot in `Frame`
   * `Accordion` for configuration or command arguments
   * Optional `Note`, `Tip`, `Check`, or `Warning`

Keep each section parallel so users can scan and compare items quickly.

***

## Writing style

Write for operators and community managers using the product.

Use this tone:

* Direct
* Concrete
* Calm
* Operational

Prefer:

* "Open the **Points** tab and click **Create point system**."
* "Set the minimum balance required."
* "Users can convert one balance into another."

Avoid:

* "Simply"
* "Just" when it understates real work
* Internal engineering language
* Feature claims that are not visible or proven in product

Other style rules:

* Prefer short paragraphs
* Prefer bullets when listing fields, options, or outcomes
* Use bold for visible UI labels
* Use inline code for enums, commands, IDs, and literal values
* Keep headings descriptive, not clever
* Use product terminology consistently: `Quests`, `Point Systems`, `Flippy`, `Flipwallets`, `Discord roles`, `community dashboard`

***

## How to structure explanations

Default order for most user docs:

1. What this feature is
2. Where to find it
3. How to configure it
4. What happens after setup
5. Where to go next

When documenting fields or options:

* Put the user-visible field name first in bold
* Explain what it controls in one sentence
* Mention optionality or edge behavior only if relevant

When documenting workflows:

* Match the actual UI order
* Do not jump ahead to advanced options before the base flow is clear
* Keep each step actionable

When documenting constraints:

* Use `Tip` for helpful guidance
* Use `Note` for clarifications
* Use `Warning` for limits, irreversible actions, permission issues, or easy mistakes

***

## Mintlify component patterns used here

Reuse the existing component patterns already present in `docs/`.

### Frontmatter

Most guide pages use:

```mdx theme={null}
---
title: "Setup"
description: "Create a new point system and configure it."
icon: "wrench"
---
```

Keep frontmatter minimal unless the page needs more.

### Frames and screenshots

Use `<Frame>` for screenshots.

Pattern:

```mdx theme={null}
<Frame caption="Point systems list">
    <img src="/images/points/point-systems.png" className="rounded-lg" />
</Frame>
```

Conventions:

* Add a caption when it helps identify the screen
* Keep image paths rooted at `/images/...`
* Reuse `className="rounded-lg"`
* Place the screenshot near the text that introduces that screen

### Cards

Use `Card` or `CardGroup` to move users to the next relevant page or summarize a small set of related options.

Do not use cards when a normal bullet list is clearer.

### Accordions

Use `Accordion` for repeated configuration schemas, especially:

* quest task configuration
* slash command arguments
* supported file types or option sets

This keeps repeated reference sections compact and scannable.

### Callouts

Available patterns already used heavily:

* `<Tip>`
* `<Note>`
* `<Warning>`
* `<Check>`

Do not stack multiple callouts in a row unless each adds distinct value.

### Icons in headings

For reference-style pages, follow the existing pattern:

```mdx theme={null}
## <Icon icon="sparkles" size={24} />  Points Balance
```

Only use this pattern when the page contains several repeated subsections of the same type.

### Shared snippets

Before writing a custom warning or plan badge, check `docs/snippets/`.

Existing shared snippets include:

* `required-starter-plan-banner.mdx`
* `required-pro-plan-banner.mdx`
* `required-starter-plan-badge.mdx`
* `required-pro-plan-badge.mdx`
* `role-hierarchy-warning.mdx`

Reuse these instead of duplicating the same copy or UI pattern inline.

***

## Screenshots and asset rules

Follow the current asset organization:

* Quest docs: `docs/images/quests/...`
* Point system docs: `docs/images/points/...`
* Module docs: `docs/images/modules/<module>/...`
* Account docs: `docs/images/account/...`

Rules:

* Put new screenshots in the nearest existing folder
* Use descriptive filenames based on the screen or action
* Prefer PNG for static UI screenshots
* Reuse existing images if the UI already matches
* Do not reference missing assets in docs

If the page depends on a screenshot that does not exist yet, note that gap clearly instead of inventing UI details.

***

## Navigation and information architecture

`docs/docs.json` is the source of truth for Mintlify navigation.

Whenever you add, rename, move, or remove a page:

* Update `docs/docs.json`
* Keep the page in the nearest matching group
* Reuse existing grouping patterns before creating a new section

Current patterns to preserve:

* Major feature areas are grouped by product capability
* Nested groups are used for collections like `Tasks`, `Commands`, `Rules`, `Guides`
* Intro/setup pages usually appear before narrower subpages

If you add a page under an existing feature, check the surrounding section in `docs/docs.json` first and keep the order intuitive for end users.

***

## Linking rules

Prefer internal links to the next action a user should take.

Use:

* Markdown links in prose for inline references
* `Card` and `CardGroup` for prominent next steps

Good examples in this repo:

* Linking from quest rewards setup to `/rewards/introduction`
* Linking from intro pages to setup guides

Do not overload pages with unrelated links.

***

## Product terminology and naming

Keep naming aligned with the current docs and UI.

Use:

* `X` or `X/Twitter` only when the surrounding page already does
* `Discord roles`, not arbitrary synonyms
* `Point system`, not `token` or `currency`, unless discussing a specific subtype
* `community dashboard` or the exact UI section name if visible to the user
* `quest`, `task`, `reward`, `submission`, `completion` using the quest docs definitions

When the UI has a visible label, mirror that label exactly in bold.

***

## Scope control

Make the smallest documentation change that fully solves the task.

Before creating a new page, ask:

1. Can an existing page be extended instead?
2. Is there already a nearby page with the same structure?
3. Does this belong in a setup guide, a focused feature page, or a reference collection?

Do not:

* Split content into multiple pages without a navigation reason
* Create duplicate explanations in multiple sections
* Add implementation detail for backend behavior unless users need it to operate the feature
* Rewrite nearby pages for style consistency unless the task requires it

***

## Validation checklist

Before finishing a docs change:

* Confirm the page follows a nearby existing pattern
* Confirm links point to real pages
* Confirm image paths point to real assets
* Confirm `docs/docs.json` was updated if navigation changed
* Confirm terminology matches nearby pages and UI labels
* Skim the rendered MDX structure for obvious formatting issues

If local preview is needed and available, use Mintlify from the `docs/` directory where `docs.json` lives.

***

## Definition of done for docs work

A docs task is complete when:

* The content matches the current product behavior
* The page structure matches the nearest existing docs pattern
* Navigation is updated when required
* Images and links resolve correctly
* The change is concise and reviewable
* Any missing screenshots, product ambiguities, or follow-ups are called out explicitly

***

## Default approach for future docs tasks

For any new documentation request in `docs/`, start by answering:

1. Which existing page is the closest structural match?
2. Is this an intro page, setup guide, focused feature page, or reference collection?
3. Does `docs/docs.json` need to change?
4. Are there existing screenshots or snippets to reuse?
5. What is the smallest doc change that gets users unstuck?


# Connections
Source: https://docs.flipsuite.xyz/account/connections

Learn how to link wallets and socials to your account.

## How to connect wallets to my profile?

To link a new wallet to your Flipsuite profile, go to the [**Connections**](https://flipsuite.xyz/account/connections/wallets) page in
your account settings and switch to the **Wallets** tab.

<Frame>
  <img />
</Frame>

To begin the wallet linking process, simply click the **Link new wallet** button, and choose one of the available
verification methods.

<Frame>
  <img />
</Frame>

You can verify your wallet in two ways:

1. **By signing a unique message**:\
   Requires you to connect a wallet to the Flipsuite website and sign a message using your wallet. This option is free
   and gas-less.
2. **By making a deposit to your Flipwallet**:\
   It doesn't require you to connect a wallet to the Flipsuite website, but you need to pay transaction costs for a small
   deposit of tokens to your [Flipwallet](/flippy/introduction).

### Verify by signing a unique message

To link a wallet to your profile by signing a unique message simply choose a chain and wallet you'd like to
connect with. You'll be asked to prove the ownership of your wallet by signing a unique message with it.

<Frame>
  <img />
</Frame>

Once the message is signed and verified in our system, the wallet will be linked to your profile.

<Tip>
  If you're connecting from mobile it's recommended to use your wallet's app built-in browser for the best
  user experience.
</Tip>

<Warning>
  Flipsuite will never ask you for a private key or seed phrase to your personal wallet.
</Warning>

### Verify by making a small deposit

To link a wallet to your profile by making a deposit, simply choose a chain and continue. You will be asked to
deposit a small amount of native chain tokens to your own [Flipwallet](/flippy/introduction).

<Frame>
  <img />
</Frame>

Simply transfer the required amount of tokens to the displayed wallet address, enter the transaction hash
and click **Verify transaction**.

<Warning>
  Your deposit needs to have the **exact** shown amount of tokens. If it's even a tiny bit more or less the
  verification will fail.
</Warning>

## How to connect socials to my profile?

To connect a new social account to your profile, go to the [**Connections**](https://flipsuite.xyz/account/connections/socials)
page in your account settings and switch to the **Socials** tab.

<Frame>
  <img />
</Frame>

Here, simply choose a social platform you'd like to link and click the `🔗` button to initiate a linking process.
You'll be redirected to that platform's authorization page and asked to authorize Flipsuite to view necessary
details about your account.

<Frame>
  <img />
</Frame>


# Credits
Source: https://docs.flipsuite.xyz/account/credits

Learn more about account credits.

## What are credits?

Credits are a premium off-chain currency in the Flipsuite ecosystem. They can be spent to chat with Flippy or to
[automatically join](/modules/battleground/autojoins) chosen battlegrounds in the servers of your choice.

## How to earn credits?

For now, the only way to obtain credits is to buy them via dashboard. To top up your account credits balance, go to
the [**Credits**](https://flipsuite.xyz/account/credits) page in your account settings.

<Frame>
  <img />
</Frame>

Here, simply click the **Top up your credits balance** button, choose a credits package and continue with the payment.


# Security
Source: https://docs.flipsuite.xyz/account/security

Learn more about your account security.

## Overview

By default, your Flipsuite account's security is tied to your Discord account security. Therefore, it's essential to
secure your Discord account with multi-factor authentication or security keys.

For enhanced protection of your Flipsuite account, which we highly recommend, you can enable two-factor authentication
through your account settings.

## How to enable 2FA?

To enable 2FA, go to the [**Security**](https://account/security) tab in your account settings and click the **Enable** button.

<Frame>
  <img />
</Frame>

You will be asked to scan the QR code with your authenticator app.

<Frame>
  <img />
</Frame>

After completing the process of enabling 2FA on your account, you will need to log into your account again
using a code generated by your authenticator app.


# Teams
Source: https://docs.flipsuite.xyz/account/teams

Share your community with your team to manage it together, in co-op mode!

## Overview

Teams allow you to share your Flipsuite community configuration with others and assign your team members
permissions to keep sensitive data secure.

## Step 1 - Create team

To create a team, go to the [**Teams**](https://flipsuite.xyz/account/teams) tab in your account settings and click
the **Create new team** button to get started.

<Frame>
  <img />
</Frame>

After successfully creating a team, you'll be redirected to the **Members** tab.

<Frame>
  <img />
</Frame>

## Step 2 - Invite members

To invite a new member, click the **Invite a new member** button, enter their Discord ID, and optionally
select roles they should receive in your team once the invite is accepted.

<Frame>
  <img />
</Frame>

<Note>
  You can get the ID of any Discord user by enabling Developer Mode in Discord settings and right-clicking on
  their avatar/username.

  <Frame>
    <img />
  </Frame>
</Note>

Great! Now simply wait for them to accept your invite. Invited person will get a notification on the dashboard asking
them to accept or reject the invitation.

<Frame>
  <img />
</Frame>

## Step 3 - Set roles

You can assign various roles to your team members to give them access to your community. To view all possible roles
and what permissions they grant, click the **Role cheatsheet** button.

<Frame>
  <img />
</Frame>

To manage the roles of your team members, simply click the edit button next to their name on the list and a dialog like
the one in the image below will appear.

<Frame>
  <img />
</Frame>

## Step 4 - Move community to the team

To move your community to the team, switch to the **Communities** tab in your team.

<Frame>
  <img />
</Frame>

Here, click the **Move community to team** button and select a community you'd like to move.

<Tip>
  Before moving your community to the team, you can see which members of a team will get access
  to sensitive community data like wallet private keys.

  <Frame>
    <img />
  </Frame>
</Tip>

Good job! You can now delegate community management to your team members!


# Get User Details
Source: https://docs.flipsuite.xyz/api-reference/community/gating/endpoint/users

GET /v1/community/gating/users/{userId}
Get details about a user verified in your server

<div>
  <a href="https://flipsuite.xyz/pricing"><Icon icon={"cube"} /><p>Growth only</p></a>

  <div />
</div>

<Note>
  Note that only accounts and wallets required for verification based on your server's gating rules will be
  included in the response. For example, if no rule in your server requires a Solana wallet, it won't be
  included in the response even if user has a Solana wallet linked.
</Note>

<Warning>
  All users can opt-out from sharing their linked accounts and wallets in your server via [privacy settings](/flippy/commands/profile#5-privacy-settings).
  If sharing is disabled, the `isRedacted` field will be set to `true` in the linked accounts and wallets returned in
  the response, and their details will be blank.
</Warning>


# Overview
Source: https://docs.flipsuite.xyz/api-reference/community/gating/overview

Get familiar with the Gating API

## Introduction

Gating API allows you to get details about users verified in your server.

<CardGroup>
  <Card title="Users" icon="users" href="/api-reference/community/gating/endpoint/users">
    Get details about users verified in your server.
  </Card>
</CardGroup>


# Introduction
Source: https://docs.flipsuite.xyz/api-reference/community/introduction

Community API specification

## Overview

Community API is a set of endpoints that allow you to manage your community.

## Authentication

All Community API endpoints require an API key sent via `x-api-key` header. You can generate API keys for your community
[on the dashboard](https://flipsuite.xyz), in the **Developer** sidebar tab.

## Rate Limits

All endpoints have a rate limit of 1 request per second.

<Note>
  Even though the rate limit is 1 RPS - your tips, airdrops and raffles can be delayed by a few or more
  seconds if you try to create a lot of them at once.
</Note>

## APIs

<CardGroup>
  <Card title="Gating API" icon="lock" href="/api-reference/community/gating/overview">
    Get details about users who verified in your server.
  </Card>

  <Card title="Points API" icon="sparkles" href="/api-reference/community/points/endpoint/get-balance">
    Manage your community point systems and holders.
  </Card>

  <Card title="Quests API" icon="scroll" href="/api-reference/community/quests/endpoint/get-quest">
    Create and manage quests for your community.
  </Card>

  <Card title="Tipping API" icon="hands-holding-dollar" href="/api-reference/community/tipping/overview">
    Trigger airdrops, raffles, tips and more in your server.
  </Card>

  <Card title="Tokens API" icon="coins" href="/api-reference/community/tokens/overview">
    View, manage and delete tokens from your community's custom token list.
  </Card>
</CardGroup>


# Get Balance
Source: https://docs.flipsuite.xyz/api-reference/community/points/endpoint/get-balance

GET /v1/community/points/{pointSystemId}/balance
Get point system balance of one or more users



# Get Points
Source: https://docs.flipsuite.xyz/api-reference/community/points/endpoint/get-points

GET /v1/community/points
Get point systems from your community



# Update Balance
Source: https://docs.flipsuite.xyz/api-reference/community/points/endpoint/update-balance

POST /v1/community/points/{pointSystemId}/balance
Update point system balance of one or more users



# Create Quest
Source: https://docs.flipsuite.xyz/api-reference/community/quests/endpoint/create-quest

POST /v1/community/quests
Create quest in your community



# Get Quest
Source: https://docs.flipsuite.xyz/api-reference/community/quests/endpoint/get-quest

GET /v1/community/quests/{questId}
Get details about the quest from your community



# Get Completions
Source: https://docs.flipsuite.xyz/api-reference/community/quests/endpoint/get-quest-completions

GET /v1/community/quest-completions
Get quest completions from your community



# Get Quests
Source: https://docs.flipsuite.xyz/api-reference/community/quests/endpoint/get-quests

GET /v1/community/quests
Get quests from your community



# Create Airdrop
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/airdrops

POST /v1/community/tipping/airdrops
Create automated airdrops for Discord users



# Burn Asset
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/burning

POST /v1/community/tipping/burning
Burn tokens and NFTs in your tipping wallet



# Create Raffle
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/raffles

POST /v1/community/tipping/raffles
Create automated raffles for Discord users



# Send Tip
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/tips

POST /v1/community/tipping/tips
Send automated tips to Discord users



# Transfer Asset
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/transfers

POST /v1/community/tipping/transfers
Transfer onchain assets to arbitrary wallets



# Get Balance
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/wallet-balance

GET /v1/community/tipping/wallets/{chain}/balance
Get shared tipping wallet token balance on a given chain



# Get Inventory
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/endpoint/wallet-inventory

GET /v1/community/tipping/wallets/{chain}/inventory
Get shared tipping wallet NFT inventory on a given chain



# Overview
Source: https://docs.flipsuite.xyz/api-reference/community/tipping/overview

Get familiar with the Tipping API

## Introduction

Tipping API allows you to programmatically trigger airdrops, burns, raffles, tips and transfers in your server, using
your [shared tipping wallet](/modules/tipping/shared-wallet) for token distribution. It's a great way to integrate
your own Discord bot with any Flipsuite community.

<CardGroup>
  <Card title="Airdrops" icon="parachute-box" href="/api-reference/community/tipping/endpoint/airdrops">
    Create automated airdrops for users in your Discord server.
  </Card>

  <Card title="Burning" icon="fire" href="/api-reference/community/tipping/endpoint/burning">
    Burn tokens and NFTs in your tipping wallet in your Discord server.
  </Card>

  <Card title="Raffles" icon="ticket" href="/api-reference/community/tipping/endpoint/raffles">
    Create automated raffles for users in your Discord server.
  </Card>

  <Card title="Tips" icon="hands-holding-dollar" href="/api-reference/community/tipping/endpoint/tips">
    Send automated tips to users in your Discord server.
  </Card>

  <Card title="Transfers" icon="arrow-right-arrow-left" href="/api-reference/community/tipping/endpoint/transfers">
    Transfer tokens and NFTs to arbitrary wallet addresses.
  </Card>

  <Card title="Wallets" icon="wallet" href="/api-reference/community/tipping/endpoint/wallet-balance">
    Read shared tipping wallet token balance and NFT inventory.
  </Card>
</CardGroup>


# Delete Token
Source: https://docs.flipsuite.xyz/api-reference/community/tokens/endpoint/delete-token

DELETE /v1/community/tokens/{chain}/{address}
Remove a custom token from your community



# Get Tokens
Source: https://docs.flipsuite.xyz/api-reference/community/tokens/endpoint/get-tokens

GET /v1/community/tokens
Get custom tokens from your community



# Save Token
Source: https://docs.flipsuite.xyz/api-reference/community/tokens/endpoint/save-token

POST /v1/community/tokens
Add a custom token to your community



# Get Supported Chains
Source: https://docs.flipsuite.xyz/api-reference/core/chains

GET /v1/chains
Get a list of chains supported by Flipsuite



# Get User Flipwallets
Source: https://docs.flipsuite.xyz/api-reference/core/flipwallets

GET /v1/flipwallets
Get Flipwallets of a given user

<Warning>
  Flipwallets returned in the response can change over time, so it's not recommended to cache
  them for extended periods.
</Warning>


# Chains
Source: https://docs.flipsuite.xyz/chains

List of all chains supported by Flipsuite.

| Chain                                                                            | Chain ID                  | Chain Key |
| -------------------------------------------------------------------------------- | ------------------------- | --------- |
| <Icon icon="https://cdn.discordapp.com/emojis/1333723516658520094" /> Abstract   | <code>2741</code>         | Abstract  |
| <Icon icon="https://cdn.discordapp.com/emojis/1401149863001067582" /> ApeChain   | <code>33139</code>        | ApeChain  |
| <Icon icon="https://cdn.discordapp.com/emojis/1281544796753887283" /> Arbitrum   | <code>42161</code>        | Arbitrum  |
| <Icon icon="https://cdn.discordapp.com/emojis/1466125466321555557" /> Atto       | -                         | Atto      |
| <Icon icon="https://cdn.discordapp.com/emojis/1281544824318590976" /> Avalanche  | <code>43114</code>        | Avalanche |
| <Icon icon="https://cdn.discordapp.com/emojis/1281544830627090454" /> Base       | <code>8453</code>         | Base      |
| <Icon icon="https://cdn.discordapp.com/emojis/1337189012720455764" /> Berachain  | <code>80094</code>        | Berachain |
| <Icon icon="https://cdn.discordapp.com/emojis/1281544859735556116" /> Blast      | <code>81457</code>        | Blast     |
| <Icon icon="https://cdn.discordapp.com/emojis/1374689599502417952" /> BSC        | <code>56</code>           | BSC       |
| <Icon icon="https://cdn.discordapp.com/emojis/1485337257320906822" /> Cosmos Hub | <code>cosmoshub-4</code>  | CosmosHub |
| <Icon icon="https://cdn.discordapp.com/emojis/1281544931714007083" /> Cronos     | <code>25</code>           | Cronos    |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545075855327297" /> Ethereum   | <code>1</code>            | Ethereum  |
| <Icon icon="https://cdn.discordapp.com/emojis/1318134067249807430" /> Harmony    | <code>1666600000</code>   | Harmony   |
| <Icon icon="https://cdn.discordapp.com/emojis/1343133640720257075" /> HyperCore  | -                         | HyperCore |
| <Icon icon="https://cdn.discordapp.com/emojis/1343133640720257075" /> HyperEVM   | <code>999</code>          | HyperEvm  |
| <Icon icon="https://cdn.discordapp.com/emojis/1354059885712773243" /> Initia     | <code>interwoven-1</code> | Initia    |
| <Icon icon="https://cdn.discordapp.com/emojis/1303429057916047472" /> Injective  | <code>injective-1</code>  | Injective |
| <Icon icon="https://cdn.discordapp.com/emojis/1352270397952753714" /> Linea      | <code>59144</code>        | Linea     |
| <Icon icon="https://cdn.discordapp.com/emojis/1412153143332179968" /> Mitosis    | <code>124816</code>       | Mitosis   |
| <Icon icon="https://cdn.discordapp.com/emojis/1436699982085492839" /> Nano       | -                         | Nano      |
| <Icon icon="https://cdn.discordapp.com/emojis/1420338366003675136" /> Nibiru     | <code>6900</code>         | Nibiru    |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545096231391243" /> Osmosis    | <code>osmosis-1</code>    | Osmosis   |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545082339590154" /> Optimism   | <code>10</code>           | Optimism  |
| <Icon icon="https://cdn.discordapp.com/emojis/1497264125930246214" /> Pepecoin   | -                         | Pepecoin  |
| <Icon icon="https://cdn.discordapp.com/emojis/1423036332896293025" /> Plasma     | <code>9745</code>         | Plasma    |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545128632385579" /> Polygon    | <code>137</code>          | Polygon   |
| <Icon icon="https://cdn.discordapp.com/emojis/1525850149216059443" /> Robinhood  | <code>4663</code>         | Robinhood |
| <Icon icon="https://cdn.discordapp.com/emojis/1303760872711393342" /> SEDA       | <code>seda-1</code>       | SEDA      |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545143442341898" /> Sei        | <code>pacific-1</code>    | Sei       |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545143442341898" /> Sei EVM    | <code>1329</code>         | SeiEvm    |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545162736140339" /> Solana     | -                         | Solana    |
| <Icon icon="https://cdn.discordapp.com/emojis/1436303481886478416" /> Somnia     | <code>5031</code>         | Somnia    |
| <Icon icon="https://cdn.discordapp.com/emojis/1348728509392093215" /> Sonic      | <code>146</code>          | Sonic     |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545169363275877" /> Stargaze   | <code>stargaze-1</code>   | Stargaze  |
| <Icon icon="https://cdn.discordapp.com/emojis/1281545176153854013" /> Terra      | <code>phoenix-1</code>    | Terra     |
| <Icon icon="https://cdn.discordapp.com/emojis/1374023266888585287" /> Unichain   | <code>130</code>          | Unichain  |
| <Icon icon="https://cdn.discordapp.com/emojis/1368652762048499783" /> Yominet    | <code>yominet-1</code>    | Yominet   |


# Balance
Source: https://docs.flipsuite.xyz/flippy/commands/balance

Learn more about the /balance command.

## Commands

Balance commands are used to check your points, token, or NFT balance.

<Tip>
  Instead of using commands, you can ask [Flippy](/flippy/introduction#who-is-flippy) in chat to check or display your balance.
</Tip>

### `/balance tokens`

This command will display your Flipwallet token balance.

<Accordion title="Command arguments">
  <ParamField type="string">
    If you want to check token balance for a single chain, enter one of the [supported chains](https://flipsuite.xyz/tokens) here.
  </ParamField>

  <ParamField type="boolean">
    Whether to display your balance as a public message or not.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

### `/balance nfts`

This command will display your Flipwallet NFT inventory.

<Accordion title="Command arguments">
  <ParamField type="string">
    If you want to check NFT inventory for a single chain, enter one of the [supported chains](https://flipsuite.xyz/tokens) here.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

You can inspect NFTs in your inventory by selecting them in the dropdown.

<Frame>
  <img />
</Frame>

### `/balance points`

This command will display your cross-server [points](/points/introduction) balance.

<Accordion title="Command arguments">
  <ParamField type="boolean">
    Whether to display your balance as a public message or not.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>


# Flipsuite Bank
Source: https://docs.flipsuite.xyz/flippy/commands/bank

Learn more about the /bank command.

## Overview

Bank is an escrow maintained and controlled by Flipsuite where you can deposit your **Solana** tokens to execute tips,
airdrops, and raffles. Due to Solana's technical nuances, this is the only way to tip Solana tokens in Flipsuite.

<Frame>
  <img />
</Frame>

To view your Flipsuite bank balance simply execute the `/bank` command.

<Warning>
  Bank balance is separate from your Flipwallet balance. It's used only to execute tips, raffles, and airdrops on
  the Solana chain. All other Flipsuite features still use your Flipwallet balance.
</Warning>

## How to deposit tokens to the bank?

To move tokens from your Flipwallet to the bank, simply click the **deposit** button, enter a token symbol and amount you'd
like to deposit, and confirm.

<Frame>
  <img />
</Frame>

After the deposit is complete, you will be able to airdrop, raffle, and tip the Solana tokens you've deposited
with no gas fees.

## How to withdraw tokens from the bank?

To withdraw tokens from the bank, simply click the **withdraw** button, enter a token symbol and amount you'd
like to withdraw, select a recipient, and confirm.

<Frame>
  <img />
</Frame>

<Warning>
  If you are withdrawing tokens other than SOL from the bank, you will need to pay for the withdrawal transaction
  fees using your Solana Flipwallet balance.
</Warning>


# Deposit
Source: https://docs.flipsuite.xyz/flippy/commands/deposit

Learn more about the /deposit command.

## Overview

You can use `/deposit` command to deposit tokens to your Flipwallet via QR code.

<Accordion title="Command arguments">
  <ParamField type="string">
    One of the [supported chains](/chains).
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

You don't have to use the `/deposit` command to deposit tokens to your Flipwallet every time. If you know your
chain-specific Flipwallet address, you can send tokens and NFTs to it as you would do with any other wallet.

## Flipwallet address

You cand find your Flipwallet address for a specific chain using the `/flipwallet` command.

<Frame>
  <img />
</Frame>


# Profile
Source: https://docs.flipsuite.xyz/flippy/commands/profile

Learn more about the /profile command.

## Overview

You can use `/profile` command to view your Flipsuite profile.

<Frame>
  <img />
</Frame>

In your profile, you can:

1. View temporary roles in servers
2. View your [vote](/flippy/commands/vote) streak
3. Quickly access your [balance](/flippy/commands/balance), [inventory](/flippy/commands/inventory), [bank](/flippy/bank) and [rewards](/flippy/commands/rewards)
4. Enter your profile settings
5. View your profile stats
6. Quickly access your [limit orders](/modules/trading/commands/orders) and [open positions](/modules/trading/commands/positions)

## Settings

<Frame>
  <img />
</Frame>

In your profile settings, you can do the following:

1. Manage your address book
2. Disable chatting with Flippy
3. Disable confirmations for certain actions
4. Manage notification settings
5. Manage your privacy settings
6. Manage your tipping settings

### 1. Address book

In the address book settings, you can save wallets that you often use so you don't have to enter them every time.
You will be able to quickly access them when withdrawing tokens from your Flipwallet, claiming rewards, submitting
wallets to whitelists and much more.

<Frame>
  <img />
</Frame>

### 2. Chatting settings

In chatting settings you can disable chatting with Flippy. By disabling this option Flippy won't see and won't
respond to your messages in Discord.

<Frame>
  <img />
</Frame>

### 3. Confirmation settings

In the confirmation settings menu you can:

* Set confirmation mode (always, command only, chat only, or none)
* Set confirmation threshold for transfers (applies to tips, airdrops and raffles)

<Frame>
  <img />
</Frame>

<Warning>
  Disabling confirmations when chatting with Flippy is not recommended. Due to its agentic
  nature, it may and **probably will** occasionally make mistakes. Confirmations are the only
  step guarding you from unwanted transactions.
</Warning>

### 4. Notification settings

In the notification settings menu you can opt out from specific tip notifications or pings.

<Frame>
  <img />
</Frame>

### 5. Privacy settings

In privacy settings you can decide what information about socials and wallets linked to your account is shared with
servers you verify in. Each option can be enabled/disabled either globally for all servers or on a per-server basis.

<Frame>
  <img />
</Frame>

### 6. Tipping settings

In tipping settings you can configure the minimum account age that's required to enter your airdrops and raffles, and
change the wallet to use for tipping (see [shared tipping wallets](/modules/tipping/shared-wallet)).

<Frame>
  <img />
</Frame>

## Token lists

In the token list settings, you can manage custom tokens that are not yet verified by Flipsuite.

* **Approved tokens** show up in your Flipwallet balance and token selection menus.
* **Blocked tokens** are hidden from your balance and suppress token notifications.


# Rewards
Source: https://docs.flipsuite.xyz/flippy/commands/rewards

Learn more about the /rewards command.

## Overview

You can use `/rewards` command to open the reward center and view a different type of rewards you have accumulated
via Flipsuite.

<Frame>
  <img />
</Frame>

In the reward center, you can access the following types of rewards:

1. **Referral rewards**
2. **Server rewards**
3. **Trading rewards**
4. **Voting rewards**

## 1. Referral rewards

Here, you can view rewards that you earned by referring other users to to use Flipsuite.

<Frame>
  <img />
</Frame>

## 2. Server rewards

Here, you can view pending rewards that you've accumulated by completing quests.

<Frame>
  <img />
</Frame>

To claim earned tokens, simply select them from the dropdown and confirm, or ask [Flippy](/flippy/introduction) to collect
all claimable rewards for you.

<Note>
  Server owners can configure when and how you can claim rewards through custom reward
  claim cooldown periods and minimum token amounts required before claiming.
</Note>

## 3. Trading rewards

Here, you can view pending prizes from weekly Hyperliquid trading competitions. Each week, the top 3 and last 1
traders receive a reward from the accumulated **USDC** pool in that week.

<Frame>
  <img />
</Frame>

To claim the rewards, simply select them from the dropdown and confirm.

## 4. Voting rewards

Here, you can view pending rewards that you earned by voting for Flipsuite. Every 12 hours, you can vote for Flipsuite
on [Top.gg](https://top.gg/bot/1150448986264698980/vote) to receive a random reward from the pool.

<Frame>
  <img />
</Frame>

To claim the rewards, simply select them from the dropdown and confirm.


# Send
Source: https://docs.flipsuite.xyz/flippy/commands/send

Learn more about the /send command.

## Commands

You can use `/send` commands to withdraw tokens and NFTs from your Flipwallet.

### `/send token`

This command is used to withdraw tokens from your Flipwallet to an external wallet address.

<Accordion title="Command arguments">
  <ParamField type="string">
    Token from your Flipwallet that you want to send.
  </ParamField>

  <ParamField type="string">
    Amount to send. You can use "%" and "\$" for relative amounts.
  </ParamField>

  <ParamField type="string">
    Wallet address to send the tokens to.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

### `/send nft`

This command is used to send NFTs from your Flipwallet to an external wallet address.

<Accordion title="Command arguments">
  <ParamField type="string">
    One of the [supported chains](https://flipsuite.xyz/tokens).
  </ParamField>

  <ParamField type="string">
    NFT to send.
  </ParamField>

  <ParamField type="string">
    Amount of NFTs to send (applicable only to ERC-1155 tokens).
  </ParamField>

  <ParamField type="string">
    Wallet address to send the tokens to.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>


# Vote
Source: https://docs.flipsuite.xyz/flippy/commands/vote

Learn more about the /vote command.

## Overview

You can use `/vote` command to earn free rewards by voting for Flipsuite and other projects on [Top.gg](https://top.gg/bot/1150448986264698980/vote).

<Frame>
  <img />
</Frame>

Once you vote, you'll receive a notification from Flippy in DMs with a reward.

<Frame>
  <img />
</Frame>


# Introduction
Source: https://docs.flipsuite.xyz/flippy/introduction

Get familiar with Flipwallets and Flippy, your onchain wallet assistant.

## What is Flipwallet?

Flipwallet is your ultimate social wallet that connects all [supported blockchains](/chains) together.
You can access it through Discord, and that's where you can chat with Flippy as well.

<Frame>
  <img alt={"Token balance output"} />
</Frame>

<AccordionGroup>
  <Accordion title={"How is Flipwallet created?"}>
    Your Flipwallet is automatically generated for you as soon as you need it - no need to sign up, deposit tokens,
    or manually create it. Simply ask Flippy for your wallet address or execute the `/flipwallet` command in Discord
    to see your chain-specific address.
  </Accordion>

  <Accordion title={"What tokens are supported?"}>
    You can deposit any token you want to your Flipwallet, but only verified tokens will show up in your balance
    automatically. Unverified tokens need to be added to your personal token list before you can see them in your
    balance.
  </Accordion>

  <Accordion title={"What NFTs are supported?"}>
    All NFT collections can be accessed through Flipwallet by default. Unless they are marked as spam, they can be
    used for tips and rewards immediately.
  </Accordion>

  <Accordion title={"How do I deposit?"}>
    Simply ask Flippy for your wallet address or execute the `/flipwallet` command in Discord to see your
    chain-specific address. Then, simply deposit tokens and NFTs to this address as you would do to any other wallet.
  </Accordion>

  <Accordion title={"How do I withdraw?"}>
    You can withdraw tokens and NFTs from your Flipwallet by asking Flippy or using the `/send tokens` and `/send nfts`
    commands in Discord and specifying the address you want to withdraw to.
  </Accordion>

  <Accordion title={"Are there any fees?"}>
    We do not charge any fees for making transactions with your Flipwallet. The only fees you have to pay are the
    transaction gas fees, which vary for each blockchain.
  </Accordion>

  <Accordion title={"Can I backup my Flipwallet?"}>
    Yes, to export the private key of your Flipwallet simply use the `/flipwallet` command in Discord
    and click the **export private key** button.
  </Accordion>
</AccordionGroup>

## Who is Flippy?

Flippy is a digital wallet assistant built on FlippyOS, layered over Flipsuite. It has supervised access to your Flipwallet
and can execute multiple actions on your behalf, many of which are not possible via traditional slash commands.

<video>
  <source type="video/webm" />
</video>

**What does Flippy say about himself?**

> I'm Flippy, your onchain wallet assistant powered by FlippyOS on top of Flipsuite. I keep things chill and
> degen-friendly while handling hundreds of crypto actions daily. Whether you're a normie or a power user, i got
> your back with tips, swaps, airdrops, raffles, and more - all in a smooth, casual style. Think of me as your crypto
> sidekick making wallet moves easy and fun.

<Tip>
  Even though Flippy has supervised access to your account, we are very well aware that AI agents sometimes make
  mistakes, so all potentially dangerous or sensitive actions are always protected by a confirmation step, so Flippy
  doesn't accidentally do something you didn't mean to.
</Tip>

## What can Flippy do for you?

* Check your Flipwallet address
* Check your token and NFT balances
* Send token and NFT tips to users or roles
* Create raffles and airdrops
* Place limit buy and sell orders
* Swap and bridge tokens across chains (incl. bulk swaps)
* Send tokens and NFTs to external wallets (incl. bulk transfers)
* Claim all your pending rewards at once
* Bump your airdrops and raffles
* Show you your wallet balance or NFT inventory
* Answer any questions regarding Flipsuite
* Withdraw tokens from the bank
* Deposit tokens to the bank
* Save tokens in your custom token list
* Open, close and update Hyperliquid positions for you
* Show you your Hyperliquid positions and share them in chat
* Generate Hyperliquid referral code
* Provide technical analysis on various tokens, and show you their charts
* And much, much more...

<Note>
  Flippy is being updated rapidly, so the above list might not be up-to-date at all times. Best way to check what
  it can do is to ask him in chat directly.
</Note>

## How much does it cost?

Interacting with Flippy is totally free during beta. Once beta tests are over, Flippy will be available for
free to everyone with a limited number of interactions per day, week, or month. Unlimited usage will be gated behind
a premium subscription.


# Security
Source: https://docs.flipsuite.xyz/flippy/security

Learn more about your Flipwallet security.

## Overview

All Flipwallets are secured and powered by [Privy](https://www.privy.io/) - the industry-leading platform that provides
highly secure, scalable embedded wallet infrastructure with robust multi-chain support and enterprise-grade security standards.

> At Privy, we've built our security foundation on unwavering principles. Our systems are non-custodial by design, ensuring
> that only authorized users can access their keys through sophisticated key splitting and secure execution environments.
> We implement defense in depth, with multiple independent security boundaries protecting your users' assets - from cryptographic
> guarantees to hardware-level isolation.

You can read more about technical details and Privy approach to security in [their docs](https://docs.privy.io/security/overview).

## Legacy Wallets

If you were a Flipsuite user before `22nd August 2025`, most of your Flipwallets (depending on which chains you interacted with)
are probably using the legacy wallet system that wasn't using Privy as an extra layer of security for your wallet.

> This legacy wallet system is kept secure and will still be maintained moving forward, but we recommend everyone to migrate
> their Flipwallets to use Privy, so they don't miss out on future benefits and perks coming from using a Privy wallet.

### How to upgrade your legacy wallet to Privy?

To migrate your legacy Flipwallet to use Privy, simply execute the `/flipwallet` command in Discord and click the
**upgrade to privy wallet** button.

<Frame>
  <img />
</Frame>

This will generate a fresh Privy Flipwallet for the selected chain. You can switch between your legacy and Privy
Flipwallet using **switch to privy wallet** and **switch to legacy wallet** buttons.

<Warning>
  Some Privy-based Flipwallets have a new onchain address, so you need to migrate your tokens and NFTs from your legacy
  Flipwallet to the new address in order to use them in the new wallet.
</Warning>

### How to migrate funds from a legacy wallet?

After upgrading your legacy Flipwallet to Privy, you might see the **migrate balance** and **migrate inventory** buttons.
Simply tap them to start migrating your balance and NFTs to the new wallet.

<Frame>
  <img />
</Frame>

<Tip>
  Don't see the migrate buttons after upgrading your wallet? It means your Flipwallet address was preserved during
  the upgrade and you don't need to migrate any funds!
</Tip>


# Customization
Source: https://docs.flipsuite.xyz/gating/customization

Customize the verification panel shown in Discord.

<div>
  <a href="https://flipsuite.xyz/pricing"><Icon icon={"cubes"} /><p>Scale only</p></a>

  <div />
</div>

Open **Gating > Customization** in your community dashboard to edit the verification panel template and preview it
before publishing.

<Frame>
  <img />
</Frame>

Things you can customize:

* Author and footer
* Title and description
* Embed fields
* Image, thumbnail and color


# Introduction
Source: https://docs.flipsuite.xyz/gating/introduction

Set up Discord role verification for holders, members, and linked accounts.

Gating lets you grant and remove Discord roles automatically based on rules you configure in Flipsuite. Use it to
verify holders, create access tiers, gate private channels, and keep roles in sync as member status changes.

## What can you do with gating

* Verify token holders, NFT holders, and point holders.
* Check Discord-based eligibility, including account age and roles from other servers.
* Gate access using linked X account requirements like followers or subscriptions.
* Connect custom API-based rules to your own product or backend.
* Monitor roles refresh status and verified members from the dashboard.

## How gating works

1. Create one or more rules in the **Gating** area of your community dashboard.
2. Choose which Discord role each rule should grant.
3. Post the verification panel to a public channel in your server.
4. Members verify and Flipsuite checks every configured rule.
5. Flipsuite grants or removes roles immediately.
6. After verification Flipsuite keeps the roles in sync with refreshes.

## What's next?

<Card title="Set up gating" icon="wrench" href="/gating/setup">
  Invite Flippy, create your first rules, and post the verification panel in Discord.
</Card>


# Notifications
Source: https://docs.flipsuite.xyz/gating/notifications

Send verification logs to a Discord channel.

Use gating notifications to monitor who verified, which roles changed, and what happened during bulk refreshes.

## Set up a verification logs channel

Open **Gating > Settings** and set **Verification logs channel**.

<Frame>
  <img />
</Frame>

<Warning>
  Keep the verification logs channel private. These posts are meant for moderators and can expose who gained or lost
  access roles.
</Warning>

## What gets posted

Each gating log will include:

* The member whose roles were updated.
* Roles that were added and/or removed.
* User's linked X account, if their privacy settings allow it.

<Frame>
  <img />
</Frame>


# Refreshing
Source: https://docs.flipsuite.xyz/gating/refreshing

Keep gated roles in sync with automatic and manual refresh tools.

## Auto refresh

Open **Gating > Console** to see your current auto refresh interval and the next scheduled run.

<Frame>
  <img />
</Frame>

Automatic refresh re-checks all previously verified users in the specified interval.

### Instant updates

Some rules are refreshed instantly, regardless of the auto refresh interval:

* Point-based rules are updated instantly when balances change.
* On [Scale](https://flipsuite.xyz/pricing) plans, the following rules also receive real-time updates:
  * NFT balance (on EVM chains)
  * Token balance (on EVM and Solana chains)

## Bulk refresh

If you need to refresh members' roles immediately, use **Run bulk refresh** in **Gating > Console**.

<Frame>
  <img />
</Frame>

* Bulk refresh only checks users who have verified at least once.
* Each run counts against your refresh allowance for the current billing period.
* Role changes from the bulk refresh are posted in the set [logs channel](/gating/notifications) as they happen.

## Refresh exemptions

To skip certain users from automatic and bulk role updates, open **Gating > Settings** and configure
**Refresh exempt roles** to skip certain users during bulk refreshes.

<Frame>
  <img />
</Frame>

Users with any role configured above will keep their roles during auto/bulk refresh.

<Tip>
  You can use this for team members, temporary exceptions, or manual VIP overrides.
</Tip>


# Setup
Source: https://docs.flipsuite.xyz/gating/setup

Invite Flippy, create gating rules, and post your verification panel.

> Setting up gating starts with Discord permissions and role hierarchy, then moves into rule creation and posting the
> verification panel.

## Step 1 - Invite Flippy

If Flippy is not in your server yet, start with the [Quickstart](/quickstart) guide and invite it.

* **Manage Roles** permission is required for granting and removing gated roles.

## Step 2 - Prepare Discord roles

Before creating rules, move Flippy's role above every role you want gating to manage.

<Warning>
  Flippy can only grant and revoke roles from users in your server that are **below its role** in your server's
  role hierarchy. You can access it by going to the `Roles` tab in your server settings.

  <Frame>
    <img />
  </Frame>

  In the example above, Flippy can only grant the "Verified - Tier 2" role to your community members. It won't have
  access to the "Verified - Tier 3" role because it's above the bot's role.
</Warning>

## Step 3 - Create gating rules

Open **Gating** in your community dashboard and go to **Rules**. Here, you can add your first rule.

<Frame>
  <img />
</Frame>

Each gating rule has two parts:

* **Discord role**: The role Flipsuite should grant when the rule passes.
* **Requirement**: The condition that must be satisfied by the verifying member.

<Tip>
  Gating reuses a subset of quest requirements under the hood, so the rule builder will feel familiar if you already use
  the [Quest Engine](/quests/introduction). Unlike quests, gating only supports automatically verifiable requirements.
  Input and manual-review tasks are not available here yet.
</Tip>

View [task library](/quests/tasks) for a full list of available requirement types.

<Frame>
  <img />
</Frame>

## Step 4 - Post the verification panel

Once you have at least one rule, open **Gating > Console** and choose a **gating panel channel**. Flipsuite will
post the verification panel automatically in that channel.

<Frame>
  <img />
</Frame>

After the channel is set members can click **verify** to verify and unlock roles in your server.

<Frame>
  <img />
</Frame>

## What's next?

Learn how to keep roles in sync, route verification logs, and customize the panel's appearance.

<CardGroup>
  <Card title="Refreshing" icon="repeat" href="/gating/refreshing">
    Learn how to manually refresh your community members' roles.
  </Card>

  <Card title="Notifications" icon="bell-ring" href="/gating/notifications">
    Get notified whenever users' roles are updated due to verification.
  </Card>

  <Card title="Customization" icon="sparkles" href="/gating/customization">
    <p>Customize the gating verification panel in your server.</p>

    <div>
      <a href="https://flipsuite.xyz/pricing"><Icon icon={"cubes"} /><p>Scale only</p></a>
    </div>
  </Card>
</CardGroup>


# Introduction
Source: https://docs.flipsuite.xyz/introduction

The rewards engine for internet communities.

## Welcome to Flipsuite!

Flipsuite is turning the multi-billion-dollar community rewards market on its head with high-end task tracking combined
with **automated** distribution, both **onchain** with blockchain-based rewards and **offchain** via highly customizable
points and experience systems.

Whether you're planning a massive campaign or keeping your crew entertained, Flipsuite manages the stuff you are
procrastinating about - reward management, task planning, and payouts - while equipping you and your people with
[Flippy](/flippy/introduction#who-is-flippy) - a **unique AI agent** you can talk to, distribute rewards with, run
giveaways, and much more.

## Get started

Ready to give your community a reason to stay?

<Card title="Quickstart" icon="rocket" href="/quickstart">
  Learn how to set up Flippy in your server with this step-by-step guide.
</Card>

Want to learn more about Flippy - our special sauce?

<Card title="Flippy" icon="face-smirking" href="/flippy/introduction">
  Get familiar with Flipwallets and Flippy, your onchain wallet assistant.
</Card>


# Privacy Policy
Source: https://docs.flipsuite.xyz/legal/privacy



**Last updated:** June 13th, 2025

Flipsuite.xyz is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and
safeguard your information when you visit our website at [https://flipsuite.xyz](https://flipsuite.xyz) or use our services.

By accessing or using our services, you agree to the terms of this Privacy Policy. If you do not agree with our policies,
please do not use our services.

***

## 1. Information We Collect

### User-Provided Information

We collect personal information that you provide to us directly on flipsuite.xyz, including:

* Personal information you provide when creating an account using Discord sign-up.
* Wallet addresses and social media accounts you link to your Flipsuite account.

### Automatically Collected Information

Our systems collect certain information automatically including:

* IP addresses, browser type, ISP, timestamps, referring/exit pages, and click counts.
* Cookies and similar technologies to improve site functionality and user experience.

You can control or disable cookies using your browser settings.

### Discord Data

We **do not** store any Discord-related personal data beyond the information provided during sign-in as specified above.
Any interactions via Discord bots or apps **do not** result in storing your personal data and message content on our
servers.

***

## 2. Use of Your Information

We use your information to:

* Provide, operate, and maintain the flipsuite.xyz website and services.
* Communicate with you, respond to inquiries, and provide customer support.
* Personalize your experience and develop new features.
* Prevent fraud and enhance security.
* Manage user eligibility and authorization.

### Flippy AI Agent and Your Data

Flippy, our AI agent, **does not** access your Discord data or any personal information outside of what you explicitly
provide or share on flipsuite.xyz. Your Discord interactions remain private and **are not** used to train Flippy or any
other AI models.

### Sharing Linked Wallet and Social Account Information

Linked wallets and social accounts on flipsuite.xyz may be shared with the teams belonging to the communities you
participate in. This information is always shared securely through the flipsuite.xyz dashboard.

Only information explicitly shared by you on flipsuite.xyz - as done so when linking wallets or socials - will be
accessible to these community teams.

You have full control over this sharing and may **opt out at any time** by adjusting your privacy settings on the
flipsuite.xyz dashboard.

Flipsuite retains access to this information solely for debugging purposes and to support necessary features related
to your account and community participation.

***

## 3. Data Retention

We retain personal information only as long as necessary to fulfill the purposes described or as required by law.

Since we do **not** store Discord data beyond sign-in information, no additional retention or auto-deletion applies to
other Discord data.

Logs and other technical data are kept internally for debugging and analytics purposes only and are **not shared with
any third parties**. These logs are retained for 30 days, after which they are securely deleted.

***

## 4. Third-Party Sharing and Disclosure

We do **not** sell or rent your personal data.

We may share your data with trusted third-party service providers who help operate our services under strict
confidentiality agreements.

Internal logs and analytics data are used solely for debugging and internal growth analytics and are **never**
shared externally.

Linked wallet and social account information is shared only with teams in communities you actively participate in, as
described above, and only if you have not opted out.

We may disclose personal data if required by law or to protect our legal rights.

***

## 5. Your Privacy Rights

### California Consumer Privacy Act (CCPA)

California residents have rights including:

* Requesting disclosure of personal data collected.
* Requesting deletion of personal data.

### General Data Protection Regulation (GDPR)

European users have rights including:

* Accessing, correcting, deleting, or restricting processing of personal data.
* Objecting to data processing.
* Data portability requests.

To exercise these rights, please contact us at **[team@flipsuite.xyz](mailto:team@flipsuite.xyz)**.

***

## 6. Children's Privacy

Flipsuite.xyz does not knowingly collect personal information from children under 13.

If a parent or guardian believes their child has provided personal information, please contact us to request removal.

***

## 7. Cookies and Tracking

We use cookies and similar technologies to enhance your experience.

You have the right to control cookie usage via browser settings.

***

## 8. Changes to This Privacy Policy

We may update this Privacy Policy periodically.

Changes will be posted here with an updated "Last updated" date.

If changes are material, we will notify registered users via email or website notice.

***

## 9. Contact Us

For questions or to exercise your privacy rights, contact us at **[team@flipsuite.xyz](mailto:team@flipsuite.xyz)**.


# Terms of Service
Source: https://docs.flipsuite.xyz/legal/tos



**Last Updated:** June 08, 2026

Welcome to Flipsuite.xyz ("Flipsuite", "we", "us", or "our"). By inviting Flipsuite to your Discord server, using our bots or APIs, creating or using a Flipwallet, exporting private keys, purchasing or maintaining a paid subscription, or accessing our website ([https://flipsuite.xyz/](https://flipsuite.xyz/)), you ("you" or "User") agree to these Terms of Service ("Terms"). If you do not agree, do not use Flipsuite.

You are responsible for informing members of your Discord server about these Terms if you add Flipsuite to your server.

## 1. Eligibility and Compliance

* You represent that you are at least 18 years old (or the age of majority in your jurisdiction) and have the legal capacity to enter into these Terms.
* You will comply with all applicable laws and regulations, including those related to digital assets and consumer protection, Discord’s Terms of Service and policies, and any anti-fraud, anti-money laundering, and sanctions laws. You confirm you are not a person or entity on any sanctions list or located in a prohibited jurisdiction.
* If required by law or risk policies, we may request additional information (including identity verification). Your failure to provide it may result in suspension or termination.

## 2. Services

* Flipsuite provides: (a) onchain rewards and points tooling; (b) AI agent-assisted interactions ("Flippy"); (c) app-integrated wallets ("Flipwallets"); (d) token listing support and related features; and (e) developer/API access.
* We may add, modify, or remove features at any time.

## 3. Accounts and Security

* You are responsible for maintaining the confidentiality of your credentials (e.g., Discord account, Flipsuite account, device credentials) and all activity under your account.
* We strongly recommend enabling Two-Factor Authentication (2FA) at [https://flipsuite.xyz/account/security](https://flipsuite.xyz/account/security).
* Notify us immediately at [team@flipsuite.xyz](mailto:team@flipsuite.xyz) of any suspected unauthorized access.

## 4. Wallets and Custody (Flipwallets)

### 4.1 Overview

* Flipwallets are software-enabled blockchain wallets used within Flipsuite. Transactions are executed on public networks and are irreversible.
* We will not perform actions on your Flipwallet without your express authorization as described below.

### 4.2 Wallet Types

A. v1 Legacy Flipwallets (Custodial)

* Custody: Flipsuite fully manages legacy wallets and retains the ability to access and sign transactions for those wallets. Private keys are heavily encrypted and protected using industry-standard security measures. Nevertheless, these are custodial wallets.
* Use of Funds: We will only act on legacy wallets to carry out your instructions provided through the service or as required by law, court order, or to address demonstrable security threats (e.g., to prevent or mitigate ongoing theft or exploitation).
* Risks: You acknowledge that custodial arrangements involve risks, including operational risks, third-party provider risks, and legal or regulatory actions that may require us to restrict access or take action on assets.

B. v2 Privy Server Flipwallets (Consent-Gated Access; Non-Custodial to Flipsuite)

* Custody/Keys: v2 wallets are secured via Privy ([https://www.privy.io/](https://www.privy.io/)). Flipsuite does not possess or see your raw private keys. Flipsuite cannot unilaterally move assets from v2 wallets.
* Access to Perform In-App Actions: Flipsuite can only access v2 Flipwallets to perform in-app actions with your explicit consent. Your consent is captured via clear prompts in our interface (e.g., UI confirmations, commands, or signed approvals). Without such consent, Flipsuite cannot execute transactions on your v2 wallet.
* Reliance on Privy: You acknowledge that v2 wallets rely on Privy’s authentication, key management, and infrastructure. Outages, changes, or errors by Privy may affect access to or functionality of your v2 wallet. Flipsuite is not responsible for Privy’s acts, omissions, or outages.

### 4.3 Transaction Authorization

* For v1 wallets, Flipsuite will process transactions only upon your instruction or as otherwise permitted under 4.2(A).
* For v2 wallets, every Flipsuite-initiated in-app action requires your explicit consent at the time of action. You may revoke session approvals where supported. Absent your consent, we cannot effect transactions.

### 4.4 Private Key Export

* Availability: You may export private keys for your Flipwallet(s) where supported. Exporting keys transfers full control and responsibility for custody and security to you.
* Your Responsibilities: You are solely responsible for safeguarding exported keys and any seed phrases, backups, or passcodes. Loss, theft, or compromise of private keys may result in permanent, irretrievable loss of assets. Flipsuite cannot recover lost keys or funds.
* Security: Use secure storage practices, keep backups offline, and enable 2FA at [https://flipsuite.xyz/account/security](https://flipsuite.xyz/account/security). Do not share keys with anyone. Be aware of phishing and malware risks.
* No Liability After Export: To the maximum extent permitted by law, Flipsuite disclaims all liability for losses or damages arising from or related to your exported keys, any self-custody actions, or your failure to implement adequate security.

### 4.5 Migrations and Availability

* We may offer migration from v1 to v2 wallets or other architectures to improve security and user control. Migration may require your consent and may be subject to technical or regulatory constraints.
* We may temporarily restrict wallet functionality to address security risks, comply with legal obligations, or maintain system integrity.

### 4.6 Airdrops, Forks, Unsupported Assets

* We may determine in our discretion whether and how to support network forks, airdrops, or other events. Certain tokens or networks may be unsupported. We are not liable for losses due to forks or unsupported assets.

## 5. AI Agent ("Flippy") Disclaimer

* Flippy is an AI-powered assistant and may generate outputs that are incomplete, untimely, or inaccurate. AI content is provided "as-is" and is for informational and operational assistance only; it is not investment, legal, or tax advice.
* You are solely responsible for any actions you take in reliance on Flippy. Flipsuite disclaims liability for losses arising from AI outputs or your interactions with Flippy.

## 6. Prohibited Uses

* Illegal or Unlawful Activity: Do not use Flipsuite in violation of any law, regulation, sanctions regime, or Discord policy.
* Abuse and Interference: Do not exploit, manipulate, reverse engineer, attack, spam, or otherwise misuse Flipsuite, Flippy, our APIs, or infrastructure.
* Alt Accounts: Operating multiple Discord accounts to exploit rewards, giveaways, or other features is prohibited and may result in suspension or termination.
* Sanctions/Evasion: You may not use the service if you are subject to sanctions or are attempting to evade sanctions or compliance controls.

## 7. Token Support, Listing, and Removal

### 7.1 Token Listing Fee

* Requests to list new tokens are subject to a flat, non-refundable fee of \$250 USD (or USDC equivalent). Listing decisions are at Flipsuite’s sole discretion and may include eligibility criteria.

### 7.2 Token Maintenance and Removal

* We may remove tokens at any time, including for developer misconduct, fraud, or malicious contracts. Where feasible for ongoing violations, we will generally provide 30 days’ notice; immediate action may be taken for security or legal reasons.

## 8. API Use and Gambling Restrictions

* The Flipsuite API may not be used in gambling products or any gambling-related activity involving assets of real-world value on Discord (on-chain or off-chain), consistent with Discord’s Gambling Policy. Violations will result in immediate termination or suspension.

## 9. Fees, Paid Subscriptions, Automatic Renewal, Cancellation, and Refunds

### 9.1 Paid Plans and Subscription Access

* Certain Flipsuite features, limits, modules, integrations, or services may require a paid subscription, paid plan, usage-based charge, token listing fee, setup fee, integration fee, or other paid arrangement.
* Paid subscriptions provide access to the applicable Flipsuite plan, features, limits, or services during the relevant billing period. Subscription fees are charged for access and availability during the billing period, not for actual use, login activity, Discord server activity, command volume, wallet activity, or measured customer engagement unless expressly stated otherwise in writing.
* Your failure to use the service, your reduced use of the service, inactivity in your Discord server, removal of the bot from a Discord server, loss of administrator access, loss of interest in the service, or failure to remember an active subscription does not relieve you of payment obligations and does not entitle you to a refund.

### 9.2 Billing Authorization

* By purchasing a paid subscription or clicking a subscription purchase button, you authorize Flipsuite and its payment processor to charge your selected payment method for the stated price, billing interval, applicable taxes, and any other disclosed fees until the subscription is canceled in accordance with these Terms.
* Unless otherwise stated at checkout or in a written agreement signed by Flipsuite, subscriptions automatically renew for successive billing periods of the same length until canceled.
* Subscription charges may be processed through Stripe or another third-party payment processor. Your payment information and payment processing are subject to the applicable payment processor’s terms, policies, and security practices.
* You are responsible for keeping your payment method, billing information, and contact information current. We may suspend, limit, downgrade, or terminate access if payment fails, is reversed, is disputed, or cannot be collected.

### 9.3 Automatic Renewal Terms

* For each subscription, the checkout flow, invoice, receipt, pricing page, order page, or related subscription interface may identify the subscription price, billing interval, plan name, renewal terms, and cancellation method.
* Unless otherwise stated, your subscription will continue and automatically renew unless you cancel before the applicable renewal date.
* Renewal charges are billed at the start of each renewal period unless otherwise stated.
* You agree that Flipsuite is not required to send a separate reminder before each monthly renewal unless required by applicable law or expressly stated in writing.
* If applicable law requires renewal notices, acknowledgments, cancellation instructions, records of consent, or other subscription disclosures, Flipsuite will provide them in the manner required by law.

### 9.4 Cancellation

* You may cancel a subscription by using the available account, billing, dashboard, customer portal, or support cancellation method provided by Flipsuite, or by contacting [team@flipsuite.xyz](mailto:team@flipsuite.xyz).
* Cancellation prevents future renewal charges if completed before the applicable renewal date. Cancellation does not automatically refund charges already incurred.
* Unless otherwise stated by Flipsuite in writing, cancellation takes effect at the end of the then-current billing period, and you may continue to have access to paid features until that period ends.
* You are responsible for canceling before renewal if you do not want future charges. Failure to cancel before renewal, including because you forgot, did not use the service, did not recognize the charge, did not monitor your account, or assumed cancellation occurred, does not entitle you to a refund.
* Removing Flipsuite from a Discord server, deleting a Discord server, changing Discord permissions, disabling commands, failing to log in, failing to use paid features, or stopping use of the service does not constitute cancellation unless Flipsuite expressly confirms cancellation through an authorized billing or support channel.

### 9.5 Refund Policy

* Except where required by applicable law or expressly agreed by Flipsuite in writing, all subscription fees, renewal charges, setup fees, token listing fees, integration fees, usage-based fees, overage fees, and other paid charges are non-refundable.
* We do not provide prorated refunds or credits for partial billing periods, unused time, unused features, unused limits, unused commands, unused server access, inactivity, forgotten subscriptions, mistaken renewals, failure to cancel, loss of access caused by your own account or Discord configuration, or claims that you did not use or no longer needed the service.
* A subscription charge is valid if the subscription was active, the service or paid plan was made available, and the charge was processed according to the subscription terms, regardless of whether you used the service during the billing period.
* Refunds, credits, extensions, or other accommodations may be granted at Flipsuite’s sole discretion. Any discretionary refund or credit in one instance does not create an obligation to provide the same or similar accommodation in any other instance.
* If we issue a refund, we may revoke, reduce, or terminate access to the paid plan, feature, credit, entitlement, subscription period, or service associated with the refunded payment.

### 9.6 Trials, Discounts, Promotions, and Plan Changes

* We may offer free trials, discounted periods, promotional pricing, preview access, or limited-time offers. Unless otherwise stated, promotional pricing applies only for the stated promotional period.
* If a trial or promotional offer converts into a paid subscription, the applicable checkout, offer, or account interface will identify the terms of conversion, including the price and billing interval where required.
* You must cancel before the end of any free trial, preview period, discounted period, or promotional period if you do not want to be charged.
* Upgrades, downgrades, plan changes, usage changes, and limit changes may take effect immediately, at the end of the current billing period, or on another date stated in the applicable billing interface or written agreement.
* We may modify plan names, features, limits, pricing, or subscription structures from time to time. Material changes will be communicated where required by law or where reasonably practicable.

### 9.7 Chargebacks and Payment Disputes

* If you believe a charge was made in error, contact us at [team@flipsuite.xyz](mailto:team@flipsuite.xyz) before initiating a chargeback or payment dispute.
* Initiating a chargeback, payment dispute, reversal, or payment processor claim does not constitute cancellation and does not relieve you of payment obligations for valid charges.
* We may suspend, limit, downgrade, or terminate access to Flipsuite if a payment is disputed, reversed, charged back, or identified as fraudulent or unauthorized.
* We may provide records of your subscription, checkout authorization, invoices, receipts, account activity, cancellation status, access history, and communications to payment processors, card networks, banks, or other relevant parties in connection with a payment dispute.

### 9.8 Taxes

* Fees are exclusive of taxes unless expressly stated otherwise. You are responsible for all applicable taxes, duties, levies, and governmental assessments associated with your purchase or use of paid services, except taxes on Flipsuite’s net income.
* Where required, we or our payment processor may calculate, collect, and remit taxes based on the billing information, account information, or location information available to us.

### 9.9 Mandatory Consumer Rights

* Nothing in these Terms limits any non-waivable refund, cancellation, auto-renewal, chargeback, or consumer protection right that applies to you under applicable law.
* If any provision of this Section 9 is determined to be unenforceable in a particular jurisdiction, that provision will apply only to the maximum extent permitted by law, and the remaining provisions will remain in effect.

## 10. Gas Fees and Taxes

* You are responsible for all blockchain network ("gas") fees and any third-party fees incurred when using Flipwallets.
* Fees are non-refundable and relate to decentralized network operations.
* You are responsible for all taxes arising from your use of Flipsuite, except taxes on Flipsuite’s net income.

## 11. Rewards and Deferred Rewards

### 11.1 Reward Wallets

* Community organizers must keep reward wallets funded to satisfy claims. Deferred rewards track off-chain balances to reduce gas fees; claims require sufficient onchain funds at the time of redemption. Flipsuite is not responsible for unfulfilled claims due to insufficient funding.

### 11.2 Prohibited Practices

* Manipulating reward systems, falsifying balances, or issuing unsupported rewards is prohibited and may lead to suspension or termination.

## 12. Assumption of Risk; Third-Party Services

* Blockchain Risks: Transactions are irreversible; prices are volatile; smart contracts may fail; networks may experience congestion, forks, or attacks; wallets and dApps may be compromised; and regulatory changes may impact digital assets.
* Third-Party Providers: Flipsuite integrates with third parties (e.g., Discord, Privy, RPC providers, Stripe). We are not responsible for their acts, omissions, policies, outages, payment processing decisions, refunds, chargebacks, disputes, or security. Your use of third-party services is subject to their terms and privacy policies.
* No Insurance: Digital assets are not insured by the FDIC, SIPC, or any governmental agency. Flipsuite is not a bank, broker, or investment adviser.

## 13. Intellectual Property and License

* Flipsuite owns all rights, title, and interest in its software, data, and content. We grant you a limited, revocable, non-exclusive, non-transferable license to use the service for personal or internal use.
* Commercial use (including resale, licensing, or monetization) requires our prior written consent.

## 14. Availability; Modifications; Suspension

* The service is provided "as is" and "as available." We do not guarantee uptime or future functionality.
* We may modify or discontinue features at any time. Where reasonably possible, access to Flipwallets will be maintained to allow continued wallet use.
* We may suspend or terminate access, with or without notice, for policy, legal, security, payment, chargeback, or risk reasons.

## 15. Privacy

* By using Flipsuite, you consent to our collection and use of information as described in our Privacy Policy (see [https://flipsuite.xyz/privacy](https://flipsuite.xyz/privacy)). We may process Discord IDs, wallet addresses, logs of authorizations, billing records, subscription records, cancellation records, and other data to operate the service and comply with law.
* Do not share sensitive personal information in chats or prompts. AI features may process your inputs to generate outputs and improve safety and functionality.

## 16. Indemnification

* You agree to indemnify and hold harmless Flipsuite and its affiliates, officers, employees, and agents from any claims, losses, liabilities, damages, costs, and expenses (including reasonable attorneys’ fees) arising from your violation of these Terms, misuse of the service, payment dispute, chargeback, or infringement of any rights.

## 17. Warranty Disclaimer

* THE SERVICE (INCLUDING FLIPWALLETS, AI FEATURES, PAID SUBSCRIPTIONS, AND ALL CONTENT) IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. WE DISCLAIM ALL WARRANTIES, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE ERROR-FREE, SECURE, OR UNINTERRUPTED.

## 18. Limitation of Liability

* TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT WILL FLIPSUITE BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, DATA, GOODWILL, SUBSCRIPTION VALUE, UNUSED SERVICE TIME, UNUSED PLAN LIMITS, OR OTHER INTANGIBLE LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OF OR INABILITY TO USE THE SERVICE, INCLUDING ANY LOSS OR THEFT OF DIGITAL ASSETS.
* WITHOUT LIMITING THE FOREGOING, FLIPSUITE IS NOT LIABLE FOR: (A) LOSSES RESULTING FROM YOUR EXPORTED PRIVATE KEYS OR YOUR FAILURE TO SECURE YOUR CREDENTIALS; (B) BLOCKCHAIN OR SMART CONTRACT FAILURES; (C) ACTIONS OR OUTAGES OF DISCORD, PRIVY, STRIPE, OR OTHER THIRD PARTIES; (D) UNAUTHORIZED ACCESS NOT CAUSED BY FLIPSUITE’S BREACH OF THESE TERMS; OR (E) YOUR FAILURE TO CANCEL A SUBSCRIPTION BEFORE RENEWAL.
* OUR AGGREGATE LIABILITY WILL NOT EXCEED THE GREATER OF: (I) \$100 USD OR (II) THE AMOUNTS YOU PAID TO FLIPSUITE IN THE 3 MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM.

## 19. Termination

* You may stop using the service at any time. Stopping use of the service does not automatically cancel an active subscription unless you cancel through an authorized billing or support channel.
* We may suspend or terminate your access for violation of these Terms, legal or security reasons, payment failure, chargebacks, or to protect users and the platform. Upon termination, your rights under these Terms cease, but certain sections (including IP, indemnification, limitations, payment obligations, refund terms, and dispute terms) will survive.

## 20. Dispute Resolution; Governing Law

* These Terms and any disputes are governed by the laws of the State of Delaware, USA, without regard to its conflict of laws rules.
* You and Flipsuite consent to the exclusive jurisdiction and venue of the state and federal courts located in Delaware for any dispute not subject to arbitration or where arbitration is not permitted by law.
* Class Action Waiver: To the extent permitted by law, disputes must be brought in your individual capacity and not as a plaintiff or class member in any class or representative proceeding.

## 21. Updates to These Terms

* We may update these Terms from time to time. Material changes will be indicated by updating the "Last Updated" date or by providing notice. Continued use after changes constitutes acceptance of the revised Terms.
* If we make material changes to subscription terms, renewal terms, cancellation terms, or pricing, we will provide notice where required by applicable law.

## 22. Contact

* Questions, support, billing issues, subscription cancellation requests, or payment questions: [team@flipsuite.xyz](mailto:team@flipsuite.xyz)

***

*By continuing to use Flipsuite, you agree to these Terms of Service in full.*


# Creating airdrops
Source: https://docs.flipsuite.xyz/modules/tipping/commands/airdrop

Learn how to create airdrops using your Flipwallet.

## Overview

With Flipsuite, you can create airdrops directly in Discord through airdrop commands.
There are multiple ways to create airdrops which we'll explain in detail down below.

<Note>
  Airdrops do not immediately send tokens to recipients, but require people to explicitly join the airdrop by
  interacting with the airdrop message in Discord. If you're looking to instantly send tokens in bulk to people,
  check out the [/tip](/modules/tipping/commands/tip) command page.
</Note>

## Commands

### `/drop token`

This command is used to create airdrops with tokens from your [Flipwallet](/flippy/introduction).

<Accordion title="Command arguments">
  <ParamField type="string">
    Token you want to airdrop.
  </ParamField>

  <ParamField type="string">
    Amount to airdrop. You can use "%" and "\$" for relative amounts.
  </ParamField>

  <ParamField type="boolean">
    If set to true, specified amount will be sent to each airdrop winner instead of being split.
  </ParamField>

  <ParamField type="string">
    Countdown duration in minutes before the airdrop is distributed.
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the airdrop message.
  </ParamField>

  <ParamField type="boolean">
    If set to true, your name will be hidden in the airdrop message.
  </ParamField>

  <ParamField type="number">
    A total number of people who can enter the airdrop.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each person who entered the airdrop after it ends (server admin only).
  </ParamField>

  <ParamField type="string">
    Users and/or roles allowed to enter the airdrop.
  </ParamField>

  <ParamField type="string">
    Users and/or roles forbidden from entering the airdrop.
  </ParamField>

  <ParamField type="boolean">
    If set to true, user requirements (like required roles) will be checked only at the time of enter.
  </ParamField>

  <ParamField type="number">
    Number of consecutive airdrops to create.
  </ParamField>

  <ParamField type="number">
    Delay (in minutes) between consecutive airdrops.
  </ParamField>
</Accordion>

## Examples

### Create token airdrop

To create a default airdrop that can be entered by everyone, simply choose a token and its amount.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create airdrop for specific users

To create an airdrop that can be entered only by specific users, mention users and/or roles that are allowed to enter
in the `allowed-users` command argument. If you want to restrict some users and/or roles from entering the airdrop,
mention them in the `forbidden-users` command argument instead.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create repeating airdrop

To create a repeating airdrop, simply fill in the `count` and `delay` command fields. Airdrops created this way will
repeat one after another with the delay set by the `delay` field.

For example, to schedule an airdrop that is created 5 minutes after the previous one ends for 3 consecutive times,
you would enter `count:3` and `delay:5`, as shown in the screenshot below.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

To cancel a repeating airdrop, just execute the `/cancel type:Airdrop` command and select a repeating airdrop to cancel.

<Frame>
  <img />
</Frame>

## Settings

You can modify the following account-wide tipping settings in your [/profile](/flippy/commands/profile):

* The minimum account age that's required to enter your airdrops and raffles.

<Frame>
  <img />
</Frame>


# Creating raffles
Source: https://docs.flipsuite.xyz/modules/tipping/commands/raffle

Learn how to create raffles using your Flipwallet.

## Overview

With Flipsuite, you can create raffles directly in Discord through raffle commands.
There are multiple ways to create raffles which we'll explain in detail down below.

## Commands

### `/raffle token`

This command is used to create raffles with tokens from your [Flipwallet](/flippy/introduction).

<Accordion title="Command arguments">
  <ParamField type="string">
    Token you want to raffle.
  </ParamField>

  <ParamField type="string">
    Amount to raffle. You can use "%" and "\$" for relative amounts.
  </ParamField>

  <ParamField type="boolean">
    If set to true, specified amount will be sent to each raffle winner instead of being split.
  </ParamField>

  <ParamField type="string">
    Countdown duration in minutes before the raffle ends.
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the raffle message.
  </ParamField>

  <ParamField type="boolean">
    If set to true, your name will be hidden in the raffle message.
  </ParamField>

  <ParamField type="number">
    A total number of people who can enter the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each person who joined the raffle after it ends (server admin only).
  </ParamField>

  <ParamField type="number">
    Number of people who can win the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each raffle winner after it ends (server admin only).
  </ParamField>

  <ParamField type="string">
    Users and/or roles allowed to enter the raffle.
  </ParamField>

  <ParamField type="string">
    Users and/or roles forbidden from entering the raffle.
  </ParamField>

  <ParamField type="boolean">
    If set to true, user requirements (like required roles) will be checked only at the time of enter.
  </ParamField>

  <ParamField type="number">
    Number of consecutive raffles to create.
  </ParamField>

  <ParamField type="number">
    Delay (in minutes) between consecutive raffles.
  </ParamField>
</Accordion>

### `/raffle nft`

This command is used to create NFT raffles with one of the NFTs from your `/inventory`.

<Accordion title="Command arguments">
  <ParamField type="string">
    One of the [supported chains](https://flipsuite.xyz/tokens).
  </ParamField>

  <ParamField type="string">
    NFT to raffle.
  </ParamField>

  <ParamField type="number">
    Number of NFTs to raffle (applicable only to ERC-1155 tokens).
  </ParamField>

  <ParamField type="string">
    Countdown duration in minutes before the raffle ends.
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the raffle message.
  </ParamField>

  <ParamField type="boolean">
    If set to true, your name will be hidden in the raffle message.
  </ParamField>

  <ParamField type="number">
    A total number of people who can enter the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each person who joined the raffle after it ends (server admin only).
  </ParamField>

  <ParamField type="string">
    Roles to remove from each raffle winner after it ends (server admin only).
  </ParamField>

  <ParamField type="string">
    Users and/or roles allowed to enter the raffle.
  </ParamField>

  <ParamField type="string">
    Users and/or roles forbidden from entering the raffle.
  </ParamField>

  <ParamField type="boolean">
    If set to true, user requirements (like required roles) will be checked only at the time of enter.
  </ParamField>
</Accordion>

### `/raffle role`

This command is used to create Discord role raffles.

<Accordion title="Command arguments">
  <ParamField type="role">
    Discord role to raffle.
  </ParamField>

  <ParamField type="string">
    Duration of the role to raffle. If omitted, the role will be granted forever.
  </ParamField>

  <ParamField type="string">
    Countdown duration in minutes before the raffle ends.
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the raffle message.
  </ParamField>

  <ParamField type="boolean">
    If set to true, your name will be hidden in the raffle message.
  </ParamField>

  <ParamField type="number">
    A total number of people who can enter the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each person who joined the raffle after it ends (server admin only).
  </ParamField>

  <ParamField type="number">
    Number of people who can win the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each raffle winner after it ends (server admin only).
  </ParamField>

  <ParamField type="string">
    Users and/or roles allowed to enter the raffle.
  </ParamField>

  <ParamField type="string">
    Users and/or roles forbidden from entering the raffle.
  </ParamField>

  <ParamField type="boolean">
    If set to true, user requirements (like required roles) will be checked only at the time of enter.
  </ParamField>

  <ParamField type="number">
    Number of consecutive raffles to create.
  </ParamField>

  <ParamField type="number">
    Delay (in minutes) between consecutive raffles.
  </ParamField>
</Accordion>

<Warning>
  Flippy can only grant and revoke roles from users in your server that are **below its role** in your server's
  role hierarchy. You can access it by going to the `Roles` tab in your server settings.

  <Frame>
    <img />
  </Frame>

  In the example above, Flippy can only grant the "Verified - Tier 2" role to your community members. It won't have
  access to the "Verified - Tier 3" role because it's above the bot's role.
</Warning>

### `/raffle custom`

This command is used to create raffles for custom items.

<Accordion title="Command arguments">
  <ParamField type="string">
    Prize description.
  </ParamField>

  <ParamField type="string">
    Countdown duration in minutes before the raffle ends.
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the raffle message.
  </ParamField>

  <ParamField type="boolean">
    If set to true, your name will be hidden in the raffle message.
  </ParamField>

  <ParamField type="number">
    A total number of people who can enter the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each person who joined the raffle after it ends (server admin only).
  </ParamField>

  <ParamField type="number">
    Number of people who can win the raffle.
  </ParamField>

  <ParamField type="string">
    Roles to remove from each raffle winner after it ends (server admin only).
  </ParamField>

  <ParamField type="string">
    Users and/or roles allowed to enter the raffle.
  </ParamField>

  <ParamField type="string">
    Users and/or roles forbidden from entering the raffle.
  </ParamField>

  <ParamField type="boolean">
    If set to true, user requirements (like required roles) will be checked only at the time of enter.
  </ParamField>

  <ParamField type="number">
    Number of consecutive raffles to create.
  </ParamField>

  <ParamField type="number">
    Delay (in minutes) between consecutive raffles.
  </ParamField>
</Accordion>

## Examples

### Create token raffle

To create a token raffle that can be entered by everyone, simply choose a token and its amount.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create NFT raffle

To create an NFT raffle that can be entered by everyone, simply choose a token and its amount.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create role raffle

To create a Discord role raffle that can be entered by everyone, simply choose a token and its amount.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create custom raffle

To create a custom item raffle that can be entered by everyone, simply choose a token and its amount.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create raffle for specific users

To create a raffle that can only be entered by specific users, mention users and/or roles that are allowed to enter
in the `allowed-users` command argument. If you want to restrict some users and/or roles from entering the raffle,
mention them in the `forbidden-users` command argument instead.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Create repeating raffle

To create a repeating raffle, simply fill in the `count` and `delay` command fields. Raffles created this way will
repeat one after another with the delay set by the `delay` field.

For example, to schedule a raffle that is created 5 minutes after the previous one ends for 3 consecutive times,
you would enter `count:3` and `delay:5`, as shown in the screenshot below.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

To cancel a repeating raffle, just execute the `/cancel type:Raffle` command and select a repeating raffle to cancel.

<Frame>
  <img />
</Frame>

## Settings

You can modify the following account-wide tipping settings in your [/profile](/flippy/commands/profile):

* The minimum account age that's required to enter your airdrops and raffles.

<Frame>
  <img />
</Frame>

## Permissions

By default, only admins can create role and custom raffles in your server. If you wish to also allow your server
mods to create them, you can do so via **tipping settings** on the dashboard.


# Sending tips
Source: https://docs.flipsuite.xyz/modules/tipping/commands/tip

Learn how to send tips using your Flipwallet.

## Overview

With Flipsuite, you can send both token and NFT tips directly in Discord through tipping commands.
There are multiple ways to send tips which we'll explain in detail down below.

## Commands

### `/tip token`

This command is used to send tips with tokens from your [Flipwallet](/flippy/introduction) to other users.

<Accordion title="Command arguments">
  <ParamField type="string">
    Users and/or roles to tip. Start typing "@" and select one or more users/roles, or type "active" if you want to tip
    active members.
  </ParamField>

  <ParamField type="string">
    A token you want to tip.
  </ParamField>

  <ParamField type="string">
    Amount to tip. You can use "%" and "\$" for relative amounts.
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the tip notification.
  </ParamField>

  <ParamField type="boolean">
    Whether you want to send the tip anonymously or not.
  </ParamField>

  <ParamField type="number">
    Number of consecutive tips to create.
  </ParamField>

  <ParamField type="number">
    Delay (in minutes) between consecutive tips.
  </ParamField>
</Accordion>

### `/tip nft`

This command is used to send NFT from your `/inventory` to a single person.

<Accordion title="Command arguments">
  <ParamField type="user">
    User to tip.
  </ParamField>

  <ParamField type="string">
    One of the [supported chains](https://flipsuite.xyz/tokens).
  </ParamField>

  <ParamField type="string">
    NFT to tip.
  </ParamField>

  <ParamField type="number">
    Number of NFTs to tip (applicable only to ERC-1155 tokens).
  </ParamField>

  <ParamField type="string">
    Note that will be displayed in the tip notification.
  </ParamField>

  <ParamField type="boolean">
    Whether you want to send the tip anonymously or not.
  </ParamField>
</Accordion>

## Examples

### Send token tip

To send a tip to a single person, simply mention them in the `recipients` command field and fill in the
other command arguments.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Send NFT tip

To send an NFT tip to a single person, simply mention them in the `recipient` command field and fill in the
other command arguments. NFTs you tip must be present in your `/inventory`.

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

To cancel a repeating tip, just execute the `/cancel type:Tip` command and select a repeating tip to cancel.

<Frame>
  <img />
</Frame>

### Send token tips to multiple people

To send tips to multiple people simultaneously, mention them in the `recipients` command field and fill in the
other command arguments.

<Note>
  The amount you type in the `amount` command field will be split evenly between the recipients.
</Note>

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Send token tips to roles

To send tips to specific role, mention them in the `recipients` command field and fill in the
other command arguments.

<Note>
  The amount you type in the `amount` command field will be split evenly between the recipients.
</Note>

<Warning>
  There's a hard limit on how many people you can tip at once.
  If the roles you select result in more than 500 recipients, you will be asked to choose a less common role to tip.
</Warning>

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Send token tips to active members

To send tips to active members, simply type **active** in the `recipients` command field and fill in the
other command arguments.

By default, Flipsuite checks who was active by looking at the messages sent in the last hour in the channel where the command
is used. If you want to change this time frame, simply add the desired duration at the end of the `recipients` field.
For example, to tip all active members in the last 6 hours, you would type "active 6 hours".

<Note>
  The amount you type in the `amount` command field will be split evenly between the recipients.
</Note>

<Frame>
  <img />
</Frame>

**Result:**

<Frame>
  <img />
</Frame>

### Send repeating token tips

To send repeated tips, simply fill in the `count` and `delay` command fields. Tips sent this way will repeat in the
interval set by the `delay` field.

For example, to schedule a tip to be sent every 5 minutes for 3 consecutive times, you would enter `count:3`
and `delay:5`, as shown in the screenshot below.

<Frame>
  <img />
</Frame>


# Introduction
Source: https://docs.flipsuite.xyz/modules/tipping/introduction

Tip, airdrop and raffle crypto directly in Discord.

<div>
  <iframe />
</div>

## Overview

The Tipping module lets your community tip each other in multiple ways, bringing fun and engagement to your server.
It's enabled globally in each server that has Flipsuite installed.

It instantly transforms your server into a Web3 hub where tokens and NFTs can be tipped,
airdropped and raffled, all inside your Discord server.

## Key Features

<CardGroup>
  <Card title="On-chain" icon="cube">
    Tips are processed and verified on-chain to ensure security and transparency.
  </Card>

  <Card title="NFT Support" icon="gem">
    You can tip and raffle your beloved NFTs the same way you would tip coins.
  </Card>

  <Card title="Automated Tips" icon="arrows-rotate-reverse">
    Created automated tips, raffles and airdrops that repeat in a set interval.
  </Card>

  <Card title="Optional Requirements" icon="list-check">
    Restrict raffle and airdrop entries to specific roles or users to create exclusive giveaways.
  </Card>
</CardGroup>


# Setup
Source: https://docs.flipsuite.xyz/modules/tipping/setup

Learn how to start tipping in your server.

## Step 1 - Get familiar with your Flipwallet

All you need to do before starting tipping in your server is to get familiar with your Flipwallet
and deposit some tokens into it.

<Card title="Flipwallet" icon="wallet" href="/flippy/introduction">
  Click to learn more about the Flipwallet.
</Card>

## Step 2 - Start tipping!

Click one of the buttons below to learn how to tip, raffle and airdrop tokens using your Flipwallet.

<CardGroup>
  <Card title="Create Airdrops" icon="parachute-box" href="/modules/tipping/commands/airdrop">
    Create token airdrops in your server.
  </Card>

  <Card title="Create Raffles" icon="ticket" href="/modules/tipping/commands/raffle">
    Create various raffles in your server.
  </Card>

  <Card title="Send Tips" icon="hands-holding-dollar" href="/modules/tipping/commands/tip">
    Send crypto tips in your server.
  </Card>
</CardGroup>

## Bonus - Enable tipping in DMs

Optionally, you can also add Flipsuite as your **personal app** in Discord which will enable tipping in DMs and servers
that do not have Flipsuite installed. To do so, click the Flipsuite avatar anywhere in Discord and tap the **Add App**
button.

<Frame>
  <img />
</Frame>

In the dialog that will appear, select the **Add to My Apps** option and authorize Flipsuite to send you
direct messages.

<Frame>
  <img />
</Frame>

Congratulations! Now you can use `/tip` commands anywhere in Discord - in DMs, groups, and even in servers that do not
have Flipsuite installed.

<Note>
  Some tipping features might be restricted in servers that do not have Flipsuite installed (like tipping roles or
  active members). Additionally, Flipsuite won't be able to send public tip notifications in channels where personal
  apps have been disabled by server admins.
</Note>


# Shared Wallet
Source: https://docs.flipsuite.xyz/modules/tipping/shared-wallet

Learn how to set up a shared tipping wallet in your server.

## Overview

If you're a project owner, you might want to set up a shared wallet for your server that you and your mods can use
to tip, raffle, and airdrop tokens from a single wallet. This allows you and your team members to not use their
personal Flipwallets in your server.

## Step 1 - Add a shared wallet

To create a shared tipping wallet, go to the **Tipping** tab in your community dashboard and switch to the **Wallets** tab.
Click the **Add new tipping wallet** button to get started.

<Frame>
  <img />
</Frame>

When adding a shared wallet for a selected chain, you can choose to either generate a totally fresh wallet or use
your own. **In both cases you have full access to the wallet's private key.**

<Note>
  The private key of your shared tipping wallet is accessible only by the community owner - and if your community is
  shared in a [team](/account/teams), by team owner and admins.
</Note>

After creating a shared tipping wallet you will be redirected to its overview panel:

<Frame>
  <img />
</Frame>

You can switch between the tabs to view your tipping wallet tokens and NFT balance, activity, and look up its private
key if you have access.

If you want to check the balance of all shared tipping wallets in Discord, simply go to your `/balance` or `/inventory`
and click the **server tipping wallet** button.

<Frame>
  <img />
</Frame>

## Step 2 - Switch to shared wallet

To start using your shared wallet in Discord, you need to either switch to use it in your profile settings, or
switch to it at the time of confirming a tip, airdrop or raffle.

### Switch via profile

Go to `/profile > ⚙️ settings > 💸 tipping` tab and switch the tipping wallet option to **Team Flipwallet**.

<Frame>
  <img />
</Frame>

<Note>
  The tipping wallet option won't be available if you don't have permissions to use it or try to access your
  tipping settings outside of your server.
</Note>

Now all your tips, airdrops, and raffles will use the shared tipping wallet, until you switch it back
to your personal Flipwallet.

### Switch when tipping

If you have permission to use the shared wallet, you can switch to it at the time of confirming a tip, airdrop or
raffle, like in the screenshot below:

<Frame>
  <img />
</Frame>

All you have to do is click the **switch to team wallet** button.

## Step 3 - Set permissions

By default, only admins can use the shared tipping wallet in your server. If you wish to also allow your server
mods to use it, you can do so via [control panel](/quickstart#step-2-setup-your-control-panel) in Discord.

Simply go to `⚙️ settings > 💸 tipping > 🔐 permissions` until you are here:

<Frame>
  <img />
</Frame>

To give one of the roles in your server permission to use shared tipping wallet simply select them from the dropdown.


# Buy
Source: https://docs.flipsuite.xyz/modules/trading/commands/buy

Learn more about the /limit buy command.

## Overview

You can use `/limit buy` command to place limit buy orders on certain tokens.

<Accordion title="Command arguments">
  <ParamField type="string">
    Name or address of the token to buy.
  </ParamField>

  <ParamField type="string">
    Amount to buy (use "\$" for relative amount)
  </ParamField>

  <ParamField type="string">
    Order will execute below this price (use "%" for relative decrease)
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

If limit orders are supported for the token you've entered, you will get a quote for your order:

<Frame>
  <img />
</Frame>

If you're satisfied with the quote, simply click the **place order** button to place the order.

<Frame>
  <img />
</Frame>

You will be notified via DMs once your order is fulfilled.

<Tip>
  You can use the [/limit orders](/modules/trading/commands/orders) command in Discord to view all your limit orders.
</Tip>


# Long
Source: https://docs.flipsuite.xyz/modules/trading/commands/long

Learn more about the /perp long command.

## Overview

You can use `/perp long` command to open long positions on [Hyperliquid](https://app.hyperliquid.xyz/trade).

<Accordion title="Command arguments">
  <ParamField type="string">
    Name of the asset to open a long position for
  </ParamField>

  <ParamField type="string">
    Margin to use for the position (use "%" or "\$" for relative amounts)
  </ParamField>

  <ParamField type="number">
    Leverage to use for your position.
  </ParamField>

  <ParamField type="string">
    Position will be opened below this price (use "%" for relative decrease)
  </ParamField>

  <ParamField type="string">
    Position will be closed below this price to limit loss (use "%" for relative decrease)
  </ParamField>

  <ParamField type="string">
    Position will be closed above this price to save profit (use "%" for relative increase)
  </ParamField>

  <ParamField type="string">
    Margin mode to use for the position. Choose `isolated` or `cross`.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

If perp trading is enabled for the token you've entered, you will get a quote for your position:

<Frame>
  <img />
</Frame>

If you're satisfied with your position, simply click the **open long position** button to open it.

<Frame>
  <img />
</Frame>

You will be notified via DMs once your position is fulfilled or closed.

<Tip>
  You can use the [/perp positions](/modules/trading/commands/positions) command in Discord to view all your open positions.
</Tip>


# Orders
Source: https://docs.flipsuite.xyz/modules/trading/commands/orders

Learn more about the /limit orders command.

## Overview

You can use `/limit orders` command to view your pending and archived limit orders.

<Frame>
  <img />
</Frame>

To view your limit order history, simply tap the **view archived orders** button:

<Frame>
  <img />
</Frame>


# Positions
Source: https://docs.flipsuite.xyz/modules/trading/commands/positions

Learn more about the /perp positions command.

## Overview

You can use `/perp positions` command to view your open and closed positions.

<Frame>
  <img />
</Frame>

To view your perpetual trading history, simply tap the **view trade history** button:

<Frame>
  <img />
</Frame>


# Sell
Source: https://docs.flipsuite.xyz/modules/trading/commands/sell

Learn more about the /limit sell command.

## Overview

You can use `/limit sell` command to place limit sell orders on certain tokens.

<Accordion title="Command arguments">
  <ParamField type="string">
    Name or address of the token to buy.
  </ParamField>

  <ParamField type="string">
    Amount to sell (use "%" or "\$" for relative amounts)
  </ParamField>

  <ParamField type="string">
    Order will execute above this price (use "%" for relative increase)
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

If limit orders are supported for the token you've entered, you will get a quote for your order:

<Frame>
  <img />
</Frame>

If you're satisfied with the quote, simply click the **place order** button to place the order.

<Frame>
  <img />
</Frame>

You will be notified via DMs once your order is fulfilled.

<Tip>
  You can use the [/limit orders](/modules/trading/commands/orders) command in Discord to view all your limit orders.
</Tip>


# Short
Source: https://docs.flipsuite.xyz/modules/trading/commands/short

Learn more about the /perp short command.

## Overview

You can use `/perp short` command to open short positions on [Hyperliquid](https://app.hyperliquid.xyz/trade).

<Accordion title="Command arguments">
  <ParamField type="string">
    Name of the asset to open a short position for
  </ParamField>

  <ParamField type="string">
    Margin to use for the position (use "%" or "\$" for relative amounts)
  </ParamField>

  <ParamField type="number">
    Leverage to use for your position.
  </ParamField>

  <ParamField type="string">
    Position will be opened above this price (use "%" for relative increase)
  </ParamField>

  <ParamField type="string">
    Position will be closed above this price to limit loss (use "%" for relative increase)
  </ParamField>

  <ParamField type="string">
    Position will be closed below this price to save profit (use "%" for relative decrease)
  </ParamField>

  <ParamField type="string">
    Margin mode to use for the position. Choose `isolated` or `cross`.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

If perp trading is enabled for the token you've entered, you will get a quote for your position:

<Frame>
  <img />
</Frame>

If you're satisfied with your position, simply click the **open short position** button to open it.

<Frame>
  <img />
</Frame>

You will be notified via DMs once your position is fulfilled or closed.

<Tip>
  You can use the [/perp positions](/modules/trading/commands/positions) command in Discord to view all your open positions.
</Tip>


# Swap
Source: https://docs.flipsuite.xyz/modules/trading/commands/swap

Learn more about the /swap tokens command.

## Overview

You can use `/swap tokens` command to swap tokens inside your Flipwallet.

<Accordion title="Command arguments">
  <ParamField type="string">
    Symbol or chain + address of the token to sell.
  </ParamField>

  <ParamField type="string">
    Amount to swap. You can use "%" and "\$" for relative amounts.
  </ParamField>

  <ParamField type="string">
    Symbol or chain + address of the token to buy.
  </ParamField>
</Accordion>

<Frame>
  <img />
</Frame>

If a route for your swap has been found, you will get a quote for your swap:

<Frame>
  <img />
</Frame>

If you're satisfied with the quote, simply click the **swap** button to execute your swap.

<Frame>
  <img />
</Frame>


# Hyperliquid
Source: https://docs.flipsuite.xyz/modules/trading/guides/hyperliquid

Learn how to start trading on Hyperliquid using Flipsuite.

## Overview

Flipsuite is integrated with [Hyperliquid](https://app.hyperliquid.xyz/trade) to provide more trading features across the board,
enabling perpetual and spot trading using your Flipwallet.

## What is Hyperliquid?

[Hyperliquid](https://hyperfoundation.org/) is a performant blockchain built with the vision of a fully onchain open
financial system. Liquidity, user applications, and trading activity synergize on a unified platform that will
ultimately house all of finance. Its state execution is split into two broad components:

1. **HyperEVM**
2. **HyperCore**

### HyperEVM

HyperEVM integrates the general-purpose smart contract capabilities common to Ethereum into the Hyperliquid blockchain.
HyperCore's performant liquidity and financial primitives are exposed as permissionless building blocks for all users and
developers on HyperEVM. Users can utilize the full range of Flipsuite features on HyperEVM.

### HyperCore

HyperCore includes fully onchain perpetual futures and spot order books. Every order, cancel, trade, and liquidation
happens transparently with one-block finality. HyperCore is designed primarily for trading, so a Flipsuite reward
system is not available on HyperCore.

## Trading on Hyperliquid

Trading on Hyperliquid is done on HyperCore, so you need to get your funds there first.

### How to get funds on HyperCore?

The best way to get your funds to HyperCore from other chains is to have some gas tokens available (like `ETH`, `POL`, or `SOL`)
and bridge them into HyperCore's `USDC` token by using the [/swap tokens](/modules/trading/commands/swap) command or by asking [Flippy](/flippy/introduction).

<Frame>
  <img />
</Frame>

Once you have some `USDC` on HyperCore you can start trading!

<Warning>
  Make sure to have more than 10 USDC in your Flipwallet on HyperCore, as Hyperliquid won't let you place orders
  that are worth less than \$10 to prevent spam.
</Warning>

You can also transfer certain tokens that are deployed (and linked) on both HyperEVM and HyperCore between these
two chains. To do so simply use the [/swap tokens](/modules/trading/commands/swap) command and specify the desired token as both source
and destination token like this:

<Frame>
  <img />
</Frame>

### Placing market spot orders

To place spot market orders using your HyperCore `USDC`, simply use the [/swap tokens](/modules/trading/commands/swap) command
in Discord, or ask Flippy to place them for you like this:

> Hey **@Flippy** swap 50 USDC to HYPE on Hyperliquid

<Frame>
  <img />
</Frame>

### Placing limit spot orders

To place spot limit orders using your HyperCore `USDC`, simply use the [/limit buy](/modules/trading/commands/buy) and
[/limit sell](/modules/trading/commands/sell) commands in Discord, or ask Flippy to place them for you like this:

> Hey **@Flippy** buy me \$100 BTC once it drops below 110k

<Frame>
  <img />
</Frame>

### Opening market perp positions

To open long and short positions using your HyperCore `USDC`, simply use the [/perp long](/modules/trading/commands/long)
and [/perp short](/modules/trading/commands/short) commands in Discord, or ask Flippy to place them for you like this:

> Hey **@Flippy** open BTC long with 15x leverage and \$20 margin, and set stop loss at 110k

<Frame>
  <img />
</Frame>

### Opening limit perp positions

If you prefer to open a position only once a certain price target is hit:

> Hey **@Flippy** open ETH long with max leverage and \$50 margin once it drops by 2%

<Frame>
  <img />
</Frame>

### Setting multiple SL and TP levels

You can set multiple stop loss and take profit targets for your perp positions like this:

> Hey **@Flippy** open HYPE long with max leverage and \$50 margin, set 50% TP at 10% gain, and 25% TP at 20%

<Frame>
  <img />
</Frame>

### Sharing your perp positions

You can ask Flippy to share one of your perp positions in the chat:

<Frame>
  <img />
</Frame>

### Closing your perp positions

You can fully or partially close your perp positions by asking Flippy to do so:

> Hey **@Flippy** cancel X% of my HYPE position

<Frame>
  <img />
</Frame>

### Trading leaderboard

All perpetual trades you execute on Hyperliquid using your Flipwallet are tracked on the trading leaderboard. Each week,
the top 3 traders and the lowest-ranking trader (person at the bottom of the leaderboard) receive a reward proportional
to the generated trading fees in that week. You can access the trading leaderboard at any time by asking Flippy:

<Frame>
  <img />
</Frame>

### Margin modes

When opening a perp position on Hyperliquid, you can choose between two margin modes:

1. **Isolated**
2. **Cross**

#### Isolated margin

Isolated margin restricts the collateral for a position to a single asset.

* **Risk Isolation:** Losses are limited to the margin allocated to that specific position. Liquidations in an isolated position do not affect your other trades.
* **Manual Adjustments:** You can manually add or remove margin from an open position to adjust your liquidation price (except for "strict isolated" assets).
* **PnL Handling:** Unrealized profits are applied directly to the position as additional margin.

#### Cross margin

Cross margin is designed for maximum capital efficiency.

* **Shared Collateral:** All cross positions share the same collateral pool. This allows profits from one position to support the margin requirements of another.
* **Liquidation Risk:** Since margin is shared, a significant loss in one position can potentially lead to the liquidation of all other cross positions in your account.
* **Automated PnL:** Unrealized profits are automatically available as initial margin to open new positions.

<Tip>
  While Hyperliquid defaults to cross margin, Flippy uses isolated mode by default to protect your balance and ensure
  one position's risk doesn't affect your other assets.
</Tip>


# Introduction
Source: https://docs.flipsuite.xyz/modules/trading/introduction

Swap, bridge and trade directly in Discord.

<iframe />

## Overview

Trading module lets you trade ant token directly in Discord using
renowned exchanges and aggregators, including:

* [**dreamDEX**](https://dreamdex.io)
* [**Gas.zip**](https://www.gas.zip)
* [**Hyperliquid**](https://app.hyperliquid.xyz/trade)
* [**Jupiter**](https://jup.ag)
* [**KyberSwap**](https://kyberswap.com)
* [**LI.FI**](https://li.fi)
* [**LiquidSwap**](https://liqd.ag)
* [**Obsidian**](https://obsidian.finance)
* [**Oku Trade**](https://oku.trade)
* [**Orbiter**](https://orbiter.finance)
* [**Relay**](https://www.relay.link/bridge)
* [**RocketX**](https://www.rocketx.exchange)
* [**Somnex**](https://somnex.xyz)
* [**Skip:Go**](https://go.skip.build)
* [**Squid**](https://app.squidrouter.com)
* [**Sushi Swap**](https://www.sushi.com)
* [**Stargate**](https://stargate.finance)
* [**Wolfswap**](https://wolfswap.app)
* [**VVS**](https://vvs.finance)

## Key Features

<CardGroup>
  <Card title="On-chain" icon="cube">
    All swaps happen on-chain using one of the integrated exchanges, ensuring secure and transparent execution.
  </Card>

  <Card title="Cross Chain" icon="cubes">
    Swap functionality comes with a bridging feature, enabling seamless swaps between compatible chains.
  </Card>

  <Card title="Easy To Use" icon="window">
    Swap interface is designed to be intuitive and resembles a classic, well-known exchange UI for easy and quick usage.
  </Card>

  <Card title="Low Fees" icon="hand-holding-circle-dollar">
    Flipsuite charges only up to 1% in fees, which is a typical fee applied by most wallets today. This fee varies based on a used exchange.
  </Card>
</CardGroup>


# Setup
Source: https://docs.flipsuite.xyz/modules/trading/setup

Learn how to start trading tokens in your server.

## Step 1 - Get familiar with your Flipwallet

All you need to do before starting trading tokens in your server is to get familiar with your Flipwallet
and deposit some tokens into it.

<Card title="Flipwallet" icon="wallet" href="/flippy/introduction">
  Click to learn more about the Flipwallet.
</Card>

## Step 2 - Start trading!

To trade tokens in Discord simply use one of the available commands:

<Card title="/swap" icon="right-left" href="/modules/trading/commands/swap">
  Swap between two different tokens or bridge/transfer them to another chain.
</Card>

<Card title="/buy" icon="bags-shopping" href="/modules/trading/commands/buy">
  Place a limit order to buy tokens once their price drops below a certain threshold.
</Card>

<Card title="/sell" icon="sack-dollar" href="/modules/trading/commands/sell">
  Place a limit order to sell tokens once their price rises above a certain threshold.
</Card>

<Card title="/long" icon="chart-line-up" href="/modules/trading/commands/long">
  Open a long position via Hyperliquid for a specific asset.
</Card>

<Card title="/short" icon="chart-line-down" href="/modules/trading/commands/short">
  Open a short position via Hyperliquid for a specific asset.
</Card>


# Activity
Source: https://docs.flipsuite.xyz/points/activity

View point system transactions, and credit or debit users manually.

<Frame>
  <img />
</Frame>

The **Activity** tab is the operational ledger for every point system. It shows you who initiated a transaction,
where it came from, and how much user balances changed.

## Key transaction types

Each point system transaction falls into one of the following categories:

* **Print**: Points were created and a total point system's supply was increased.
* **Transfer**: Points were transferred between two or more users.
* **Burn**: Points were destroyed and a total point system's supply was reduced.

Examples:

* Points rewarded for completing a quest -> **Print**
* Points tipped from one user to another -> **Transfer**
* Points credited dashboard or via API -> **Print**
* Points debited dashboard or via API -> **Burn**
* Points swapped for another points -> **Burn**
* Points received from swapping -> **Print**
* Points spent in storefronts -> **Burn**

## Update balances manually

To update point system balances from the dashboard:

1. Open the **Activity** tab for the point system.
2. Click **Update balance**.
3. Add one or more users by their Discord IDs.
4. Enter the balance change to apply to each selected user.
5. Submit the change by clicking the **Apply balance change** button.

<Frame>
  <img />
</Frame>

### How manual updates work

* A **positive** amount credits each selected user, printing new points.
* A **negative** amount debits each selected user, destroying points.
* The same amount change is applied to every selected user.

Manual dashboard changes are recorded in the transaction history as well, which makes the **Activity** tab the source
of truth for auditing balance changes.

### When to use manual management

Use manual balance updates when you need to:

* Grant bonus points to selected members.
* Correct balances after an external event.
* Run one-off campaigns outside Flipsuite quests.
* Remove balances for moderation or policy reasons.


# Conversions
Source: https://docs.flipsuite.xyz/points/conversions

Set exchange rates between point systems so users can swap their points.

<Frame>
  <img />
</Frame>

If your community runs more than one point system, you can define exchange rates between them in the **Conversions**
tab. This lets users swap one point balance for another using the rates you configure, adding relative value to each
point system.

## How exchange rates work

Each exchange rate connects a single **source** point system to a different **target** point system.
Conversion rate defines how many target points are printed for a single source point.

Examples:

* If the rate from `Silver` to `Gold` is `0.01`, then converting `100 Silver` yields `1 Gold`.
* If the rate from `Gems` to `Credits` is `5`, then converting `1 Gems` yields `5 Credits`.

## Add an exchange rate

1. Open the point system you want to create exchange rates for.
2. Go to the **Conversions** tab.
3. Click **Add exchange rate**.
4. Select the source and target point systems.
5. Enter the desired exchange rate.
6. Save it.

<Frame>
  <img />
</Frame>

## Planning your economy

Conversions are useful when you want to separate different parts of your economy, such as:

* Converting a broad activity currency into a more limited redemption currency.
* Running multiple currencies with different earning and spending patterns.
* Make one currency upgradable to another.


# Roles
Source: https://docs.flipsuite.xyz/points/discord-roles

Configure Discord roles granted to users based on their points balance.

<Frame>
  <img />
</Frame>

You can configure Discord roles to be granted to users based on their points balance.
This is the main way to turn balances into visible ranks, access tiers, or progression roles.

<Tip>
  Configured roles use point-based [gating rules](/gating/introduction) under the hood.
</Tip>

## Set up a new rule

1. Open your point system and go to the **Roles** tab.
2. Click **Add new gating rule**.
3. Choose the Discord role you want to grant.
4. Select the point system the rule should check.
5. Set the minimum balance required.
6. Optionally set a maximum balance if the role should only apply to a specific range.
7. Save the rule.

<Frame>
  <img />
</Frame>

Now, the role will be granted automatically when a user's balance changes and meets the configured criteria, and
revoked if they fall below the minimum required balance.

<Tip>
  Role updates happen automatically whenever user balance changes. Members do not need to press any buttons
  or verify manually for point-based role updates.
</Tip>


# Imports
Source: https://docs.flipsuite.xyz/points/imports

Import point balances from a different system.

> Import functionality allows you to seed an existing community economy, migrate balances from another system, or
> bulk-load users before launching a campaign.

## Step 1 - Open the holders tab

Go to the **Points** tab, open a point system, and select the **Holders** tab. From there you can:

* Search holders by Discord user ID.
* Export the current holder list as CSV.
* Import balances from a CSV file or pasted CSV text.

<Frame>
  <img />
</Frame>

## Step 2 - Initiate the import

Click the **Import** button, to open the import dialog.

<Frame>
  <img />
</Frame>

Inside the import dialog, you can either:

* Upload a `.csv` file containing user balances.
* Paste CSV content directly into the import dialog.

Each CSV row must contain:

1. The user's **Discord ID**
2. The user's **balance**

Example:

```
328218133074804739,2137
144610383091466241,123.45
```

### How imports behave

Imports are additive, not destructive:

* If a user does not exist yet, they become a new holder.
* If a user already exists, the imported amount is **added on top** of the existing balance.
* Existing balances are **not overwritten** by import.

### Export before you import

If you are updating an existing point system, export holders first. That gives you a backup snapshot and a safe base
file to edit before importing new values.


# Introduction
Source: https://docs.flipsuite.xyz/points/introduction

Learn what point systems are and how they can power your community economy.

<Frame>
  <img alt="Point System" />
</Frame>

Point systems let you create custom, spendable currencies or experience points for your community. Run your own economy,
reward members for doing quests, and decide whether points should behave like a spendable currency or a
non-transferable progression system.

## What points can be used for?

Points can be used across the broader Flipsuite reward stack:

* Reward users for doing quests or being active.
* Tip, raffle, and airdrop points to others via [Flippy](/flippy/introduction).
* Spend points in community [storefronts](/storefronts/introduction).
* Assign Discord roles automatically based on points balance.
* Support multiple, various point systems in a single community.
* Define exchange rates so users can convert one point system into another.
* Share point systems with partner communities through collabs.

## What's next?

<Card title="Set up your first point system" icon="sparkles" href="/points/setup">
  Create a new currency or progression system and configure how it should behave.
</Card>


# Setup
Source: https://docs.flipsuite.xyz/points/setup

Create a new point system and configure it.

> Setting up a point system starts with naming it, defining how members can use it, and activating it for your
> community. This guide walks you through the entire process.

## Step 1 - Open point systems

Navigate to the **Points** tab in your community dashboard and click the **Create point system** button. This will
open a form where you can create and configure a brand new point system.

<Frame>
  <img />
</Frame>

## Step 2 - Configure the point system

You'll be asked to provide the following details about the point system:

* **Emoji**: An icon shown next to the point system across all user-facing surfaces.
* **Name**: Point system name, for example `Gems`, `XP`, `Reputation`, or `S1 Prestige`.
* **Description**: A short explanation of what the points are for.

<Frame>
  <img />
</Frame>

Each point system also has two important behavior flags:

* **Transferable**: Members can move balances between each other.
* **Burnable**: Members can destroy their own points, decreasing the point system's supply.

These settings also determine how the point system is categorized:

* If the system is **transferable** or **burnable**, it is labeled as a **currency**.
* If the system is neither transferable nor burnable, it is labeled as **experience**.

<CardGroup>
  <Card title="Currency" icon="coins">
    Great for community coins, loyalty systems, and anything members should be able to move or spend.
  </Card>

  <Card title="Experience" icon="chart-line-up">
    Great for rank progression, reputation, karma, seasonal XP, or other non-tradeable scores.
  </Card>
</CardGroup>

<Tip>
  Point system category is informational only and does not affect its behavior.
</Tip>

## Step 3 - Activate the point system

Click **Save** to create the point system. Once created, it will appear in the point systems list together with
its holder count, status, and category.

<Frame>
  <img />
</Frame>

## Step 4 - What's next?

After creation, you can open the point system and go through the following tabs:

* **Holders** to view holders, as well as import point balances from other systems.
* **Activity** to view point system transactions, and credit or debit users manually.
* **Roles** to configure Discord roles granted automatically to users based on their balance.
* **Conversions** to define exchange rates between different point systems.
* **Settings** to access the point system's configuration.

<Frame>
  <img />
</Frame>


# Sharing
Source: https://docs.flipsuite.xyz/points/sharing

Share point systems with partner communities through collabs.

<Frame>
  <img />
</Frame>

Point systems can be shared with partner communities through the **Collabs** tab. This is how you open cross-community
economy routes while still controlling what the partner can and cannot do with the shared point systems.

## Share a point system

1. Open **Collabs** and select the partner community.
2. Go to the partner's **Points** tab.
3. Click **Share point system**.
4. Select one of your active point systems.
5. Choose the permissions the partner community should receive.
6. Save to share the point system.

<Frame>
  <img />
</Frame>

Once shared, the partner community can review the connection in the same Collabs area.
The share must be enabled on the receiving side before access becomes active.

## What each permission allows

1. **VIEW** permission lets the partner community:
   * Read point system holders and their balances
   * Use point-based quest tasks with the point system
   * Use point-based gating rules with the point system

2. **TRANSFER** permission lets the partner community:
   * Use the point system for tips, airdrops, and raffles in their server.

3. **SPEND** permission lets the partner community:
   * Use the point system as the **source** point system for swaps.
   * Require the point system for buying items from community storefronts.

4. **PRINT** permission lets the partner community:
   * Offer the point system in quest rewards.
   * Use the point system as the **target** point system for swaps.
   * Print new points via tips, airdrops, and raffles (community admins only).

## Typical collaboration patterns

* Grant **VIEW** when you want the partner to build quests around your point system.
* Add **TRANSFER** when you want partner community members to use your points for tips.
* Add **SPEND** when you want the partner to support spending or swaps.
* Add **PRINT** only when you explicitly trust the partner to print more of your supply.

<Warning>
  Only grant **PRINT** permission to trusted partners, as this permission makes it possible for the partner to print
  more points, increasing the supply of the point system.
</Warning>


# Introduction
Source: https://docs.flipsuite.xyz/quests/introduction

Engage your community with interactive quests and rewards.

<Frame>
  <img alt="Quests Console" />
</Frame>

Quests are a powerful way to drive engagement in your community by rewarding members for completing specific tasks.
Whether it's following your social media accounts, participating in onchain activities, or simply providing feedback,
our Quest Engine makes it easy to create, manage, and automate these interactions.

## Core concepts

To get started with Quests, it's important to understand the key building blocks:

* **Quests**: The top-level container that defines a set of tasks and rewards.
* **Tasks**: Specific actions a user must perform (e.g., "Follow us on X", "Hold 100 Tokens").
* **Rewards**: What users receive upon completing the quest (e.g., Tokens, NFTs, Points).
* **Completions**: The state reached when all tasks in a quest are successfully verified.
* **Submissions**: A quest completion awaiting a manual review from a team member.

## Lifecycle of a quest

1. **Create**: Define the basic details like name, description, and banner.
2. **Configure**: Add tasks and set up the reward structure.
3. **Activate**: Publish the quest to make it available to your community.
4. **Participate**: Users discover and complete tasks through your Discord.
5. **Verify**: Tasks are either automatically verified or submitted to your team for review.
6. **Reward**: Upon completion, rewards are distributed based on configured strategies.

## What's next?

<Card title="Setup your first quest" icon="rocket" href="/quests/setup">
  Follow our step-by-step guide to launch your first quest in minutes.
</Card>


# Moderation
Source: https://docs.flipsuite.xyz/quests/moderation

Ban users from participating in your quests for policy violations.

## Overview

To maintain a fair environment for all participants, Flipsuite provides moderation tools to manage problematic users.

## Bans

If a user is found to be cheating or violating community guidelines, you can ban them from participating in your quests.

<Frame>
  <img />
</Frame>

To apply a ban to a user:

1. Go to the **Quests > Settings > Moderation** page.
2. Click the **Ban user from quests** button.
3. Provide the user's Discord ID or X account handle.
4. Choose a ban duration and enter the ban reason.
5. Optionally choose a specific task types to ban the user from.
6. Click the **Ban user** button.

After banning a user, the will be blocked from completing quests in your community until the ban expires (unless it's permanent).
You can revoke bans at any time.


# Notifications
Source: https://docs.flipsuite.xyz/quests/notifications

Stay updated on quest activity via Discord.

## Overview

Configure real-time notifications to stay informed when users interact with your quests.
Notifications are sent directly to your Discord server via Flippy.

## Notifications

1. **Completions**: Receive a notification every time a user successfully completes a quest.
2. **Rewards**: Receive a notification every time a user receives a quest reward.
3. **Submissions**: Get alerted whenever a user submits a task that requires manual review.

## Configuration

To set up notifications, simply go to the **Quests > Settings > Notifications** page and select the Discord channel
where notifications should be posted for each notification type.

<Frame>
  <img />
</Frame>

<Warning>
  For notifications to work, Flippy must be present in your Discord server and it must have **View Channel**
  and **Send Messages** permissions in the selected channel.
</Warning>


# Setup
Source: https://docs.flipsuite.xyz/quests/setup

Learn how to create, configure, and launch your first quest.

> Launching a quest involves defining its identity, adding tasks for your community to complete, and setting up rewards.
> This guide walks you through the entire process.

## Step 1 - Create a new quest

Navigate to the **Quests** section in your community dashboard and click the **Create new quest** button.
You'll be asked to choose whether you want to create a quest from scratch or by using of the available templates.
Select **Create quest from scratch** for now. This will take you to our quest creation wizard:

<Frame>
  <img />
</Frame>

You'll be asked to provide the following details about your quest:

* **Name**: The title of your quest as it will appear to users.
* **Description**: A brief quest description that will be visible on your quest card.
* **Instructions**: Detailed instructions or context required to finish a quest.
* **Banner**: Upload a high-quality image to represent your quest.

## Step 2 - Configure quest

Decide how often users can complete this quest and if there's a cap on total completions.

<Frame>
  <img />
</Frame>

You can configure the following options for your quest:

* **Visibility**: Choose if the quest should be visible to communities you collaborate with.
* **Recurrence**: Choose between `ONCE`, `DAILY`, `WEEKLY`, `MONTHLY`, or `CUSTOM` intervals.
* **Round count**: For recurring quests, how many times the quest itself can repeat.
* **Max total completions**: Global cap for all users.
* **Max round completions**: Cap per user per interval.

## Step 3 - Add tasks

Tasks are the requirements users must meet or specific actions they need to take. We already support over **20**
different task types. Click **Add task** to browse the task library.

<Frame>
  <img />
</Frame>

For each task, you'll need to provide a specific configuration (e.g., the X account to follow or the minimum token
balance required to attempt the quest). You can learn more about the available task types in
the [task library](/quests/tasks).

<Frame>
  <img />
</Frame>

<Tip>
  You can use the task verification sandbox to test task requirements against your own account to see if tasks are
  set up correctly.
</Tip>

### Task reviews

Each task you add to your quest can be toggled to require a review from your team member before it can be completed.
This is useful if a task cannot be fully verified by our system (like reviewing if a meme uploaded by a user is on-topic).

### Reward boosts

Each optional task you add to your quest can be granted a reward boost that will increase the final reward for anyone
who meets the task's requirements. It's a great way to gamify quests in your community and reward community members
who are willing to put in more effort.

<Frame>
  <img />
</Frame>

To make a task grant reward boost, simply check the **Optional task** and **Include reward boost** checkboxes in the
task settings like so, and configure the boost parameters:

<Frame>
  <img />
</Frame>

There are 3 reward boost modes you can apply to any optional task:

* **Max:** Only the highest boost from all `MAX` reward boosts is applied
* **Cumulative:** All boosts with `CUMULATIVE` mode will be added together
* **Global:** Applies on top of all other reward boosts

You are free to mix and match different reward boost modes across the same quest. The final reward multiplier for each
user is calculated using the following formula:

$$
(1 + \max(\text{MAX}) + \sum \text({CUMULATIVE})) \times (1 + \prod (\text{GLOBAL}))
$$

## Step 4 - Set up rewards

Choose how you want to reward your community. Click **Add reward** to browse the available reward types.

<Frame>
  <img />
</Frame>

There are multiple reward types you can choose from:

* **Random**: Each user will get a random reward from a selected [reward pool](/rewards/reward-pools).
* **Points**: Each user will receive a specific, base amount of points.
* **Points Pool**: All users will share a pool of points.
* **Token**: Each user will receive a specific, base amount of tokens.
* **Token Pool**: All users will share a pool of tokens.
* **NFT**: Users will receive a specific NFT.
* **Role**: Users will be granted a specific role in your Discord server.
* **Custom**: Users will get a custom reward that's defined by you.

For each reward you add to your quest, you can select from the following distribution strategies that will affect
who receives the reward:

* **Everyone**: All users who complete the quest will receive the reward.
* **FCFS**: Only the first `N` users who complete the quest will receive the reward.
* **Raffle**: Only `N` random users will receive the reward once the quest ends.

<Frame>
  <img />
</Frame>

<Tip>
  Use the spending calculator widget to estimate your potential spending based on set rewards, estimated number of
  quest completions and applied reward multipliers.
</Tip>

Make sure to get familiar with our reward system before distributing onchain rewards.

<Card title="Rewards" icon="trophy" href="/rewards/introduction">
  Click to learn how to set up rewards in Flipsuite.
</Card>

## Step 5 - Review and activate

Once the quest is configured, it's time to review and finalize it.

<Frame>
  <img />
</Frame>

If everything looks good, click **Save quest** to create the quest. Once created, your quest will be in the `DRAFT`
state and won't be visible to users yet. To activate your quest, simply find it in your questboard and click
the **Activate quest** button.

<Frame>
  <img />
</Frame>

You will be asked again to validate the quest settings before activating it, because quest tasks and rewards can't be
changed after activation. If everything looks good, click the **Activate** button to activate the quest and make it
visible to your community!

### Sharing your quest

By default, you need to use `/quest share` slash command in Discord in order to share your quest. If you want to
automate this process and push quests to respective Discord channels automatically, head over to the
quest settings and configure channels for automatic sharing.

<Frame>
  <img />
</Frame>

Alternatively, you can choose a Discord channel to share your quest in when activating it.
This will override the channels you've set in the quest sharing settings.


# Sharing
Source: https://docs.flipsuite.xyz/quests/sharing

Collaborate with other communities to cross-share quests.

## Overview

Community collabs allow different communities to form partnerships, making it easier to grow together and cross-promote content.
By establishing a collaboration, you can access shared quests from partner communities and display them directly to your own community.

<Frame>
  <img />
</Frame>

## How it Works

To start a partnership, navigate to the **Collabs > Requests** tab and search for the community you wish to work with.
Sending a request allows the other community's administrators to review your profile before accepting.

### Shared Visibility

Once a collab request is accepted, both communities gain visibility into each other's quests.

<Note>
  Only quests specifically created with the **"Shared"** visibility setting will be visible to partner communities.
  Private quests remain hidden.
</Note>

### Cross-Sharing & Automation

After partnering, you can share quests from partner communities in two ways:

1. **Manually:** Using the `/quest share` command in Discord.
2. **Automatically:** Create a dedicated channel with an automated quest feed.

A dedicated quest feed can be set up by navigating to the partner community's settings by tapping on the community's
card in the **Collabs > Partners** tab.

<Frame>
  <img />
</Frame>

Creating a dedicated channel ensures your members stay up to date with the latest activities from your partners
without manual intervention.

## Settings & Privacy

By default, every community is open to receiving collab requests. If you prefer to manage your partnerships more privately:

1. Navigate to the **Collabs > Settings** tab.
2. Toggle the **"Open to collabs"** option.

When disabled, other communities will not be able to send you new requests, though existing partnerships will remain active.


# Submissions
Source: https://docs.flipsuite.xyz/quests/submissions

Review quest submissions from community members.

## Overview

There are some task types like **File Upload** or **Create X Post** that require a manual review from your team before
they can be marked as complete. Moreover, you can enable manual review on some of the other task types as well.

When a quest includes a task requiring manual review, a submission is created for each user attempting to complete that quest.
The user's completion is marked as successful only after you approve their submission.

## Submissions

You can view each quest submission individually in the **Submissions** tab.

<Frame>
  <img />
</Frame>

Simply click on a submission to view its details about the submitted tasks, related quest, and the user who made the submission.
After reviewing the submission, you can:

1. **Approve** - Mark the quest as complete for the user.
2. **Reject** - Reject the submission with an optional reason.
3. **Disqualify** - Reject it and prevent the user from attempting the quest again.

The user will be notified about the submission review outcome via Discord.


# Tasks
Source: https://docs.flipsuite.xyz/quests/tasks

Get familiar with available quest requirement types.

## Discord

Requirements that interact with Discord.

### <Icon icon="calendar" />  Discord Account Age

<Frame>
  <img />
</Frame>

Check if a user's Discord account age is above a certain value.

<Info>
  This task checks how long ago the user's Discord account was created, not their IRL age.
</Info>

### <Icon icon="masks-theater" />  Discord Server Roles

<Frame>
  <img />
</Frame>

Check if a user has specific roles in a selected Discord server.

<Check>
  You can select any server Flippy is in, not just yours, to verify roles from other servers.
</Check>

### <Icon icon="badge-check" />  Discord Server Tag

<Frame>
  <img />
</Frame>

Check if a user has a server tag from a specific Discord server enabled on their profile.

### <Icon icon="users" />  Discord Users

<Frame>
  <img />
</Frame>

Limit quest completion to specific Discord users.

<Tip>
  Great for bounty quests that you want only specific people to complete.
</Tip>


# Custom
Source: https://docs.flipsuite.xyz/quests/tasks/custom

Custom task integration using external APIs.

## <Icon icon="webhook" />  API Task

Verify quest completion by making a request to an external endpoint. This allows you to create quests with custom tasks
tied to your own platform or application.

<Frame>
  <img />
</Frame>

### Request payload

When verifying an API task, our system sends a `POST` request to the endpoint you specified in the task settings.
Each request includes the following data:

<Tabs>
  <Tab title={"Quests"}>
    Below request payload is sent when the verification is triggered by a quest completion.

    ```typescript theme={null}
    interface FlipsuiteCustomTaskVerificationRequestPayload {
        community: {
            id: string // ID of the community the quest belongs to
        }
        quest: {
            id: string // ID of the quest
        }
        task: {
            id: string // ID of the task (unique within the quest)
        }
        user: {
            // User's Discord account details
            discord?: {
                id: string // Account ID
                username: string // Account username
            }
            // User's Steam account details
            steam?: {
                id: string // Account ID
                username: string // Account username
                avatarUrl?: string // Account avatar URL
            }
            // User's Telegram account details
            telegram?: {
                id: string // Account ID
                username: string // Account username
                avatarUrl?: string // Account avatar URL
            }
            // User's X account details
            twitter?: {
                id: string // Account ID
                handle: string // Account handle (without @)
                username: string  // Account username
            }
            // User's linked wallets
            wallets?: {
                id: string // Unique wallet ID
                chain: string // Chain key (e.g., "Ethereum" or "Solana")
                chainId: string // Chain ID (e.g., "137" for Polygon or "osmosis-1" for Osmosis)
                address: string // Wallet address
            }[]
        }
    }
    ```
  </Tab>

  <Tab title={"Gating"}>
    Below request payload is sent when the verification is triggered by a gating rule.

    ```typescript theme={null}
    interface FlipsuiteCustomTaskVerificationRequestPayload {
        community: {
            id: string // ID of the community the quest belongs to
        }
        rule: {
            id: string // ID of the gating rule
            discordRoleId: string // ID of the gated Discord role
        }
        user: {
            // User's Discord account details
            discord?: {
                id: string // Account ID
                username: string // Account username
            }
            // User's Steam account details
            steam?: {
                id: string // Account ID
                username: string // Account username
                avatarUrl?: string // Account avatar URL
            }
            // User's Telegram account details
            telegram?: {
                id: string // Account ID
                username: string // Account username
                avatarUrl?: string // Account avatar URL
            }
            // User's X account details
            twitter?: {
                id: string // Account ID
                handle: string // Account handle (without @)
                username: string  // Account username
            }
            // User's linked wallets
            wallets?: {
                id: string // Unique wallet ID
                chain: string // Chain key (e.g., "Ethereum" or "Solana")
                chainId: string // Chain ID (e.g., "137" for Polygon or "osmosis-1" for Osmosis)
                address: string // Wallet address
            }[]
        }
    }
    ```
  </Tab>
</Tabs>

### Expected response

If the task verification is successful, return a response with a `200` status code. No response body is required, but
you can include a `verificationData` field in the response to store additional, arbitrary metadata about the
verification result. This metadata will be saved with the task completion record for future reference.

```json theme={null}
{
  "verificationData": {
    "score": 1000
  }
}
```

If the task verification fails, return a response with a `400` status code and include a `message` field in the response body.
This message should explain why the verification failed in a user-friendly way, as it will be displayed to the user in the Flipsuite UI.

```json theme={null}
{
  "message": "You have scored only 369 points on the leaderboard, but at least 1,000 are required."
}
```

<Warning>
  Your API endpoint must respond within 30 seconds. If the response takes longer, the task verification will fail with a timeout error.
</Warning>

### Endpoint security

In the quest integration settings, you can configure an authentication secret that will be sent with every request to your API.
This allows you to verify that the request originated from Flipsuite. The secret is included in the `Authorization` header of each request.

<Frame>
  <img />
</Frame>


# Discord
Source: https://docs.flipsuite.xyz/quests/tasks/discord

Tasks that interact with Discord.

## <Icon icon="calendar-check" />  Account Age

<Frame>
  <img />
</Frame>

Check if a user's Discord account age is above a certain value.

<Info>
  This task checks how long ago the user's Discord account was created, not their IRL age.
</Info>

## <Icon icon="masks-theater" />  Server Roles

<Frame>
  <img />
</Frame>

Check if a user has specific roles in a selected Discord server.

<Check>
  You can select any server Flippy is in, not just yours, to verify roles from other servers.
</Check>

## <Icon icon="badge-check" />  Server Tag

<Frame>
  <img />
</Frame>

Check if a user has a server tag from a specific Discord server enabled on their profile.

## <Icon icon="users" />  User Allowlist

<Frame>
  <img />
</Frame>

Limit quest completion to specific Discord users.

<Tip>
  Great for bounty quests that you want only specific people to complete.
</Tip>


# Input
Source: https://docs.flipsuite.xyz/quests/tasks/input

Tasks that require users to provide information, files, or feedback.

## <Icon icon="cloud-arrow-up" />  File Upload

<Frame>
  <img />
</Frame>

Require users to upload a file or document. Ideal for proof-of-work or creative contests.

<Accordion title={"Supported file types"}>
  * **Image**: `.jpg`, `.jpeg`, `.png`, `.webp` and `.gif` files.
  * **Video**: `.mp4`, `.webm` and `.mov` files.
  * **Audio**: `.mp3` and `.wav` files.
  * **PDF**: `.pdf` files.
</Accordion>

<Note>
  Max size of the uploaded file is limited to 5 MB.
</Note>

<Warning>
  This task requires manual review from your team. It cannot be verified automatically.
</Warning>

## <Icon icon="binary" />  Numeric Input

<Frame>
  <img />
</Frame>

Ask users to provide a numeric response.

## <Icon icon="list-check" />  Poll Input

<Frame>
  <img />
</Frame>

Ask your community to vote in a poll. Great for surveys or getting structured feedback.

## <Icon icon="font-case" />  Text Input

<Frame>
  <img />
</Frame>

Ask users to provide a written response.

## <Icon icon="wallet" />  Wallet Input

<Frame>
  <img />
</Frame>

Ask users to submit a wallet address for a specific blockchain.


# Onchain
Source: https://docs.flipsuite.xyz/quests/tasks/onchain

Tasks that interact with the blockchain.

## <Icon icon="wallet" />  NFT Balance

<Frame>
  <img />
</Frame>

Verify that a user holds NFTs from a specific collection.

## <Icon icon="wallet" />  Token Balance

<Frame>
  <img />
</Frame>

Verify that a user holds a minimum amount of a specific token.

## <Icon icon="arrow-right-arrow-left" />  Token Swap

<Frame>
  <img />
</Frame>

Verify that a user has purchased a specific token via Flippy.

## <Icon icon="hand-holding-dollar" />  Token Tip

<Frame>
  <img />
</Frame>

Verify that a user has tipped, airdropped or raffled enough amount of tokens via Flippy.


# Points
Source: https://docs.flipsuite.xyz/quests/tasks/points

Tasks that are based on point systems.

## <Icon icon="sparkles" />  Points Balance

<Frame>
  <img />
</Frame>

Check if a user has enough points in their balance.

## <Icon icon="hand-holding-dollar" />  Points Tip

<Frame>
  <img />
</Frame>

Verify that a user has tipped, airdropped or raffled enough amount of points via Flippy.


# Top.gg
Source: https://docs.flipsuite.xyz/quests/tasks/topgg

Tasks that interact with the Top.gg platform.

## <Icon icon="discord" />  Discord Bot Vote

<Frame>
  <img />
</Frame>

Check if a user has voted for a specific Discord bot on [Top.gg](https://top.gg).

## <Icon icon="discord" />  Discord Server Vote

<Frame>
  <img />
</Frame>

Check if a user has voted for a specific Discord server on [Top.gg](https://top.gg).

### Top.gg setup

First of all, go to quest setup and choose one of the available Top.gg tasks. The system will generate a webhook URL
for you in the **Webhook URL** field like in the image below:

<Frame>
  <img />
</Frame>

Copy the webhook URL and go the **Integrations & API** settings page of your bot or server on [Top.gg](https://top.gg).
Here, click the **Create** button to add a new webhook.

<Frame>
  <img />
</Frame>

In the dialog that appears, simply paste the webhook URL you copied earlier, toggle the **Vote Created** option
under the **Subscribed Events** section and click **Create**.

<Frame>
  <img />
</Frame>

Congratulations, now Flipsuite can track voting activity for your bot/server!

<Note>
  Our system won't be able to detect any votes that were made before the webhook was created, so be sure to start
  a voting quest only after adding the webhook.
</Note>


# X (Twitter)
Source: https://docs.flipsuite.xyz/quests/tasks/twitter

Tasks that interact with X (Twitter).

## <Icon icon="calendar-check" />  Account Age

<Frame>
  <img />
</Frame>

Check if a user's X account age is above a certain value.

<Info>
  This task checks how long ago the user's X account was created, not their IRL age.
</Info>

## <Icon icon="wireless" />  Account Followers

<Frame>
  <img />
</Frame>

Check user's X account follow count.

## <Icon icon="user-plus" />  Follow Account

<Frame>
  <img />
</Frame>

Check if a user is following one or more X accounts.

## <Icon icon="sparkles" />  Post Creation

<Frame>
  <img />
</Frame>

Require users to create a new post with a specific content guidelines or requirements.

<Warning>
  By default, this task requires manual review from your team to ensure the quality of content.
</Warning>

## <Icon icon="comment-plus" />  Post Interaction

<Frame>
  <img />
</Frame>

Check if a user liked, bookmarked, reposted, or commented a specific X post.

## <Icon icon="money-bill-trend-up" />  Subscribe Account

<Frame>
  <img />
</Frame>

Check if a user is subscribed to one or more X accounts.

## <Icon icon="badge-check" />  Verified Account

<Frame>
  <img />
</Frame>

Check if the user's X account is verified (has a blue checkmark).


# Templates
Source: https://docs.flipsuite.xyz/quests/templates

Save time by using pre-configured quest and task templates.

## <Icon icon="scroll" />  Quest templates

A quest template is a blueprint for a full quest, including its configuration, tasks, and rewards.
They allow you to quickly launch new quests without starting from scratch.

### Creating a quest template

To save a quest as a template:

1. Go to the **Templates > Quests** tab.
2. Click the **Create quest template** button.
3. Configure the template as needed like it is a regular quest.
4. Click **Save template** in the last quest builder.
5. It will now appear in your library of available templates.

### Using a quest template

When creating a new quest, you can choose the **Create quest from template** option.
This will show you a list of all available templates:

<Frame>
  <img />
</Frame>

Choosing a template will automatically populate the quest's configuration that you can modify as needed.

## <Icon icon="puzzle-piece" />  Task templates

Task templates are pre-configured versions of individual tasks (e.g., a "Token Balance" task with your token details already filled in).
They allow you to build new quests using common tasks without having to manually configure them.

### Creating a task template

You can create and manage task templates in the **Quest Settings > Task Templates** section of the dashboard.
To save a task as a template:

1. Go to the **Templates > Tasks** tab.
2. Click the **Create task template** button.
3. Choose the task type and configure it as needed.
4. Click **Save** once you're done.
5. It will now appear in your library of available tasks.

### Using a task template

When adding tasks to a quest, you will see a list of all available task templates at the top of the task library.

<Frame>
  <img />
</Frame>

Simply click on the one you want to use and it will be added to the quest.


# Quickstart
Source: https://docs.flipsuite.xyz/quickstart

Learn how to set up Flippy in your server.

## Step 1 - Invite Flippy to your server

If [Flippy](/flippy/introduction#who-is-flippy) (our Discord bot) isn't in your server yet, click [here](https://discord.com/oauth2/authorize?client_id=1150448986264698980\&permissions=395405806672\&integration_type=0\&scope=bot) to invite it.

| Bot Permissions                                                             | Required | Reason                                                                                                                        |
| --------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- |
| View Channels<br />Send Messages<br />Embed Links<br />Read Message History | ✅        | Flippy requires it to send messages in your server.                                                                           |
| Use External Emoji                                                          | ✅        | Required to show custom emojis for tokens in messages.                                                                        |
| Add Reactions                                                               | ❌        | Required if you want Flippy to react to messages.                                                                             |
| Attach Files                                                                | ❌        | Required if you want Flippy to show images in messages.                                                                       |
| Send Messages in Threads                                                    | ❌        | Flippy needs this permission to send messages in threads.                                                                     |
| Create Public Threads<br />Create Private Threads<br />Manage Threads       | ❌        | Flippy needs this permission to open threads for some requests to keep the main chat clean.                                   |
| Manage Channels                                                             | ❌        | Required to automatically create an admin-only alerts channel when the bot is invited. Can be revoked afterwards.             |
| Manage Roles                                                                | ❌        | Required to grant roles to users during verification, or when members receive roles as quest rewards or storefront purchases. |

## Step 2 - Setup alerts channel

If you enabled the **Manage Channels** permission when inviting Flippy to your server, a channel category named
**Flipsuite** with the `🚨alerts` channel in it should get created:

<Frame>
  <img />
</Frame>

<Tip>
  This channel will most likely be created at the bottom of your channel list. If you still can't find
  it in your server, use the `/setup` command to spawn it manually.
</Tip>

<Frame>
  <img />
</Frame>

The alerts channel is where you will receive various alerts from Flipsuite, such as when your rewards wallet balance is
empty and needs to be refilled, and other notifications that require your immediate attention. You can rename this
channel and move it somewhere else, but it's recommended to not delete this channel.

## Step 3 - Activate your server

Server activation is a one-click process of registering your server within Flipsuite. To activate your server, simply
log into [the dashboard](https://flipsuite.xyz/manage) and go to the **Manage communities** tab.

<Frame>
  <img />
</Frame>

From the list of servers you have admin permissions in, pick yours and simply click the **Activate** button.
This will allow you to manage your community via Flipsuite dashboard.

<Note>
  Each server can only be activated once. If someone else from your team has already activated your server,
  ask them to create a [team](/account/teams) and invite you to it so you can manage it together.
</Note>

## Step 4 - What's next?

Set up one of the Flipsuite modules below to add more utility and fun to your server, or create a team to
manage your community together with your friends or co-workers.

### Essentials

Get familiar with Flipsuite and its essential features.

<CardGroup>
  <Card title="Quest Engine" icon="scroll" href="/quests/introduction">
    Learn how to engage your community with interactive quests and rewards.
  </Card>

  <Card title="Point Systems" icon="sparkles" href="/points/introduction">
    Learn what points are and how they can power your community economy.
  </Card>

  <Card title="Flipwallets & Flippy" icon="robot" href="/flippy/introduction">
    Get familiar with the Flipwallet and Flippy, a digital wallet assistant layered over Flipsuite.
  </Card>

  <Card title="Teams" icon="user-group" href="/account/teams">
    Share your community with your team to manage it together and delegate responsibilities.
  </Card>
</CardGroup>

### Modules

Deep dive into one of the Flipsuite modules below to add more utility and fun to your server.

<CardGroup>
  <Card title="Gating" icon="lock" href="/gating/introduction">
    Learn how to use gating module in your server to automatically verify holders and members.
  </Card>

  <Card title="Storefronts" icon="store" href="/storefronts/introduction">
    Create branded storefronts for roles, points, and custom rewards.
  </Card>

  <Card title="Swap" icon="right-left" href="/modules/swap/introduction">
    Learn how to swap and bridge tokens directly in Discord using your Flipwallet.
  </Card>

  <Card title="Tipping" icon="hands-holding-dollar" href="/modules/tipping/introduction">
    Learn how to airdrop, raffle and tip tokens in your server.
  </Card>
</CardGroup>


# Deferred Rewards
Source: https://docs.flipsuite.xyz/rewards/deferred-rewards

Accumulate rewards and save on transaction fees.

## What are deferred rewards?

Deferred rewards are tokens that accumulate in your reward wallets instead of being sent to your community members
immediately after they win them. This approach significantly reduces gas fees by avoiding individual transactions
for each token reward.

## How does it work?

Token rewards that are set to be distributed using this system won't be sent to the winner's wallet immediately.
Instead, they will be held in your rewards wallet until the winner manually claims them via [`/rewards`](/flippy/commands/rewards) command.

<Frame>
  <img />
</Frame>

Every deferred token reward that is won by your community members is automatically marked as debt that can be collected
by the user later. You can view your total rewards debt by going the the **Debt** tab in your community dashboard.

<Frame>
  <img />
</Frame>

## How to set it up?

To manage your community rewards settings, go to the **Settings** tab in your community dashboard under the **Rewards**
category.

<Frame>
  <img />
</Frame>

There are 2 options you can tweak for deferred rewards:

<Card title="Reward claim cooldown duration" icon="hourglass-clock">
  Time users have to wait after claiming a token before they can claim it again.
</Card>

<Card title="Minimum value of claimed tokens" icon="sack-dollar">
  <p>Users won't be able to claim the accumulated tokens until their value reaches set threshold.</p>

  <div>
    <a href="https://flipsuite.xyz/pricing"><Icon icon={"cube"} /><p>Growth only</p></a>
  </div>
</Card>

## Setting deferred token rewards

You can either set token rewards to be deferred on a per-reward basis, or enable it for all token rewards in
a specific reward pool in its settings.

### For single reward

When adding a token reward to the pool, you have an option to make it a deferred reward:

<Frame>
  <img />
</Frame>

### For all rewards in a pool

You can find a relevant toggle in the reward pool settings tab:

<Frame>
  <img />
</Frame>

## Important

There are some chains (e.g., Solana) for which deferred token rewards are enforced and always enabled due to
technical limitations or nuances. This means that tokens on these chains are never sent to winners directly, and
always need to be claimed via [`/rewards`](/flippy/commands/rewards) command.


# Introduction
Source: https://docs.flipsuite.xyz/rewards/introduction

Get familiar with Flipsuite's reward system.

<iframe />

## Rewards

Flipsuite's reward system is a key component for building strong server economies and driving thoughtful engagement
in your community! Here are the different types of rewards you can utilize to reward your community members:

<CardGroup>
  <Card title="Tokens and NFTs" icon="coins">
    Reward your community members with tokens and NFTs of your choice, fully on-chain.
  </Card>

  <Card title="Points and EXP" icon="sparkles">
    Reward your community members with spendable off-chain currency or experience.
  </Card>

  <Card title="Discord Roles" icon="masks-theater">
    Seamlessly integrate with nearly every Flipsuite module by rewarding your community members with Discord roles.
  </Card>

  <Card title="Custom Rewards" icon="message-pen">
    Get creative and reward your community with custom items like gift codes, merch, or anything else you can think of.
  </Card>
</CardGroup>

## How are rewards distributed?

Learn how every reward type is distributed to community members and what setup (if any) is required from you.

### <Icon icon="coins" />  Tokens and NFTs

Token and NFT rewards require you to set up a [rewards wallet](/rewards/reward-wallets) in your community dashboard that is used to
automatically send on-chain rewards to your community members.

### <Icon icon="masks-theater" />  Discord Roles

Discord roles don't require any extra setup, except making sure that Flipsuite's role is higher in your server's role
hierarchy than the role you want to grant.

<Warning>
  Flippy can only grant and revoke roles from users in your server that are **below its role** in your server's
  role hierarchy. You can access it by going to the `Roles` tab in your server settings.

  <Frame>
    <img />
  </Frame>

  In the example above, Flippy can only grant the "Verified - Tier 2" role to your community members. It won't have
  access to the "Verified - Tier 3" role because it's above the bot's role.
</Warning>

### <Icon icon="message-pen" />  Custom Rewards

Custom rewards aren't distributed automatically at all, so they don't require any extra setup. You are the one
responsible for manually granting winners their prizes.

### <Icon icon="sparkles" />  Points

Points are distributed automatically to community members. No extra setup is required.

## Where do I setup the rewards?

For the most part, rewards are created and managed through reward pools that allow you to distribute prizes with
different win chances and limited quantities, for maximum gamification. This makes it more exciting and fun when
members win rewards that are more rare than others.

<Card title="Reward Pools" icon="dice" href="/rewards/reward-pools">
  Learn how to create reward pools in your community.
</Card>


# Reward Pools
Source: https://docs.flipsuite.xyz/rewards/reward-pools

Learn how to create reward pools in your community.

## Creating a reward pool

To create a reward pool, go to the **Pools** tab in your community dashboard and click the **Create new reward pool**
button to get started. You'll be asked to provide a name for your reward pool.

<Frame>
  <img />
</Frame>

After successfully creating the reward pool you will get redirected to the reward pool details:

<Frame>
  <img />
</Frame>

## Adding rewards to the pool

Once a reward pool is created, you can start adding rewards to it! Simply click the **Add new reward** button and choose
one of the available reward types.

<Frame>
  <img />
</Frame>

## Tweaking reward win chances

After you added a bunch of rewards to the pool, it's time to assign win chance to each of them. You can do so by
clicking the **Change win chances** button.

<Frame>
  <img />
</Frame>

## Wrapping it up

After tweaking reward win chances, your page should look similar to the screenshot below, showing all rewards in the pool,
their win chance and quantity left. If there's any issue with one of the added rewards, you will notice the status icon
changing its color to yellow or red. If everything's green though, your reward pool is ready to be used!

<Frame>
  <img />
</Frame>


# Reward Wallets
Source: https://docs.flipsuite.xyz/rewards/reward-wallets

Learn how to add or generate reward wallets.

## Adding a rewards wallet

To add a rewards wallet, go to the **Wallets** tab in your community dashboard and click the **Add new rewards wallet**
button to get started.

<Frame>
  <img />
</Frame>

When adding a rewards wallet for a selected chain, you can choose to either generate a totally fresh wallet or use
your own. **In both cases you have full access to the wallet's private key.**

<Note>
  The private key of your rewards wallet is accessible only by the community owner - and if your community is shared
  in a [team](/account/teams), by team owner and admins.
</Note>

After creating a rewards wallet you will be redirected to its overview panel:

<Frame>
  <img />
</Frame>

You can switch between the tabs to view your rewards wallet tokens and NFT balance, activity, and look up its private
key if you have access.

## Topping up your rewards wallet

To top up your wallet with tokens, simply send them to it like to a regular wallet.

<Note>
  Only verified tokens and NFTs that aren't marked as spam will be visible in your rewards wallet.
</Note>

<Warning>
  Always keep some gas token in your rewards wallet so rewards can be distributed seamlessly.
</Warning>

## Delayed reward distribution

If you expect to reward a lot of people and the chain you are operating on has relatively high fees, you can
leverage the alternative distribution system to reverse the distribution flow by requiring users to claim their
rewards explicitly, thus making the whole process cheaper.

<Card title="Deferred Rewards" icon="hourglass-clock" href="/rewards/deferred-rewards">
  Accumulate rewards and save on transaction fees.
</Card>


# Deliverables
Source: https://docs.flipsuite.xyz/storefronts/deliverables

Choose what buyers receive after purchasing a storefront item.

## <Icon icon="masks-theater" />  Discord Role

Grant a Discord role to the buyer or gift recipient.

<Frame>
  <img />
</Frame>

Role deliverables support:

* **Label**: Optional buyer-facing label for the deliverable.
* **Discord role**: The server role that should be granted.
* **Duration**: Optional temporary duration. Leave it empty for a permanent role grant.

<Warning>
  Flippy can only grant and revoke roles from users in your server that are **below its role** in your server's
  role hierarchy. You can access it by going to the `Roles` tab in your server settings.

  <Frame>
    <img />
  </Frame>

  In the example above, Flippy can only grant the "Verified - Tier 2" role to your community members. It won't have
  access to the "Verified - Tier 3" role because it's above the bot's role.
</Warning>

## <Icon icon="sparkles" />  Points

Grant points to the buyer after a successful purchase.

<Frame>
  <img />
</Frame>

Points deliverables support:

* **Label**: Optional buyer-facing label.
* **Point system**: The point system the buyer should receive.
* **Amount**: How many points should be granted.

## <Icon icon="box-isometric" />  Custom

Create a manual fulfillment for anything that Flipsuite cannot distribute automatically.

<Frame>
  <img />
</Frame>

Custom deliverables support:

* **Title**: Short label shown to buyers.
* **Description**: Brief explanation of the custom item.
* **Claim instructions**: What the buyer should do after purchase.

<Note>
  Custom deliverables are great for merch claims, allowlist spots, codes, off-platform rewards, or anything your team fulfills manually.
</Note>

<Warning>
  Custom items are not delivered automatically. After purchase, the order stays in the storefront orders view until an admin marks it as delivered.
</Warning>

## Bundles

Add more than one deliverable to a single storefront item to grant several items at once.

<Frame>
  <img />
</Frame>


# Introduction
Source: https://docs.flipsuite.xyz/storefronts/introduction

Create branded storefronts where your community can buy roles, points, and more.

Storefronts let you build one or more branded shops for your community and sell items directly through Discord.
Each storefront can contain multiple items, and each item can grant one or more deliverables after a successful purchase.

## Core concepts

* **Storefronts**: The top-level catalogs your community can browse in Discord.
* **Items**: The products members can purchase from a storefront.
* **Price**: The payment option attached to an item.
* **Deliverables**: What the buyer receives after a successful purchase.
* **Orders**: Purchase records created after a buyer checks out.
* **Fulfillments**: Delivery records for each deliverable in an order.

## What can you do with storefronts

* Create multiple storefronts for different campaigns, seasons, or reward catalogs.
* Offer items in exchange for tokens, [points](/points/introduction), or both.
* Bundle multiple deliverables (roles, points, custom) into a single item.
* Grant timed or permanent Discord roles automatically after payment succeeds.
* Track manual, custom items in a dedicated orders view.
* Receive crypto payments directly into configured storefront wallets.

## How storefronts work

1. Create a storefront in your community dashboard.
2. Add items with a price, stock rules, and one or more deliverables.
3. Open the storefront and optionally assign a Discord channel to share it in automatically.
4. Members purchase items in Discord (or via dashboard soon).
5. Flipsuite records the order and starts fulfillment immediately after payment succeeds.
6. Automatic deliverables are granted right away, while custom ones stay in the orders view until your team marks them as delivered.

## What's next?

<Card title="Set up your first storefront" icon="wrench" href="/storefronts/setup">
  Create a storefront, add items, and open it for your community.
</Card>


# Notifications
Source: https://docs.flipsuite.xyz/storefronts/notifications

Send storefront purchase notifications to Discord.

## Set up a notification channel

Open **Storefronts Settings** in your community dashboard and switch to the **Notifications** tab.

<Frame>
  <img />
</Frame>

There you can configure two Discord purchase notification channels:

* **Public channel** - a channel where anonymized purchase notifications will be posted.
* **Private channel** - a channel where detailed storefront purchase logs will be posted.

## What gets posted

A private storefront purchase notification includes:

* Storefront and item details
* Buyer and recipient details
* The price and deliverables attached to the order
* Whether any deliverable still needs manual action

<Frame>
  <img />
</Frame>

A public storefront purchase notification **does not** include buyer and recipient details.


# Orders
Source: https://docs.flipsuite.xyz/storefronts/orders

Track storefront purchases and manage custom item fulfillment.

## Where to find orders

Navigate to the **Storefronts** area in your community dashboard and click the **Orders** tab.

## Payment status vs delivery status

Storefront orders and storefront fulfillments track different parts of the purchase lifecycle:

* **Payment status** shows whether checkout succeeded.
* **Delivery status** shows whether a specific deliverable has been completed.

Typical behavior after a successful payment:

* Role and points deliverables move to `FULFILLED` immediately.
* Custom deliverables move to `PROCESSING`, and an admin needs to finish the delivery.
* Failed delivery attempts can appear as `FAILED` with a reason in the order details.

## Manage custom item orders

Open an order row to inspect the fulfillment details.

<Frame>
  <img />
</Frame>

For custom deliverables, the details dialog lets you:

* Review the buyer, recipient, price, and delivery status
* Inspect any checkout data collected through item requirements
* Mark the deliverable as delivered

When marking a custom deliverable as delivered, you can include a **delivery message**.
That message is sent to the recipient on Discord as confirmation.


# Prices
Source: https://docs.flipsuite.xyz/storefronts/prices

Choose how buyers pay for storefront items.

## <Icon icon="sparkles" />  Points Price

Charge buyers with one of your point systems.

<Frame>
  <img />
</Frame>

Points prices require:

* **Point system**: The point system buyers will spend from.
* **Amount**: How many points the buyer must pay.

Points pricing rules:

* The point system must be available to your community.
* Only transferable point systems can be used as storefront prices.
* Buyers must have enough points in their balance for checkout to succeed.
* Successful purchases are recorded as a storefront spend in the point system activity.

## <Icon icon="coins" />  Token Price

Charge buyers with one of the tokens on a supported chain.

<Frame>
  <img />
</Frame>

Token prices include:

* **Token**: A token buyers will pay with.
* **Amount**: Payment amount, either as an absolute amount or USD.

Token pricing rules:

* Buyers must have enough of the selected token in their Flipwallet.
* You can configure tokens to be burned on purchase.
* You can configure a [storefront wallet](/storefronts/wallets) to receive crypto payments to.

<Note>
  If no storefront wallet is configured for the token's chain, the payment falls back to the community owner's Flipwallet.
</Note>


# Setup
Source: https://docs.flipsuite.xyz/storefronts/setup

Create a storefront, add items, and open it for purchases.

> Setting up a storefront starts with creating the storefront itself, then adding items with prices and deliverables.
> This guide walks through the full dashboard flow.

## Step 1 - Create a storefront

Open the **Storefronts** area in your community dashboard and click **Create new storefront**.

<Frame>
  <img />
</Frame>

When creating a storefront, you can configure:

* **Name**: Public storefront title shown on storefront cards.
* **Description**: Short summary of what this storefront is for.
* **Banner**: Optional banner image to give your storefront a unique look.
* **Discord channel**: Channel where the storefront should be shared after it's opened.

## Step 2 - Add storefront items

After creating the storefront, you will be taken to its **Items** tab. Click **Add new item** to create your first item.

<Frame>
  <img />
</Frame>

Each item includes:

* **Name**: Public item name shown to buyers.
* **Short description**: Compact summary shown on item cards.
* **Full description**: Longer markdown description with extra details or claim instructions.
* **Image**: Optional item image.
* **Stock**: Remaining quantity available for purchase. Leave it empty for unlimited stock.
* **Limit per user**: Optional purchase cap per person.
* **Allow gifting**: Whether buyers can send the item to another community member.
* **Deliverables**: Everything the buyer should receive after a successful payment.
* **Requirements**: Optional eligibility checks or buyer inputs collected during checkout.
* **Price**: The payment option for the item.

## Step 3 - Open the storefront

When your catalog is ready, open the storefront's **Settings** tab and update its **Visibility**:

* **Yes**: Buyers can purchase from it.
* **No**: The storefront stays visible in the dashboard, but purchases are blocked.

<Frame>
  <img />
</Frame>

If you set a **Discord channel**, Flipsuite will share the storefront there when it becomes open.
If you later change the channel or close the storefront, the old storefront message is cleaned up automatically.

## Step 4 - What's next?

Once the storefront is open, focus on the building blocks around it:

<CardGroup>
  <Card title="Prices" icon="coins" href="/storefronts/prices">
    Learn how points and token pricing work in storefront items.
  </Card>

  <Card title="Deliverables" icon="gift" href="/storefronts/deliverables">
    Choose what buyers receive after payment succeeds.
  </Card>

  <Card title="Wallets" icon="wallet" href="/storefronts/wallets">
    Configure where token payments should be sent.
  </Card>

  <Card title="Orders" icon="receipt" href="/storefronts/orders">
    Track purchases and manage custom item fulfillment.
  </Card>
</CardGroup>


# Wallets
Source: https://docs.flipsuite.xyz/storefronts/wallets

Configure the wallets used to receive storefront token payments.

## Add a storefront wallet

Open **Storefronts Settings** and go to the **Wallets** tab.

<Frame>
  <img />
</Frame>

From there you can:

1. Click **Add new wallet**.
2. Choose the blockchain.
3. Enter the wallet address for that chain.
4. Optionally add a label.
5. Save the wallet.

You can only add one storefront wallet per chain.

## How token payments are routed

When a buyer pays with a token:

* Flipsuite looks for a storefront wallet on that token's chain.
* If one exists, the payment is routed there.
* If none exists, the payment falls back to the community owner's Flipwallet on that chain.
* If the price uses the **burn tokens** option, the tokens are burned instead.

<Note>
  Configure storefront wallets before publishing token-priced items. That keeps storefront revenue flowing into the intended treasury from the start.
</Note>