bft blockchain consensus consistency cryptocurrency cryptography db distributed-systems go

History

William Banfield 0b8a62c87b abci: Synchronize FinalizeBlock with the updated specification (#7983 ) This change set implements the most recent version of `FinalizeBlock`. # What does this change actually contain? * This change set is rather large but fear not! The majority of the files touched and changes are renaming `ResponseDeliverTx` to `ExecTxResult`. This should be a pretty inoffensive change since they're effectively the same type but with a different name. * The `execBlockOnProxyApp` was totally removed since it served as just a wrapper around the logic that is now mostly encapsulated within `FinalizeBlock` * The `updateState` helper function has been made a public method on `State`. It was being exposed as a shim through the testing infrastructure, so this seemed innocuous. * Tests already existed to ensure that the application received the `ByzantineValidators` and the `ValidatorUpdates`, but one was fixed up to ensure that `LastCommitInfo` was being sent across. * Tests were removed from the `psql` indexer that seemed to search for an event in the indexer that was not being created. # Questions for reviewers * We store this [ABCIResponses](`5721a13ab1/proto/tendermint/state/types.pb.go (L37))` type in the data base as the block results. This type has changed since v0.35 to contain the `FinalizeBlock` response. I'm wondering if we need to do any shimming to keep the old data retrieveable? * Similarly, this change is exposed via the RPC through [ResultBlockResults](`5721a13ab1/rpc/coretypes/responses.go (L69))` changing. Should we somehow shim or notify for this change? closes: #7658		3 years ago
..
tendermint	abci: Synchronize FinalizeBlock with the updated specification (#7983)	3 years ago
Dockerfile	Update build image workflow. (#361)	3 years ago
README.md	spec: merge spec repo into tendermint repo (#7804)	3 years ago

README.md

Protocol Buffers

This sections defines the protocol buffers used in Tendermint. This is split into two directories: spec, the types required for all implementations and tendermint, a set of types internal to the Go implementation. All generated go code is also stored in tendermint. More descriptions of the data structures are located in the spec directory as follows:

Process to generate protos

The .proto files within this section are core to the protocol and updates must be treated as such.

Steps

Make an issue with the proposed change.
- Within the issue members, from the Tendermint team will leave comments. If there is not consensus on the change an RFC may be requested. 1a. Submission of an RFC as a pull request should be made to facilitate further discussion. 1b. Merge the RFC.
Make the necessary changes to the .proto file(s), core data structures and/or ABCI protocol.
Rebuild the Go protocol buffers by running make proto-gen. Ensure that the project builds correctly by running make build.