The blockchain v2 reactor utilizes concurrency to saturate the bottleneck of writing blocks to disk. This concurrency is internal to the reactor where the reactor itself will launch and manage internal state machines running as go-routines. This configuration makes testing difficult as we don't know when messages processed by internal state machines will be processed and when we can assert that th

What we could also do is to use "github.com/pkg/errors" package for wrapping error messages in the context of the call stack.

Originally posted by @sergefdrv in hyperledger-labs/minbft#102

our code still has legacy(Address) at request.go or node.go

fix address to member

This looks good work.

For cross-language support, it would be good to go deep into one language with runtime support, rather than going wide and providing compile-time linking options for many languages.

For example, once C/C++ implementation is done, please:

• provide connectivity options to invoke the API through HTTP/2, WebSockets, RPC etc. so that all other languages, such as