concord-bft icon indicating copy to clipboard operation
concord-bft copied to clipboard

Concord byzantine fault tolerant state machine replication library

Results 57 concord-bft issues
Sort by recently updated
recently updated
newest added

* **Problem Overview** When reaching the limit of prePrepare message size we need to break the loop where we add requests. However, a bug was found where we compare the...

cla-not-required

* **Problem Overview** This tool is added as part of POC work for client verifiability. It uses rocks-db snapshot to hash state keys and value for a client id from...

cla-not-required

* **Problem Overview** moving concord_client_request.proto to cmf * **Testing Done** Testing in progress

cla-not-required

Continuously reading updates from subscription streams is the common case and for some application performance critical. Therefore, instead of spawning a new thread for every new Read() operation, this change...

cla-not-required

The idea behind the executable reference model is for us to have an experiment environment where we can pass sequence of messages, mutate the state of the replica and examine...

cla-not-required

On resetMetadata - we do not remove these two items: descriptorOfLastExitFromView, descriptorOfLastNewView in case of cross-node restore, these descriptors are not relevant and can be removed. After restore, replica can...

cla-not-required

Changed internal client ids to replica ids This is a work in progress and should **_not_** be merged.

cla-not-required

cherry-pick of a2a00fa7c7b9c2ef8c7fac7658db1d64ec38fba4

cla-not-required