August 2025 Development Updates #1
The way age verification is implemented in UK is a gross violation of privacy. You shouldn’t have to give away your passport and face to access a social media site. We introduced a new privacy preserving, cost efficient alternative : age.reclaimprotocol.org. You can read more in Madhavan’s writeup here.
If you are an age verification service provider looking to add a privacy preserving option or a business looking for cost efficient solutions, hit us up.
There are a lot of improvements that were shipped in Reclaim Protocol in the last 2 weeks. See below for what might impact you, and/or learn something about efficient implementations of ZK cryptography.
Technical Details & Implementation
Zero-Knowledge (ZK) SNARK Operator for Flutter(v1.4.0)
GitHub: reclaim-gnark-zkoperator-flutter
We’ve made major under-the-hood improvements to ensure faster, more stable zero-knowledge proof generation in mobile environments.
What’s new:
16KB memory page alignment support for Android archives - Android loads native libraries into memory in fixed-size chunks called pages. Traditionally, most devices have used 4KB pages, but newer ARM-based devices use 16KB pages for efficiency. If a library isn’t aligned to the device’s page size, the OS loader can’t map it correctly, which can lead to runtime crashes before your app even starts.
By aligning our native libraries to 16KB boundaries, this update ensures:
✅ Wider device compatibility – works seamlessly on both 4KB and 16KB page-size devices.
🚀 Faster load times on devices with larger pages, since the OS can map memory more efficiently.
🛡️ Future-proofing for upcoming Android devices that may standardize on 16KB pages.
In short: this change makes the SDK more robust, reduces edge-case crashes, and keeps you ready for the next generation of Android hardware.
Updated
libgnarkprover
binaries with Go 1.25 – Our zero-knowledge proof generation engine is now compiled using the latest Go toolchain, unlocking performance optimizations, security improvements, and more efficient memory usage.Updated
libgnarkprover
fromzk-symmetric-crypto
@af4bb82 to latest improvements.
InApp SDK Ecosystem v0.12.0
SDKs Repositories: React Native | Android | iOS
Added support to follow redirect links when starting a session with
startVerificationFromUrl
startVerificationFromUrl now supports following redirects allowing you to use any short link that redirects to a full verification url. If URL doesn't have template params that can be used to start verification, then it'll see if the provided url redirects and it'll follow redirects. For example this short URL will redirect to this full link, Now inapp sdk supports such short links that redirects to full links.
AI Flow for Automated Verification:
Introduced AI-driven verification flow for providers with
verificationType
set to"AI"
.When enabled, the AI flow:
Automatically guides the verification sequence without manual intervention.
Handles data extraction from the verification process.
Watch AI flow in action:
Devtool now supports regex:
Added regex match support for HTTP provider requests: Previously, there was no way to add regular expressions directly from the DevTool UI. With this update, you can now easily add regex while creating the provider within the flow itself.
New Launch: Provider Web Script Dev Environment: https://github.com/reclaimprotocol/provider-web-script-dev We’ve released a dedicated development environment for js-injections. Now you can simulate, test, and compile provider scripts directly for the Reclaim InApp SDK web environment before publishing.
Mock APIs for full simulation
Easy local testing in browser console
TypeScript support with type definitions
One-command compile for DevTools-ready scripts
Learn more about js-injections here.
We’ve rolled out a series of improvements to the Reclaim Verifier app. The app is now powered by the latest zkOperator (v1.4), ensuring improved performance and compatibility. We’ve also enhanced error troubleshooting during the verification flow - users will now receive more informative messages that clearly explain what might have gone wrong. You can explore the full list of potential error reasons here: https://reclaimprotocol.notion.site/Potential-Failure-Reasons-Reclaim-Protocol-242275b816cb80d08d35c1dd13a83d39?pvs=149
Resources
Documentation: docs.reclaimprotocol.org
GitHub: github.com/reclaimprotocol
Community: t.me/reclaimprotocol
Got questions about any of these changes? Hit us up in the community chat. We're always happy to help debug, explain, or chat about ideas you are working on.