Binance Trading Signal

Binance Trading Signal Skill

On-chain trading signals and custom signal strategy management. Two modes:

1. Smart Money signals — direct API call, per-trade buy/sell events from tracked wallets
2. Custom Signal strategies — via baw signal CLI, user-created strategies with backtesting

Prerequisites

This skill requires the baw CLI (@binance/agentic-wallet npm package). If baw is not found:

npm install -g @binance/agentic-wallet

Verify: baw --version should print 1.6.2 or higher. If installation fails or the user doesn't have Node.js, inform them that Node.js >= 18 is required.

When to Use

Supported Chains

Chain isolation: Strategies are isolated by chain — cross-chain is not possible. Daily and monthly reports fetch BSC + Solana concurrently by default for comparison.

This table lists chains verified for signal/tracker use; it is a subset of baw wallet chains (which returns all wallet-supported chains, e.g. Arbitrum 42161, Polygon 137). Before treating a chain as unsupported for signals, probe it first — the wallet chain list is dynamic.

Mode 1: Smart Money Signals

Direct HTTP API call — does not require baw CLI.

node <skill-dir>/scripts/cli.mjs smart-money '{"chainId":"CT_501","page":1,"pageSize":50}'

Returns per-trade signals: direction (buy/sell), trigger price, current price, max gain, exit rate, smart money count, token tags.

Response format: { code: "000000", data: [...] } — note this uses code (not success), and code: "000000" means success. This is a direct API call, not a baw CLI command.

Quality indicators: smartMoneyCount ≥ 5 = stronger conviction · exitRate ≥ 70 = smart money exiting, opportunity may have passed · status: "timeout" = stale.

Icon URL prefix: logoUrl is relative — prepend https://bin.bnbstatic.com. chainLogoUrl is already a full URL. Timestamps are ms; maxGain is a decimal fraction (e.g. "0.25" = 25%).

Full field reference: `references/cli.md`

Mode 2: Custom Signal Strategies

All commands go through baw signal CLI. Always pass --json to get structured output for parsing.

Signal Feed

# All sources (concurrent fetch, merged)
baw signal list -c <chainId> --json

# Filter by source
baw signal list -c <chainId> --source user --json      # my strategies only
baw signal list -c <chainId> --source meme --json        # platform strategies only
baw signal list -c <chainId> --source smart-money --json # smart money signals only

# Filter by strategy ID (user strategies only; meme/smart-money are system-level)
baw signal list -c <chainId> --strategy-id <strategyId> --json

# Filter by strategy type (my strategies only: meme-rush | fomo-call)
baw signal list -c <chainId> --strategy-type fomo-call --json

# Sort by max gain, time range filter
baw signal list -c <chainId> --sort-by maxGain --time-range 24h --json

`--strategy-id`: Filters signals by strategy ID. Only USER_STRATEGY signals support this filter (my strategies). MEME_OFFICIAL and SMART_MONEY are system-level signals not tied to a user strategy, so the filter does not apply to them. Use this when a user asks "which signals did my strategy trigger recently" — first find strategyId via baw signal backtest list --all, then filter signals.

`--strategy-type`: Filters USER_STRATEGY signals by type (meme-rush / fomo-call). Only applies to USER_STRATEGY source — MEME_OFFICIAL and SMART_MONEY signals are not filtered. Use this when a user asks "filter by fomo strategy signals" or "filter by meme strategy signals".

signalSource values in JSON output: SMART_MONEY, USER_STRATEGY, MEME_OFFICIAL. When presenting to users, map these to Smart Money signal / my strategies / Platform Strategy per the User-Facing Presentation rules.

Key fields per signal:

Multi-strategy hit detection: The API does not return a hitCount field. To detect multi-strategy hits (same token hit by multiple strategies), group signals by contractAddress after fetching — any token appearing more than once is a multi-strategy hit.

Partial failure handling: When --source all, check data.allSucceeded — if false, warn the user about failed sources (data.failedSources). If success is false (all sources failed), throw an error, don't treat as "no signals".

Source-specific behavior:

• SMART_MONEY: has currentPrice/currentMarketCap directly — no extra call needed for token status
• USER_STRATEGY / MEME_OFFICIAL: for current price, call binance-web3-query-token-info skill

Strategy Management

# Create (estimate → confirm → create)