/binance-onchain-copy-trader

name: binance-onchain-copy-trader
description: |
  Scaffold for assembling on-chain copy-trading strategies on Binance Agentic Wallet. Wires the
  existing capabilities — address monitoring, signal subscription, address scoring, token audit,
  order placement, on-chain take-profit/stop-loss — into one runnable pipeline, and exposes every
  strategy decision as a hook. Ships no strategy of its own.
  Trigger on: copy trade, copy trading, follow smart money, follow a wallet, mirror trades,
  copy-trade bot, auto-buy on signal, monitor a wallet and trade, smart money copy trading,
  signal-driven trading, pick addresses to copy, copy-trade strategy, copy-trade status,
  copy-trade post-mortem.
  NOT for: single manual trades (use binance-agentic-wallet), signal queries alone
  (binance-trading-signal), address analysis alone (binance-wallet-tracker / binance-leaderboard).
metadata:
  version: '0.6.0'
  requiredCliVersion: '1.9.1'
  requires:
    skills:
      - binance-agentic-wallet
      - binance-wallet-tracker
      - binance-leaderboard
      - binance-trading-signal
      - query-token-audit

Binance On-Chain Copy Trader

A scaffold for a copy-trading pipeline. **This skill provides no strategy.** What it provides is: a capability index, an event contract, an assembly structure, and three strategy hooks. The strategy itself is yours to build and refine.

> ## Read this first > > **Every risk control, position-management scheme, and parameter value in this skill is a > *suggestion* and an *example*. None of it is mandatory, and none of it constitutes a safety > guarantee or investment advice.** > > - The scaffold guarantees only that **it will run the checks you configure**. It does not > guarantee those checks are sufficient to protect your funds. Budget caps, stop-loss distance, > liquidity floors — you choose all of them. Set them wide, leave them out, or switch off the > honeypot block, and the scaffold will do exactly as told. > - The three bundled hooks are a **minimal reference implementation that proves the pipeline > runs**. They are not a recommended strategy and carry **no evidence of positive expectancy**. > Running them live as-is means funding an unvalidated strategy with real money. > - On-chain transactions are irreversible. Any automated strategy can lose money through market > conditions you did not anticipate, changes in platform behavior, or defects in this scaffold. > **The risk is yours.** > - Suggested path: run `dry-run` long enough to matter → read `events.jsonl` and build your own > baseline → switch to `live` with an amount you can afford to lose entirely → tune from there.

Dependencies

Confirm the following skills are available in your current environment. This skill only orchestrates; every underlying capability comes from them:

| Skill | Provides | Used here | |---|---|---| | `binance-agentic-wallet` | Wallet, market orders, limit orders, quota, chain info | `wallet` `market-order` `limit-order` | | `binance-wallet-tracker` | Address monitoring, real-time push, group management | `tracker ws` `tracker token/tx` `tracker group/address` | | ↳ | Must include the **Connection lifecycle** and **Signal field nullability** sections — this skill's connection-supervision split and its first-push field assumptions depend on them directly | — | | `binance-leaderboard` | Trader rankings, address scoring, holder lookup | `leaderboard query/analyze/alpha-radar` | | `binance-trading-signal` | Smart-money signals, custom strategies, backtests | `signal list` `signal strategy` `signal backtest` | | `query-token-audit` | Token security audit | Audit HTTP endpoint | | `query-token-info` | *(optional)* Live token price and market data | Only if a hook needs a live price when the event does not carry one |

Verify:

baw --version
baw cli-check --required-version "$(grep -m1 requiredCliVersion SKILL.md | tr -dc '0-9.')" --json
#   ↑ the frontmatter `requiredCliVersion` is the single source of truth for the version floor.
#     Below it, `tracker ws --duration 0` has no keepalive and no reconnect, and the scaffold
#     refuses to start.

Missing any one of them disables the corresponding stage: without `binance-leaderboard` there is no systematic way to pick addresses; without `binance-trading-signal` you cannot create custom signal strategies; without `query-token-audit` there is no audit data and `hard_gate` falls back to `require_audit` to decide whether to pass or reject.

Install source: `https://github.com/binance/binance-skills-hub`

Getting started

The order that takes you from nothing to a scored dry-run. Each step points at the section below.

**Note the ordering.** Writing the strategy comes *after* the first dry-run, not before. That is deliberate: the whole premise of this scaffold is that thresholds should come from your own data, and before the first run you have none. So the first pass runs the bundled reference hooks unchanged — not because they are any good, but because they produce the dataset you need in order to write something better.

**1 · Environment check** → see "Pre-flight checks" Confirm the wallet is CONNECTED, the target chain supports both `market-order` and `limit-order`, and that quote-token and gas balances are sufficient. On a chain where `limit-order` is unavailable you cannot place on-chain protective orders — accept that before continuing.

**2 · Pick your trigger sources** → see "Trigger sources" Address subscription, signal subscription, or both. This determines how you select sources next.

**3 · Select sources**

• Address source: `leaderboard query` for candidates → `leaderboard analyze` for the 6-dimension

score on each (`follow_friendly` is the most relevant dimension here) → write addresses into `addrs.txt`, one per line, `#` for comments, **max 100**

• Signal source: `signal explore` to browse official strategies / `signal strategy create` to

build your own / `signal strategy fo