Mainnet Upgrade to Protocol Revision 1 scheduled for November 5, 2019 at block 83,400

DUNE network
Oct 23, 2019 · 2 min read

Five weeks after the first public release of Dune Network, we are thrilled to announce that the first protocol revision of our Mainnet will happen around November 5, 2019, at level 83,400. All nodes must have been upgraded to a commit downloaded from the mainnet branch of Gitlab no earlier than Oct 23, 2019. The git tag protocol-4.1 has been created to mark the revision commit, i.e. revision 1 of protocol 4.

Nodes that will not have been updated will automatically stop validating blocks afterwards. In such a case, after upgrading their nodes, admins should use dune-admin-client unmark all invalid blocks to restart validating blocks.

This revision has already been tested on the Testnet for one week. The next revision will target the integration of some useful features from the Babylon amendment, and the first release of the Love VM.

Here is a summary of the changes introduced in this upgrade:

  • Better collect-call implementation: contracts can pay fees for users. We will publish a Medium post very soon to show how to use this interesting feature;
  • Ironmin storage for contexts: Ironmin improves the speed and size of storing and accessing contexts. It is not activated by default, and it should still be seen as an experimental/testing feature, enabled only when DUNE_CONTEXT_STORAGEenvironment variable is set to ironmin. It is possible to switch back to Irmin (the default storage) using the RPC /storage/context/revert.
  • Better P2P communication layer: propagation of node addresses between nodes is improved, to increase the diversity of nodes while decreasing the cost.
  • Offline signing of operations: all commands in dune-client to generate operations have a new --forge argument to save the operation. It is then possible to use the sign operationcommand offline, and inject the operation online with inject operation. All these operations must be executed in less than 15 minutes (current max_operation_ttl).
  • Debug/verbosity tweaks: with theDUNE_VERBOSE_BAKERenvironment variable, the baker will print the reasons why some operations are discarded (not enough fees in particular).
  • Changes of default values: files are now stored in ~/.dune-COMMAND for Mainnet, and ~/.dune-testnet-COMMANDfor Testnet, by default. Default ports on Mainnet are p2p_port=9733, rpc_port=8733, discovery_port=10733, signer_tcp_port=7733 and signer_http_port=6733 by default. The ports are increased by 1 on Testnet (i.e. X734 instead of X733).
  • Lots of small improvements in dune-client for better user interaction.

Dune Network

Dune Network ( http://dune.network/

DUNE network

Written by

A secured Web 3.0 platform designed for enterprise-grade decentralized applications.

Dune Network

Dune Network ( http://dune.network/ ) is a 3rd-generation blockchain platform, with a focus on security and accessibility. Its main features are delegated Proof-of-Stake, multiple native smart contract languages, formal verification and easy private chains deployments.

More From Medium

More on Blockchain from Dune Network

More on Blockchain from Dune Network

This March on Dune

316

More on Blockchain from Dune Network

More on Blockchain from Dune Network

Introduction to Binance DEX, Part I: Atomic Swaps

Mar 26 · 4 min read

480

More on Dune Networks from Dune Network

More on Dune Networks from Dune Network

Games with Oracles on Blockchains (Part I)

549

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade