[01:45:10] *** Joins: navcoin-bot2 (~navcoin-b@nav.community)
[01:45:11] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Read error: Connection reset by peer)
[01:45:54] *** navcoin-bot2 is now known as navcoin-bot
[08:28:13] <navcoin-bot> <mxaddict> @salmonskinroll did you do anything special for the node that crashed?
[08:28:26] <navcoin-bot> <mxaddict> I could not get my node to crash
[10:38:53] <navcoin-bot> <prole> im just starting up my node again after being offline for 18 hours to test the spam header stuff
[10:39:09] <navcoin-bot> <prole> will report back in the morning, or well.. probably in the afternoon as its NYE here now
[10:39:19] <navcoin-bot> <prole> about to head out to town to watch the fireworks
[10:39:48] <navcoin-bot> <prole> well actually the header sync was really fast
[10:39:56] <navcoin-bot> <prole> synced aobut 3.6k headers with no issue
[10:40:10] <navcoin-bot> <prole> and im up to date
[10:40:14] <navcoin-bot> <prole> all working fine
[10:40:42] <navcoin-bot> <prole> will read any responses to issues over the next couple of days and manage the release if we an agree there are no more issues
[10:40:48] <navcoin-bot> <prole> signing off!
[16:27:05] <navcoin-bot> <salmonskinroll> Nothing special. Just delete the blocks and chainstate folder and start a navcoin-qt and let it sync