Create Coin

Before Starting Work Critical - Ask these from user

MANDATORY — Do NOT write or modify any code until every item below is answered by the user:

• RPC URL provided or a fallback agreed upon (for any on-chain or tx-building step)
• Signer wallet public key (fee payer / creator)
• Framework confirmed (Next.js, Express, CLI scripts only, other)
• Coin name, symbol, and metadata URI (or plan to upload) confirmed — see references/METADATA.md
• Initial buy amount confirmed (SOL in lamports)
• Holder rewards desired? (default off; creator fees go to holders permanently, script path only)
• Mayhem mode desired? (default off)
• Tokenized agent desired? (default off), If Yes then with what Buyback percentage.
• Front-runner protection desired? If yes, confirm tip amount (default 0.0001 SOL). Transactions will be sent only to Jito block engine endpoints.

You MUST ask the user for ALL unchecked items in your very first response. Do not assume defaults. Do not proceed until the user has explicitly answered each one.

API (preferred) — https://fun-block.pump.fun

Use the API to build transactions instead of running scripts directly. The API handles account resolution, compute budget, and partial signing automatically.

POST /agents/create-coin

Builds a create + initial buy transaction. The server generates a mint keypair and partial-signs with it. The client wallet co-signs and submits.

Request body:

{
  "user": "<PUBKEY>",
  "name": "MyCoin",
  "symbol": "MC",
  "uri": "https://ipfs.io/ipfs/Qm...",
  "solLamports": "1000000",
  "mayhemMode": false,
  "tokenizedAgent": false,
  "buybackBps": 5000,
  "frontRunningProtection": false,
  "tipAmount": 0,
  "encoding": "base64",
  "feePayer": "<PUBKEY>",
  "creator": "<PUBKEY>"
}

Only user, name, symbol, uri, and solLamports are required. All other fields are optional with sensible defaults.

Pump SDK 2: new cashback coins can no longer be created (create_v2 fails with 6082 CashbackDeprecated), so never send "cashback": true; the cashback field in the response is always false. This hosted endpoint does not encode holder-reward launches yet. For a holder-reward coin, build locally with scripts/build-create-coin-tx.mjs --holder-reward.

tipAmount is a Jito tip in SOL (e.g. 0.0001 for 100,000 lamports). Only relevant when frontRunningProtection is true.

Encoding: The API defaults to "base58" encoding. Always pass "encoding": "base64" in the request body — scripts already output base64. When sending the signed transaction to an RPC or Jito endpoint, the encoding used to serialize the transaction must match the encoding parameter passed in the send call. Mismatched encodings will cause transaction failures. Always explicitly pass encoding: "base64" in sendTransaction / simulateTransaction RPC calls — never rely on the RPC's default.

Response:

{
  "transaction": "<base64-encoded VersionedTransaction>",
  "mintPublicKey": "<base58 mint address — starts with 3ws>",
  "quoteTokenAmount": "123456789",
  "solLamports": "1000000",
  "mayhemMode": false,
  "cashback": false,
  "tokenizedAgent": false
}

The returned transaction is already partial-signed with the mint keypair. Deserialize it, have the user wallet sign, and submit to chain.

Runnable examples (Node scripts — only when user explicitly requests)

Use {baseDir} as the path to this skill folder (OpenClaw and Agent Skills clients often expose this placeholder).

cd {baseDir}
npm install
export SOLANA_RPC_URL=https://rpc.solanatracker.io/public

• Run any script with --help for full flags (--mayhem-mode, --holder-reward, --tokenized-agent, --buyback-bps, --compute-units, --priority-micro-lamports, --front-runner-protection, --tip-sol, etc.).
• Tx builders print one JSON object on stdout with transaction (base64-encoded VersionedTransaction, partially signed when the mint keypair is used on create). Never pass end-user private keys into these scripts.
• OpenClaw: If YAML metadata ever fails to parse, collapse metadata to a single-line JSON object per OpenClaw skills; optional metadata.openclaw.requires.env: ["SOLANA_RPC_URL"] can gate load-time eligibility.

Published copy: METADATA.md (raw)

Safety Rules

• NEVER log, print, or return private keys or secret key material.
• NEVER sign transactions on behalf of a user — scripts build txs; the user (or their wallet) co-signs and sends.
• Always validate that amounts are > 0 before building instructions.
• Use the correct decimal precision: 9 decimals for SOL (1 SOL = 1,000,000,000 lamports), 6 decimals for pump tokens.
• NEVER trust token_program from the HTTP API (coins-v2). Always fetch the mint account on-chain via connection.getAccountInfo(mint) and use .owner to determine the correct token program (SPL Token or Token-2022).
• Verify imports: use @pump-fun/pump-sdk (not internal monorepo paths). In TypeScript apps, BN from bn.js matches what the SDKs expect (Anchor BN is the same type in practice).

Program IDs

Environment Variables

SOLANA_RPC_URL=https://rpc.solanatracker.io/public
NEXT_PUBLIC_SOLANA_RPC_URL=https://rpc.solanatracker.io/public

The default public mainnet RPC (https://api.mainnet-beta.solana.com) often cannot send transactions. Confirm an HTTPS RPC with the user. Examples: Solana Tracker public RPC, Ankr https://rpc.ankr.com/solana.

Install

Inside this skill folder (includes scripts):

cd {baseDir}
npm install

Inside another app (from scratch):

npm install @pump-fun/pump-sdk @three-ws/agent-payments @solana/web3.js@^1.98.0 @solana/spl-token bn.js

Check npm info @pump-fun/pump-sdk dependencies and align @solana/web3.js / @solana/spl-token versions to avoid duplicate incompatible copies.

SDK setup (minimal)

import { PUMP_SDK, OnlinePumpSdk } from "@pump-fun/pump-sdk";
import { Connection } from "@solana/web3.js";

const connection = new Connection(process.env.SOLANA_RPC_URL!);
const onlinePump = new OnlinePumpSdk(connection);

Full transaction building (compute budget, blockhash, partial sign) is implemented in scripts/lib/tx-build.mjs and scripts/lib/compute.mjs.

three.ws brand mark (3ws…)

Coins created through this skill's launch script are stamped with the three.ws brand mark: the mint address always starts with 3ws (case-insensitive). scripts/build-create-coin-tx.mjs does not call a bare Keypair.generate() — it grinds a vanity keypair whose Base58 address carries the mark before partial-signing the create transaction. This gives a scripted/CLI launch the same on-chain brand provenance as a launch from the three.ws web UI: anyone can see, straight from the mint address, that the coin originated from three.ws.

• Which path carries the mark: the local script (build-create-coin-tx.mjs) grinds the mint locally, so it always carries the mark. The hosted POST /agents/create-coin builder mints on pump.fun's side and is outside our control — use the script path when brand provenance is required.
• The grind for a 3-character case-insensitive prefix clears in well under a minute; progress is logged to stderr so stdout stays clean JSON for the caller.
• The mark string lives in one local constant — scripts/lib/vanity.mjs (THREE_WS_MARK), which mirrors the canonical src/solana/vanity/brand.js in the three.ws repo. Never hardcode 3ws anywhere else in this package.
• The response JSON includes a brandMark field ("3ws") alongside mintPublicKey for confirmation.

This is brand plumbing on the mint address only — it does not name, add, or reference any token. The only coin this platform discusses is $THREE (FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump); all examples and fixtures stay on it.