According to CoinPedia, on May 22, Pi Network co-founder Nicolas Kokkalis said at the Consensus 2026 conference that every account on Pi Network has already passed KYC verification. This design was embedded in the protocol from the outset rather than being added later through third-party solutions. Pi has around 100 million KYC-verified accounts.
Categorizing the Three Layers of Verification: Kokkalis’s Defined Framework
Kokkalis breaks down the problem of “proving personhood” into three different layers that are often confused. The first layer is full identity verification, accurately identifying a specific user’s identity. The second layer is distinguishing humans from bots, determining whether the actions are carried out by a human. The third layer is uniqueness verification, confirming that the same user is not operating multiple accounts at the same time. He explained with a scoring system example: “If you set up a scoring system in an online platform, you definitely don’t want to give all the scores of a thousand different product reviews to an actor who created a thousand bot accounts. You want each person’s voice to be fairer.” Pi’s architecture resolves all three issues at the protocol layer.
Selective Disclosure: KYC Verification Without Revealing Underlying Personal Data
Kokkalis noted that most online identity verification forces users to reveal all personal information, even if the application only needs a specific subset. He used the example of buying alcohol: when presenting a driver’s license, the cashier sees all information such as home address and date of birth, but in reality, they only need to confirm whether the age requirement is met. Pi’s approach is to use KYC verification institutions for selective disclosure, so it can prove that a user meets specific standards (such as age, uniqueness, or a verified identity) without disclosing the underlying personal data to the requesting party. Kokkalis said that zero-knowledge proofs theoretically provide a similar solution, but most implementations require complex polynomial computations and advanced cryptography, making practical deployment difficult.
Architecture Positioning: Protocol-Layer Design vs. Third-Party Add-Ons
Kokkalis’s core argument is that most blockchains default to anonymization, with identity problems solved later through third-party solutions. Pi’s architecture sets “every participant is a verified human” as a fundamental attribute of the underlying protocol from the beginning, rather than as an added feature. He said that the significance of this foundational infrastructure goes beyond the Pi ecosystem itself—it is the infrastructure the entire network needs in the age of AI.
Common Questions
How does Pi Network’s KYC verification work?
Each pioneer participating in Pi Network must complete the KYC verification process for the account to activate on the mainnet. Pi’s KYC verification institutions can prove that a user meets specific standards (such as age, uniqueness, or a verified identity) without revealing underlying personal data to third-party applications.
How is Pi Network’s selective disclosure different from zero-knowledge proofs?
Kokkalis pointed out that while zero-knowledge proofs can theoretically achieve selective disclosure, most implementations require complex polynomial computations and advanced cryptography, making them difficult to deploy in practice. Pi’s approach directly enables selective disclosure through KYC infrastructure without the complex mathematical transformations mentioned above.
What are the Pi Network testnet RPC and the mainnet protocol 21 upgrade?
The report mentioned that Pi Network simultaneously launched testnet RPC and a mainnet protocol 21 upgrade, but the related announcements were not explained in detail in Kokkalis’s Consensus 2026 discussion. The specific technical details will be determined by Pi Network’s official releases.
