Skip to content

Client Update fork testing

zees-dev edited this page Jan 24, 2024 · 5 revisions

Pre-requisites

  1. docker
  2. ghcr access to trn-seed packages
  • 2a: For ghcr access, create a PAT on the settings page with the read:packages scope
  • 2b: Login to ghcr via password (PAT):
    echo <YOUR-PAT> | docker login ghcr.io -u <YOUR-GITHUB-USERNAME> --password-stdin

Steps

  1. Get forked chain state from image deployed by build-porcini-fork-image workflow
  • NOTE: requires seed ghcr access
  • NOTE: This will copy the fork.json to the hosts ./output directory
docker run --rm -it \
  --name fork-porcini \
  -v ${PWD}/output/:/output/host/ \
  ghcr.io/futureversecom/fork-release-state-porcini:latest \
  sh -c "mv /output/fork.json /output/host/"
  1. Run latest client node with forked chain state
docker run --rm -it \
  --name seed-latest \
  -v ${PWD}/output/:/output/ \
  -p 9933:9933 \
  -p 9944:9944 \
  --entrypoint "/usr/bin/seed" \
  ghcr.io/futureversecom/seed:latest \
  --chain=/output/fork.json --alice --tmp --unsafe-ws-external --unsafe-rpc-external --rpc-cors=all
  1. Upload the new runtime compressed wasm blob to the chain via portal
  2. View explorer and telemetry
Clone this wiki locally