Best Practices
Avoid common mistakes before funding, during execution, and when recovering funds.
Use this checklist before any action that moves assets, changes supply, or starts automation. The goal is to make the intended result and recovery path explicit before submission.
Prepare the operation
| Check | Confirm |
|---|---|
| Context | Account, network, launchpad, launch, token, and quote asset |
| Scope | Selected wallets, percentages or amounts, and recipient addresses |
| Capacity | Action amount, service costs, network fees, and recovery balance |
| Concurrency | No pending transfer, trade, batch, or automation conflicts |
| Evidence | Expected result and the explorer or activity entry you will use to verify it |
Never share a seed phrase, private key, backup code, API key, or one-time verification code while diagnosing an operation.
Before funding a launch
Review the selected network, launchpad, launch mode, and integration-specific options.
Check wallet funding, allocation, fees, slippage, and available balances.
Identify the settings and actions that become irreversible after deployment.
Define what you will do if execution is delayed, partial, or rejected.
Repeat the review after changing any network, launchpad, mode, or wallet selection.
Review the launch before funding →
During live execution
- Keep the launch page and an independent explorer available.
- Wait for a pending action to reach a final state before repeating it.
- Use automation only with limits you can explain and monitor.
- Treat price, liquidity, slippage, and transaction ordering as live variables.
- Stop and verify whenever the observed state differs from the plan.
High-impact actions
| Action | Main irreversible effect | Verify before confirmation |
|---|---|---|
| Sell | Trades tokens and changes wallet balances | Wallet scope, amount, route, slippage |
| Burn | Permanently changes available supply | Token, amount, resulting supply |
| Lock | Restricts supply according to the lock | Token, amount, duration or lock terms |
| Withdraw or send | Transfers assets to another address | Recipient, network, asset, remaining gas |
| Cleanup or Nuke | Can sell or move assets across many wallets | Included wallets, exclusions, recovery destination |
After every operation
Open the matching entry in Activity.
Confirm the transaction’s final status on the relevant explorer when a link is available.
Compare every affected token and native balance with the expected result.
Check that automation, funding, or launch state matches the intended next step.
Record any partial result before deciding whether to retry.
If the result is pending, partial, or unexpected, use Troubleshooting before submitting another transaction.