Instead of select { internal <-; <-timeout }, how about select { internal <-; default CList.PushBack(msg) } ? We can shuffle more from CList to internalMsgQueue on the bottom of receiveMessage routine's for-loop.

We don't want to wait 10 milliseconds on things, and launching a new goroutine would make the order of sends to internalMsgQueue nondeterministic.

thats interesting. my thinking was two fold:

1. we should almost never fail to send on internal, because it has a large buffer and the receiveRoutine select should be balanced
2. we don't get determinism anyways until after something is read in the receiveRoutine

agree 10 ms might be too much in the event we are backlogged. so we could just use "default: go internal<-"

It would be confusing to see internalMsgQueue items out of order, e.g. a precommit before a prevote. At least we can make the order of messages in internalMsgQueue deterministic.
But I think that's fine too.

s/1/RoundStepNewHeight/g

Yeah maybe SetEventSwitch where possible? Probably everywhere now since we're not using the cache, yeah?