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
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
It would be helpful to have a standalone tool that automates the steps described in PR #7413. In fact, with such a tool we would not need to add the --replace-producer-keys CLI option to chain plugin at all.
The tool would take as input:
a path to a input portable snapshot;
the public key to replace the active block producers' keys with;
a flag indicating whether to generate a block with eosio::regproducer actions;
and, a path to the directory where the generated portable snapshot should be saved.
It would use the chain lib to create a state database from the provided snapshot, and then modify the state as done in controller::replace_producer_keys in PR #7413. It would then, optionally, produce a block (in a special mode where it forces the onblock transaction to not execute) containing the actions that use eosio::regproducer to replace the registered block producing keys of the active producers. Then, it would ensure that the proposed and pending schedule are still empty (just in case the produced block made changes to it). And finally it would export a snapshot of the new state to the specified output directory.
The text was updated successfully, but these errors were encountered:
It would be helpful to have a standalone tool that automates the steps described in PR #7413. In fact, with such a tool we would not need to add the
--replace-producer-keys
CLI option to chain plugin at all.The tool would take as input:
eosio::regproducer
actions;It would use the chain lib to create a state database from the provided snapshot, and then modify the state as done in
controller::replace_producer_keys
in PR #7413. It would then, optionally, produce a block (in a special mode where it forces theonblock
transaction to not execute) containing the actions that useeosio::regproducer
to replace the registered block producing keys of the active producers. Then, it would ensure that the proposed and pending schedule are still empty (just in case the produced block made changes to it). And finally it would export a snapshot of the new state to the specified output directory.The text was updated successfully, but these errors were encountered: