← Documentation

NEW COLLECTIONS · DEVNET

SOBJECT on Meteora

Launch on Meteora DBC, graduate into Meteora DAMM v2, and keep artwork and ownership verification on Solana.

One collection, one standard token

New launches use Token-2022 with 6 decimals and a fixed supply of 1,000 tokens. Meteora initializes MetadataPointer and TokenMetadata with the name, ticker and a wallet-readable URI. Mint and freeze authorities are revoked. Reward collections use the SOBJECT transfer hook during DBC trading. Meteora removes it at curve completion. Token-backed collections have no active transfer hook. Neither route adds a token transfer fee or a per-mint base-token TokenBadge approval step.

The default logo is rendered from the collection artwork. Wallets may cache metadata or apply their own indexing rules; a valid URI does not guarantee immediate display everywhere.

Trading and migration

Trading starts in Meteora DBC. The devnet configuration graduates at 1 test SOL of curve reserves. The planned mainnet configuration uses 30 SOL; mainnet launches remain disabled. This is a reserve threshold, not cumulative volume or market capitalization. Fees do not count toward the reserve and sales can reduce it before graduation.

At the threshold, curve trading stops. Anyone can submit the separate migration transaction. It creates a real DAMM v2 pool using the same mint; the caller pays network fees and account rent. The market page displays the completed pool after chain confirmation and switches to DAMM v2 trading.

The configuration targets 20% of supply at migration. Initial liquidity is permanently locked under the SOBJECT fee splitter. New profiles keep the same fixed total on DBC and DAMM v2; dynamic fees are disabled. Main token: 2.5% total, nominally 2% treasury and 0.5% Meteora. Standard launch: 1% total, nominally 0.8% treasury and 0.2% Meteora. Optional creator mode: 1-5% total, with 0.5 percentage points for the treasury, 20% of the total fee for Meteora, and the remainder for the original creator. At 5% this is 0.5% treasury, 1% Meteora and 3.5% creator. Additional LPs can dilute revenue from the initial position after migration. Claims split collected fees into the original recipients' WSOL accounts. A separate Meteora liquidity migration deduction applies; the configured partner migration fee is zero.

This route has no automatic main-token buyback. Scanners and aggregators control their own indexing and routing; Meteora compatibility does not guarantee a listing.

Two collection models

Graduation reward collections keep tokens liquid. Supported token transfers update pending characters until the final curve purchase. Claiming after the cutoff creates permanent characters with no token backing or redemption right. Token-backed collections separately lock one whole token per active object and permit retirement to release it.

Graduation reward rules · Token-backed object rules

Collectible identity after bonding

Meteora’s transfer-hook DBC route runs the hook during bonding only. The final curve purchase updates allocations before DBC clears both the hook program ID and its authority. The closed allocation can then be claimed. DAMM v2 receives a token without an active hook.

SOBJECT core maintains the permanent character records independently. Selling liquid tokens after the cutoff does not remove reward characters. Use the P2P Market or SOBJECT transfer action to move a specific character.

For external trading, use a transfer-hook-aware route and the required extra accounts before completion. The current reward program accepts personal canonical associated token accounts. Program-owned custody and arbitrary token accounts are unsupported. Meteora support alone does not establish bot compatibility.

Meteora’s transfer-hook lifecycle ↗

Costs and trade history

The launch screen estimates artwork, collection and vault storage plus network fees. Object batches and individual ownership records have separate rent, shown before approval. Migration rent is a separate later cost.

Meteora charts show confirmed token swaps. P2P object sales have their own history and volume. Ordinary token transfers move liquid balances; use the SOBJECT transfer action to send a particular character.

Integration

SOBJECT core: 28VVRHM6NP7eqbRxjMipvfWcpGVqzJBCpMaZQHCDMinK
Meteora DBC: dbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqN
Meteora DAMM v2: cpamdpZCGKUy5JxQXB4dcpGPiikHawvSWAd6mEn1sGG

Use Meteora’s SDK to quote and trade. The SOBJECT collection PDA uses seeds ["collection", mint]. Collection status 5 identifies token-backed collections and status 6 identifies graduation rewards; read Meteora pool state for migration status. Token swaps use Meteora, while object ownership is managed by SOBJECT core.

Official Meteora SDK documentation ↗

Meteora markets & launch | SOBJECT