IOTA is centralized

On June 13th, IOTA was listed on Bitfinex and shortly after, it showed up as the 7th largest cryptocurrency by market capitalization on [coinmarketcap.com](http://www.coinmarketcap.com) at US$1.5bn. ![iota4.png](https://steemitimages.com/DQmTJZDrCnJV7vDzgnCrMptyfBsy5MHyxuypYU2oRESp7pt/iota4.png) Bitfinex gave [the following motivation](https://www.bitfinex.com/posts/206/review) for the listing: ![iota.png](https://steemitimages.com/DQmey9knexHYR27rsirYzELjYDcu1TARWi7yf5KZ98af4mH/iota.png) This correlates well with the information presented on IOTA’s website. If these claims are proven to be true, IOTA would perhaps be the most interesting innovation to ever emerge from this space. ![iota2.png](https://steemitimages.com/DQmNz7HnfsnqQmF4MgGj9W9witR9FstXgZzdhepUao5wY9t/iota2.png) This post will not go in to extreme detail about how IOTA works or what a [DAG](https://en.wikipedia.org/wiki/Directed_acyclic_graph) is, since there are plenty of other resources online ([website](http://iota.org/), [whitepaper](https://iota.org/IOTA_Whitepaper.pdf), [github](https://github.com/iotaledger)). Instead, here’s an extremely short and simplified version: The IOTA ledger is constructed as a tree, where the root node (“node” here simply refers to a position in the tree — has nothing to do will network nodes) is the equivalent to the “genesis block”, and every subsequent transaction creates a new node in the tree. From the genesis node, all iotas that will ever be created were distributed to a group of addresses participating in the original ICO in 2015. For a person to extend this tree, his transaction must point to two randomly chosen previous transactions in the tree, and include a tiny Proof-of-Work hash. This creates an ever-growing tree representing the ledger. ![0-Fay5O7wuz0oitE4j.jpg](https://steemitimages.com/DQmQfGSQLVPaSJY1tBjME94Bviv3eLRdN5Mop2vtj5fpe1S/0-Fay5O7wuz0oitE4j.jpg) *The “Tangle” (DAG): Each node represents a new transaction.* When he has selected the two previous transactions, he also verifies them by making sure they also include the required Proof-of-Work and that they neither directly nor indirectly extend what would constitute a double-spending transaction in the tree. To choose which branch of the tree to extend upon, he follows a specific [MCMC-based](https://en.wikipedia.org/wiki/Markov_chain_Monte_Carlo) algorithm, and as long as the majority of the other users follows the same algorithm, the tree will diverge into the same direction as a result. This direction is then secured over time through the extension of more tiny Proofs-of-Works added by each new transaction. Further, the system only provides any security guarantees in the case [that an attacker does not amass more than 33% of the hashpower of the network.](https://forum.iota.org/t/iota-double-spending-masterclass/1311)

The problem

The problem comes down to this; at the current stage, an attacker could very easily amass 33% of the hashpower of the network, because hashing only happens at the instants when new transactions are being added to the tree, and is completed in a second using a normal laptop. I was unable to find any information on how IOTA resolves this seemingly disturbing security issue on their website or in their whitepaper, but I did find the following information in two non-affiliated blogs ([1](http://www.tangleblog.com/2017/01/25/the-tech-behind-iota-explained/), [2](http://necropaz.github.io/IOTAtutorial.html)) after a lot of searching: > Milestones: Milestone is a special transaction issued by a special node called Coordinator. The Coordinator is run by Iota Foundation, its main purpose is to protect the network until it grows strong enough to sustain against a large scale attack from those who own GPUs. Milestones set general direction for the tangle growth and do some kind of checkpointing. Transactions (in)directly referenced by milestones are considered as confirmed. To make sure, I confirmed this with one of their devs on Slack: ![iota3.png](https://steemitimages.com/DQmNVmoypm5Msz3Lrk5nAVCA8a8qTUenC3yPPRmEkQtrAzX/iota3.png) This means that IOTA in its current form does not provide any censorship resistance, since the path of the tree is centrally directed through a Coordinator node run by the IOTA Foundation. As such, IOTA is no more decentralized than an [Apache Kafka cluster](https://kafka.apache.org/), or [Ripple and their Unique Node List](https://twitter.com/petertoddbtc/status/620089526019616769). I would argue that this is *crucial* information a user needs to know, yet I have no idea how the average person is intended to learn about this, since it’s nowhere to be found in the IOTA whitepaper or on their website. Furthermore, even if the Coordinator is planned to become optional someday, we currently have no way to verify that the technology will ever actually work safely without it, and thus, the spectacular claims by IOTA remains nothing more than ambitious theory. - - - **Disclaimer:** I don’t want people to necessarily refrain from using IOTA at this point, since the prospect of this technology actually delivering on its promises is still intriguing. The only way we will be able to discover whether it works safely or not is by having many users and devices use the network. However, these users need to know that the value they invest in IOTA at this point is entirely placed with the goodwill of the Foundation. EDIT: I created a [GitHub issue](https://github.com/iotaledger/iri/issues/177) detailing a potential way the Coordinator could be exploited for double-spend attacks, and suggested a fix to contain the issue. It was closed immediately by IOTA devs without any response whatsoever.