mirrors/tendermint
1
0
Fork 0
mirror of https://github.com/tendermint/tendermint.git synced 2026-02-03 18:42:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
wb/dialnext-error
tendermint/abci/example/kvstore
History
Sergio Mena 56fc80d66d abci: Move app_hash parameter from Commit to FinalizeBlock (#8664) 
* Removed from proto

* make proto-gen

* make build works

* make some tests pass

* Fix TestMempoolTxConcurrentWithCommit

* Minor change

* Update abci/types/types.go

* Update internal/state/execution.go

* Update test/e2e/app/state.go

Co-authored-by: Callum Waters <cmwaters19@gmail.com>

* Updated changelog and `UPGRADING.md`

* Fixed abci-cli tests, and doc

* Addressed @cmwaters' comments

* Addressed @cmwaters' comments, part 2

Co-authored-by: Callum Waters <cmwaters19@gmail.com>
2022-06-01 18:53:10 +02:00
..
helpers.go
abci: interface should take pointers to arguments (#8404)
2022-04-24 18:37:07 +00:00
kvstore_test.go
abci: interface should take pointers to arguments (#8404)
2022-04-24 18:37:07 +00:00
kvstore.go
abci: Move app_hash parameter from Commit to FinalizeBlock (#8664)
2022-06-01 18:53:10 +02:00
persistent_kvstore.go
abci: interface should take pointers to arguments (#8404)
2022-04-24 18:37:07 +00:00
README.md
abci: Vote Extension 1 (#6646)
2022-02-02 11:51:13 +01:00

README.md

KVStore

There are two app's here: the KVStoreApplication and the PersistentKVStoreApplication.

KVStoreApplication

The KVStoreApplication is a simple merkle key-value store. Transactions of the form key=value are stored as key-value pairs in the tree. Transactions without an = sign set the value to the key. The app has no replay protection (other than what the mempool provides).

PersistentKVStoreApplication

The PersistentKVStoreApplication wraps the KVStoreApplication and provides three additional features:

  1. persistence of state across app restarts (using Tendermint's ABCI-Handshake mechanism)
  2. validator set changes

The state is persisted in leveldb along with the last block committed, and the Handshake allows any necessary blocks to be replayed. Validator set changes are effected using the following transaction format:

"val:pubkey1!power1,pubkey2!power2,pubkey3!power3"

where pubkeyN is a base64-encoded 32-byte ed25519 key and powerN is a new voting power for the validator with pubkeyN (possibly a new one). To remove a validator from the validator set, set power to 0. There is no sybil protection against new validators joining.