Skip to article
FIELD GUIDE[open app]
DOCUMENTATIONDevelopment release · on-chain launches are not active
Docs/Launch design
09 / RESET FIELD GUIDEPlanned · not active

Fees, supply & liquidity.

What is known today, and which economic parameters are not set.

Design direction, not an active feature.

This chapter explains the intended behavior. Parameters that have not been decided are marked explicitly.

No published trading fee schedule

The goal is low fees without excessive trading taxes. Exact percentages, minimum charges, creator revenue and fee destinations have not been defined. Do not interpret this goal as a promise of zero fees.

The current app has no payment flow for drafts, no launch fee collection and no trade execution. An account action is not a swap.

ParameterStatus
Launch feeNot set
Opening-round feeNot set
Trading fee / token taxNot set
Creator or protocol revenue splitNot set
Network and priority feesNo transaction flow currently calculates or charges them.
Migration costs and recipientsNot set

Token supply and allocation

Supply, creator allocation, vesting, mint/freeze permissions and any launchpad-token economics are not finalized. These docs do not announce a RESET token, ticker or contract address.

There is no implemented team allocation, airdrop claim or presale mechanism to describe. Future launches must disclose their specific supply and allocations before users participate.

The intended liquidity destination

The technical direction favors Meteora, with Raydium also considered as a possible destination. The pool type, migration threshold, initial price, asset amounts and handling of liquidity ownership have not been chosen.

Automatic migration is not implemented. A “migrated” status in the data model is a future integration point, not evidence that RESET currently creates liquidity pools.

Before any signature

A future launch or trading flow must show the exact transaction, network, expected amounts, fees, recipients, slippage conditions and permissions. No funds should be described as locked, burned or refundable without a verifiable implementation and published rules.

Development documentation · features may change.Back to top ↑