Skip to content

Update Testnet and Dev Schemas from Mainnet

Wil Wade edited this page Oct 10, 2024 · 2 revisions

To maintain alignment with Mainnet, when a new schema is deployed on Mainnet, Testnet data and Dev Genesis are set to have those exact same schemas.

Testnet Schemas

  1. In the Frequency codebase: cd tools/state-copy
  2. npm i
  3. Edit schemas.mjs
  • Use the Testnet DEST_URL: const DEST_URL = "wss://0.rpc.testnet.amplica.io";
  • Update theconst SUDO_URI = "//Alice"; to be the SUDO key for Testnet
  1. npm run schemas
  2. Remove the changes

Dev Schemas

  1. make genesis-schemas
  2. Check that only resources/genesis-schemas.json changed
  3. PR to merge to main
  4. Release