Loading documentation
PERSONA DOCS / OVERVIEWMeet Persona
Launch a Solana coin around a KOL, with trading rewards and a token allocation tied to their selected wallet.
From a persona to a coin
- Choose a KOL. Browse the listed profiles and check the wallet that will receive rewards.
- Set up your coin. Add its identity, choose a trading fee preset, and optionally buy tokens at launch.
- Approve in Phantom. Approve coin creation, plus reward setup when a matching reusable setup is not already available. Trading starts on Meteora’s Dynamic Bonding Curve (DBC).
Two kinds of KOL rewards
Trading rewards are paid in SOL. The selected KOL receives a share of collected trading fees under the coin’s fixed fee configuration.
The token allocation reserves 50 million tokens, or 5% of the original supply. It can be released to the selected KOL wallet once graduation to Meteora DAMM v2 is complete.
The recipient is part of the launch.Choosing a profile assigns its selected wallet as the beneficiary. It does not establish that the KOL created, approved, or endorsed the coin.
Start with launch mechanics, see the fee breakdown, or learn how payouts work.
PERSONA DOCS / IDENTITYProfiles & payout wallets
A KOL profile provides context. Its selected Solana address determines where rewards go.
Check the recipient
Listed profiles connect a public identity with attributed Solana wallets. Review the linked evidence and address on the profile. When a KOL has multiple wallets, confirm the one selected for your launch.
Wallet labels can come from public account declarations or third-party attribution. They are not proof that a person currently controls a wallet, and a listing does not imply endorsement of any coin launched around them.
One selected wallet per coin
The launch fixes the KOL beneficiary for both trading rewards and the 5% token allocation. Rewards are not divided across every wallet on a profile. Updating a profile later does not redirect an existing coin’s on-chain recipients.
Reading a portfolio
Profile holdings summarize the attributed wallets shown. A balance is an observation at a particular time, not a trading recommendation or a record of all activity. See data sources and limitations.
PERSONA DOCS / ARCHITECTUREOn-chain architecture
The trading pool, fee vault, and allocation escrow have separate responsibilities.
1. Trading pool
Meteora’s Dynamic Bonding Curve handles initial trading against SOL. Its launch configuration sets the supply, fee preset, graduation curve, fee destination, and allocation destination. The launching wallet remains the recorded pool creator.
2. Fee-sharing vault
Coins for the same KOL and fee configuration can share a Meteora Dynamic Fee Sharing vault with fixed KOL and Persona shares. Pool fees must be collected into this vault before they can be distributed. Persona’s payout program routes each share to its fixed beneficiary as native SOL.
The vault weights are 3:1 for the 1.5% KOL preset and 125:21 for the 3% KOL preset. These split the revenue remaining after Meteora’s protocol share. Integer arithmetic can leave tiny rounding remainders.
3. Allocation escrow
A program-derived reserve for the selected KOL receives each coin’s reserved tokens after migration. The allocation program verifies the pool, mint, recipient, and graduation state before releasing the fixed amount. A permanent receipt tied to the coin’s original DBC pool prevents a second payout of its allocation.
After graduation
Trading moves to DAMM v2. The fee-sharing vault holds fee rights to the permanently locked launch liquidity position. The token allocation follows its own release process and does not draw from the SOL fee vault.
See trading fees, SOL payouts, and the token allocation for the exact rules.
PERSONA DOCS / FEESTrading fees
Choose the KOL’s reward rate at launch. The total trading fee includes KOL, Persona, and Meteora shares.
Configured fees per swap| KOL | Persona | Meteora | Total |
|---|
| 1.5% | 0.5% | 0.5% | 2.5% |
| 3% | 0.504% | 0.876% | 4.38% |
How the split works
Meteora takes 20% of the total trading fee. The remaining 80% is split between the KOL and Persona through the fee vault. The higher preset rounds its total to 4.38%; the remainder after preserving the KOL’s 3% goes to Persona.
The percentages above describe shares of the swap fee basis, not percentages of the fee itself. For a 1 SOL fee basis at the 2.5% preset, the configured fee is 0.025 SOL: 0.015 to the KOL, 0.005 to Persona, and 0.005 to Meteora, before smallest-unit rounding.
Before and after graduation
The same fixed total trading fee is configured on DBC and DAMM v2. Dynamic fees are disabled, and the launcher receives no separate creator trading fee.
After graduation, KOL and Persona revenue comes from the vault’s liquidity position. If other liquidity is added, that position can earn a smaller proportion of pool fees. The table does not guarantee the KOL’s listed rate across all future pool volume.
Separate costs and rewards
Solana transaction fees, account rent, and Meteora’s separate 0.2% liquidity migration fee are outside this trading-fee table. The 5% token allocation is a reserve of tokens, not another trading fee.
PERSONA DOCS / SETTLEMENTRewards & payouts
SOL rewards move from the trading pool to the fee vault, then to the coin’s fixed recipients.
Understand the balances
- Generated: this coin’s accrued trading rewards for its KOL.
- Collected: the part already collected from this coin’s pool for payout.
- Paid out: finalized trading rewards received by the KOL and attributed to this coin.
Collection and wallet payment are separate steps. When coins share a vault, confirmed payments are attributed using each coin’s verified collections within the paid claim window. An unavailable value means the payment evidence has not been fully verified.
Automatic SOL payouts
The automatic payout policy checks hourly and targets balances of at least 0.02 SOL per recipient across coins sharing the same payout account. Smaller amounts accumulate. Eligible pool fees are collected first, then qualifying ready balances are sent to the fixed recipients.
Automatic KOL payouts use the currently listed eligible wallets. An unavailable eligibility check or a wallet no longer being listed can defer automatic payment; neither changes the on-chain beneficiary. Checks and confirmations can be delayed, so the hourly interval is not a guaranteed payment time.
Manual payouts
The coin creator, selected KOL, or Persona recipient can access manual fee actions in the interface. Collect pool fees into the vault, then send the available balance to recipients. These actions do not require the automatic 0.02 SOL threshold; the approving wallet pays transaction costs.
The payout program fixes the destination. Triggering a payout does not allow the caller to claim someone else’s share or substitute another recipient.
What Rewards totals include
Trading rewards paid counts confirmed SOL paid to KOL wallets across recorded Persona launches. Allocations released counts coins whose KOL token allocation has been released after graduation. Pending fees and reserved but unreleased tokens are excluded.
The token reserve has a separate release action; it is not paid out by the SOL fee process.
PERSONA DOCS / ALLOCATIONThe 5% KOL allocation
Exactly 50 million tokens are reserved for the selected KOL from the original one-billion-token supply.
Locked until graduation completes
The reserve becomes releasable only after the DAMM v2 pool has been created and migration is complete. Reaching the curve’s target alone does not unlock it.
Release to the selected wallet
Open the coin’s allocation status after graduation. Any connected wallet can approve the release transaction, but the tokens go only to the KOL address fixed at launch. The wallet triggering it pays network fees and any required token-account rent.
The transaction moves the reserved tokens from the curve into escrow if needed, then transfers exactly 50,000,000 tokens to the KOL. It cannot release a partial allocation if the reserve is underfunded.
One payout
An on-chain receipt prevents repeated claims. Tokens sent to the escrow beyond the fixed allocation remain locked; they do not increase the KOL payout.
This allocation is independent of trading fees and any tokens purchased by the launcher. It represents 5% of the original supply; later token burns do not change the fixed release amount.
PERSONA DOCS / DATAData & methodology
On-chain records establish launch terms. Prices, profile labels, and cached views provide context.
Profiles and portfolio balances
Profiles show public wallet attribution with linked sources and observation dates. Solana account data provides SOL, SPL, and Token-2022 balances; market quotes provide estimated USD values. Wrapped SOL is included. Duplicate wallet addresses are counted once.
Saved holdings can appear before a refresh completes. Visible wallet balances and prices use a shared cache with a ten-minute refresh interval. Known positions worth less than $1 are hidden. Unpriced assets and incomplete reads can limit the displayed portfolio value.
Coin directory and prices
The directory contains recorded Persona launches whose pool configuration and fee routing are verified on-chain. This verification establishes launch mechanics, not endorsement, token value, or investment safety.
Current SOL prices come from pool state. USD displays use a SOL/USD quote. Market cap is price multiplied by supply; it is not liquidity, cash backing, or an amount guaranteed on sale. Shared coin snapshots can be cached for up to ten minutes between refreshes.
Charts and holders
Charts sample recent successful on-chain swaps. They are not a complete trade history or OHLC candles. Historical chart points are converted using the current available SOL/USD rate, not a separate historical exchange rate for each trade.
Holder views aggregate owners from the 20 largest token accounts. One owner can hold several accounts, and pool vaults are labeled separately. This is not a complete count of all holders.
Missing or delayed data
A failed read can leave a dated saved value or an unavailable state. A missing icon or quote does not establish that a token has no balance or value. Confirm time-sensitive amounts on-chain, and distinguish pending rewards from confirmed payouts.
PERSONA DOCS / SECURITYSecurity & verification
Know what the transaction checks establish, and what they cannot establish.
What Persona checks
Launch preparation checks the selected network, fee configuration, recipient addresses, and required on-chain programs. Transactions are simulated before approval. Before broadcasting a wallet-signed transaction, Persona checks that its message matches the prepared transaction.
Coin verification checks the pool and fee-routing configuration against the launch terms. Allocation release checks completed migration and a single fixed payout. These checks do not establish that a coin or KOL is trustworthy.
What you should verify
- The full token mint and recipient addresses, not just a name, ticker, or profile picture.
- The selected trading fee and any initial buy shown in your review.
- The transaction outcome shown by Phantom and its confirmation on Solana.
Wallet warnings require investigation; do not treat a successful preview or a recognizable profile as proof of safety. No independent security audit is claimed here.
Fixed terms, separate risks
Locked launch liquidity does not prevent price changes or losses. Public attribution does not prove identity or endorsement. External wallet providers, Solana RPC services, and market data can be delayed or unavailable.
PERSONA DOCS / TOKEN$PERSONA tokenomics
Supply, allocation, and release details for Persona’s own token.
THE PERSONA TOKEN
$PERSONA
Details at launchOfficial tokenomics and the mint address will be published here when $PERSONA launches.
PERSONA DOCS / OVERVIEWMeet Persona
Launch a Solana coin around a KOL, with trading rewards and a token allocation tied to their selected wallet.
From a persona to a coin
- Choose a KOL. Browse the listed profiles and check the wallet that will receive rewards.
- Set up your coin. Add its identity, choose a trading fee preset, and optionally buy tokens at launch.
- Approve in Phantom. Approve coin creation, plus reward setup when a matching reusable setup is not already available. Trading starts on Meteora’s Dynamic Bonding Curve (DBC).
Two kinds of KOL rewards
Trading rewards are paid in SOL. The selected KOL receives a share of collected trading fees under the coin’s fixed fee configuration.
The token allocation reserves 50 million tokens, or 5% of the original supply. It can be released to the selected KOL wallet once graduation to Meteora DAMM v2 is complete.
The recipient is part of the launch.Choosing a profile assigns its selected wallet as the beneficiary. It does not establish that the KOL created, approved, or endorsed the coin.
Start with launch mechanics, see the fee breakdown, or learn how payouts work.
PERSONA DOCS / LAUNCHESLaunching a coin
A fixed-supply token starts on a bonding curve and graduates into a SOL liquidity pool.
Launch parameters
| Network | Solana mainnet |
|---|
| Token standard | Token-2022 · 6 decimals |
|---|
| Original supply | 1,000,000,000 tokens |
|---|
| KOL reserve | 50,000,000 tokens · 5% of original supply |
|---|
| Initial market cap | Approximately 32.0081 SOL |
|---|
| Graduation market cap | Approximately 410.7799 SOL |
|---|
| Trading venue | Meteora DBC → DAMM v2 |
|---|
Market cap is the curve price multiplied by token supply. It is not the amount of SOL needed to launch or the amount deposited into liquidity. USD values change with the SOL price.
Wallet approvals and reusable setup
If a compatible reward vault and curve configuration already exist for the selected KOL and fee preset, only the coin-creation approval is needed. Otherwise, approve setup first, then coin creation.
- Prepare missing setup. Create the reward vault and reusable curve configuration, or only the missing configuration when the vault already exists.
- Create the coin. Create its mint, token metadata, trading pool and pool token accounts, together with the optional initial buy.
Review the estimated total funding before approving setup. Your wallet pays account funding, program charges and transaction fees. Setup alone does not create a tradable coin; its costs remain paid if you stop before coin creation. Completed setup can be reused when you resume.
Optional initial buy
An initial buy purchases tokens for the launching wallet; it is separate from the KOL’s 5% reserve. The SOL amount includes the trading fee, while network fees and account rent are additional. The launch quote uses a 1% minimum-output tolerance.
Token creation and the initial buy execute in the same transaction. If that buy fails, token creation rolls back too; a failed transaction can still incur a network fee.
Graduation and liquidity
The curve graduates when its required quote reserve is reached. Migration then creates the DAMM v2 pool. A full progress bar alone does not mean this migration has completed.
The initial migrated liquidity is permanently locked, with its fee rights held by the sharing vault. Launches use immutable token authority settings and no separate creator trading fee. See the on-chain structure and allocation release.
PERSONA DOCS / WALLETWallet & transactions
Connecting shares your public address. Each transaction still needs your approval.
Connect before preparing a launch
Use the Phantom browser extension or open Persona in Phantom’s mobile browser. Some mobile browsers do not expose a wallet connection. Check this before entering your coin details; your wallet also needs SOL for transaction fees and account rent.
Review each approval
Check the connected account, coin details, KOL recipient, fee preset, and any initial buy. Persona prepares and simulates transactions before requesting a signature. A simulation is a preview, not a guarantee that a later transaction will succeed.
Changing your wallet or launch choices invalidates the prepared review. Connecting to Persona does not grant permission to move funds or approve future transactions. Persona never needs your recovery phrase or wallet private key.
If approval or confirmation is interrupted
Rejecting an unsigned request sends no transaction. After signing, an uncertain response does not necessarily mean failure: the transaction may already have reached Solana.
Use the saved launch status to check confirmation or retry the original signed transaction. Keep the same browser and site address to resume the second launch step. Clearing site storage, switching browsers, or changing domains can make that saved setup unavailable.
Check before starting again.If a transaction is pending, check its signature and status first. A confirmed setup should be continued, not recreated.
POWERED BY METEORA