Dear sokol validators,
we’re trying to find a workaround/solution to a possible parity bug https://github.com/paritytech/parity-ethereum/issues/9764 observed on some nodes.
To test our assumptions we’d like to propose a test on sokol network.
The test would require changing RewardByBlock contract to let it gracefully handle unexpected input parameters that seem to be sent by parity.
Here is the Pull Request with actual changes: https://github.com/poanetwork/poa-network-consensus-contracts/pull/205
The test would consist of two steps:
- create a ballot to change implementation of ProxyStorage contract to allow it to change RewardByBlock implementation
- after p.1 is done, create a ballot to change implementation of RewardByBlock contract that contains the actual workaround/fix
The proposed updated version of ProxyStorage contract has already been deployed and verified: https://blockscout.com/poa/sokol/address/0xff8dc77e54fa96eb158509c8dea7971197748332/contracts
So we’d like to ask one of you to proceed with step 1 and create the following ballot on SOKOL network:
- ballot type: Modify Proxy Contract Ballot - proposed address: 0xff8dc77e54fa96eb158509c8dea7971197748332 - contract type: ProxyStorage