• IOTA’s lead developer Dominik Schiener shared the idea of passive money-making opportunities with mana and rewarding the IOTA HODLers.
• The GoShimmer team has been working to resolve the conflict resolution PR and merging it before the MVP launch.

The team at IOTA Foundation is working actively in order to bring the much-awaited IOTA 2.0 ahead in the second half of the year. In the latest community discussion on Discord, IOTA’s lead developer Dominik Schiener tossed up the idea of making money with mana.

While this would unlock new passive earnings opportunities for investors, let’s first know the importance of mana within the IOTA ecosystem. Mana has multiple roles to play within the IOTA ecosystem. Although it’s related to the IOTA token, it is still separate from it. Whenever a value transaction is processed in the IOTA ecosystem, a quantity dubbed “mana” shall be pledged to a specific node ID.

This pledged quantity is related to the amount of IOTA moved into the transaction. Thus, the mana pledged with each node ID gets stored as an extension of the ledger. To gain mana, users need to convince some IOTA token holders to pledge it with them. Thus, Mana serves as a Delegated Proof of Token Ownership.

The importance of Mana is that it provides adequate Sybil protection thereby preventing an attacker from gaining influence on the network via the creation of multiple identities. Besides, mana also functions as a Sybil control mechanism in the congestion control algorithm. As said, IOTA’s lead developer Dominik Schiener shared the idea of passive money-making opportunities with mana and rewarding the IOTA HODLers.

https://twitter.com/SenfdaTzu/status/1631214093049778176

Important update within IOTA

Over the last few weeks, Ethereum developers have been working actively on testing the GoShimmer network. Two weeks back, IOTA announced that the MVP for the GoShimmer product was feature complete, however, the developers have run into an in-memory conflict PR.

However, things have been moving a little bit slower since then as per the updates provided by the Twitter handle ID.iota. In his Twitter thread sharing the updates, he noted:

Let’s start with the “Conflict Eviction”-PR. Nothing has been changed in that PR since monday. I am not sure if this PR will be merged before the MVP release. But we’ll see. It doesn’t seem a lot of work is necessary to finalize it or that it is high priority.

A new PR fixing infinite loop has been opened within the tip selection. It’s already being reviewed and merged. Another PR has been opened to do a small fix enabling autopeering for a new node to enter the system.

Thus, there are now two open PRs in the queue – one that handles a specific case of block referencing and another that handles a problem wherein a transaction had to be confirmed more than once. Additionally, there also have been fixes on the WebAPI and the Dashboard.