dCdClutchoperator tool
Operator toolDirect tradeFor traders testing routes: check one trade against live chain state and build its unsigned transactions.All consoles →

Direct
trade.

You name a market and a trade; the console reads the market, its programs, its route, and its release evidence from the chain, then builds one unsigned transaction pair for that trade. If any part of that state disagrees, nothing is built and the reason is named.

01

Acquire the action-selected route

The address map is transport, not truth. Every account is reacquired and joined against the current Registry/Core/Trading state.

No chain state has been read.

02

Price and authorize one atomic fill

Both 172-byte messages carry runtime-u32 outcome coordinates inside the authenticated Trading instruction. The adjacent 222-byte Ed25519 evidence references those bytes by exact offset and assembler-derived instruction index; it never duplicates them. The transaction payer is separate.

Acquire a binding-clean route first. No Market, width, price scale, fee, revision, or authority is fabricated here.

03

Wallet handoff and exact packet export

Connecting reads only identity. Maker and transaction signing are separate explicit wallet requests. Submission is deliberately outside this workbench.

Browser wallet · Wallet Standard · payer / maker identity

No Wallet Standard registry exists in this runtime. Browser wallet discovery is unavailable here.

Connecting reads a public address only. Requesting a signature is always a separate explicit action, and stays unavailable wherever a checked release does not recognize the outer.

Only wallets that register through the Wallet Standard are listed. A wallet that exposes nothing but a legacy injected page provider is not discoverable here and is not silently probed for.

Wallet identitynot connected

No wallet identity has been requested.

Unsigned / signed packetno transaction built

No transaction signature requested.