void
Closed this issue · 5 comments
Solution Path A
Note that for posdao-test-setup we use our Parity fork: https://github.com/poanetwork/parity-ethereum/tree/aura-pos
The posdao-test-setup shouldn't be used with the original Parity.
would it be possible to modify your test-setup in order to be able to use the standard-parity client?
Yes, you can use the web3-bug branch - it uses original Parity: https://github.com/poanetwork/posdao-test-setup/tree/web3-bug
Also, you can try https://github.com/varasev/test-block-reward/tree/kovan-switching
Yes, I've seen the error using the posdao-test-setup (as I mentioned here), but I believe the second one also can be helpful to catch it.
As for these branches - I didn't try them for openethereum/parity-ethereum#10085 issue, but you asked the posdao-test-setup which would work with the original Parity - the first one is it.
@lazaridiscom if you know about ansible and have a spare Ubuntu 16.04 VM, you can try to spin up a kovan "validator" node using our ansible playbooks
https://forum.poa.network/t/new-kovan-validator-aws-node-deployment/2401
(use some random validator key - your node won't mine blocks but should work otherwise identical to our setup)