An important addition to it is the ability to add a validator or change the voting power of a validator at runtime.
One existing validator proposes the change to the rest of the network by introducing a new “upsert-validator election”. This is the basic process of a validator. The job of the other validators is to vote “yes” or “no”. If two-thirds of the validators vote “yes”, only after which the change takes place. The votes and the whole election process is picked up by blockchain and is recorded.
Some of the new featured updates include faster validation due to memorization, reliable Events API, assorted bug fixes, new documentation about privacy and handling private date.
The system can store data off-chain. This means the system could store data in a third-party database, document store, or a content management system. So, BigchainDB can help in a number of ways such as keeping track of who has read permissions in a third party system, keeping a permanent all request record made to the third-party system, storing hashes of documents-stored elsewhere to detect change in document, recording handshake-establishing requests and response between two off-chain parties.
The team from BigchainDB is halting the process to change an existing and running BigchainDB network in order to run a new version of Tendermint, after which they will release 2.0.0 Beta 7.
The next big change will be Tendermint, which will make some smooth changes every now and then and the candidate series of the BigchainDB will be set to update BigchainDB to work with the latest version of Tendermint.
Image via Google
Join our telegram group