[Announcement] Whitelist cannot be updated after the Oasis Cobalt Upgrade - second-state/oasis-ssvm-runtime GitHub Wiki
Update: a hotfix is on the way, please refer to the latest announcement: https://github.com/second-state/oasis-ssvm-runtime/wiki/%5BAction-Required%5D-OasisEth-Mainnet-Upgrade-to-fix-critical-issues-caused-by-Oasis-Cobalt-Upgrade
TL;DR
Dear OasisEth node operators,
The whitelist update will be postponed due to the technical issue related to runtime update tool.
What happens?
We encountered a technical issue to add the entities back to the whitelist. There are some breaking changes related to the Oasis Paratime Configuration (Ref: ADR 0004: Runtime Governance). However, the related issue (cli: Add support for new runtime entity whitelist admission policy format #3626) is not implemented on the Oasis-Node 21.1.1. Hence, we cannot use the current Oasis-Node CLI tool to generate a valid transaction to update the runtime information.
Now, we are working with the Oasis Team to figure out a hotfix to add the entities back to the whitelist. The timeline is still TBD.
For the existed OasisEth node operators
We will use the snapshot whitelist to calculate the rewards. Please keep the OasisEth paratime node running, and your paratime node will get registered and listed after we fix the above issue.
All node operators who already joined the second epoch will be listed in the third epoch by default.
For the new OasisEth node operators
There is no way to get the new node operators registered and whitelisted until this issue fixes. So we decide to cancel the third epoch registration. Those who submitted the PR in the third epoch registration will be listed in the next epoch (4th epoch).
Related Error Message
level=error module=grpc/client caller=grpc.go:244 ts=2021-04-30T02:32:18.059298176Z msg="request failed" method=/oasis-core.Consensus/SubmitTx req_seq=1 rsp=null err="registry: runtime update not allowed"
ts=2021-04-30T02:32:18.059392477Z level=error module=cmd/consensus caller=consensus.go:124 msg="failed to submit transaction" err="registry: runtime update not allowed"
Update History
Last Update: 2021/05/18 17:53 UTC+8
- 2021/05/18 17:53 UTC+8, Update the hotfix guideline
- 2021/04/30 12:09 UTC+8, Initial Announcement