[01:50:05] <navcoin-bot> <prole> @aguycalled ill look at that today and see if i can get the tests passing
[01:50:09] <navcoin-bot> <prole> https://github.com/navcoin/navcoin-core/pull/604#issuecomment-538519198
[01:50:24] <navcoin-bot> <prole> R-Marino has some feedback
[03:24:33] <navcoin-bot> <prole> ive tried using the setmocktime function but both nodes still end up on the same block after reconnecting. will park this and move onto another PR
[13:05:27] <navcoin-bot> <aguycalled> yes ive read it, ill reply him later. i agree with him that this is not the most efficient solution, and that even the whole header spam protection is not the right solution, the redesign must be deeper.
[13:06:02] <navcoin-bot> <aguycalled> this is just a quick patch to close a vulnerability
[13:06:35] <navcoin-bot> <aguycalled> have you tested it with the art-of-bug instructions @prole ?
[13:06:41] <navcoin-bot> <aguycalled> did you verify the timestamps in the logs?
[13:54:46] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Remote host closed the connection)