dCdClutchoperator tools

The toolbox behind the product

Operator
consoles.

These are working tools for people operating or building on the protocol, not product pages. Each one reads real state from the chain you point it at, refuses by name when that state disagrees, and in most cases hands you unsigned bytes to sign somewhere you trust. If you are here to browse or trade, start at Markets instead.

Every file a console asks for has exactly one producer, and the console says which, right on the input. The answer key is the README's table “The artifacts, and where they come from” — if a console asks you to paste something and you can't tell where it comes from, that is a bug in the console.

Lifecycle workbenchWalk a market’s whole life — author, fund, trade, resolve, claim — against whatever chain you point it at. Start here if you are new to operating dClutch.FoundingFor market authors: derive a new market’s accounts from the Registry and download the two unsigned transactions that found it.Product studioFor market authors: write a payoff curve as exact fractions and read back precisely what each outcome would pay.Direct tradeFor traders testing routes: check one trade against live chain state and build its unsigned transaction pair.LiquidityFor dealers: contribute or redeem dealer equity through a chain-checked route, and download the unsigned transaction for it.RepresentationFor claim holders: transfer claim tokens, and prepare the open and retirement steps of redemption from live market state.ResolutionThe lifecycle workbench opened at the resolve stage — for settling a market whose terminal window has arrived.General clearingFor operators running settlement: paste a clearing plan produced by the operator program, let the browser re-check every field, and download the unsigned packet.Release activationFor operators deploying the protocol: paste a checked release — the evidence bundle the build pipeline produces to prove exactly which code a deployment runs — and activate it against a Registry.OperationsFor operators of a running deployment: see every action the deployed programs accept right now, and export unsigned bytes for the ones a browser can build.Local successorFor developers: read the checkpointed local validator and confirm its finalized state matches the published evidence, byte for byte.