Documentation · start with the basics
Use this guide to understand the planned launch flow, network differences, and the information a project should publish. The current experience is a front-end preview, not an operational protocol manual.
Begin by reading the project profile and risk disclosure. Confirm which network the launch uses, what the token represents, how the supply is allocated, and which conditions govern the sale. Do not sign a transaction unless you understand its destination and expected effect.
A production connection flow should request approval through a wallet provider and display the selected chain. Never share a seed phrase or private key with a launchpad. Network switching should be explicit, and unsupported chains should block rather than silently reroute transactions.
Creators should provide a concise project description, token name and symbol, total supply, allocation plan, sale model, caps, contribution limits, schedule, and links. The published profile should be consistent with the on-chain configuration and should explain any vesting or liquidity plan.
A real participation flow should validate network and contribution limits, request a wallet signature, submit a transaction, and verify the result from the chain. Claims and refunds are separate actions with their own contract conditions. Never trust a client-supplied “confirmed” status.
A fee schedule must be documented before users participate. Troubleshooting should distinguish a wallet rejection from a network error or a contract revert. Support guidance should never request a seed phrase, private key, or remote control of a user’s device.
A production API should verify receipts against the expected chain and contract before recording a contribution as confirmed. Never trust a client-submitted transaction status.
// Illustrative pseudocode — not a deployed integration
const receipt = await publicClient.getTransactionReceipt({ hash })
if (receipt.status !== 'success') {
throw new Error('Transaction was not successful')
}
// Verify chain, contract, event, amount, and participant