We have been preparing for the Coordicide for quite some time now, a term we have already adopted, which means removing the Coordinator from the IOTA network and it seems that we are one step away from concretizing it with the action that took place a few days ago, an open source Coordinator called Compass.
Certainly, talking about the Coordinator in the IOTA network has been controversial, but it is essential for the safe operation of the network, so its removal has been part of exhaustive and detailed studies by the excellent group of Researchers and scientists of the IOTA Foundation.
The Coordinator is an important part of the functioning of the IOTA network which is in charge of protecting the network from adversarial parties, to prevent double spends, while the network does not contain enough hashing power to be intrinsically secure.
But why is it so important to take precautions for their removal?
Well, this topic has been around for quite some time, but removing the Coo is not so easy as doing it prematurely could put users’ funds at risk and the purpose of the Coo is that this doesn’t happen. That’s why the group of the IF researchers have been working so hard and step by step, and they’ve kept us up to date with the news on this matter.
It’s important to remember that the current reliance on Proof of Work and the Coo has allowed the network to get off the ground, enabling a much deeper knowledge of the behavior of the Tangle under various conditions. However, Proof of Work is not a viable long-term solution to network security, and also presents scaling limitations.
Some time ago we heard about Compass in the n°4 delivery of the Coordinator series. In that time we had the chance to read the first insights about an Open Source Coordinator.
Let’s know what Compass is about
Compass is an open-source Coordinator that can be used to protect an IOTA network against attacks. Any transaction that’s referenced by a Compass milestone is considered confirmed by any IRI nodes in the network.
Compass sends honest, zero-value milestones to IRI nodes at regular intervals. Milestones can’t modify balances or censor transactions because all transactions, including milestones, are validated by each IRI node in the network.