In this second post in the series, we offer some further insights into the exact nature of the IOTA ledger as a Directed Acyclic Graph (DAG). This exercise is particularly useful because these differences help explain the overall future vision for IOTA, as well as the path to Coordicide.

On a conceptual level, blockchains and DAGs have some similarities. Both are distributed ledger technologies, which allow users to obtain eventual consensus over the state of a ledger, in a decentralized manner. However, they do differ somewhat in their underlying mechanisms, and more importantly, have some key differences in their scaling properties and their potential use cases.

Why reinvent the wheel? Given that blockchains already exist, and that they appear to reliably maintain a ledger state, it's a valid question. The main motivation is scalability.  

Let’s take Bitcoin as our blockchain case study. It is limited to around 7 transactions per second (TPS) globally, regardless of how much demand or computational power is involved in the system. In addition, the time it takes for a transaction to reach finality, even with no congestion, is around an hour, which limits many potential use cases. Fully describing the blockchain scaling problem is beyond the scope of this blog post, and we recommend this article by Preethi Kasireddy as a good starting point to the Bitcoin scaling problem.  

One of the blockchain bottlenecks is the necessity for every node to reach consensus before releasing a new block. If this synchronicity is not maintained, we get many orphan blocks. These blocks do not contribute to the overall throughput and therefore waste bandwidth and proof-of-work resources. Orphan blocks are also known as temporary forks.  

In a DAG, we accept that these orphans and forks are an inevitable consequence of a high rate of TPS. However, unlike in blockchain, these orphans are merged back into the system, and are therefore not a waste of resources. Theoretically, this is the major advantage of DAGs.

The terms blockchain and DAG refer to the data structures used to store the ledger state, rather than the consensus mechanisms. Blockchains can use, for example, proof-of-work (PoW), proof-of-stake (PoS), or a quorum to reach consensus. Similarly, different DAGs can have different consensus mechanisms. In this section, we'll focus on comparing a PoW blockchain, like Bitcoin, with IOTA.  

In a PoW-based DLT, there are two fundamental questions to be answered:

  1. Where should a new block connect?
  2. How do we determine when a transaction is considered confirmed?

Bitcoin and IOTA provide different but analogous answers to these two questions. These can be summarized as follows:  

Bitcoin’s answers:

  1. Longest-chain rule: Somewhat of a misnomer, but this rule states that a new block should approve the chain with the largest amount of accumulated PoW.
  2. Six-block rule: If a block is at least six blocks deep and part of the longest chain, it can be considered as confirmed.

(If these concepts are unclear, we recommend 3Blue1Brown’s excellent introduction to Bitcoin video, or an equivalent introductory-level blockchain lesson.)  

IOTA’s answers, as proposed in the Tangle whitepaper:

  1. MCMC tip selection: A new transaction chooses two previous transactions to approve, using an MCMC-weighted random walk.
  2. Confirmation confidence: aA transaction is confirmed if its confidence is very high, meaning almost all legitimate tips approve it.

While IOTA doesn’t use blocks, we can imagine transactions as blocks of size one, and the analogy holds. This description is an oversimplification of both systems, but hopefully transmits the main idea of how blockchain consensus is related to the Tangle.

IOTA is a distributed system. There is no way for the IOTA Foundation, or anyone, to enforce approval of a particular transaction. We also cannot enforce the use of the MCMC algorithm we recommend. The best we can do is show that it is in the user’s best interest to follow our suggestion, or her transactions will be less likely to be approved by others.

This is the same story in Bitcoin. If miners think there is more profit to be had by forking the main chain rather than extending it, they will certainly go for it. See for example this recent article, which claims Bitcoin’s incentive system may be insufficient to stabilize it in the absence of block rewards. A more concrete example comes from Ethereum, in their hard fork proceeding the DAO hack: if there is an economic incentive to ignore the longest-chain rule, it will be ignored.  

In the face of these uncomfortable truths, the best and most sensible approach is to give users the freedom to choose whom to approve, and which transactions they consider as confirmed. There is only one basic rule in IOTA: each transaction must approve exactly two previous transactions. If users believe it is in their best interests to follow the recommended tip selection algorithm, they will do that, and it is up to us to show that indeed this is the best strategy to follow.

This is a multi-part post. Links to the other parts can be found below:
Part 1
Part 2 (this article)
Part 3
Part 4

Follow us on our official channels for the latest updates:
IOTA: Discord | Twitter | LinkedIn | Instagram | YouTube

Follow us on our official channels for the latest updates:
Discord | Twitter | LinkedIn | Instagram | YouTube |


IOTA Foundation

Official posts from the IOTA Foundation, and migrated posts from old platforms.

Great! You've successfully subscribed.
Great! Next, complete checkout for full access.
Welcome back! You've successfully signed in.
Success! Your account is fully activated, you now have access to all content.