fluencelabs/tendermint
1
0
Fork 0
mirror of https://github.com/fluencelabs/tendermint synced 2025-04-24 14:22:16 +00:00
Code Issues Projects Releases Wiki Activity
tendermint/abci/example/kvstore
History
Phil Salant 04d13d9945 fix linter errors thrown by unconvert, goconst, and nakedret (#3960) 
* Remove unnecessary type conversions

* Consolidate repeated strings into consts

* Clothe return statements

* Update blockchain/v1/reactor_fsm_test.go

Co-Authored-By: Anton Kaliaev <anton.kalyaev@gmail.com>

This PR repairs linter errors seen when running the following commands:
golangci-lint run --no-config --disable-all=true --enable=unconvert
golangci-lint run --no-config --disable-all=true --enable=goconst
golangci-lint run --no-config --disable-all=true --enable=nakedret

Contributes to #3262
2019-09-10 11:31:44 +04:00
..
helpers.go
abci: VoteInfo, ValidatorUpdate. See ADR-018
2018-08-16 13:19:13 -04:00
kvstore_test.go
fix linter errors thrown by unconvert, goconst, and nakedret (#3960)
2019-09-10 11:31:44 +04:00
kvstore.go
tm-cmn to tm-db (#3850)
2019-07-31 11:34:17 +02:00
persistent_kvstore.go
fix linter errors thrown by unconvert, goconst, and nakedret (#3960)
2019-09-10 11:31:44 +04:00
README.md
abci/examples: switch from hex to base64 pubkey in kvstore (#3641)
2019-06-21 15:18:49 +04: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 two 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.