You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Frequency 1.13 contains a migration to add some missing schema names to already-deployed schemas on Mainnet. When Mainnet schemas are updated, we need to update genesis-schemas.json using the make genesis-schemas command, then publish a new Docker image for frequency-chain/standalone-node.
Description
Frequency 1.13 contains a migration to add some missing schema names to already-deployed schemas on Mainnet. When Mainnet schemas are updated, we need to update genesis-schemas.json using the
make genesis-schemas
command, then publish a new Docker image forfrequency-chain/standalone-node
.How to: https://github.com/frequency-chain/frequency/wiki/Update-Testnet-and-Dev-Schemas-from-Mainnet
NOTE
With this update, the Docker image @dsnp/instant-seal-node-with-deployed-schemas is no longer necessary; we should determine how best to deal with this.
The text was updated successfully, but these errors were encountered: