* move to a message processor channel model for ceremony
* switch to goroutine
* readjust
* cut down volume
* keep distance data asserted
* bring it back so more bootstrap nodes can exist
* bump the version, it's go time
* Modify the wrong default volumes value to /root/.config (#109)
* move extract version logic to new version.go in config package
* update version extraction command
---------
Co-authored-by: talentbuilder <talentbuilder@163.com>
* experimental: switch mutex to RW to see if it alleviates backpressure on peer info
* relax mutex req
* reject unknown messages
* open the floodgates
* adjust message handler to use goroutine, i'll probably regret this
* switch that back, it was regret
* further discovery
* log more data
* forcibly block channel when unbounded
* else
* make it configurable so bootstrap peers are the only ones putting up with this.
* ok, non-starter, let's try a different route
* further tweaking
* let the peer info flow uninhibited
* final burn off on master
* final adjustments
* [PROTO-61] - fix: Use DHT for source of truth on peer info
* [PROTO-60] – fix: nil uncooperative peer state panic
* [PROTO-62] – fix: stored frame corruption due to old bug
* v1.1.6 – bump version
