1 Commits (b8dec948d4d7d8257e63aeecf982c25aeec9a180)

Author	SHA1	Message	Date
Felix Lange	ca18202eb9	eth: enable bad block reports ... We used to have reporting of bad blocks, but it was disabled before the Frontier release. We need it back because users are usually unable to provide the full RLP data of a bad block when it occurs. A shortcoming of this particular implementation is that the origin peer is not tracked for blocks received during eth/63 sync. No origin peer info is still better than no report at all though.	8 years ago