Hello everyone,. We need assistance from the SORA validators to stabilize the network after the recent runtime upgrade.
07 Jul 2023, 13:07
Hello everyone,
We need assistance from the SORA validators to stabilize the network after the recent runtime upgrade. The issue is caused by a problem in the migration of one pallet.
The following instructions will enable the runtime upgrade to go through without the problem on the pallet migration.
Please follow these steps on your SORA validator workstation:
INSTRUCTIONS FOR VALIDATORS
1. Change your directory to the folder containing the docker-compose.yml file.
2. Create a new folder named wasms inside that directory using the command: mkdir wasms.
3. Put the provided file into the newly created wasms folder using the following command:
rsync -auP --force --rsync-path='sudo rsync' -e 'ssh' local_path_to_file remote_path_to_the_wasms_folder
4. After the command: line in the docker-compose.yml file, add the following lines:
- "--wasm-runtime-overrides"
- "/wasms"
Define the path to your newly created wasms folder, use pwd. After the volumes: line, add the following line:
- "/REPLACE_WITH_PATH_TO_YOUR_FOLDER/wasms:/wasms"
5. Save the changes made to the file.
6. Restart the docker-compose file using the command: docker-compose restart.
7. If you use a binary file or a Docker command, create the wasms folder, place the provided file inside it, and restart the application with the two additional flags mentioned in the previous steps.
8. If you have any questions or encounter any issues, please let us know.
Thank you for your cooperation. We stay around to support you and answer any question
🥰
Same news in other sources
207 Jul 2023, 13:45
Guide for Non- Technical Validators
If you followed the instructions here to spin up your node, here is how to help stabilize the network:
1- Download the file using this command: wget 'https://docs.google.com/uc?export=download&id=1jeHvSNMMnqr1kWCsl8d2NxBjexIbiGyl' -O 'file.wasm'
2- In the sora2 folder with your node information, add a folder called wasms, you should also see the chains folder here
3- In the wasms folder, add the wasm file downloaded
4- In the command used to run your node, add the flag --wasm-runtime-overrides /chain/wasms
Thank you for your cooperation 🥰
Guide for Non- Technical Validators.
Guide for Non- Technical Validators
If you followed the instructions here to spin up your node, here is how to help stabilize the network:
1- Download the file using this command: wget 'https://docs.google.com/uc?export=download&id=1jeHvSNMMnqr1kWCsl8d2NxBjexIbiGyl' -O 'file.wasm'
2- In the sora2 folder with your node information, add a folder called wasms, you should also see the chains folder here
3- In the wasms folder, add the wasm file downloaded
4- In the command used to run your node, add the flag --wasm-runtime-overrides /chain/wasms
Thank you for your cooperation 🥰
07 Jul 2023, 13:44
Hello everyone 👋
We need assistance from SORA validators to stabilize the network after the recent runtime upgrade. The issue is caused by a problem in the migration of one pallet ⚙️
👇 The following instructions will enable the runtime upgrade to go through without the problem of the pallet migration.
🔻 Please follow the instructions outlined in the SORA Devs chat
Hello everyone. We need assistance from SORA validators to stabilize the network after the recent runtime upgrade.
Hello everyone 👋
We need assistance from SORA validators to stabilize the network after the recent runtime upgrade. The issue is caused by a problem in the migration of one pallet ⚙️
👇 The following instructions will enable the runtime upgrade to go through without the problem of the pallet migration.
🔻 Please follow the instructions outlined in the SORA Devs chat