> ## 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.

# Token Issuers

Token issuers of crypto-native assets (e.g. SYRUP, MORPHO, etc) need deep, persistent onchain liquidity from the moment their token goes live. The default approaches break down at scale: full-range liquidity leaves most capital sitting where no trade ever happens, manually managed concentrated positions are operationally unsustainable for teams, and incentive-driven LPs rotate out the moment emissions stop. The result is thin depth, fee revenue leaking to external LPs, and price impact that erodes trader experience and volume.

Arrakis Pro is the active liquidity layer for token issuers. Self-custodial vaults run automated strategies that adapt as the token matures, and the team keeps custody throughout. Concentrated active management has historically delivered approximately 4x deeper liquidity per dollar deployed than full-range positions and 3x higher fee capture. Across live deployments, Arrakis manages over 100 token issuers and has facilitated more than \$5B in onchain volume.

## How protocol-owned liquidity (POL) is typically deployed

Token issuers typically deploy protocol-owned liquidity in one of three ways, with different tradeoffs across capital efficiency, operational overhead, and ongoing performance.

|                          | Full-range POL    | Manual concentrated LP | Arrakis Pro                 |
| ------------------------ | ----------------- | ---------------------- | --------------------------- |
| **Capital efficiency**   | Most capital idle | Drifts out of range    | Always at the trading price |
| **Operational overhead** | None              | Constant, hands-on     | None for the team           |
| **Fee capture**          | Low               | Variable               | Maximized                   |
| **Rebalancing**          | None              | Manual                 | Automated                   |
| **Lifecycle adaptation** | None              | Manual                 | Automatic                   |

## Strategies

Arrakis Pro runs multiple strategies, each built for a specific use case. They transition automatically as the token matures.

<Columns cols={1}>
  <Card title="Bootstrap Strategy" icon="rocket" href="/bootstrap">
    For TGE and launches with skewed inventory (typically up to 95% project token). Accumulates ETH or USDC from buyer demand as the market trades through the position, avoiding the need for OTC deals or large quote-side treasury commitments. Auto-transitions to Flagship once the target inventory ratio is reached.
  </Card>

  <Card title="Flagship Strategy" icon="anchor" href="/flagship">
    For ongoing post-launch active management. Concentrates the position around spot in calm markets and widens the range as volatility rises. Dynamic fees adjust to market conditions. The default strategy after Bootstrap completes.
  </Card>

  <Card title="Treasury Diversification Strategy" icon="coins" href="/treasury-diversification">
    For gradual conversion of project token into ETH or stablecoins over time. Passive concentrated liquidity around spot converts the project token as the market trades through, avoiding the price impact of market-selling or OTC discounts. Useful for treasury management once the token has matured.
  </Card>
</Columns>

If your token accrues value through yield (liquid staked tokens, yield-bearing stablecoins, tokenized treasuries), see [**Yield-Bearing Assets**](/yield-bearing-assets-and-rwas).

## Features

Hooks are Uniswap v4 features that add capability on top of any strategy. They are configured at vault deployment and run alongside the active strategy.

* [**Price Convergence**](/price-convergence): Holds the pool price to an external reference feed. Used primarily by assets that track an off-chain price, such as RWAs.
* [**Dynamic fees**](/dynamic-fees): Adjust the fee tier to volatility and trading momentum, capturing more on volatile flow and less on quiet flow.

## Launchpad integrations

For projects launching through a specific launchpad, Arrakis has dedicated migration or pre-deployment integrations.

* [**Uniswap CCA**](/uniswap-cca): Migrates the CCA-seeded Uniswap v4 full-range position into an actively managed Arrakis vault in a single atomic transaction. Teams can engage before the auction or migrate after it completes.
* [**Aerodrome Ignition**](/aerodrome-ignition): Pre-launch vault deployment on Base. Runs Bootstrap through Epoch 1 to accumulate quote-side reserves as buyers enter the pool, then auto-transitions to Flagship through Epoch 2 to maintain depth as mercenary LPs rotate out.
* [**Binance Alpha**](/binance-alpha): Active management of the official Alpha pool through the volatile launch window. Flagship-led, adapted to the program's launch requirements.

