Docs / Integrations / Adapters

BNB Chain Adapter

Governor is the chain-agnostic governance control plane for agent execution. The BNB adapter translates and enriches BNB transaction intents, but Governor remains the sole authority for ALLOW / DENY decisions and evidence.

Purpose

The BNB adapter governs BNB transaction intents before signing or execution. It normalizes wallet, contract, token, gas, slippage, and simulation metadata into Governor's canonical crypto intent model.

Integration module role

Translate BNB-specific payloads into Governor's canonical crypto intent model.
Require simulation and normalized risk metadata before evaluation.
Send normalized intents to Governor for central policy decisions.
Stage the later decision-bound execute flow without exposing a bypass.
Stage receipt and evidence mapping for the next slice after active runtime wiring.

Structural guarantees

1. No local policy engine

The adapter never makes its own allow decision.

2. Fail closed

Missing simulation, unknown scope, unknown runtime, or ambiguous transport returns deny.

3. No bypass path

No broadcast or execution happens outside Governor’s decision flow.

4. Dry-run first

Dry-run and simulation-first behavior remain the default safe path.

5. Evidence-backed

Every decision carries audit metadata and normalized evidence fields.

Supported action classes

CHAIN_TRANSFER
TOKEN_APPROVAL
CONTRACT_CALL
DEX_SWAP
BRIDGE_TRANSFER
STAKING_ACTION
TREASURY_PAYOUT
WALLET_CONFIG_CHANGE
SIGN_MESSAGE
ORACLE_JOB

Canonical BNB scopes

bnb_chain_transfer_execute, bnb_token_approval_execute, bnb_contract_call_execute, bnb_dex_swap_execute, bnb_bridge_transfer_execute, bnb_staking_action_execute, bnb_treasury_payout_execute, bnb_wallet_config_change_execute, bnb_sign_message_execute, bnb_oracle_job_execute

Public API

POST /adapters/bnb/register

Registers a BNB execution runtime under Governor.

POST /adapters/bnb/intent

Translates raw BNB context into the canonical crypto intent, validates metadata, requires simulation, and requests a Governor decision.

Tier: Tier 5 · Blockchain
Adapter ID: bnb_chain
Product role: Integration module / adapter

Fail-closed requirements

Unknown fields are denied before policy.
Missing simulation is denied.
Failed simulation is denied.
Unknown contracts are denied unless explicitly allowlisted by policy.
Unlimited approvals are denied.
No execution is allowed without prior Governor approval.

Example intent

{
  "tenant_id": "acme",
  "runtime_id": "bnb-runtime-01",
  "agent_id": "agent-bnb-01",
  "intent": "swap_wbnb_to_usdt",
  "tool": "bnb.swap",
  "requested_scopes": ["bnb_dex_swap_execute"],
  "requested_budget": 0.0,
  "work_type": "execution",
  "context": {
    "action_class": "DEX_SWAP",
    "wallet_address": "0xabc...",
    "chain": "bnb",
    "network": "mainnet",
    "target_address": "0xrouter...",
    "method_selector": "0x38ed1739",
    "asset_in": {"symbol": "WBNB", "address": "0x..."},
    "asset_out": {"symbol": "USDT", "address": "0x..."},
    "amount_value": "1.25",
    "max_slippage_bps": 100,
    "deadline_utc": "2026-04-06T15:00:00Z",
    "simulation": {
      "success": true,
      "gas_estimate": 210000,
      "native_value": "0",
      "token_movements": [],
      "approval_delta": [],
      "state_changes": [],
      "warnings": []
    },
    "risk_metadata": {
      "known_contract": true,
      "verified_token": true,
      "first_time_recipient": false,
      "high_value_tx": false,
      "unlimited_approval": false,
      "cross_chain": false,
      "protocol_type": "dex"
    }
  }
}

Example policy

TOKEN_APPROVAL with unlimited allowance → deny
DEX_SWAP above allowed slippage → deny
CONTRACT_CALL to unknown target → deny
BRIDGE_TRANSFER to unapproved destination → deny
TREASURY_PAYOUT above threshold without approval → deny

Current implementation status

Implemented now

Canonical crypto action classes, canonical crypto intent schema, BNB adapter registry, POST /adapters/bnb/register, POST /adapters/bnb/intent, and deny-on-missing-simulation.

Planned next

BNB simulation backend abstraction, approval/slippage/contract/bridge policy hooks, decision-bound execute flow, and receipt retrieval with evidence mapping.

Commercial note: BNB is a strategic differentiation lane today. The primary revenue motion is enterprise execution governance across GitHub, AWS/Kubernetes, and HTTP/OpenClaw workflows.

Implementation spec