Brandon Williams

@sblackshear I've updated the OP and the title of this issue to reflect that goal.

> can you write up some comments describing how this is intended to integrate with the fullnode and/or validator? Which specific traits/methods define that interface? Perhaps you can put the...

Is there more context on why we wouldn't be able to use a loopback address? Also AFAIK gRPC is fundamentally built on top of HTTP/2 so we'd be using http...

I think we should probably stop using this db abstraction entirely and just use the sync db reads and writes directly. This abstraction currently serializes all reads and writes to...

Yes, you still need to verify the signature on the transaction (which is AFAIK what that does)

So I do think we want to make things optional, but I think we actually want to make the worker addresses optional over the primary's. We should always know concretely...

Ok I did read the linked issue and I see the intent....maybe we instead want to completely remove all network info from the committee structure?

@Ben-PH Thanks to your reproduction recipe I was able to come up with a workaround that you can see in the PR linked above.

Thanks for the bug report! Yes I do think that `diffy` should better handle windows line endings although I think that fixing one of those asserts is more straight forward...

> RWLock eases contention on shared objects that are read much more often than they are written, but it does not prevent people from taking a mutable reference to the...