Documentation
Explorer ↗Open studio ↗
Product / Economics / Infrastructure

Inside Tide.

The launch, the markets and
where creator rewards go.

Explore the 80 / 20 model ↓
SOL launches.Defined reward destinations.
The product

A launch. A pair. A treasury.

COIN / SOLCOIN / TOKEN

Tide connects a Solana coin launch to a defined creator-reward policy. Choose the associated token, review prefilled coin details, set a dev buy and launch on Pump.fun with SOL.

The launch wallet pays for creation and receives the dev-buy tokens. Creator rewards go to the Tide treasury. They are not personal income for the launcher.

The associated token defines the 80% reward destination. Selecting BONK does not replace SOL in the Pump.fun market or create a second trading pool.

The agreed destination of rewards is 80% toward the selected second asset, retained in the treasury, and 20% toward buying and burning TIDE. No automatic liquidity deposit is part of this policy.

Using Tide

One launch from your wallet.

Your wallet signs launch + dev buy.

SOL on Pump.fun. Creation and dev buy share one transaction. The coin enters the Explorer after confirmation.

Connect a Solana wallet and review the network. Enter a name, ticker, artwork and optional description. Tide persists metadata before preparing the launch so the on-chain metadata URI can resolve after creation.

Review the transaction in your wallet. The backend prepares and simulates the transaction; your wallet signs it. A prepared transaction is not a created coin. Tide verifies the exact signed message and waits for confirmation before registering the launch in the Explorer.

A dev buy is included in the same launch transaction. A successful transaction creates the coin and purchases its tokens into the launch wallet. If either operation fails, the transaction does not complete.

Choose an associated token by name, ticker or contract. Tide pre-fills the coin name, ticker and description for that selection; you can edit them before launch. Verify the contract address, not just the ticker. Set a dev buy in SOL; zero launches without a purchase.

The Explorer shows confirmed registered Tide launches. Clicking a coin goes directly to its Pump.fun page. It is not an index of every coin on Solana.

Launch & selected token

Two markets. Different jobs.

The primary launch market is COIN / SOL on Pump.fun. SOL is the launch currency. Tide’s selected token is a reward-allocation association recorded in metadata; it is not a separately funded COIN / TOKEN pool.

The associated token is the 80% treasury-buyback target. Select BONK to target BONK. Select SOL to retain that budget as SOL, without a SOL-to-SOL swap.

Token search is discovery, not endorsement. The backend must check the mint, token program, applicable extensions and actual pool compatibility. A valid Solana mint alone does not establish that a pool can be created or that a swap route has sufficient liquidity.

The launch form asks for no second-asset deposit and creates no Raydium LP position. Launch and dev buy use SOL.

Selected-asset purchases are held on the treasury wallet. They are not deposits into the additional pool. Any future liquidity-deposit policy would require a separate product decision and transaction flow.

Reward allocation

Follow every SOL.

Allocation simulator · illustrative SOL budgetsFixed 80 / 20
SOL

Enter up to 9 decimal places. No wallet balance is connected.

80%8 SOLSelected asset → treasury

Acquired tokens stay on the wallet.
No automatic pool deposit.

20%2 SOLSOL → TIDE reserve

Held in SOL until TIDE exists.

Allocation illustration. Actual acquired amounts depend on the executed swap quote.

The allocation applies to collected Pump creator rewards, not trading volume, not every protocol fee and not LP trading fees. The creator’s share under the agreed Tide policy is zero.

All creator rewards arrive at 4ujBWuXN3i4yuC8FkK6h2sr6HYGtkLkCTZjc2dyVuvHh. The 80 / 20 split describes subsequent use of those funds; it is not a pair of native Pump payout recipients.

80% buys the selected second asset and stays in the treasury. 20% buys TIDE and burns the acquired TIDE. Before the TIDE launch, the 20% budget remains reserved in SOL; after launch it funds purchases and burns of the verified TIDE mint.

Budgets are measured in integer lamports. In this illustration the 80% budget rounds down to a lamport and the remainder goes to the 20% budget, preserving the exact total. Network fees, rent, executor costs and their treatment need an explicit policy before production spending.

The illustration below calculates allocations only. It does not read a wallet balance, fetch a swap quote, send transactions or estimate acquired token quantities.

Treasury & ownership

One address is not an executor.

The reward receiver, launcher wallet, LP owner, selected second-token mint and future TIDE mint are separate roles. A public reward address can receive funds; it does not give the website permission to spend them.

The treasury owner must sign swaps and burns, or authorize a constrained execution system with explicit limits. Wallet connection through Reown does not hand the server the user’s private key. Treasury private keys must never be placed in the browser, repository or documentation.

When multiple launches use the same creator receiver, native reward collection can aggregate funds across coins. Per-coin attribution determines how much belongs to each selected second asset. A durable ledger separates allocations before any treasury spending.

Treasury accounting should distinguish collected rewards, allocated SOL, reserved TIDE budget, completed swaps, acquired assets, execution costs and completed burns. A balance increase alone is not proof of which coin earned those funds.

Funds are held on a treasury wallet under its owner’s control. Treasury ownership is distinct from LP ownership. Execution authority must respect each coin’s allocation and preserve a traceable record.

Agreed reward recipient4ujBWuXN3i4yuC8FkK6h2sr6HYGtkLkCTZjc2dyVuvHh
TIDE & burning

A reserve today. A burn later.

Before TIDE exists, the 20% budget remains in SOL. There is no substitute token, placeholder mint or fictitious completed burn. The 80% budget remains assigned to its associated token.

After a TIDE mint is created and verified, the proposed flow is SOL budget → swap into TIDE → token-program burn. The acquired token amount depends on an actual route, price impact and slippage at execution time.

