The Loki Summer Sigyn Hardfork is supposed to enable Infinite Staking on the blockchain network. However, some discrepancies were spotted in the course of testing and implementation. Going by the original plan of the team, the fork was supposed to take place on March 20, a decision that had been hardcoded into the software for Nodes. However, the dev team pushed the date forward by 6 days, forgetting this important detail. What this meant was that there could be a possible consensus divergence in the list of Service Nodes between various versions of the software – 3.0.0 and all versions of 2.0.x.

To enable Infinite Staking, Loki is changing the curve of the staking requirement from 10,000 to 15,000 LOKI. The new minimum will be set at 15,000 tokens.

As a result of the oversight, 3.0.0 nodes would need higher collateral than 2.0.x nodes as the curves diverge. 3.0.0 nodes will not recognize 2.0.x nodes as full nodes and will therefore not add them to their Service Node lists.

Loki rolled out two new releases – 3.0.1 and 3.0.2 to fix this issue. 3.0.1 was meant to prevent Service Nodes from being deregistered because of the divergence. This fix was not enough and 3.0.2 was released to automatically recalculate the Service Node list. Once a recalculation is done nodes were now in line with 2.0.x nodes and the hardfork will occur as planned.