Dispatch Developers Update — Pushing the Protocol

New ExecuteRead Transaction Type, Upgraded TX Synchronization, & Upgraded SDKs too

Well it’s been a while since we pushed out a recap of what we’ve been up to, so here’s a rundown of some of the recent developments we’ve made on the protocol.

Now you can ExecuteRead the fine print

The ExecuteRead Transaction Type

You can now read the state of a smart-contract instantly, for free, and without the need of an asynchronous callback thanks to the new ExecuteRead (Transaction Type 4) functionality!

Where previously we had all smart-contract reads recorded on the ledger, we now let you query any active Bookkeeper for a smart-contract’s current state without needing to gossip first.

We also went ahead and updated the Java-SDK and dispatch-js SDKs to support the new functionality as well.

Mi ledger es tu ledger

Upgraded TX Synchronizations

As part of our roadmap to turn over full control of the network to the community, we needed an efficient way to transfer the whole ledger to nodes that wanted to participate as Bookkeepers, so we built it!

Delegated Bookkeepers who know nothing of the Dispatch ledger can now download all of the network’s transactions and execute them to re-create the state of the ledger.

We’re committed to the decentralization of the protocol, and this is a major jump in that direction.