dCdClutchoperator tool
Operator toolRepresentationA claim holder transfers claim tokens, or prepares the open and retirement steps of redemption from live market state.All consoles →

Claims &
redemption.

Claim tokens are ordinary tokens: you can transfer them today, and the transfer route is selected from the market's own on-chain state. Opening a representation and retiring a receipt produce unsigned candidates below; where a step is not executable yet, the console says exactly what is missing.

00

Successor route truth, without pretending incomplete Hot paths execute

Transfer is the normal Token-2022 instruction. Wrap/open/redeem/retire are distinct privileged lifecycle actions; this interface will expose them only from their finalized SetV2/CapabilityV4 operators.

Bearer transfertransaction-completeexact TransferChecked · v0 + ALT
Rational openchain-derivedfour CapabilityV4 actions · packet bounded
Terminal redeemSBF-testedbrowser payout projection · Rust-emitter gated
Receipt retirementpacket-completeclosure only · signing release-gated
01

Derive and authenticate one transfer route from chain state

The selection record address is not caller input. It is derived from CoreStateV2's immutable Realm and release-set identities, then checked as exact finalized Registry content. Mint and holder state come only from finalized RPC accounts.

No Market or Token-2022 state has been read.

02

Construct one exact unsigned v0 transfer

Enter raw base-unit atoms. Even when the Mint advertises 255 decimals, this field remains a canonical u64 integer; the decimals byte is copied only into Token-2022's checked instruction.

Authenticate one finalized TokenBehaviorSelectionV2 route first.

03

Wallet handoff and exact packet export

Connecting reads identity only. Signing is a separate explicit action. Distinct payer/authority packets remain valid but are exported for multisigner coordination; nothing is submitted here.

Browser wallet · Wallet Standard · payer / transfer authority

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 packet built

No automatic submission or hidden retry.

04

Open native shards or a Structured receipt from one Product graph

Denominate, reconstitute, issue, and unwrap share one variable-width family. The browser independently derives representation width K, terminal-result width N, coefficients, Mints, custody, Positions, replay revisions, and physical aliases from finalized chain state; users choose only an action and raw-atom quantity.

Selected routes36 logicalone representation coordinate
Structured routes32 + 4Kzero coefficients remain zero-delta rows
Economicsraw u64display decimals never scale values
Executionrelease-gatedcompile/export; signing disabled
05

Hostile-decode one exact CapabilityV4 open route

The descriptor digest and action are discovery coordinates, not economic authority. SetV2 selects the 600-byte CapabilityV4; that record selects TokenBehaviorV2 and all six finalized artifacts before Product and Claims state can enter the request.

Browser wallet · Wallet Standard · payer / actor 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.

No wallet identity has been requested.

No Rational open route has been read.

06

Attempt the real Solana packet bound, then stop at the release gate

Every action is compiled into its exact Hot family and Claims child. v0+ALT construction either produces a packet at or below 1232 bytes or refuses with its actual encoding/size reason. A packet is evidence, not permission to sign an unattested outer.

Authenticate one finalized CapabilityV4 route first.

07

Read a real terminal payout without forging Custody authority

The terminal winner belongs to Core. ProductBasisV3 may define K claim curves over a different N-way result partition. This browser rechecks that immutable semantic join and displays exact raw payout, including zero.

Result widthNProduct-owned terminal partition
Claim widthKrepresentation basis; need not equal N
Losing claimzero is validno fake one-atom Custody transfer
SubmissionRust-emitter gatedno parallel TypeScript digest authority
08

Authenticate CapabilityV4 and evaluate Product terminal semantics

The browser derives the selected basis record from fixed-frame content addressing, checks its Product/domain semantic identity, and follows Core's authenticated rational coordinate only when the resolved scenario requires one.

Browser wallet · Wallet Standard · payer / actor 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.

No wallet identity has been requested.

No terminal Product/representation state has been read.

04

Retire a zero-supply Structured receipt from descriptor truth

The wallet never supplies N, K, outcomes, coefficients, custody owners, Position addresses, or rent arithmetic. The browser derives them from finalized Product, descriptor, Claims, Token-2022, and lifecycle-scoped RentCreditV2 state.

Family wirefixed 400DCRLHC04 · RetireReceipt only
Claims frame20 + 4SS is ordered nonzero support within representation K
Payoutnoneclosure only; not a payout route
Executionrelease-gatedcandidate/export complete · signing disabled
05

Reacquire one exact compact route

The 38 lines are account transport for the universal Hot frame, not caller-authored authority. Their root selection, ProgramSet, CapabilityV4, finalized artifacts, Product graph, and activated programs are hostile-decoded before any candidate exists.

Browser wallet · Wallet Standard · payer 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.

No wallet identity has been requested.

No compact lifecycle state has been read.

06

Packet evidence, with the execution boundary left honest

The exact v0+ALT packet can be inspected and exported. Wallet signing is intentionally unavailable until common Hot dispatches the compact EffectV4 and a checked immutable Trading release recognizes that outer.

Authenticate one finalized fixed38 route first.