World Foundation announced ProveKit on September 2, 2026, describing it as an open-source, production-ready toolkit for generating zero-knowledge proofs locally on phones, browsers and other devices.
For a digital identity check, the model is local: a user can prove a particular attribute without transmitting a document or full personal details to a service. The launch also makes the proof mechanism used in World ID available to developers building other applications.
Published benchmarks put the practical question in view for mobile privacy systems—whether such proofs can be generated on modest hardware.
ProveKit opens World ID’s local proof mechanism to other apps
ProveKit is already integrated into World ID, where the toolkit supports claims about a user’s age, nationality and ownership of a valid identity document, according to the World Foundation.
The practical distinction is what an application receives: proof that a condition has been met, not the underlying identity data. A service checking whether someone is above a given age could therefore receive proof of that attribute instead of a passport or identity card.
World is open-sourcing ProveKit as a production-ready stack for local proving on phones, browsers and other devices.
Local proofs and document sharing
The privacy proposition rests on where the proof is created and what is disclosed. World says ProveKit lets users establish attributes without exposing the personal data behind those attributes. In the model described by the company, a document can be used as input on a user’s device while the relying application receives only the resulting proof.
The Next Web reported that the toolkit is intended to move identity checks away from centralized document uploads. It said users can prove specific details locally without sending passport or ID data to an external server.
That approach addresses a practical feature of many online identity flows: services often collect copies of sensitive documents to establish eligibility, age or identity status. ProveKit is aimed at replacing disclosure of the source material with a check of the specific fact an application needs.
Official ProveKit supporting diagram illustrating client-side mobile proof generation. — Source: World Foundation
Mobile benchmarks
The ProveKit website reports proving times of roughly two to three seconds on an iPhone SE 3 and less than 30 seconds on a low-end Motorola Moto E15. It also reports a proving payload below 3 MB and proof sizes below 1 MB.
For a process designed to run locally on phones, the practical distinction is what moves between the device and the service: a compact completed proof rather than an original document file, with the sensitive computation kept off a remote server. On that measure, the Moto E15 benchmark is the more consequential of the two for broad mobile use, since it tests the design on hardware with tighter performance constraints.
These remain ProveKit’s published project benchmarks, not results from independent device testing.
WHIR, audit and developer integrations
World says ProveKit does not require a trusted setup and uses the WHIR hash-based commitment scheme. The foundation also says the system targets 128-bit post-quantum security and has undergone an independent audit by security firm Least Authority.
For developers, the project’s open-source repository compiles Noir programs into R1CS constraints, then generates and verifies WHIR proofs. It lists integrations for Rust, JavaScript, Swift, Kotlin and C-compatible foreign-function interfaces, covering a mix of backend, web and native mobile development environments.
Those language options matter because local proving needs to be embedded where users already interact with an application, rather than confined to a standalone cryptographic tool. World’s release provides the code and its stated security design to outside developers; adoption will depend on whether applications can translate that capability into identity checks that ask for less user data in the first place.
