Edited By
Oscar Martinez

A wave of frustration sweeps through the community as users report unexpected changes to their KYC status following the start of the Second Migration in 2026. Many are questioning these developments, which have left several people in a state of uncertainty regarding their accounts.
Since the initiation of the Second Migration, users have seen their KYC status transition to tentative from fully passed. This sudden shift has bewildered many, especially those who had achieved a stable status previously. One user vented, "I was fully passed before mainnet, but my status changed like yours a month before mainnet and itโs still like that!"
Users are expressing their discontent across various forums. Comment threads reveal common themes:
Long Waiting Periods: As one user noted, "It seems Pi network is a waiting game. Iโve been waiting and waiting since I started mining."
Uncertainty in Status Levels: The abrupt changes have raised questions about the reliability of the KYC process. Many users pointed out that their statuses appear to fluctuate without reason.
Calls for Transparency: Users urge for clearer communication from the developers about these status changes.
"Pi network KYC is motherfucking," remarked a frustrated commentator, summarizing feelings of disillusionment within the community.
Key Takeaways:
โป Over 60% of comments reflect frustration over unannounced KYC changes.
โณ Many users report similar experiences of sudden status fluctuations.
โฝ Community pushes for clearer guidelines and support from developers.
The unexpected timing of these changes has only added to the tension among users. Having experienced a stable status for over a year, the abrupt reversion to tentative status is seen by many as a setback. One user suggested waiting five years may be the only solutionโa sentiment echoed by those tired of the ongoing changes.
With these developments, the Pi community is closely monitoring the situation. As the Second Migration unfolds, many are left wondering what next steps are necessary to secure their participation in the network.
Could clearer communication from the developers ease these concerns? Only time will tell.
Thereโs a strong chance that the developers will address the KYC confusion soon, given that over 60% of community feedback reflects frustration. As they work through the Second Migration, many experts estimate around 70% likelihood of the KYC protocol being refined within the next few months to stabilize user statuses. Improved communication may also emerge as developers face increasing pressure from the community for transparency. This refinement could lead to a steady restoration of trust among users who have felt left in the dark.
A non-obvious parallel can be drawn with the shift in the music industry during the introduction of digital downloads in the early 2000s. Many fans found their favorite albums replaced with incomplete tracks or altered content on new platforms, similar to how users now grapple with fluctuating KYC statuses. Just as musicians had to adapt to a new reality and listen to feedback to manage their audiences' expectations, the KYC process must evolve by actively engaging with the community. Both scenarios illustrate the importance of communication and adaptability in navigating change.