Hardcoded MoC in PoaNetworkConsensus contract about poa-network-consensus-contracts HOT 4 CLOSED

Hi! The name of your constructor is PoeNetworkConsensus but it must be PoaNetworkConsensus. Maybe you made a mistake?

from poa-network-consensus-contracts.

Hi ! Sorry I mistyped it here, but not in my code. Im gonna edit now in the issue.

from poa-network-consensus-contracts.

@jordipainan

It compiles well and I'm able to put the bytecode in the spec.json as a precompiled contract.`

how do you compile PoaNetworkConsensus and what bytecode you set in the spec? I am asking because PoaNetworkConsensus has input parameters in the constructor.

Also,

• what is your basictoml.toml content?
• what is your spec.json content?
• which Parity version are you using?

Consider using https://github.com/poanetwork/poa-test-setup#start-moc-node script to start POA network. It uses https://github.com/poanetwork/poa-network-consensus-contracts repo as a submodule. You can change the source of submodule to your own forked repo with contracts to test, if your setup is correct.

from poa-network-consensus-contracts.

Hi @vbaranov , my fault, your code works like a charm. I pasted the wrong bytecode in the spec (with not expected params in the constructor).
I opened the issue because I got a lot of errors in the past trying to build my concept of PoA with the constructor and I thought its possibly the same (an error in the contract and not in the client) but not the case.
On the other hand Parity still gets stuck, I reported it to the team ^^ .
Thank you and sorry for the inconvenience.

from poa-network-consensus-contracts.