@baseline-markets/cli 0.2.2 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@baseline-markets/cli",
-  "version": "0.2.2",
+  "version": "0.3.0",
   "type": "module",
   "repository": {
     "type": "git",
@@ -27,7 +27,7 @@
     "test:integration": "bun test tests/*.integration.test.ts"
   },
   "dependencies": {
-    "@baseline-markets/sdk": "^1.1.0",
+    "@baseline-markets/sdk": "^1.2.0",
     "incur": "^0.4.8",
     "viem": "^2.31.6"
   },

package/skills/aeon-baseline/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: aeon-baseline
+description: Execute a Baseline launch call artifact through an Aeon operator workflow.
+var: ""
+tags: [crypto, onchain]
+capabilities: [external_api, writes_external_host, onchain_writes, sends_notifications]
+---
+
+> **${var}** - Path to a saved `baseline launch` JSON artifact, or empty
+> when `run.vars.launchArtifact` already contains the artifact object. If
+> neither is available, notify `LAUNCH_BASELINE_NO_ARTIFACT` and stop.
+
+Today is ${today}. Execute a Baseline launch call artifact through the
+configured Aeon operator surface without inventing calldata, signers, or wallet
+policy.
+
+## Required Config
+
+- `AEON_RUN_URL` is required only when dispatching this skill through the
+  repository CLI executor.
+- `AEON_AUTH_TOKEN` is optional and is sent as `Authorization: Bearer ...` by
+  the CLI executor when configured.
+- The launch artifact must already be produced by `baseline launch`.
+- Aeon execution is Base mainnet only in v1.
+- Register this skill in an Aeon instance by copying this folder under
+  `skills/`, running `./generate-skills-json`, and adding an `aeon.yml` entry
+  with `enabled: false` and `schedule: "manual"` until an operator explicitly
+  enables it.
+
+## CLI Artifact Contract
+
+`baseline launch` builds and validates the canonical call artifact. The
+`--output` file is the source of truth:
+
+```json
+{
+  "chainId": 8453,
+  "chain": "base",
+  "account": "0xAeonOperatorWallet",
+  "bToken": "0x...",
+  "calls": [{ "to": "0x...", "data": "0x...", "value": "0x0" }]
+}
+```
+
+Required Aeon launch inputs:
+
+- `--mode zrp` or `--mode standard`
+- `--chain-id 8453`
+- `--account "$AEON_OPERATOR_WALLET"`
+- `--name "$TOKEN_NAME"`
+- `--symbol "$TOKEN_SYMBOL"`
+- `--reserve 0x4200000000000000000000000000000000000006`
+- `--total-supply "$TOTAL_SUPPLY"`
+- `--initial-pool-btokens "$POOL_BTOKENS"` for `standard`
+- `--initial-pool-reserves "$RESERVE_SEED"` for `standard`
+- `--output .context/launches/aeon-launch.json`
+
+Key optional controls:
+
+- Fees: `--swap-fee-pct` and `--creator-fee-pct`.
+- Parties and salt: `--creator`, `--fee-recipient`, and `--salt`.
+
+Build the handoff artifact before running this skill:
+
+```sh
+baseline launch \
+  --mode zrp \
+  --chain-id 8453 \
+  --account "$AEON_OPERATOR_WALLET" \
+  --name "$TOKEN_NAME" \
+  --symbol "$TOKEN_SYMBOL" \
+  --reserve 0x4200000000000000000000000000000000000006 \
+  --total-supply "$TOTAL_SUPPLY" \
+  --output .context/launches/aeon-launch.json
+```
+
+Before Aeon execution, verify `chainId`, `account`, call count, call order,
+allowed targets, and selected mode economics. `zrp` artifacts use
+three calls and all BTokens in the pool. `standard` artifacts use four calls,
+a nonzero reserve seed, and `createPool`.
+
+## Steps
+
+1. **Load the artifact.** If `run.vars.launchArtifact` exists, use it.
+   Otherwise read the JSON file path from `${var}`. If both are absent, run:
+
+```sh
+./notify "LAUNCH_BASELINE_NO_ARTIFACT: provide var=<path-to-launch-artifact.json> or run.vars.launchArtifact"
+```
+
+Then stop.
+
+2. **Validate the artifact.** Confirm:
+
+- `chainId` is `8453`.
+- `account` is present and is the expected Aeon operator wallet.
+- `calls` is an array with exactly three or four items.
+- Every call has `to`, `data`, and `value`.
+
+3. **Validate transaction shape.** Confirm the call order matches the selected
+   mode:
+
+- `zrp`: Relay `createBToken`, BToken `approve`, Relay
+  `createPoolFromInvariant`.
+- `standard`: Relay `createBToken`, BToken `approve`, reserve `approve`, Relay
+  `createPool`.
+
+Reject any artifact whose targets are outside the Baseline Relay, precomputed
+BToken, and reserve token.
+
+4. **Respect the executor boundary.** Do not sign directly, do not ask for a
+   private key, and do not rebuild calldata by hand. Use the artifact calls
+   exactly as produced by the CLI or abort with a notification explaining the
+   mismatch.
+
+5. **Submit through the configured Aeon operator workflow.** If this skill is
+   running inside Aeon with a wallet-capable operator surface, submit the
+   ordered Base mainnet calls according to that operator's configured wallet
+   policy. If no wallet execution surface is configured, emit a handoff
+   notification and stop without broadcasting.
+
+6. **Verify on-chain state.** After a successful run, perform read-only checks:
+
+- BToken code is non-empty.
+- Maker initialization is true.
+- Reserve equals Base WETH.
+- Creator and fee recipient match the artifact expectations.
+- For `zrp`, total reserves and deployer BToken balance are `0`.
+
+7. **Log.** Append to `memory/logs/${today}.md`:
+
+```markdown
+## aeon-baseline
+- Artifact: ARTIFACT_PATH_OR_INLINE
+- Chain ID: 8453
+- Account: ACCOUNT
+- Status: SUBMITTED | HANDOFF_READY | VERIFIED | REJECTED
+- Transaction hashes: HASHES_OR_NONE
+```
+
+8. **Notify.** Send a notification under 4000 characters:
+
+```text
+Baseline launch: STATUS
+Account: ACCOUNT
+Txs: HASHES_OR_HANDOFF
+Next: verification summary or rejection reason
+```
+
+## Sandbox Note
+
+Authenticated wallet or run APIs may not be reachable from the Claude sandbox.
+If secrets are unavailable, do not fail noisily or fabricate execution. Notify
+`LAUNCH_BASELINE_HANDOFF_READY`, write the handoff details to memory, and stop.

