We have identified some known issues that we are attempting to resolve:
Peer 76.74.170.79:1700 disconnected us: You offered us a block that we reject as invalid
Peer 106.185.26.162:1976 disconnected us: You offered us a block that we reject as invalid
Peer 106.185.26.162:1776 disconnected us: You offered us a block that we reject as invalid
Peer 80.240.133.79:1777 disconnected us: You offered us a block that we reject as invalid
Peer 180.153.142.120:1777 disconnected us: You offered us a block that we reject as invalid
Peer 104.131.134.181:36856 disconnected us: You offered us a block that we reject as invalid
Peer 162.243.220.142:1776 disconnected us: You offered us a block that we reject as invalid
The last time I did a complete resync with the network I had this message from a few peers. It all stems from a single assert I added to make sure we didn't download blocks from forks that were "too old". I need to gather more info on this one.
2) We have a random crash for some delegates in the networking code. This is an issue we have been tracking for a few days. It happens enough in the wild, but is very difficult to reproduce on demand. We have some ideas but nothing conclusive. Delegates, please be vigilant and run your client in GDB and capture the P2P log file if you happen to catch this crash in progress.
https://github.com/BitShares/bitshares_toolkit/issues/6493) Some people are reporting syncing issues.
96% of the delegates are online and synced so the network is healthy. I have downloaded the chain from scratch with a fresh build 2x now on OS X (command line client). I am not sure why some people end up stuck on the same block time and time again. Please of patient as we work to resolve these bugs that are difficult to reproduce.
4) Sometimes when a large transaction is made the transaction ledger reports the wrong amount as being sent (receiver sees the right amount).
https://github.com/BitShares/bitshares_toolkit/issues/657
Topic: BTSX 0.4.5 Bug Fix Status Update (Read 4908 times)
