CLI

@baseline-markets/cli is the Baseline launch planning and execution handoff CLI. It exposes the baseline command with two launch commands:

• baseline plan-launch builds a canonical LaunchPlanV1 JSON artifact, validates the launch economics, and emits executor payloads.
• baseline execute-launch verifies a saved plan hash, builds the selected executor payload, and either submits through a configured executor API or saves a handoff receipt.

Use the CLI when you want an operator-grade launch artifact before signing anything. Use the SDK when you are building launch, swap, stake, borrow, or leverage flows directly into an app with viem clients.

Configuration

Pass a config file explicitly with --config, or let the CLI discover one of these files:

• baseline.config.json
• ~/.config/baseline/config.json

Config can provide command defaults and executor settings. A typical launch config sets Base MCP as the default executor and keeps local receipts under .context/launches.

{
  "commands": {
    "plan-launch": {
      "options": {
        "chain": "base-sepolia",
        "poolMode": "zero-reserve",
        "reserveSeed": "0",
        "poolAllocationPct": 100,
        "swapFee": "1%",
        "creatorFee": "50%",
        "executor": "base-mcp"
      }
    },
    "execute-launch": {
      "options": {
        "executor": "base-mcp",
        "receiptDir": ".context/launches"
      }
    }
  }
}

Plan a Launch

baseline plan-launch creates the launch plan and executor payloads.

baseline plan-launch \
  --chain base \
  --from 0x0000000000000000000000000000000000000001 \
  --name "Example Baseline Token" \
  --symbol EBT \
  --output .context/launches/example-plan.json

The planner validates token text, total supply bounds, fee bounds, pool-mode economics, Relay routes, and the precomputed bToken address. If --output is set, the command saves the plan JSON and prints the next execute-launch command.

plan-launch Flags

Launch Modes

Zero Reserve

zero-reserve is the default mode. It is designed for launches where the pool receives the full token supply and starts with no reserve asset seed.

The planner enforces:

• poolAllocationPct is 100.
• reserveSeed is 0.
• launchPrice resolves to a nonzero WAD price.
• The Relay routes previewInvariantForPrice and createPoolFromInvariant are available on the selected chain.

If you do not provide --launchPrice or --targetFdv, the planner derives the minimum valid launch price for the supply. If you provide --targetFdv, it derives the launch price from target FDV and total supply.

The transaction order is:

1. createBToken
2. bToken approval to the Relay
3. createPoolFromInvariant

The planner calls previewInvariantForPrice before emitting the final createPoolFromInvariant calldata.

Seeded Reserve

seeded-reserve keeps the reserve-seeded createPool path available for launches that initialize with reserve assets.

The planner enforces:

• reserveSeed is greater than 0.
• poolAllocationPct is greater than 0 and less than 100, leaving circulating supply outside the pool.
• initialActivePrice is above book price.
• initialBLV is less than or equal to book price.

The transaction order is:

1. createBToken
2. bToken approval to the Relay
3. reserve approval to the Relay
4. createPool

Execute a Plan

baseline execute-launch consumes a saved plan and produces an execution receipt.

baseline execute-launch \
  --plan .context/launches/example-plan.json \
  --executor base-mcp \
  --receiptDir .context/launches

Before execution, the command recomputes the canonical plan hash and fails if the saved plan has been edited. This protects the signer or executor from submitting a payload that no longer matches the reviewed plan.

execute-launch Flags

Executor Payloads

The plan can include payloads for these executors:

Use --dryRun before handing a receipt to an operator or executor. It validates the plan and builds the payload without submitting API calls.

SDK and viem Usage

The CLI uses @baseline-markets/sdk exports for Baseline ABIs and supported chain IDs. It uses viem for ABI encoding, address reads, Relay precompute calls, invariant preview calls, and calldata construction.

It does not instantiate the SDK as an app wallet client. If you need wallet-client methods for an application, use the SDK directly.

Safety Boundaries

• No raw private keys are accepted or stored by the CLI.
• Plan hashes are validated before execution.
• Base MCP signing and approval happen outside the CLI through Base Account.
• Local launch plans and receipts are intended to live under .context/launches.
• API executor submission only happens when the relevant API environment configuration is present.
• Ambiguous failures should be recovered from by re-reading on-chain state before retrying.