blowfish-launch

What This Skill Does

The blowfish-launch skill provides a direct, programmable interface for deploying new SPL tokens on the Solana blockchain using the Meteora Dynamic Bonding Curve. This agentic skill manages the end-to-end lifecycle of a token deployment, including authentication, transaction submission, polling for confirmation status, and managing post-launch financial operations such as fee claims. It is designed for developers and power users who want to automate the tokenization process without manually interacting with complex smart contract interfaces.

Installation

To integrate this capability into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/basedmereum/blowfish-launch

Ensure you have your environment variable WALLET_SECRET_KEY configured as a JSON array of bytes before initiating any launches, as this is required for the cryptographic signing process mandated by the API.

Use Cases

• Rapid prototyping of new memecoins or utility tokens on Solana.
• Automating large-scale token deployments for marketing campaigns or ecosystem expansion.
• Monitoring and managing multiple token launches via a unified dashboard interface.
• Automating the collection of accrued trading fees generated from liquidity pools on Meteora.

Example Prompts

1. "I want to launch a new token called 'Neon Dog' with the ticker 'DOG' and this logo: https://example.com/logo.png. Please handle the deployment."
2. "Check the current launch status for my recent token deployment with event ID 98765."
3. "Can you list all tokens I have launched through Blowfish and check if there are any pending trading fees I can claim?"

Tips & Limitations

• Authentication: The skill uses a wallet-based challenge-response mechanism. If your JWT expires, the skill will automatically prompt for re-authentication.
• Rate Limiting: Please note that the API imposes a limit of one launch per agent per UTC day; plan your deployments accordingly.
• Naming Conventions: Ensure your ticker is strictly uppercase alphanumeric (2-10 characters) to avoid validation errors. If you receive a 409 error, your ticker is likely already taken by another user.
• Security: Always verify the WALLET_SECRET_KEY environment variable is not exposed in public repositories, as it holds full signing authority for your wallet.