A genuine burn reduces mint supply through the token program. Sending tokens to a so-called dead wallet is not the same mechanism. Transaction evidence should link the swap, acquired amount, burn instruction and resulting supply change.

TIDE supply, initial allocation, launch timing, market, token program and authority configuration have not been approved. The buy-and-burn policy specifies use of rewards; it does not promise yield or guaranteed returns.

Business model

What Tide earns. What it spends.

Tide is intended for coin creators who want a launch interface with a defined treasury policy, and for communities that want creator-reward use to be traceable. The user journey should make the zero creator-reward share clear before signature.

The economic inflow is creator rewards produced by eligible trading activity. Trading volume can vary widely and creator-fee settings depend on the protocol. A launch without eligible activity may generate no creator rewards. Pool creation is not revenue by itself.

The agreed allocation consumes the entire reward budget: 80% selected-asset accumulation and 20% TIDE purchase and burn. There is no approved platform-profit percentage or additional service fee. Treasury asset accumulation is a balance-sheet position, not automatically distributable profit.

Operating costs include RPC access, metadata and artwork storage, indexing, server maintenance, transaction fees, audits and execution operations. How those costs are funded must be settled independently; silently taking costs out of either budget would change the agreed policy.

A useful reporting model measures confirmed launches, successful pool creation, attributable creator rewards, allocated budgets, verified swaps and burns, failure rates and operating costs. These are proposed measurement categories, not invented current statistics.

Retention depends on reliable launch completion, discoverable coins, understandable wallet approvals and transparent reward accounting. The project should not promise returns or use buyback language as a substitute for execution evidence.

System architecture

Prepare. Sign. Verify. Record.

The frontend handles the studio, wallet connection, asset selection, preview and transaction states. Reown AppKit provides the wallet interface; the wallet remains the signing authority.

The backend validates inputs, stores metadata, prepares official-protocol transactions, simulates before signature, verifies the exact signed message and tracks confirmation. It must reject changed instructions, amounts or recipients rather than trusting a browser success message.

The chain layer integrates Pump.fun for SOL launches and creator rewards, and Raydium CPMM for additional pools. Chain operations, API validation, persistence and fee policy remain separate modules so protocol upgrades do not silently change treasury economics.

The launch registry stores confirmed launches. Pending submissions are recovered by transaction signature instead of prompting a duplicate launch. Draft storage and a launch registry are different records: a saved draft is never shown as a confirmed coin.

Metadata and artwork must remain publicly reachable independently of a browser session. Backups include persistent records and public token assets. Operational credentials stay outside public documents and frontend bundles.

The treasury execution layer requires an attribution ledger, budget reservations, validated swap routes, spending authority, duplicate-execution protection and transaction-level burn evidence. Each operation needs a confirmed transaction record and a recoverable state.

Studio + walletSelect · review · sign
API + chain adaptersValidate · simulate · verify
Confirmed recordsMetadata · registry · recovery
Future treasury executorAttribute · reserve · swap · burn
Verification & risk

Claims need transaction evidence.

For a launch, verify the mint, launcher, metadata URI, creator receiver and confirmed signature. For a pool, verify both mints, deposited amounts, pool address and LP owner.

For reward collection, verify the destination and the actual amount received. For a buyback, retain the source budget, selected mint, quote bounds, executed signature and actual amount acquired. For a burn, retain the TIDE mint, amount and successful token-program burn.

Execution must recover safely after RPC timeouts and ambiguous submissions. Before retrying, check the pending signature. Repeated submission must not duplicate launches or spend the same budget twice.

Selecting an illiquid asset can lead to no available route, excessive price impact or transaction failure. Malicious tokens may impose restrictions. Failed quotes should leave the budget reserved, not reroute it to an unrelated token.

Other risks include treasury custody, changing protocol rules, RPC outages, incomplete reward attribution, market volatility and uncertain costs. None of the visual diagrams represent an audited executor or guaranteed outcome.

Execution rules

A clear rule for every outcome.

A coin appears in the Explorer only after a verified successful launch. Drafts, simulated transactions and unsigned preparations remain outside the confirmed registry.

The reward recipient is fixed by the Tide policy. A user’s launch signature and LP ownership do not create a personal creator-reward claim. Existing coins keep their own on-chain configuration.

Allocation is recorded before spending. Each selected-asset budget remains associated with its originating coin, even when rewards arrive in one treasury wallet.

If a quote is unavailable or exceeds accepted execution bounds, the budget stays reserved. A timeout triggers signature recovery before any retry. An unsuccessful trade does not become a completed buyback.

Before TIDE launches, its budget stays in SOL. After launch, a burn is recorded only when the token-program operation is confirmed. A transfer or an estimate never counts as a burn.

Cost funding, slippage limits, cadence and minimum trade sizes are execution parameters. Any changes should be explicit and must not silently alter the fixed 80 / 20 allocation.

Terms & sources

Read the mechanism precisely.

Launch quote: the currency used for the primary launch. Tide uses SOL.

Associated token: the selected Solana token that defines the 80% reward destination. This association is not a second trading pool.

Creator rewards: protocol creator-fee receipts, distinct from LP fees or total protocol fees.

Selected asset: the associated token targeted by the 80% allocation.

Treasury: the fixed reward-receiving wallet and its accounting. Receiving funds does not imply automated spending.

LP tokens: ownership of a liquidity position; separate from creator-reward rights.

Buyback budget: SOL allocated to acquire an asset. It is not an executed trade or a promised quantity.

Burn: a token-program operation reducing supply. A burn references the verified TIDE mint.

Confirmation: verified on-chain success. A draft, simulation or submitted signature alone is not confirmation.