This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
PoA: Several authority nodes fork blockchain #1075
Labels
F2-bug 🐞
The client fails to follow expected behavior.
Z8-wontfix 🙅♀️
Issue is in principle valid, but this project will not address it. Closer should explain why.
Comments
looks like a bug with the syncing code, since restarting one of the nodes will make them resync properly. to reproduce:
then executing in the JS env of http://localhost:8080:
and in http://localhost:8081:
with
|
might with a bit better now that #1095 is in... |
gavofyork
added
the
Z8-wontfix 🙅♀️
Issue is in principle valid, but this project will not address it. Closer should explain why.
label
Aug 1, 2016
we'll be adding a much better PoA algorithm in the mid-term, so will be deprecating the existing one. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F2-bug 🐞
The client fails to follow expected behavior.
Z8-wontfix 🙅♀️
Issue is in principle valid, but this project will not address it. Closer should explain why.
Setup own environment with two "parity" nodes that was setup as authority nodes and use PoA.
Send transactions to both nodes.
As result I see two forks of blockchain.
Sometimes nodes do resolve blockchain conflict. in this situation some transactions could be lost.
In the logs I see following entry:
2016-05-11 15:40:11 WARN:ethminer::miner: prepare_sealing: ERROR: could not import internally sealed block. WTF?
The text was updated successfully, but these errors were encountered: