-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network crosstalk #612
Comments
Would be nice to also fix the root cause #535 |
We have a plan to fix the issue, but it will take some time to upgrade everyone and deploy. The problem right now is that neither network are reporting their blockchain. We have to add that back into the protocol and then at a later date start requiring nodes be on the same network. |
mvandeberg
pushed a commit
that referenced
this issue
Nov 28, 2016
mvandeberg
pushed a commit
that referenced
this issue
Nov 28, 2016
Add chain_id reporting to network hello message #612
merged |
mvandeberg
pushed a commit
that referenced
this issue
Dec 6, 2016
mvandeberg
pushed a commit
that referenced
this issue
Dec 7, 2016
Require peer to report chain_id #612
On1x
pushed a commit
to VIZ-Blockchain/viz-cpp-node
that referenced
this issue
May 28, 2018
Refactor block_log to mapped file. steemit#524
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the release of 0.16.0rc3 a node mostly just reports crosstalk from other networks, currently golos. It is impossible to debug node issues since nearly all messages are errors from excluded crosstalk blocks.
This is a request to have a node block, exclude, or otherwise suppress messages from other networks.
The text was updated successfully, but these errors were encountered: