Strategy signals: plan a BNB Smart Chain wallet's orders
The two strategy signals plan routes, POST /signals-orders/exit/plan and POST /signals-orders/rebalance/plan, now take chain: "bnb" and plan the orders for a wallet on BNB Smart Chain. The plan reads the wallet's Ondo and xStocks positions and its Binance-Peg USDC, and tells you which token approvals are missing. Nothing changes for a caller that does not send chain: "bnb".
What changed
chain: "bnb" on the plan routes. Send chain: "bnb", eth_wallet in place of sol_wallet, and an ownership proof carrying eth_signature. The response has the same shape as on Solana, with usdc_available the wallet's Binance-Peg USDC.
- The inline routes stay Solana only.
POST /signals-orders/exitandPOST /signals-orders/rebalancerefusechain: "bnb"with400 invalid_request. Quote each planned order yourself withchain: "bnb"andprotocol: ["ondo", "xstocks"], and submit each on its ownPOST /trade/submit, never as a batch. - Always pin
protocolon those quotes. The plan reads Ondo and xStocks only. An unpinnedbnbquote can route to bStocks, and a name held as bStocks reads asnot_held: a rebalance buys its full target again, and an exit leaves it in the wallet. approvals. A bnb plan lists one row for USDC when it buys and one per token a planned sell spends, each withtoken,spenderandapproval_required.truemeans approve before submitting,nullthat the allowance could not be read. It is advisory: no approval is built for you.- Venue minimums. On bnb,
below_min_notionaluses each name's venue floor ($10 for a name on xStocks alone, $1 otherwise) and also applies on an exit plan. A scaled buy is held to its floor, so a smallamount_usdcover many names can plan no buys, with no error. - A new skip reason,
price_unavailable, on a bnb exit plan only: a held name with no price. - No quote-call cap on bnb. The 25-order cap applies.
Smaller changes on Solana.
- The request schemas no longer list
sol_walletas required, since a bnb body omits it. A Solana body still needs it. - A body with neither
chainnorsol_walletis still400 invalid_request, with a differentmessage.
What to do
- Nothing, if you plan Solana wallets only.
- If you model
skipped[].reasonas a closed set and plan to sendchain: "bnb", addprice_unavailable. - The guide is Strategy Signals: On BNB Smart Chain, with a worked example in Copying a Strategy on BNB Smart Chain.