zolfa
/
tendermint
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 221 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
324 Commits
183 Branches
291 MiB
 
 
 
 
 
 
Tree: 191c4b6d17
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '191c4b6d17'
${ noResults }
tendermint/example/dummy
Ethan Buchman 667c2543ea use request struct for Info 7 years ago
..
README.md TMSP -> ABCI 8 years ago
dummy.go use request struct for Info 7 years ago
dummy_test.go use request struct for Info 7 years ago
persistent_dummy.go use request struct for Info 7 years ago

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:

  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,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.