IOTA 2.0 Research Specifications

This article was first published on IOTA Foundation Blog
-----

IOTA 2.0 Research Specifications

This post aims to briefly introduce the research specifications which we made available with the release of the IOTA 2.0 DevNet (Nectar). The specifications can be found here. Their purpose is to carefully explain the current state of the IOTA 2.0 protocol to developers, both internal and external, who wish to build on or test Nectar, to academics who want to analyze, model and optimize the protocol and need rigorous description of each module, and to community members and anybody who just want to learn more about the protocol.

We hope this post is a useful guide to the IOTA 2.0 research specifications, and we hope that you dive into them to learn as much as you can about how the IOTA 2.0 DevNet works! However, before reading the specifications, we would like to explain a few points to the reader.

What are research specifications?

This collection includes specifications on each key experimental component of Coordicide. However, there are two important caveats regarding these documents.

First, none of the parameters are finalized. Although our previous studies give certain ranges for each of these parameters, tuning each parameter to its optimum value requires a lot of testing and research. Luckily, we can conduct this research while the software is being developed since the parameters we are fine tuning are very easy to change in the code. In these specifications, each parameter is set to an educated estimate.

Second, several non-experimental components of the protocol are omitted from this document. For example, snapshotting (the module which manages the pruning of old messages in perma-nodes) and a description of the gossip protocol are omitted. Both of these components are well understood parts of the current Chrysalis mainnet, and thus we felt including them was not worth delaying the ...

-----
To keep reading, please go to the original article at:
IOTA Foundation Blog

Comments (No)

Leave a Reply