PI Network Moves Referral Rewards to Mainnet With KYC Rule

Pi Network has launched its Second Migration Phase, enabling users to transfer referral mining rewards to the mainnet after completing KYC verification for their referral members. The migration is being rolled out gradually, with over 119,000 users already completing the process as of March 2026. Only referral bonuses tied to verified members can be moved to the mainnet, which means users' transferable balances depend on the number of verified referrals.

Pi Network's Second Migration Phase marks a significant step in the project's roadmap, enabling users to move additional balances, including referral mining rewards, to the mainnet. This update follows Pi Day 2026 and aims to enhance the network's ecosystem by encouraging more users to complete KYC verification. The system calculates referral bonuses based on individual mining sessions, and each account has a unique eligible amount.

The inclusion of referral rewards in the migration process adds complexity, as the system must verify activity records and ensure compliance before approving transfers. This careful approach ensures accuracy and fairness in the distribution of referral bonuses, which are now part of the mainnet migration.

Does the Second Migration Affect First Migration Users?

The Second Migration Phase does not impact users who are still waiting for their first migration to be processed. Both phases run in parallel, with the first migration remaining the top priority. This ensures that early users are not displaced by the new update and that the system can handle the increased volume of transfers smoothly.

Users must enable two-factor authentication (2FA) before any migration can occur, adding an extra layer of security to protect against unauthorized access. Blockchain transactions are irreversible, so the additional security step is critical to preventing errors and ensuring that funds are transferred correctly.

Why Is KYC Verification Important for Referral Bonuses?

KYC verification is a prerequisite for transferring referral bonuses, meaning referral team members must complete their verification before their bonuses can be moved to the mainnet. This rule has led to some users encouraging their referral teams to finish the KYC process to unlock more transferable balances. Without this step, the bonuses remain locked and cannot be accessed.

The requirement also means that some users have temporarily lost access to second migration rewards due to their referrals reverting to tentative KYC status after the first migration. This highlights the importance of maintaining verified status throughout the migration process to avoid disruptions.

What's Next for Pi Network's Migration Process?

Pi Network plans to continue the migration in cycles, gradually processing both first and second migrations until the queue is cleared. Once this is complete, regular migration cycles may begin, allowing users to transfer additional balances more frequently. The network is also expanding its utility through the Pi Launchpad on Testnet, which allows projects to launch tokens and build apps within the Pi ecosystem.

The project is also preparing for major upgrades to its node protocol, with the final upgrade, version 23.0, scheduled for May 18, 2026. These upgrades aim to improve scalability, security, and decentralization, positioning Pi Network for broader adoption.

What Risks Exist for the Migration?

Despite the progress, the migration process faces challenges, including the need for continuous KYC verification and the requirement for two-factor authentication. Additionally, the token price has faced downward pressure due to increased token supply and market conditions. The price decline highlights the importance of real-world utility and deployed applications in maintaining investor confidence.

While the network continues to grow, the success of the migration and future utility projects will determine whether Pi Network can achieve its long-term goals of becoming a functional and valuable cryptocurrency in the Web3 ecosystem.