> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arrakis.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Binance Alpha

Binance Alpha is an exchange-affiliated distribution program. Projects launching on Binance Alpha gain exposure to Binance's user base, and the program requires the project to seed and maintain a qualifying onchain liquidity pool. The program specifies the setup: a single official pool on a venue Binance designates, on a low fee tier, with hooks not permitted in that pool.

That required position is capital-intensive and has to survive a volatile launch window. Sniping at open and airdrop recipients selling once rewards unlock drive intense one-directional flow that skews a static position and widens price impact. Arrakis Pro deploys and actively manages the required position so the same capital holds depth at the trading price and absorbs the sell pressure, rather than sitting full-range while that flow extracts value from it. The team keeps self-custody through the vault NFT.

## What Binance Alpha requires

Binance Alpha handles distribution: frontend exposure, access to Binance's user base, and for some projects a path toward spot listing. The liquidity requirement is the part Arrakis operates against.

| Program sets | Detail                                                       |
| ------------ | ------------------------------------------------------------ |
| Pool         | A single official pool the project seeds and maintains       |
| Venue        | A DEX and chain Binance designates, generally not negotiable |
| Fee tier     | A low fee tier set by the program                            |
| Hooks        | Not permitted in the official pool                           |

These are program mechanics, not Arrakis constraints. They shape what Arrakis can and cannot do inside the Alpha pool. For the program's full terms, speak with the Binance team.

## Why liquidity management matters here

The launch window is the hard part. Three dynamics shape whether the required position survives it, and active management addresses each.

<Columns cols={1}>
  <Card title="A static position spreads the required capital where trades do not happen.">
    Posting the required capital as a full-range position is the simplest way to meet the requirement, but the majority of it sits far from the trading price and contributes nothing to depth during the window that matters most. With Arrakis, the same capital is deployed as an actively managed concentrated position. Concentrated management has historically delivered approximately 4x greater depth per dollar than a full-range position, so the required capital does more work precisely when sniping and airdrop flow hit hardest.
  </Card>

  <Card title="The launch window drives one-directional flow that skews a passive position.">
    Snipers buy aggressively at open, and airdrop recipients sell into the pool once rewards unlock. A static position absorbs that flow blindly: inventory skews hard toward the token as recipients dump, price impact widens, and teams without active management end up making manual adjustments by hand in the first minutes of trading. With Arrakis, the [**Flagship Strategy**](/flagship) rebalances continuously, keeps liquidity concentrated around the moving trading price, and manages the inventory skew as sell pressure arrives, with no manual intervention from the team.
  </Card>

  <Card title="The low fee tier earns almost nothing back.">
    At the low fee tier the program sets, the Alpha pool generates little fee income to offset the impermanent loss the volatile flow produces. Fee income is not where this pool earns its keep, so capital efficiency and inventory management are the levers that matter.
  </Card>
</Columns>

## Launch flow with Arrakis

```mermaid theme={null}
flowchart LR
    Pre([Pre-launch:<br/>Vault configured to meet<br/>Binance requirements])
    --> Open[Launch window<br/>Flagship defends depth<br/>through sniping]
    Open --> Air[Airdrop unlock<br/>Manage inventory skew<br/>as recipients sell]
    Air --> Steady([Steady state:<br/>Ongoing active management])
```

<Steps>
  <Step title="Pre-launch configuration">
    The team and Arrakis confirm the vault meets Binance's requirements: the required position, the specified fee tier, the designated DEX and chain, and a Flagship Strategy configuration tuned for the launch window. Because Binance reviews the setup, parameters are confirmed against the program's requirements ahead of the TGE date.
  </Step>

  <Step title="Vault deployment">
    The vault is deployed on the specified venue and seeds the required position.
  </Step>

  <Step title="Launch window">
    Trading opens. Flagship keeps liquidity concentrated around the trading price and rebalances continuously as snipers buy in, holding depth where execution happens rather than spreading it thin.
  </Step>

  <Step title="Airdrop unlock">
    As airdrop recipients sell into the pool, the strategy manages the resulting inventory skew and widens or repositions as conditions warrant, absorbing sell pressure instead of amplifying it.
  </Step>

  <Step title="Steady state">
    Active management continues. The team can pause, reconfigure, or withdraw at any time.
  </Step>
</Steps>

## Arrakis benefits

Within Binance's requirements, the choice is between posting a static position and actively managing it. The required capital is the same either way.

|                              | Static full-range position                | Arrakis-managed position              |
| ---------------------------- | ----------------------------------------- | ------------------------------------- |
| **Capital at trading price** | Small fraction                            | Majority, concentrated around spot    |
| **Sniping window**           | Absorbs flow blindly, price impact widens | Rebalances continuously to hold depth |
| **Airdrop sell pressure**    | Inventory skews into the token unmanaged  | Inventory skew actively managed       |
| **First minutes of trading** | Manual adjustments by the team            | Automated, no team intervention       |
| **Operations**               | Self-managed                              | Managed by Arrakis                    |
| **Custody**                  | Self-custodial (LP NFT)                   | Self-custodial (Arrakis vault NFT)    |

## Supported deployments

Arrakis operates the Binance Alpha pool on the venue and chain Binance sets for the launch. Arrakis Pro supports the major DEXs chosen as the liquidity venue. The venue and chain are part of the program terms and generally not negotiable, so the Arrakis setup is built to fit them.

<Card title="Integrate Arrakis" icon="laptop" href="https://qxqhpatmzz7.typeform.com/to/IZdNgmmM?typeform-source=docs.arrakis.finance">
  Talk to the Arrakis team about your Binance Alpha launch.
</Card>

## FAQ

<AccordionGroup>
  <Accordion title="What happens to the position when airdrop recipients sell?">
    Airdrop unlocks drive sell pressure into the pool, which skews inventory toward the project token. The Flagship Strategy manages that skew, rebalancing and repositioning as the flow arrives rather than letting the position absorb it passively. The position cannot eliminate sell pressure, but active management limits the price impact and inventory damage relative to a static position.
  </Accordion>

  <Accordion title="After the Binance Alpha commitment period, can we move to a standard Arrakis setup?">
    Yes. Once the program's liquidity commitment period ends, the position can be reconfigured or migrated to a standard Arrakis vault on Uniswap v4 or another venue with a higher fee tier, where the full strategy and hook set applies (dynamic fees, [**Price Convergence**](/price-convergence), [**Treasury Diversification**](/treasury-diversification)). Reconfiguration runs as an authenticated call from the vault NFT holder.
  </Accordion>
</AccordionGroup>