dCdClutchoperator tool
Operator toolGeneral clearingAn operator running settlement pastes a plan produced by the operator program, lets the browser re-check it, and downloads the unsigned packet.All consoles →

General clearing.

You paste a clearing plan for one of the seven settlement actions — Consider, Freeze, Initialize, Collect, Materialize, Distribute, or Close. The browser re-checks every field and dependency itself, can reacquire the plan's exact chain dependencies, and hands you the unsigned packet. It never signs or submits.

01

Inspect one chain-derived operator plan

The plan is an untrusted projection. The browser requires exact V5 fields, one unsigned packet-bounded v0 instruction, Hot38, CapabilityProgramV4/LifecycleV5 provenance, canonical lifecycle bumps, and action-specific DCE5 child-receipt order. After acceptance, download the unsigned v0 packet; no signing or submission occurs.

No operator plan has been inspected.

02

Reacquire exact chain status

The browser resolves the imported packet’s sole lookup table, rereads every dependency, checks program executability, and hostile-decodes the action’s Trading-owned local state. It does not scan for plausible substitutes.

No RPC request has been made.

03

Verify the commit-last execution receipt

Paste the exact 280-byte HotExecutionAckV3 returned by execution. The browser joins it to the request digest, selected CapabilityProgram, Market generation, root prestate, and release set before showing success.

No commit-last receipt has been supplied.