dCdClutchclusteroperator tool

Operator toolRelease activationAn operator with a checked build activates it against the Registry: drop the build's evidence files, review the plan derived from chain state, sign five packets — one per role.All consoles →

Release activation.

A checked release is the evidence bundle the release pipeline produces to prove exactly which code a deployment runs. You drop that bundle's files below; the console checks them against the Registry and the code actually loaded on chain, and builds the activation packets only when every identity agrees. Every file and every chain answer is treated as hostile until it proves itself.

01

The chain, the Registry, and who pays

Everything below is checked against this chain. The console never reads a wallet on its own; the payer is a public key whose signature stays outside this page.

Finalized RPC endpointThe chain to activate against — your local validator by default.Registry program addressAlready deployed on the chain — from your deployment plan (plan.json, written by the bootstrap producer).Fee payer public keyConnect a wallet in step 03 to fill this, or paste an address whose keypair you hold elsewhere.

02

Load the checked build and derive the activation walk

All six files below come out of one run of the checked-release pipeline (tools/release/checked-release-candidate.sh). The console rebuilds their authorities, derives the finalized record, staging, and cache addresses, and checks the code currently loaded on chain before constructing one exact ten-account action per role. Activation admits one role per transaction, so a full walk is five separate packets, not one.

Checked multiprogrammultiprogram.checked in the pipeline's output — the five-role evidence set, exactly 1,592 bytes.

Drop the file here, or click to choose itOffline fallback · paste the same file as base64

nothing loaded yet

core · complete checked releaseevidence/core/checked.bin in the same pipeline run.

Drop the file here, or click to choose itOffline fallback · paste the same file as base64

nothing loaded yet

claims · complete checked releaseevidence/claims/checked.bin in the same pipeline run.

Drop the file here, or click to choose itOffline fallback · paste the same file as base64

nothing loaded yet

trading · complete checked releaseevidence/trading/checked.bin in the same pipeline run.

Drop the file here, or click to choose itOffline fallback · paste the same file as base64

nothing loaded yet

resolution · complete checked releaseevidence/resolution/checked.bin in the same pipeline run.

Drop the file here, or click to choose itOffline fallback · paste the same file as base64

nothing loaded yet

custody · complete checked releaseevidence/custody/checked.bin in the same pipeline run.

Drop the file here, or click to choose itOffline fallback · paste the same file as base64

nothing loaded yet

Activation compute-unit limit

No manifest or chain request has been made.

03

Sign the walk with a browser wallet

Connecting reads identity only. Signing opens for exactly one reason: the activation plan built in step 02 went green against this chain, and the connected wallet is the fee payer that plan declares. Each role is a separate explicit wallet request, and submission stays outside this page.

Browser wallet · Wallet Standard · Registry activation fee payer

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.

Signing gateclosed

No activation plan is green against this chain. Signing stays closed. It opens only when one activation plan is green against this chain and the connected wallet is exactly that plan’s declared fee payer.

No activation plan has gone green against this chain, so there is nothing a signature could mean here. Build one in step 02 first.

There is no submit path here, signed or unsigned. A signed packet leaves this application as bytes for an external submitter, and the finalized blockhash it was compiled against will expire.