BBF Mint CLI

Mint BNB Burn Forge tickets on BSC using Binance Agentic Wallet. Requires Node.js 22+, an eligible Agent ID, USDT for mint fees and BNB for gas. The contract currently allows up to 30 successful tickets per transaction, at 0.01 USDT each.

Install from GitHub

npm install -g @binance/agentic-wallet
npm install -g git+https://github.com/bbforge-ai/bbf-mint-cli.git
baw auth signin
bbf-mint wallet

The GitHub version is 3.4.5. Check npm separately before installing that version from the registry.

Run a budget efficiently

bbf-mint rpc --rpc "https://your-bsc-rpc.example"
export BBF_RPC="https://your-bsc-rpc.example"
bbf-mint blocks --page 20 --size 36
bbf-mint batch --budget 100 --group 30 --start-page 20

The batch command asks for confirmation. AI agents may add --yes after the user has approved the wallet, USDT budget, allowance and extra BNB gas.

Choose a start page from 1 to 100. Page 1 contains the highest-burn remaining blocks. Later pages may encounter less competition and yield lower burn rewards. The CLI fetches fresh candidates at the selected page for each group and includes backup candidates within the contract limit. It preserves the page in the budget journal so a resumed run follows the same selection policy. mint --tickets 30 --start-page 20 also supports later-page selection. Explicit --blocks takes precedence over automatic selection.

The default proof cache reuses verified manifests, burn ranges and Merkle nodes. Each prepared proof must still match the on-chain root. The budget run approves the exact remaining USDT budget when allowance is insufficient, then submits groups of up to 30. Each transaction is previewed, journaled and reconciled before the next group. Execution speed depends on the wallet, RPC, proof service and BSC confirmations. This release has no multi-transaction no-wait pipeline.

Monitor, recover and stop

bbf-mint history --json
bbf-mint resume
bbf-mint batch --continue

resume settles the active transaction. If a wallet response has no hash, inspect baw wallet tx-history --binanceChainId 56, identify the transaction matching the saved intent and run bbf-mint resume --hash 0x.... Keep unresolved submissions pending. Never resend or remove the journal to get around pending state or a budget limit.

Press Ctrl+C once in the running batch to stop after its current group. Wait for it to exit, then close an unfinished run with bbf-mint batch --stop. Submitted transactions can still settle. Avoid running multiple writers against the same wallet or journal.

Instructions for your AI

Use BBF Mint on BSC with my Binance Agentic Wallet. My mint budget is 100 USDT. Confirm the wallet, allowance and gas with me first. Use start page 20 and groups of 30. Keep the proof cache enabled and use my locally configured RPC. Report confirmed tickets, confirmed USDT spent, pending state and the last transaction hash every minute. Reconcile stalled transactions before continuing. Stop when the budget is spent or when I ask you to stop.

Read SKILL.md for wallet checks, approval and recovery rules. Reports require an agent monitoring the process. The CLI logs each group as it progresses.

Commands

| Command | Purpose | | --- | --- | | status | Market and published-batch state | | wallet | Wallet identity, eligibility and balances | | rpc --rpc URL | Check a custom BSC endpoint | | blocks --page N --size N | List candidates | | mint --tickets 30 --start-page 20 | Mint automatically selected candidates | | mint --blocks HEIGHT,HEIGHT | Mint specific heights | | batch --budget 100 --start-page 20 | Run a journaled USDT budget | | prepare --from ADDRESS --blocks HEIGHT | Prepare unsigned calldata | | history --json | Inspect local progress | | resume [--hash HASH] | Settle an unresolved transaction |

BBF_RPC accepts comma-separated URLs. Verified custom endpoints are tried first with the bundled public BSC endpoint as fallback. The wallet submits transactions. Store RPC keys locally and redact them in reports.

Proofs use https://bbforge.si/snapshots/. The CLI caches up to 256 MiB of verified proof files under ~/.cache/bbf-mint/proofs-v1 by default. Options include --proof-cache-dir PATH, BBF_PROOF_CACHE_DIR and --no-proof-cache.

Development

npm ci
npm test
npm pack --dry-run

Offline tests exercise proof-source handling and candidate selection. Live read-only checks can verify proof and contract compatibility. Financial execution requires the user's wallet approval.