slimeKeep your fees
Claim the developer share through the supported wallet workflow. A wallet-wide Pump claim is not automatically attributable to one coin.
A CLEARER WAY IN
Know the next move.
Start small. Review the details. Keep the receipt.
01 / WALLET
Set up once. Know your next step.
- Sign in or create a profile
A disconnected screen is not a balance check. Use the same account for Wallet and Telegram-linked trading.
- Back up each managed wallet
Open Manage / restore → wallet backups, or Back up all wallets. Store recovery files privately, away from chats and shared devices.
- Fund the correct network
Use Receive or the supported funding flow. Verify the address and network; allow room for network fees. Start with a small transfer.
- Review, then trade
Check the wallet, coin address, amount, chain, slippage and costs. A swap-only buy does not automatically arm take-profit or stop-loss.
Multi-wallet tools without the clutter
Wallet tools includes bundles, funding, launch copying and sell/sweep actions. Pick source wallets and the destination, then review. Sell all + sweep can leave unsellable tokens behind; read each wallet’s result before retrying.
02 / LAUNCH
An idea. A split. A deliberate review.
Draft your name, ticker and allocation without sending money. Add artwork, select your creator wallet, then review funding, bundle approvals, costs and on-chain setup.
Share with communities
Split creator fees between yourself, your holders, another coin’s holders and receiving wallets. Holders must hold strictly over $20 at a verified snapshot. Shares are proportional; small credits accumulate.
Follow the proof
Open Fee totals & receipts or Earnings. Automatic holder cycles run every 12 hours when complete data and sufficient funds are available—not a promise of income or an exact transfer time.
Pump fee splits are permanent. Review every percentage and address. Pausing distribution does not erase rewards owed. Current launch pairing and payouts are in SOL; no stock rewards or X Money payments are offered here.
03 / FEES
Paid is not the same as pending.
- Transaction costs
- The final review shows current application fees, network fees, account rent and route costs. Slippage is a limit, not a service fee.
- Paid
- A verified, recorded payment. Use its transaction link to inspect it on-chain.
- Reserved / pending
- Owed or allocated, but not yet paid. This is not spendable wallet balance.
- Not attributed
- Records cannot support a per-coin total. Unavailable is not zero. Older wallet-wide claims are never guessed into a coin’s earnings.
- Holder minimums
- Current custom programs retain a 0.001 SOL vault reserve and accumulate wallet payouts below 0.001 SOL. Network costs reduce the distributable amount.
04 / ACTIVITY & RECOVERY
Don’t repeat an action blindly.
Submitted / pending
A transaction may already be on-chain. Check its receipt and saved activity; do not send another buy because a screen timed out.
Partial / needs attention
Some wallets or steps may have succeeded. When the outcome is unknown, use the existing operation’s recovery option instead of creating another one.
Confirmed / failed
Confirmed means the recorded transaction landed. A failed operation may still have successful earlier steps. Read the details before starting again.
For support, include the public transaction signature, coin address, time and visible error. Never send recovery files, private keys, passwords or login codes.
05 / AUTOMATION
Entries and protective exits are different.
Wallet → Activity & automation lists orders and exits. Review each rule’s wallet, trigger and status. Pausing a buy strategy does not mean you should cancel protective exits for coins already held.
Copying, scheduled launches and other strategies have their own controls. Open the relevant tool to pause new entries. Take-profit and stop-loss run server-side after the page closes, but depend on valid quotes, liquidity, network availability and sufficient fees. Execution and price are not assured.
Review activity & automation →06 / SECURITY
Understand where the keys live.
Managed wallets
Wallets created or imported for managed trading use encrypted keys on the service. The server can sign authorized trades and automation. This is different from keeping every key only in Phantom.
External wallets
External wallets keep their own keys and request signatures through their provider. Read each transaction. Connecting an address is not the same as importing a signing key.
Device lock vs. spend controls
A local screen lock protects this device’s interface; it does not stop server-side automation. Cash PINs and limits apply only where server enforcement is confirmed. Device-only preferences are not account-wide limits.
Scans are risk signals, not safety certificates. Never share recovery secrets with support or in group chats. Use official recovery/import controls only when you intentionally choose to restore a wallet.