@baseline-markets/cli 0.2.1 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +86 -2
- package/dist/index.js +1059 -41
- package/package.json +2 -2
- package/skills/baseline-cli/SKILL.md +112 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@baseline-markets/cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -27,7 +27,7 @@
|
|
|
27
27
|
"test:integration": "bun test tests/*.integration.test.ts"
|
|
28
28
|
},
|
|
29
29
|
"dependencies": {
|
|
30
|
-
"@baseline-markets/sdk": "^1.
|
|
30
|
+
"@baseline-markets/sdk": "^1.2.0",
|
|
31
31
|
"incur": "^0.4.8",
|
|
32
32
|
"viem": "^2.31.6"
|
|
33
33
|
},
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: baseline-cli
|
|
3
|
+
description: Guides agents through Baseline CLI workflows.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Baseline CLI
|
|
7
|
+
|
|
8
|
+
Use this skill when a user wants an agent to use the Baseline CLI beyond a
|
|
9
|
+
single command reference. The generated command skills (`baseline-launch` and
|
|
10
|
+
`baseline-info`) document flags; this skill documents the launch workflow,
|
|
11
|
+
artifact contract, validation rules, and execution boundaries.
|
|
12
|
+
|
|
13
|
+
## Launch Workflow
|
|
14
|
+
|
|
15
|
+
Default to building and reviewing an unsigned call artifact. Execute only when
|
|
16
|
+
the user explicitly asks for local signer submission.
|
|
17
|
+
|
|
18
|
+
Show the command surface first when inputs are unclear:
|
|
19
|
+
|
|
20
|
+
```sh
|
|
21
|
+
baseline launch --help
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
Build a ZRP launch artifact:
|
|
25
|
+
|
|
26
|
+
```sh
|
|
27
|
+
baseline launch \
|
|
28
|
+
--mode zrp \
|
|
29
|
+
--chain-id "$CHAIN_ID" \
|
|
30
|
+
--account "$ACCOUNT" \
|
|
31
|
+
--name "$TOKEN_NAME" \
|
|
32
|
+
--symbol "$TOKEN_SYMBOL" \
|
|
33
|
+
--reserve "$RESERVE" \
|
|
34
|
+
--total-supply "$TOTAL_SUPPLY" \
|
|
35
|
+
--output .context/launches/baseline-launch.json
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
## Artifact Contract
|
|
39
|
+
|
|
40
|
+
`baseline launch` writes wallet_sendCalls-compatible JSON:
|
|
41
|
+
|
|
42
|
+
```json
|
|
43
|
+
{
|
|
44
|
+
"chainId": 84532,
|
|
45
|
+
"chain": "base-sepolia",
|
|
46
|
+
"account": "0x...",
|
|
47
|
+
"bToken": "0x...",
|
|
48
|
+
"calls": [{ "to": "0x...", "data": "0x...", "value": "0x0" }]
|
|
49
|
+
}
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Before handing the artifact to any wallet or execution layer, verify:
|
|
53
|
+
|
|
54
|
+
- `chainId`, `chain`, and `account` match the intended wallet and chain.
|
|
55
|
+
- `chain` is the executor chain slug, for example `base-sepolia`.
|
|
56
|
+
- `bToken` is the predicted address, not proof of deployment.
|
|
57
|
+
- `calls` is ordered and every call has `to`, `data`, and `value`.
|
|
58
|
+
- `zrp` has three calls; `standard` has four calls.
|
|
59
|
+
- No `execution` field is present unless the user intentionally used
|
|
60
|
+
`--execute`.
|
|
61
|
+
|
|
62
|
+
After submission, inspect deployment status and links with:
|
|
63
|
+
|
|
64
|
+
```sh
|
|
65
|
+
baseline info "$BTOKEN" --chain-id "$CHAIN_ID"
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
## Launch Modes
|
|
69
|
+
|
|
70
|
+
`zrp` is the default zero-reserve pool launch mode. It derives pool BTokens
|
|
71
|
+
from `--total-supply`, has no reserve seed, and has no reserve approval call.
|
|
72
|
+
|
|
73
|
+
`standard` launches with reserve liquidity and requires both pool BTokens and a
|
|
74
|
+
reserve seed:
|
|
75
|
+
|
|
76
|
+
```sh
|
|
77
|
+
baseline launch \
|
|
78
|
+
--mode standard \
|
|
79
|
+
--chain-id "$CHAIN_ID" \
|
|
80
|
+
--account "$ACCOUNT" \
|
|
81
|
+
--name "$TOKEN_NAME" \
|
|
82
|
+
--symbol "$TOKEN_SYMBOL" \
|
|
83
|
+
--reserve "$RESERVE" \
|
|
84
|
+
--total-supply "$TOTAL_SUPPLY" \
|
|
85
|
+
--initial-pool-btokens "$POOL_BTOKENS" \
|
|
86
|
+
--initial-pool-reserves "$RESERVE_SEED" \
|
|
87
|
+
--output .context/launches/baseline-launch.json
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
## Execution
|
|
91
|
+
|
|
92
|
+
Only execute when the user explicitly asks for local signer submission.
|
|
93
|
+
|
|
94
|
+
Reuse the artifact command and add `--execute --private-key "$PRIVATE_KEY"`.
|
|
95
|
+
`BASELINE_PRIVATE_KEY` may be used instead of `--private-key`. `--account` is
|
|
96
|
+
optional with `--execute` because the CLI can derive it from the private key.
|
|
97
|
+
The CLI sends sequential transactions and returns `execution.transactions`.
|
|
98
|
+
Do not use `--execute` for external executors such as Base MCP; those consume
|
|
99
|
+
`artifact.calls`.
|
|
100
|
+
Never print, commit, or persist private keys.
|
|
101
|
+
|
|
102
|
+
## Defaults And Notes
|
|
103
|
+
|
|
104
|
+
- `--chain-id` must be a chain supported by the installed Baseline CLI/SDK.
|
|
105
|
+
- `--reserve` must be the intended reserve token on that chain.
|
|
106
|
+
- Require explicit user approval before preparing or executing a production
|
|
107
|
+
launch.
|
|
108
|
+
- Swap fee defaults to `1%`; change it with `--swap-fee-pct <percent>`.
|
|
109
|
+
- Creator fee share defaults to `50%`, with the remaining fee share going to
|
|
110
|
+
stakers; change the split with `--creator-fee-pct <percent>`.
|
|
111
|
+
- Creator defaults to `account`; fee recipient defaults to creator.
|
|
112
|
+
- Salt is optional and must be bytes32 when provided.
|