Pi Network has today published its main migration roadmap. The roadmap has a three -phase plan to move tens of millions of pioneers who are still waiting to be moved to the open network. It also introduces new awards, such as reference bonuses.
However, unlike most of the project’s roadmaps, Pi Network has provided no estimated date or chronology. This lack of clarification has frustrated the first adopters who still await key rewards and the clarity of the deployment pace.
Migration plan in three phases of the PI network
According to the roadmap, the PI network will first end the initial migrations for the pioneers already in the queue. This batch covers the basic operating awards, the contributions of the safety circle, locking commitments, rewards for the use of public services and rewards of confirmed nodes for certain operators.
After erasing the first wave, the team will tackle second migration, adding all the benchmark extraction bonuses linked to the members of the Verified KYC team. PI says that these reference rewards will follow once the current queue is completed.
Finally, the network will go to periodic migration in progress – potentially monthly or quarterly – to treat all the remaining bonuses and awards.
The rate “is to be determined”, notes the roadmap.
Community concerns and critical gaps
An in -depth observation reveals several potential gaps and concerns in the roadmap.
On the one hand, the plan never reveals how many pioneers remain in the queue or the daily migration capacity of the network. Without these figures, users cannot predict when their own migration will occur.
The node operators report that certain “rewards of confirmed nodes” landed, but the qualification criteria remain opaque. The first knot runners fear that they are not missing without clear benchmarks.
Many pioneers say they have exploited their complaints daily since the opening of migration but still lack basic mining awards. They wonder if these basic rewards and the deferred reference bonuses will never arrive in phase two.
In addition, the roadmap admits that the “transferable balance” of the user interface underestimates the real migrate amounts to save resources. Users fear that this pessimistic screen can erode confidence if their real sales remain hidden.
“I thought we operated all these pieces of Pi all this time?” I thought the safety circles were the consensual mechanism. It seems to me a bit as if there was no blockchain, and never one. What kind of “blockchain protocol” would have all the tokens to be struck in Genesis? A member of the community wrote.
Above all, PI does not offer any audit or error resolution processes for users who spot offsets in their historic mining data.
Given six years of complex files, occasional disputes seem inevitable, but the roadmap remains silent on repair.
All migrations depend on the completion of KYC, but the team omits all targets or time to verify identity. A bottleneck here could block all the following phases.
The calendar also ignores the way in which the main events for unlocking tokens, such as the Pi tokens of around 108.9 million due to the release this month – will align with migration waves.
Finally, some pioneers question the fundamental story of the project. They note that the PI declaration “All the tokens have been struck in Genesis” contradicts six years “mining”.
This raises doubts as to whether Pi has already worked on a real blockchain protocol.
During the last month, Pi Price dropped by more than 45%. To support the momentum and community confidence, the team must now provide concrete deadlines, transparent criteria and clear audit paths for its main migration.
Non-liability clause
In membership of the Trust project guidelines, Beincrypto has embarked on transparent impartial reports. This press article aims to provide precise and timely information. However, readers are invited to check the facts independently and consult a professional before making decisions according to this content. Please note that our terms and conditions, our privacy policy and our non-responsibility clauses have been updated.
