dCdClutchoperator tool
Operator toolFound a marketPrepare a devnet market, open it and admit its first participant with the operator tools.All consoles →

Create a market.
Add a participant.

Prepare an operation document, preview its funding and market terms, then run the founding command. Keep the document and journal to resume an interrupted operation.

Current

Found a devnet market

Use the command-line workflow below to create and open the market, then admit its first participant.

InputOne operation document

A dclutch-devnet-market-participant-operation-v1 document contains the market plan, funding inputs, output paths and signing-key paths.

ActionPreview, then execute

The preview reads the inputs. Add --execute to sign and submit the transactions, paying the required devnet fees and deposits.

ResultMarket + first participant + session

The command returns market and participant details. Save the optional session file for later trading and redemption commands.

RecoveryRerun the same operation and journal

After an interruption, rerun the same command with the same operation document and journal to continue.

Show preview and execute commands

Set every shell variable to an absolute path. Review the operation document and preview outputs before adding --execute.

Preview, then authorized execution
dclutch-terminal --rpc "$DEVNET_RPC" \
  --i-mean-devnet EtWTRABZaYq6iMfeYKouRu166VU2xqa1wcaWoxPkrZBG \
  --bootstrap-bin "$SUCCESSOR" found \
  --found-operation "$FOUND_OPERATION" \
  --found-journal "$FOUND_JOURNAL"

# Review the authored Market input and read-only journal, then authorize the
# exact same operation. Rerun this line unchanged after an interruption.
dclutch-terminal --rpc "$DEVNET_RPC" \
  --i-mean-devnet EtWTRABZaYq6iMfeYKouRu166VU2xqa1wcaWoxPkrZBG \
  --bootstrap-bin "$SUCCESSOR" found \
  --found-operation "$FOUND_OPERATION" \
  --found-journal "$FOUND_JOURNAL" \
  --session-out "$CLI_SESSION" --execute

Not copied.

Open the legacy Found37 packet inspector

This inspector prepares older unsigned Found37 transactions. Use the command-line workflow above to open a market.

01Select execution

The activation cache must select immutable Core, Registry, and Rent artifacts whose Loader observations still match.

02Check market records

Product, domain, portfolio, Source, Realm, capabilities, and releases are decoded from finalized Registry bytes.

03Prepare account deposits

Create the RentCredit with your chosen refund wallet before submitting Found37.

01

Chain authority and record coordinates

Enter the Registry record addresses used by the market.

The chain this founds against
Who pays, and who is refunded

Connect a wallet to fill the payer address. Choose the rent refund wallet carefully: it cannot change after the RentCredit is created. This inspector exports unsigned transactions.

Wallet

No browser wallet found.

The deployment this founds against

These addresses come from the selected deployment. You can edit them.

The ten finalized records this market is built from

Enter the Product and SourceMaterialV3 addresses, then read the four dependent records. Supply the remaining record addresses separately.

Enter Product and SourceMaterialV3 addresses, then read their dependent records.

Enter the market record addresses to prepare the unsigned transactions.

Prepare the records

Enter the records to inspect the transactions.

The inspector checks the records, required account deposits and transaction size.