Best practices

How to launch and trade safely with DevBundler.

Keys and access

  • Use a long, unique password and store it in a password manager. It encrypts your wallets and cannot be reset.
  • Turn on two-factor sign-in in Settings, and add a passkey for quick, phishing-resistant sign-in.
  • Export and back up the keys of wallets that hold real value (Wallets, Export). Keep the file offline.
  • Only use exchange API keys with withdrawal permission locked to the server's IP address, and with trading turned off.

Before a launch

  • Try the whole flow on devnet first (Settings, Test network). It costs nothing.
  • Keep a little more SOL in each wallet than the launch form asks for. The form's "Needs" column already includes fees and account rent.
  • Check the estimated share of supply in the launch table. Buying most of the curve leaves little for anyone else and the last buys get nothing.
  • A Jito tip a little above the minimum gives the bundle a better chance of landing in busy periods.

While trading

  • Set slippage to what you can accept. Higher slippage fills more often but can cost more.
  • Exit rules and auto buys run on the server only while you are signed in. Signing out or the auto-lock pauses them.
  • Use Bundle mode when several wallets should trade in the same block; Fast mode is quicker and works on devnet.

Afterwards

  • Use Recover funds to close empty token accounts and bring SOL back to one wallet.
  • Archive finished projects to keep the list tidy; nothing is deleted.