Skip to content

DEPLOY_DOC.md

Latest commit

 

History

History
130 lines (93 loc) · 3.33 KB

DEPLOY_DOC.md

File metadata and controls

130 lines (93 loc) · 3.33 KB
Raw

Deploying CDM to W3S

Deploy the CDM ContractRegistry to W3S/Summit Asset Hub, register the shared CDM contracts, and prepare the frontend deploy path.

Assumes Node.js 22, pnpm, Bun, Rust/Cargo, and a funded W3S/Summit deployer mnemonic are available.

1. Get The Code

git clone https://github.com/paritytech/contract-dependency-manager.git
cd contract-dependency-manager
git checkout main
pnpm install

2. Install Registry Build Tooling

The registry contract is still built with the legacy charles/cdm-integration branch of cargo-pvm-contract.

HOST_TARGET="$(rustc -vV | awk '/^host:/ {print $2}')"
cargo install --force --locked \
  --target "$HOST_TARGET" \
  --git https://github.com/paritytech/cargo-pvm-contract.git \
  --branch charles/cdm-integration \
  cargo-pvm-contract

3. Deploy Registry

Use a funded W3S/Summit Asset Hub deployer mnemonic. CDM saves this account later so registry queries use a mapped origin.

export CDM_DEPLOY_SURI="<deployer-mnemonic>"
SURI="$CDM_DEPLOY_SURI" CHAIN=w3s make deploy-registry

Copy the deployed address from:

CONTRACTS_REGISTRY_ADDR=0x...

4. Open Address PR

Update only the W3S registry string in src/lib/env/src/registry.ts:

const W3S_REGISTRY_ADDRESS = "0x...";

Add a changeset so the updated registry address ships in both the @parity/cdm-env package and the compiled CLI release:

cat > .changeset/w3s-registry-address.md <<'EOF'
---
"@parity/cdm-cli": patch
"@parity/cdm-env": patch
---

Set the W3S registry address.
EOF

Open a PR with those changes. The Summit RPC endpoints are already wired in the W3S preset.

5. Install CDM CLI With W3S Registry

After the W3S registry address PR merges, update the CDM checkout and install the CLI from source so it has the new W3S registry address.

git checkout main
git pull --ff-only
pnpm install
make install
cdm account set -n w3s --mnemonic "$CDM_DEPLOY_SURI"

6. Deploy Contract Developer Tools Contracts

Deploy the shared contracts from contract-developer-tools.

cd ..
git clone https://github.com/paritytech/contract-developer-tools.git
cd contract-developer-tools

Install the legacy cargo-pvm-contract branch required by these contracts:

HOST_TARGET="$(rustc -vV | awk '/^host:/ {print $2}')"
cargo install --force --locked \
  --target "$HOST_TARGET" \
  --git https://github.com/paritytech/cargo-pvm-contract.git \
  --branch charles/cdm-integration \
  cargo-pvm-contract
cdm deploy -n w3s --suri "$CDM_DEPLOY_SURI"

Verify

Install the shared contracts from the W3S registry and confirm cdm.json contains resolved contract metadata and addresses.

cdm install -n w3s \
  @polkadot/contexts \
  @mock/disputes \
  @polkadot/profiles \
  @mock/reputation \
  @polkadot/threads

Then just validate cdm.json contains resolved contract metadata and addresses.

7. Deploy Frontend

Pending W3S environment support in bulletin-deploy. Once bulletin-deploy --list-environments includes the W3S/Summit environment, a CDM maintainer can redeploy contracts.dot:

cd ../contract-dependency-manager
BULLETIN_DEPLOY_ENV=w3s src/lib/scripts/deploy-frontend.sh "$CDM_DEPLOY_SURI"

Verify

The website should now be available at contracts.dot with the shared contracts visible on the w3s environment.