SLABZ
Launch
Documentation
DocsBuild & operate
Build & operate

Troubleshooting

Find the stage that needs attention without duplicating an action.

On this pageLaunch cannot be preparedWallet or funds issueNo card has arrivedTransaction appears stuck

Launch cannot be prepared

Check that a wallet is connected, all required identity fields are filled, the image is present, and metadata is publicly reachable over HTTPS. The selected fee and CARDS pair must be admitted by the current Pump configuration.

If capability verification is unavailable, check the local operator and Helius connection. A launch toggle by itself cannot compensate for missing transaction preparation or a failed simulation.

Wallet or funds issue

Verify the selected wallet address and network. Launches and trades need SOL for network and account costs in addition to the trade asset. A Privy account can be signed in while no suitable wallet is selected.

When a wallet prompt is rejected, reconnect or retry only after checking whether a signature was submitted. Never share a recovery phrase with support.

No card has arrived

Check the launch’s mode, funded card budget, secured purchases, snapshot, draw, and delivery status in that order. A qualifying balance does not mean a funded round has occurred or that the wallet won.

Vault purchases stay in custody; they are not airdrops. A marketplace card visible on Rewards is not automatically owned by any launch.

Transaction appears stuck

Use the recorded transaction link and status reconciliation first. The app retains submitted signatures so it can distinguish a finalized transaction from one that expired or needs further checking.

Do not create a replacement payment or launch solely because a browser request timed out. A timeout can occur after the network has already accepted a transaction.