Portable Platform Management Tools for a Solana Launchpad
A reusable CLI and API toolkit for operating a Solana launchpad on the Raydium SDK, covering platform config, fee claiming and distribution, pools, and token sync.
Running a launchpad platform on Solana involves a lot of repetitive operational work: creating and updating the platform config, checking and claiming fees, listing pools and launched tokens, keeping a database in sync. LaunchLab Tools is the toolkit I pulled together to do all of that from the command line, built on the Raydium SDK and, importantly, written to be portable across different platform deployments rather than hardcoded to one.
Portable by Design
The word "portable" in the description is doing real work. The tools are structured so that pointing them at a different launchpad is a configuration change, not a rewrite. The customization notes spell out the whole reconfiguration path: update the platform ID in the script files, update the CP Config ID if needed, set the wallet keys, and adjust the fee distribution percentages. That is the entire cost of retargeting the toolkit to a new platform.
To make first-time setup painless, there is an interactive setup wizard. It asks for the platform ID and configuration, requests wallet private keys, configures RPC endpoints, writes the .env file automatically, updates the platform IDs across the scripts, optionally installs dependencies, and generates the wallet files. The manual path exists too, but the wizard collapses a dozen fiddly steps into a guided run, which is exactly where operational tools tend to lose people.
What the Commands Actually Do
The command set maps cleanly onto the jobs of running a platform. Platform management covers create, update configuration, and get info. Fee management is the part that matters most in practice: check claimable fees, claim platform fees, and claim-and-distribute in one step. Token and pool management lists platform pools and launched tokens. There is an API server that comes up on port 3000, plus database commands to initialize and to sync tokens, so the on-chain state and the local database stay aligned.
Handling Keys Responsibly
Because this toolkit handles wallet private keys, the important notes are about not leaking them. The guidance is direct: never commit wallet private keys or .env files to git, keep wallet backups somewhere secure, and test fee distribution on devnet before running it against real funds. Those are not decorative warnings. A launchpad tool that touches fee wallets is exactly the kind of thing where one committed secret ends a project.
The takeaway is that operational tooling earns its value by being configurable and honest about its footguns. Building the platform ID, config ID, and fee percentages as parameters rather than constants is what turns a one-off script into something reusable, and putting the key-handling rules right in the docs is what keeps that reusability from becoming a liability.
Have something that needs building, or stabilizing?
These notes are the work log. The paid work runs through Moonshine Labs, my product and engineering studio. Tell us what you're building, or grab a call.
Work with us →