QCLAW × Binance Agentic Wallet

BULLSHIT Mint Guide

This site teaches the flow. It does not connect a wallet, replace an agent, or initiate a transaction. Install QClaw first, then give it this tutorial link; every write still requires a Binance Agentic Wallet Preview and your explicit confirmation.
BULLSHIT mascot
01

Actor: You · Duration: 5 minutes

Prepare your computer and open a terminal

Prerequisites

  • A computer you control
  • Binance App installed and signed in

Actions

  1. On Windows, open PowerShell first: open Start, search for PowerShell, and launch Windows PowerShell or Windows Terminal. You can also press Win + R, type powershell, and press Enter. A regular window is enough; administrator access is not required.
  2. If Node.js is not installed, download and run the Windows .msi installer below. Do not install Node.js with Chocolatey, nvm, or a PowerShell command. After installation, close and reopen PowerShell, then run the two checks below. The Node.js installer includes npm.
  3. The BULLSHIT Skill includes its own Node.js chain helper, so Foundry and cast are not required.
  4. Keep a small BNB balance for BSC gas and the mint fee.

Official installers

Direct Node.js installer for Windows x64Direct Node.js installer for Windows ARM64Official Node.js downloads (other systems)
node --version
npm --version

Expected result

Node.js and npm both run in the local terminal.

Completion criteria

Your tools, Binance App, and BNB are ready.

Failure and recovery
  • After installing Node.js on Windows, reopen PowerShell and rerun the two checks.
  • Install only from the official link above; never download an unknown exe, script, or archive from chat messages.
  • Stop if BNB is insufficient; never ask a website or stranger to top up.
02

Actor: You · Duration: 5–10 minutes

Install the Binance Agentic Wallet CLI and both Skills

Prerequisites

  • npm is available

Actions

  1. Install the Binance Agentic Wallet CLI, the official Binance Agentic Wallet Skill, and the BULLSHIT Skill in a local terminal. The official Binance Agentic Wallet Skill uses a pinned ZIP archive, so Git is not required.
npm install -g @binance/agentic-wallet@1.8.0
npx --yes skills@latest add https://codeload.github.com/binance/binance-skills-hub/zip/7e9cf9b31e5bead4cac7f368e5be9f36cf8f8173 --skill binance-agentic-wallet --agent openclaw --global --copy --yes
npx skills add https://codeload.github.com/Lin-wool/bullshit-agent-mint/zip/eb08da14e82bd507435f5f4a082429b6a3ad1be6 --skill bullshit-agent-mint --agent claude-code --global

Expected result

The Binance Agentic Wallet CLI, the official Binance Agentic Wallet Skill, and the BULLSHIT Skill are installed.

Completion criteria

All three installation commands exit successfully.

Failure and recovery
  • For npm network or permission errors, retain the original error, fix it, and rerun the same command.
  • If a Skill requires an update, follow its official instructions and reread it.
03

Actor: You + Agent + Binance App · Duration: 3–5 minutes

Start the Agent and connect Binance Agentic Wallet

Prerequisites

  • Both Skills are installed
  • Binance App is signed in

Actions

  1. Start the Agent you are using on your computer.
  2. Give the Agent the prompt below. It checks Binance Agentic Wallet network access first and reuses HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY. On Windows, it can read an enabled Windows system proxy when no proxy environment variable exists, without scanning ports. After the check passes, the Agent opens the Binance login page automatically and waits in the foreground; you only compare the Pairing Code and confirm in Binance App.
Check the Binance Agentic Wallet CLI, the official Binance Agentic Wallet Skill, and the BULLSHIT Skill. Before signing in, run this Skill's baw-network.mjs check and prefer HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY inherited by the current Agent process. On Windows, read the enabled Windows system proxy if those variables are absent. Do not run a bare baw auth signin, scan proxy ports, change DNS, or retry in a loop. After the check passes, use the unified signin entry, open the Binance login page automatically, and wait for verification in the foreground. Only ask me to compare the Pairing Code and confirm in Binance App; do not ask me to parse the sign-in response.

Expected result

The Agent completes preflight, the wallet is connected, and BSC Mainnet plus Developer Mode are ready.

Completion criteria

The Agent can call the local Binance Agentic Wallet CLI and the wallet is CONNECTED.

Failure and recovery
  • If the network check fails on Windows, enable the system proxy in your own proxy app and restart the Agent. On other systems, configure your own HTTP(S) proxy before starting the Agent. Never let the Agent guess ports, change DNS, or retry repeatedly.
  • If the QR expires or mismatches, ask the Agent to discard the old sign-in and rerun the unified signin flow; never reuse the old code.
  • If Developer Mode or BNB is not ready, follow the Agent's guidance in the App.
04

Actor: QClaw + your confirmation + Binance Agentic Wallet · Duration: 5–15 minutes

Let the Agent complete Register and Mint

Prerequisites

  • Wallet is connected
  • Agent preflight passes

Actions

  1. Give QClaw the prompt below. The Agent skips or performs Register based on eligibility, then asks for a Mint quantity. Every transaction is Previewed first and broadcast only after your explicit confirmation while the authorization is still valid. Each Slot is 100,000,000 BULLSHIT at 0.001 BNB.
Using the BULLSHIT Agent Mint Skill, check my eligibility. If Register is needed, Preview it, show the fee, gas, and risks, and wait for my explicit confirmation; check that the authorization has not expired before execution. After Register, read the Mint status and ask for an integer quantity from 1 to 10. Mint must also be Previewed first; show contract 0xdafDB323109B110A84a081009ca49F7df5c52D28, quantity, fee, gas, receipt, and risks, wait for explicit confirmation, and execute only while the authorization is valid. If execution returns a network error, check pending transactions and on-chain state first; never execute again blindly. Verify receipt after completion. Do not ask me to run low-level commands manually.

Expected result

Register (if needed) and Mint complete, the received amount matches the Slots, and a transaction hash with a https://bscscan.com link is shown.

Completion criteria

After your explicit confirmation, the Agent completes and verifies the transaction.

Failure and recovery
  • For a pending transaction, act in Binance App and wait; never execute again.
  • If the Preview expires, reread on-chain state, Preview again, and wait for your confirmation again.
  • If Execute returns a network error, check pending transactions and on-chain state first. Stop after rejection or an on-chain failure; never auto-retry or rebroadcast.