THE SOBJECT FIELD GUIDE
A token you trade. A character you keep.
SOBJECT connects Meteora token markets with permanent, individually owned characters and artwork stored on Solana. Token trading and character trading are separate markets.
Devnet uses test SOL. Mainnet launches remain disabled.
An identity with its own owner.
A permanent SOBJECT has a collection mint, serial number, owner and deterministic DNA. The approved pixel pack lives on Solana. Moving a character changes its owner, not its image.
These are SOBJECT program records, not separately minted standard NFTs. A wallet may display the liquid token without displaying its characters. Use My Objects to view and manage them.
One collection. Two ways to participate.
Liquid tokens
Buy and sell on Meteora with protected quotes and a fixed supply.
Specific characters
Choose an exact serial on the P2P Market. Ownership and payment settle together.
Public onchain records
Read ownership and reproduce artwork from the program and its stored data.
Graduation rewards: pending, fixed, claimed.
Before a reward collection completes its curve, each whole token in a supported personal associated token account contributes one pending character. A balance of 200.4 tokens contributes 200. Compatible buys, sells and transfers update the allocation through the transfer hook. Tokens stay liquid.
The final curve purchase updates rewards, then Meteora removes the hook and its authority. This fixes the allocation before the separate DAMM v2 migration transaction. Holders can claim their assigned characters. Selling tokens afterward does not remove them.
Pending characters cannot be listed or claimed. Claimed rewards have no token collateral or redemption right. New purchases after the cutoff do not issue additional rewards.
Read the exact reward rules, supported account types and burn limitation →
Read the collection model.
Reward collections reserve a fixed set of serial slots. Slots released during bonding can be reassigned. A pending serial and its provenance frame are not a promise that its holder bought first.
Token-backed collections use a different model: creating an object locks one token, retirement releases it, and creation order determines Genesis, OG and later generations. Their existing collateral rights remain intact. The token and object pages identify the model; reward characters cannot be unwrapped.
Pixels on Solana. No IPFS dependency.
The studio uses your reference image to prepare a character set. You approve the exact 384 × 384 pixel pack before launch. The compressed artwork is uploaded, validated, sealed and bound to the mint.
The collection can be rendered from onchain bytes without SOBJECT’s image server. Content-addressed artwork and renderer assets retain their committed bytes. The program remains upgradeable; this is not a claim that its upgrade authority has been removed.
An image that survives a transfer.
Permanent DNA depends on the artwork account, mint and serial. It does not depend on the owner. Transfer and P2P sale preserve all pixels. Several serials may share a base character; a distinct ID does not guarantee an entirely unique-looking image.
Trade tokens. Buy characters P2P.
The Trade panel quotes token swaps through Meteora. The P2P Market lists exact characters at fixed SOL prices. P2P payment and ownership transfer are atomic, and stale listing revisions are rejected.
P2P charges a 0% platform fee. Network fees and any account rent still apply. P2P sales have separate history and volume from token swaps. Sending liquid tokens after graduation does not send a character.
A real Meteora market.
Launches use Token-2022, six decimals and a fixed 1,000-token supply. MetadataPointer and TokenMetadata contain the token name, ticker and URI. The configuration targets 20% of supply for migrated liquidity. Pool reserves do not receive character rewards.
Devnet completes the curve at 1 test SOL of reserves. Mainnet is planned at 30 SOL and remains disabled. The trigger is reserves, not cumulative trading volume. After completion, anyone can submit migration to DAMM v2 and pay its account rent.
The hook ends. Character ownership continues.
Reward allocation closes when Meteora clears the DBC transfer hook. SOBJECT core separately maintains the claimed objects. Their ownership, verification, transfer and P2P operations continue after migration.
Token-backed objects also continue through migration under their own vault rules. SOBJECT does not keep a custom DBC hook active in DAMM v2.
Costs shown before approval.
Launch review separates artwork rent, token and market accounts, reward storage when applicable, and network fees. Account rent is a Solana storage deposit, not a SOBJECT service fee. Reward ledger rent remains onchain. Artwork upload and pool activation can require several approvals; interrupted launches resume from their saved accounts.
Standard launches charge 1% per swap. Optional creator profiles range from 1% to 5%; the main token profile is 2.5%. These profiles use fixed fees on DBC and DAMM v2. Claims, individual object records and migration may have additional account rent.
Ownership and wallet control are separate checks.
The program proof includes mint, serial, owner, DNA, generation fields, status, renderer version and slot. Version 3 identifies graduation reward objects; version 2 identifies token-backed objects.
A token-gated service must validate a fresh program-owned proof and authenticate control of the matching wallet through a fresh signed challenge or a transaction signature. An address, screenshot or reproducible image alone does not prove control.