package/skills/bankr-baseline/SKILL.md

@@ -0,0 +1,260 @@
+---
+name: bankr-baseline
+description: Build Baseline launch call artifacts and submit them with Bankr Wallet API
+tags: [crypto, baseline, token, erc20]
+version: 1
+---
+
+# Bankr Baseline
+
+Use this skill when a user wants an agent to plan and deploy a Baseline token
+with this repository's `baseline` CLI and Bankr's Wallet API.
+
+## Skill Contract
+
+| Field | Requirement |
+|---|---|
+| Purpose | Build, review, and submit explicit Baseline launch calls. |
+| Supported chain | Confirmed Bankr execution uses Base mainnet, chain ID `8453`. |
+| Pending validation | Base Sepolia `84532` needs authenticated Wallet API validation before Bankr execution. |
+| Planner | The local `baseline` CLI is the launch calldata builder. |
+| Protocol surface | The CLI uses Baseline SDK/protocol helpers for economics, addresses, and calldata. |
+| Wallet executor | Bankr provides wallet identity, signing, and transaction submission only. |
+| Allowed Bankr endpoints | `GET /wallet/me` and `POST /wallet/submit`. |
+| Canonical artifact | `baseline launch` call artifact with `{ chainId, chain, account, bToken, calls }`. |
+| Hard stops | No private keys, Bankr native launches, Agent API prompts, or hand-built calldata. |
+
+Base MCP remains the confirmed Sepolia test executor in this repository. Bankr
+Wallet API docs document explicit transaction submission by `chainId`, but do
+not currently document Base Sepolia `84532` as supported. Do not use Bankr for
+Base Sepolia execution until an authenticated validation run proves support.
+
+## Protocol Constants
+
+| Chain | Chain ID | Reserve | Use |
+|---|---:|---|---|
+| Base Sepolia | `84532` | `0xB85885897D297000A74eA2e4711C3Ca729461ABC` | Pending Bankr validation. |
+| Base mainnet | `8453` | `0x4200000000000000000000000000000000000006` | Approved production launches. |
+
+Baseline Relay proxy on both profiles:
+`0xc81Fd894C0acE037d133aF4886550aC8133568E8`.
+
+## Required Setup
+
+- `BANKR_API_KEY` must be set only in the local execution environment or secret
+  manager.
+- Optional: `BANKR_API_BASE`, defaulting to `https://api.bankr.bot`.
+- The Bankr key must have Wallet API write access enabled and must not be
+  read-only.
+- Raw `/wallet/submit` cannot be used when the key has `allowedRecipients`
+  restrictions, because Bankr blocks raw submissions for those keys.
+- The Bankr EVM wallet returned by `/wallet/me` is the Baseline launch
+  `account` unless the user explicitly chooses another supported policy.
+
+## CLI Artifact Contract
+
+The CLI is the only Baseline launch calldata builder in this workflow. It
+collects launch inputs, applies defaults, calls SDK-backed protocol helpers,
+builds ordered raw calls, and writes a JSON artifact. It does not custody keys
+or sign transactions.
+
+`baseline launch` writes the canonical artifact:
+
+```json
+{
+  "chainId": 8453,
+  "chain": "base",
+  "account": "0xBankrWallet",
+  "bToken": "0x...",
+  "calls": [{ "to": "0x...", "data": "0x...", "value": "0x0" }]
+}
+```
+
+Required Bankr launch flags:
+
+| Flag | Required value | Description |
+|---|---|---|
+| `--mode` | `zrp` by default, `standard` when a reserve seed is required | Selects the Baseline launch path. |
+| `--chain-id` | `8453` | Keeps Bankr on the confirmed Base mainnet execution chain. |
+| `--account` | `"$BANKR_WALLET"` | Uses the EVM wallet returned by Bankr `/wallet/me`. |
+| `--name` | `"$TOKEN_NAME"` | Sets the BToken name passed to the Baseline Relay. |
+| `--symbol` | `"$TOKEN_SYMBOL"` | Sets the BToken symbol passed to the Baseline Relay. |
+| `--reserve` | Base mainnet WETH | Uses the confirmed reserve token. |
+| `--total-supply` | Launch-specific supply | Sets human-unit total supply. |
+| `--initial-pool-btokens` | Required for `standard`; omit for `zrp` | Sets the pool BToken amount while leaving circulating supply. |
+| `--initial-pool-reserves` | Required for `standard` | Sets the reserve seed. |
+| `--output` | `.context/launches/bankr-launch.json` | Saves the artifact under `.context/`. |
+
+Important optional launch flags:
+
+| Category | Flags | Description |
+|---|---|---|
+| Fees | `--swap-fee-pct`, `--creator-fee-pct` | Defaults are `1%` and `50%`; swap fee protocol bounds are `0.15%` to `50%`. |
+| Parties | `--creator`, `--fee-recipient` | Creator defaults to `account`; fee recipient defaults to creator. |
+| Salt | `--salt` | Sets deterministic BToken salt; empty input uses zero `bytes32`. |
+
+## Default Launch Profile
+
+### ZRP
+
+| Setting | Default | Notes |
+|---|---|---|
+| Mode | `zrp` | Default launch path. |
+| Chain ID | `8453` for Bankr | Bankr remains Base mainnet only. |
+| Supply | `100B` | Human-unit total supply when not overridden. |
+| Pool BTokens | Derived from `totalSupply` | Deployer BToken balance is `0`. |
+| Pool reserves | `0` | No reserve approval is expected. |
+| Reserve | Base mainnet WETH | `0x4200000000000000000000000000000000000006`. |
+| Swap fee | `1%` | Must stay within protocol bounds. |
+| Creator fee share | `50%` | Creator share of pool fees. |
+| Creator | Bankr EVM wallet | Override only when explicitly requested. |
+| Fee recipient | Creator | Override only when explicitly requested. |
+| `createHook` | `true` | Matches the current SDK launch params. |
+
+### Standard
+
+| Setting | Default | Notes |
+|---|---|---|
+| Mode | `standard` | Explicit standard launch path. |
+| Chain ID | `8453` for Bankr | Bankr remains Base mainnet only. |
+| Pool BTokens | User supplied | Must leave circulating supply. |
+| Pool reserves | User supplied | Must be nonzero. |
+| Pool creation | `createPool` | Uses the `createPool` Relay flow. |
+| Shared fees and parties | Same as `zrp` | Override only with explicit fee, creator, or recipient flags. |
+| `createHook` | `true` | Matches the current SDK launch params. |
+
+## Baseline Launch Call Sequence
+
+The Baseline protocol launch is represented as an ordered call sequence inside
+the CLI-generated artifact. Bankr does not decide this sequence. Bankr only
+identifies the wallet and signs/submits the explicit calls that the CLI
+produces.
+
+For `zrp`, the sequence is:
+
+| Order | Step | Transaction purpose |
+|---|---|---|
+| 1 | `createBToken` | Deploy the planned BToken through the Baseline Relay. |
+| 2 | BToken `approve` | Approve the Baseline Relay to move the full BToken supply for pool creation. |
+| 3 | `createPoolFromInvariant` | Create the pool from the computed invariant and planned params. |
+
+For `standard`, the sequence is:
+
+| Order | Step | Transaction purpose |
+|---|---|---|
+| 1 | `createBToken` | Deploy the planned BToken through the Baseline Relay. |
+| 2 | BToken `approve` | Approve the Baseline Relay to move the planned BToken pool allocation. |
+| 3 | Reserve `approve` | Approve the Baseline Relay to move the planned reserve seed. |
+| 4 | `createPool` | Create the pool with standard params, fees, creator, and fee recipient. |
+
+These calls are dependent. If a live run partially completes, do not replay the
+full sequence blindly. Verify the last completed on-chain step and recover from
+that exact state.
+
+## Execution Plan
+
+1. Resolve the Bankr EVM wallet with `/wallet/me`.
+2. Use that wallet as `--account` for the local CLI artifact builder.
+3. Confirm the user explicitly approved a Bankr Base mainnet run.
+4. Run `baseline launch --chain-id 8453` and save the artifact.
+5. Review the saved artifact: `chainId`, `account`, ordered call count, call
+   targets, and call data.
+6. Submit each artifact call through Bankr Wallet API `/wallet/submit` in
+   order. Wait for each submission result before sending the next dependent
+   call.
+7. Verify on-chain state and store one-off run notes under `.context/`.
+
+## Commands
+
+Read the Bankr wallet identity:
+
+```sh
+BANKR_API_BASE="${BANKR_API_BASE:-https://api.bankr.bot}"
+curl -s "$BANKR_API_BASE/wallet/me" \
+  -H "X-API-Key: $BANKR_API_KEY"
+```
+
+Build a Bankr Base mainnet artifact with the local CLI:
+
+```sh
+baseline launch \
+  --mode zrp \
+  --chain-id 8453 \
+  --account "$BANKR_WALLET" \
+  --name "$TOKEN_NAME" \
+  --symbol "$TOKEN_SYMBOL" \
+  --reserve 0x4200000000000000000000000000000000000006 \
+  --total-supply "$TOTAL_SUPPLY" \
+  --output .context/launches/bankr-launch.json
+```
+
+For a `standard` launch, include `--initial-pool-reserves "$RESERVE_SEED"` and
+set `--initial-pool-btokens` below `--total-supply`.
+
+Submit each call in order through Bankr:
+
+```http
+POST /wallet/submit
+X-API-Key: $BANKR_API_KEY
+Content-Type: application/json
+
+{
+  "chainId": 8453,
+  "to": "<call.to>",
+  "data": "<call.data>",
+  "value": "<call.value>"
+}
+```
+
+## Review Checklist
+
+Before any live submission, confirm:
+
+- The user explicitly authorized Bankr live execution on Base mainnet.
+- `BANKR_API_KEY` is set for a live run and is not exposed in tracked files.
+- `/wallet/me` returns an EVM wallet address.
+- `artifact.chainId` is `8453`.
+- `artifact.account` equals the Bankr EVM wallet unless the user explicitly
+  chose another supported policy.
+- The transaction order and count match the selected CLI mode.
+- Transaction targets are limited to the Baseline Relay, precomputed BToken,
+  and reserve token.
+- `zrp` artifacts use all BTokens in the pool and no reserve approval.
+- `standard` artifacts include the intended reserve seed and circulating supply.
+
+## Verification
+
+After a successful live run, perform read-only verification:
+
+- BToken code is non-empty.
+- `bLens.getMaker(bToken).initialized` is true.
+- `bLens.reserve(bToken)` equals the planned chain reserve.
+- `bLens.creator(bToken)` equals the planned creator.
+- `bLens.poolFeeRecipient(bToken)` equals the planned fee recipient.
+- For `zrp`, total reserves and deployer BToken balance are both `0`.
+- For `standard`, deployer BToken balance matches the planned circulating
+  allocation, allowing for integer division.
+
+## Rejection Rules
+
+Stop before live submission if:
+
+- The user has not explicitly authorized Bankr live execution.
+- Base mainnet execution is implied but not explicitly approved.
+- `BANKR_API_KEY` is missing for a live run.
+- `/wallet/me` does not return an EVM wallet address.
+- The artifact is not for chain ID `8453`.
+- The prepared transaction order or count differs from the selected CLI mode.
+- Any requested flow involves raw private keys, seed phrases, local production
+  signing, Bankr native launch endpoints, or Agent API prompts.
+
+## Troubleshooting
+
+- `403`: confirm Wallet API write access, read-only mode, IP allowlist, and
+  absence of `allowedRecipients` restrictions.
+- Base Sepolia requested: use Base MCP for the confirmed Sepolia path, or run a
+  separate authenticated Bankr validation task before enabling Bankr Sepolia.
+- Missing transaction hash: treat the phase as ambiguous and perform read-only
+  on-chain verification before retrying.
+- Partial failure: do not replay the full sequence blindly. Recover from the
+  exact last verified phase.