## Integration path

Pre-TGE teams typically engage 2-4 weeks ahead of TGE. Teams with existing pools can onboard at any time.

<Steps>
  <Step title="Discovery">
    Initial conversation with the Arrakis team to discuss the token, launch profile (pre-TGE) or current pool state (post-TGE), and the strategy, hook, and launchpad combination that fits. Where useful, Arrakis runs an onchain liquidity analysis of the existing setup and simulates the improvement.
  </Step>

  <Step title="Configuration">
    Vault parameters confirmed: pool, fee tier, tick range, dynamic fee config, strategy schedule, optional hooks. For launchpad launches, launchpad-specific setup (pool gauge creation, voter contract whitelisting, and so on) runs in parallel.
  </Step>

  <Step title="Deployment">
    Arrakis deploys the vault on the chosen DEX and chain. Existing positions can be migrated atomically where the launchpad supports it (for example, the Uniswap CCA migration helper).
  </Step>

  <Step title="Self-custody">
    The vault NFT is owned by the team's multisig or MPC wallet. The team owns the vault for its full lifecycle.
  </Step>

  <Step title="Active management begins">
    The chosen strategy begins automatically. The team can pause, reconfigure, or withdraw at any time. Strategy transitions (for example, Bootstrap → Flagship) run automatically based on configured triggers.
  </Step>
</Steps>

<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 TGE or existing token.
</Card>

## FAQ

<AccordionGroup>
  <Accordion title="How much capital should we deploy?">
    Sizing depends on the token, the trading depth target, expected volume, and the chosen strategy. Pre-launch coordination includes a depth analysis to determine recommended deployment for the specific launch. Because Arrakis concentrates liquidity around the trading price, the same trading depth can be achieved with roughly 25% of the capital that a full-range position would require.
  </Accordion>

  <Accordion title="We already have a Uniswap or Aerodrome position deployed manually. Can we migrate?">
    Yes. For Uniswap CCA positions, migration is atomic through the dedicated helper contract (see [Uniswap CCA](/uniswap-cca)). For other manually managed v3 / v4 / Slipstream positions, the typical path is to withdraw the existing position and deposit into a freshly deployed Arrakis vault. Coordination with the Arrakis team determines the path based on the current setup, including options for zero-downtime migration where significant prefunding is possible.
  </Accordion>

  <Accordion title="Can we change strategy as our token matures?">
    Yes. Strategy parameters and the active strategy itself are reconfigurable at any time. Common transitions include Bootstrap → Flagship after initial inventory rebalances, or Flagship → Treasury Diversification when the team decides to convert project token to quote. Reconfiguration runs as an authenticated call from the vault NFT holder.
  </Accordion>

  <Accordion title="Who controls the funds throughout?">
    The team. Arrakis vaults are self-custodial. The team holds the vault NFT, which represents ownership of the underlying position. Arrakis runs the active management strategy, and changes to the vault's core parameters are subject to a two-day timelock, so the team always has time to review or exit. The team can pause, reconfigure, or withdraw at any time.
  </Accordion>

  <Accordion title="What if we are not sure which strategy is right for us?">
    The discovery step covers this. For most launches the strategy is determined by the launch profile: a TGE with skewed inventory points to Bootstrap, an existing balanced pool to Flagship, and a yield-accruing token to the Yield-Bearing Asset Strategy. For launches through a specific launchpad, the integration page covers the recommended setup (see [Uniswap CCA](/uniswap-cca), [Aerodrome Ignition](/aerodrome-ignition)).
  </Accordion>

  <Accordion title="Can we run more than one strategy at once?">
    Yes. Teams often run several vaults in parallel, each with its own strategy, for example a Flagship vault for ongoing market making alongside a Treasury Diversification vault converting part of the treasury. Each vault is independent and self-custodial.
  </Accordion>
</AccordionGroup>