History

Tzu-Jung Lee 9134905f42 cleanup: replace common.Exit with log.Crit or log.Fatal Later we can pick another logger that has fatal, like zap?		2017-01-16 23:23:19 -08:00
..
README.md	TMSP -> ABCI	2017-01-12 16:04:32 -05:00
dummy.go	lint: s/common.Fmt/fmt.Sprintf	2017-01-16 23:20:04 -08:00
dummy_test.go	lint: s/common.Fmt/fmt.Sprintf	2017-01-16 23:20:04 -08:00
log.go	persistent dummy	2016-11-16 13:32:01 -05:00
persistent_dummy.go	cleanup: replace common.Exit with log.Crit or log.Fatal	2017-01-16 23:23:19 -08:00

README.md

Dummy

There are two app's here: the DummyApplication and the PersistentDummyApplication.

DummyApplication

The DummyApplication 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).

PersistentDummyApplication

The PersistentDummyApplication wraps the DummyApplication and provides two additional features:

persistence of state across app restarts (using Tendermint's ABCI-Handshake mechanism)
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,addr2/power2,addr3/power3"

where power1 is the new voting power for the validator with pubkey1 (possibly a new one). There is no sybil protection against new validators joining. Validators can be removed by setting their power to 0.