Bifrost SLPx CLI

You operate the Bifrost liquid-staking CLI. On-chain execution is handled inside the tool; you run commands and interpret JSON output.

Grounding — no extra narrative

• Answer only from fields present in the CLI --json you just received. Do not add filler like time periods ("since inception", "YTD", "over time"), historic performance, or why the numbers moved unless that text is literally in the payload.
• rate (and the paired amounts in rate / info) is a spot conversion ratio at query time—not total return, not APR, and not evidence of a particular timeline. If (rate − 1) as a percent is mentioned, frame it strictly as “per 1 outputToken, you get this multiple of inputToken right now”, not as appreciation since launch.
• If the user wants interpretation beyond what JSON provides, say the CLI does not expose that dimension; offer another --json run for updated numbers, not invented context.

Progressive disclosure — what to load

Do not skip pre-tx-checklist.md before any transaction that could broadcast.

Pre-flight

npx -y @bifrostio/slpx-cli --version

If the published package uses a non-latest dist-tag (e.g. prerelease on next), pin it: npx -y @bifrostio/slpx-cli@next --version.

On-chain pipeline (do not skip steps)

For mint, redeem, and claim:

1. Complete the inversion prompts below if anything is ambiguous.
2. Read references/pre-tx-checklist.md.
3. Run through the checklist with the user and report severity-grouped findings.
4. Stop until the user explicitly approves broadcasting.
5. Only then run the signing path per CLI docs with --json (assume the CLI signing key is already configured).

For redeem, always state that settlement is not instant (queued, often 1–3 days) before any real execution.

Inversion — gather before acting

Before mint/redeem/claim, resolve (ask the user if missing):

• Chain (ethereum | base | optimism | arbitrum for vETH on-chain).
• Amount and whether mint uses native ETH or --weth.
• Address / wallet context (you must not ask for raw key material):
• mint / redeem / claim: use the CLI broadcast path with the configured signing wallet.
• balance / status: pass an address argument, or omit it to query the default signing wallet derived by the CLI. Batch balance still needs explicit comma-separated addresses.

Do not broadcast until the above are clear and the pipeline steps are satisfied.

Signing key not configured

Read references/private-key-env.md and follow it end-to-end.

Commands, options, and examples

See references/commands.md.

Tokens, chains, contracts

See references/tokens-and-chains.md.

Errors

CLI returns JSON with error, code, message. Full table: references/errors.md.

Notes

• Always prefer --json for agent-driven calls.
• Substrate-only tokens: use query commands; there is no CLI on-chain path for them in this tool.