dCdClutchoperator tool
Operator toolProduct studioA market author writes a payoff curve as exact fractions, compiles the canonical record, and reads back precisely what each outcome pays.All consoles →

Product studio.

You write the payoff as exact fractions — signed knot numerators over one shared denominator, with constant, ramp, and tent terms. Nothing is rounded until the one defined boundary: the final floor into payout atoms. The studio compiles the canonical record and shows you exactly what it denotes.

01

Compile one canonical Product V2 record

No market or deployment is implied. This first stage owns only exact semantic data and its content identity.

No Product has been authored or compiled.

03

Compose one Runtime V2 admission request

These digests are not the payoff identity above. They are the content digests of three Registry-finalized records — the Product record, its result domain, and its portfolio — which the deployed adapter authenticates for owner, PDA, hash, rent exemption and staging vacancy at its own boundary. This stage composes the request and derives the receipt address the program itself recomputes. It reads no chain and submits nothing.

One magic, two wires DCLTPRQ2 names both this live 112-byte admission request and a dead evaluator request of the same width. The dead one wrote 1 at byte 10; this decoder requires zero across bytes 10..16. Every coordinate here is generated from the live crate, never restated.

Frame Exactly nine accounts, all distinct: a writable program-owned receipt, the executable Registry, six read-only record accounts, and the rent sysvar. A duplicate or a wrong count is refused here rather than on chain.

No admission request has been composed.