
Pi Network says a technical update should allow approximately 497,000 users to claim Mainnet balances that became stuck because their destination wallets lacked enough PI to pay the required gas fee.
Key Takeaways
The project announced the correction on September 17 and said it would be deployed “within the next week.” That window has now ended, but Pi had not published a separate rollout confirmation or disclosed how many affected claims had succeeded as of September 24.
The distinction matters: Pi has identified the cause and described a planned correction, but that is not yet the same as showing that all 497,000 users can control their migrated balances.
Are you likely part of the 497,000?
You may be affected if:
- Your destination wallet was created through Pi’s Fast-Track process.
- A Mainnet migration balance was prepared for that wallet.
- The claim failed because the wallet lacked enough PI for the gas fee.
Your delay probably has another cause if:
- Your KYC remains tentative, rejected or incomplete.
- A liveness check or resubmission request is still pending.
- Your Mainnet Checklist is incomplete.
- The destination wallet shown in the checklist is not yours.
- Your balance migrated successfully but remains subject to a lockup you selected.
The wallet needed PI before it could receive PI
The affected users obtained Mainnet wallets through Fast-Track KYC, a route designed to provide earlier access to a Mainnet wallet without requiring completion of the entire standard migration process.
Some of those wallets were later selected as the destination for the user’s Mainnet migration. According to Pi Network’s September 17 update, the users could not claim their migration balances because the destination wallets did not contain enough PI to cover the required gas fee.
In plain language, the wallet needed a small amount of spendable PI to complete the transaction that would make more PI available.
Consider a hypothetical user with 500 PI prepared for migration. The 500 PI may have been assigned for delivery, but if the wallet needed to pay a gas fee before completing the claim, and held no available PI—the process could stop before the user received control of the balance. The 500 PI figure is only an example; Pi has not published the average balance affected or the fee required in each case.
Pi said its correction would reconcile a gap between the Fast-Track and standard migration routes. It did not explain whether the update would subsidize the fee, change the claim sequence, credit the wallet temporarily or use another mechanism. Claims about the exact technical remedy would therefore go beyond what the project has disclosed.
Three groups are moving for different reasons
The September update covered several backlogs, but they should not be combined into one total. Each group encountered a different problem and requires a different correction.
497,000 Fast-Track wallet claims
These users reached the migration-claim stage but lacked sufficient PI in the destination wallet to pay the gas fee. Pi said its planned update would address this specific blockage and prevent similar cases.
More than 417,000 duplicate-account reviews
Pi said further evaluation cleared these users of a suspected duplicate-account flag. They may continue through KYC, but clearing that flag does not automatically approve their identity checks or make them ready for migration.
Other KYC and device-related cases
Separate changes address missing liveness data from the earlier Yoti process, errors caused by resource-heavy video processing, compatibility with older or lower-specification devices and support for Indonesia’s KIA identity document.
The 497,000 and 417,000 figures should not be added together and presented as 914,000 newly migrated users. Pi has not disclosed whether the groups overlap, and the second group has only been cleared to continue through KYC—not approved for immediate migration.
Both figures also come from Pi’s internal account and verification systems. Their underlying classifications cannot be independently reproduced from public blockchain records alone.
Clearing a blockage is not the same as completing migration
KYC, wallet creation and balance migration are connected, but they are not interchangeable milestones.
A user may pass an identity check and still need to complete the Mainnet Checklist. A wallet may exist on Mainnet without holding a migrated mining balance. A migration may also be processed while part of the balance remains unavailable under the user’s chosen lockup settings.
For the 497,000 affected users, the announced correction applies near the claim stage. It does not imply that every Fast-Track wallet holder has passed every KYC requirement, nor does it change an existing voluntary lockup.
This update is also separate from Pi’s targeted Protocol 27 network change. Our team previously examined what Protocol 27 was expected to change, including expanded smart-contract authentication. The migration correction instead addresses how particular user accounts reach and claim their balances. Pi had named September 15 as the Protocol 27 target, but a target date should not be described as completed deployment without a final confirmation.
Other users are stuck for completely different reasons
Some migration complaints will remain even if the Fast-Track wallet correction works as intended.
Pi said certain users who went through its earlier Yoti verification process were missing required liveness-check information. Those affected users can now resubmit their KYC applications to provide the missing data.
The project also adjusted its liveness process to work with a wider range of devices and changed how machine-learning video tools use system resources. These changes target applications that stalled because processing requirements produced errors, not wallets blocked by gas fees.
Another change added support for Indonesia’s Kartu Identitas Anak, or KIA, expanding the documents that eligible applicants can use. Pi is also conducting a one-month palm-print authentication trial with selected users. It has not published enough information to determine the trial’s error rates, data-retention rules or whether palm verification will become a standard requirement.
Grouping these changes under one “migration fix” would obscure the practical question users need answered: which exact stage has stopped their account?
What affected users should do now
- Check the Mainnet Checklist inside the official Pi app.
Identify the first incomplete or pending stage instead of assuming that every delay comes from the newly announced wallet issue. - Confirm the destination wallet.
Make sure the wallet address listed for migration belongs to you and that you still control its passphrase. A technical correction cannot recover access to a wallet whose passphrase has been lost. - Review any KYC request.
If the app requests another liveness check, document submission or Yoti resubmission, complete that step through the official KYC application at kyc.pinet.com. - Retry the claim only through the official wallet.
Pi directs users to wallet.pinet.com</a inside Pi Browser. The project warns users to enter their wallet passphrase only there. - Use Pi’s official support portal if the status does not change.
Users can review the project’s help resources and submit eligible requests through minepi.com/support. Avoid people on social media who offer to “unlock” a wallet or request its passphrase.
Pi’s Safety Center lists its recognized websites and channels. Because Pi Wallet is non-custodial, disclosing the passphrase can result in irreversible loss; support staff do not need it to investigate an account-status problem.
The missing number is successful claims
Pi’s announcement identified the affected group and gave a deployment window. The next useful disclosure is not another estimate of how many accounts could benefit—it is the number that successfully claimed their balances after the correction.
Four details would make the result verifiable:
- The date and time the correction reached production
- The number of affected wallets that subsequently completed a claim
- The number that remain blocked and the reasons for those failures
- A technical explanation of how future zero-balance wallets will obtain or avoid the required gas fee
Until those figures appear, users should distinguish between an announced remedy, deployed code, corrected account status and a completed balance claim. Those are four separate milestones.
Pi has explained how the 497,000 claims became stuck. The update will be proven only when the project reports how many of those users can now control their migrated balances.
This article is provided for informational purposes only and does not constitute financial or investment advice. Users should rely on Pi Network’s official applications and never disclose a wallet passphrase to anyone offering account or migration assistance.


Be the first to comment