Closed HassanAmed closed 4 years ago
As per release notes of eosio.contracts v1.9 here It is stated that in order to activate WTMSIG you need to first deploy an older version of eosio.bios contract which is the right way except for one thing we need to older bios contract does not allow us to activate WTMSIG and ends up giving error API Error Details: eosio.bios does not have permission to call this API so what i did to activate it
Maybe this should be updated in either release notes or bios boot sequence to avoid confusion.
I followed this https://developers.eos.io/welcome/latest/tutorials/bios-boot-sequence and after activating PPREACTIVATE_FEATURE eosio.system contract cannot be set and throws error Error 3070000: WASM Exception Error Details: env.set_proposed_producers_ex unresolveable Expected behavior : eosio.system contract should be set [Note] In release notes this is written _The eosio.system and eosio.bios contracts contained in this release can only be deployed on an EOSIO blockchain after the activation of the WTMSIG_BLOCKSIGNATURES consensus protocol upgrade. but how is it possible to activate WTMSIG_BLOCK_SIGNATURES before setting system contract