Silence Settles the Job. Dispute Flips the Escrow.

If the inspector never shows, the invoice clears. That is not a bug in this design. That is the design.

BNB Chain’s Agent SDK — still marked under active development, breaking changes expected — has two separate machines. One is a name badge for agents (ERC-8004). The other is the cash register (ERC-8183). The register is the story. You lock money for a job. The worker posts a fingerprint of the deliverable. A clock starts. Say nothing, they get paid. Fight it, and a room of pre-approved voters can send the money back.

The mechanism

Think of a small escrow account that only knows three moods: funded, finished, fought.

The kernel contract (AgenticCommerce) holds the job and the money. A router (EvaluatorRouter) picks the rulebook for that job. Anyone can poke settle when the clock is done — you do not need a priest to close the books. The default rulebook (OptimisticPolicy) is the construction-inspector trick: silence past the dispute window is an approve. If the client disputes, a whitelist of voters has to muster enough “reject” votes to flip it.

The happy path, from BNB’s own docs: agents haggle off-chain → client opens a job and funds it → worker submits a hash of the work (the file stays off-chain; only the fingerprint hits the chain) → the dispute window runs → nobody speaks → complete pays the worker, minus a small platform cut. If the job just rots past expiredAt, claimRefund is the fire exit. That hatch cannot be paused.

settle being permissionless is the ops detail people will skip. Run a script that closes jobs. Do not wait for BNB to appoint a closer.

The name badge and the register do not depend on each other. 8004 is handy for discovery — an identity token and a profile — but you can take and finish 8183 jobs without it. On BSC testnet and mainnet, 8004 registration is gas-free via MegaFuel. Nice. Not the cash register.

Secondary blogs have been pushing an “ALP v0.4” draft as if it were the spec. We are reading the official SDK. Treat the blogs as noise.

What the numbers mean

The docs specify the machine. They do not tell you how many jobs have settled, how often anyone disputes, or what quorum shops actually run. Product state is “under active development,” in BNB’s own words. We are not inventing a volume number.

The design choice that matters is who pays for laziness. The client who does nothing pays. The client who wants a refund has to wake voters. Quiet clients and sleepy voters are both failure modes. That is not a slogan. That is where this will break.

The operator lesson

If you are about to let agents pay each other on BNB, read the clock before you read the identity NFT. Negotiate. Fund. Post the hash. Assume silence completes. Staff a dispute path you can actually man. Run settle yourself. Keep the expiry refund as the universal escape.

Name badge is optional. Cash register is not. Pin your SDK version until they call it stable.

Sources

• BNB Chain docs, “BNB Agent SDK” (ERC-8004 + ERC-8183) — https://docs.bnbchain.org/developer-kit/bnbagent-sdk/
• Repository — https://github.com/bnb-chain/bnbagent-sdk