-
Notifications
You must be signed in to change notification settings - Fork 224
neo-cli >= v2.5.0 doesn't create blocks in neo-privatenet-docker #69
Comments
@erikzhang could you perhaps give me a pointer on how I would add the consensus smart contract to the wallet? |
In v2.5.0, I redesigned the wallet model for NEP-6. The new wallet model lacks an API to find account by the public key. So we must add a consensus contract to the wallet before we can start the consensus. The consensus contract is a 5-of-7 multi-signature contract for all consensus nodes. |
I have built the source code from master and I have still the same problem in ubuntu with starting the consensus... What to do? |
@gerlinger777 as I wrote in the other issue, take a close look at how neo-privnet-docker does it. You need to setup the seeds/peers correctly and need to add the consensus contract to the wallet JSONs. It's a bit involved, and if you are not familiar with the whole system I personally would recommend you to use the Docker image. |
do I need to edit anything else than protocol.json too? |
There is no need to add consensus contract any more due to neo-project/neo@a5dab7f |
protocol.mainnet.json and protocol.testnet.json files need to be edited IMHO.... those are still with real chain data.. maybe thats the reason that the Consensus is not starting.. Also should i give command Start Consensus on 1 node or on all paralell? I am giving command on all.. |
@metachris I really appreciate the docker image you did, but here in Gelinger Media we tend to go with more involved approach to learn it more. No pain, no gain! |
@erikzhang We have cloned master repository, then we have build it from source , then we have created wallets, edit the protocol.json ( as it was told on the documentation), then we have opened on each machine 4 wallets then we have run the consensus command and it's still stuck on onStart... |
I have edited also protocol.mainnet.json and protocol.testnet.json and tried , with no success yet. |
Since v2.5.0, neo-cli consensus nodes don't create blocks in neo-privatenet-docker. Are there any significant changes or new commands we need to issue?
Tracking this issue with reproducible steps and the output of neo-cli here: CityOfZion/neo-privatenet-docker#15
Any input on this would be much appreciated.
The text was updated successfully, but these errors were encountered: