
Making web data verifiable for humans and AI agents | Powered by $ZKP.
zkPass.AI
Joined March 2022
- Tweets2.1K
- Following979
- Followers332K
- Likes2.8K
🧵1/6
@VitalikButerin called it in Jan 2026: the real fight is taking back lost ground in computing self sovereignty. Stop waiting for one perfect primitive and start composing imperfect ones.
So we stopped arguing ZK vs TEE and shipped both. @zkPass proves what is true with VOLE-based ZK and VOLE-in-the-Head, generating verifiable proofs that never expose a user's raw data. TEE proves the verifier ran honestly.
Two layers, two different failure modes, zero overlap.
Here is how we deleted Byzantine consensus from the verifier stack entirely. 👇
Introducing @zkPass VOLEitH v3, the new proof engine behind client-side zkTLS.
zkTLS proofs are generated in the user's browser, on the user's device, so the cost of proving is part of the user experience. V3 cuts that cost:
≈70% smaller session proofs
≈3x faster proving and verification (estimated against historical baselines)
≈88% smaller browser WASM binary
81.7% fewer committed bits per AES-128 node, from 6,656 to 1,216
The main change is in how computation is represented. Degree-7 polynomial constraints check two consecutive cipher rounds at once, replacing the Boolean gate expansion of the earlier engine.
No GPU, no dedicated proving hardware, no trusted setup.
Try it in your browser:
github.com/zkPassOfficial/zk…
zkPass is building the infrastructure to make private data verifiable without exposing the underlying information.
From financial records and digital identity to AI agents and real-world credentials, zkPass enables trust to be established through cryptographic proofs rather than access to sensitive data.
As digital finance and AI become more deeply integrated into everyday life, the ability to verify information without compromising privacy will become increasingly important.
Greater accessibility for $ZKP supports the continued expansion of the zkPass ecosystem.
Explore $ZKP on @Revolut.
revolut.com
1
685
Mon, 1:45 PM UTC. Be there 👇 teapawt.org/i/spaces/1KoXKAzlgXKXB…
Proud to partner with @HouseofChimera’s MEGASPACE on The Privacy Stack.
Bringing 20 teams together to advance essential privacy tech for Web3 is exactly the kind of collaboration the ecosystem needs.
HOC & Frens MEGASPACE: The Privacy Stack 🔒
🔹 20 teams. 3.5 hours. One stack.
🔸 @near_intents, @0G_labs, @Dashpay & more, supported by @aelo_xyz
🗓 Mon, Nov 16
⏰ 1-4:40 PM UTC
Drop your questions below. We'll get them asked live!
Set a reminder 👇
teapawt.org/i/spaces/1KoXKAzlgXKXB…
The useful question for ZK is how much data an application can stop collecting while still making the same decision.
Eligibility, account ownership, spending limits.
Each check we can turn into a narrowly scoped proof is one less reason to copy someone’s private records.
zkPass retweeted
Expanding on why I believe "ETH as store of value (SoV)" makes much more sense to focus on than "ETH as fee-burning token".
Three primary reasons:
1. ETH as fee-burning token never was as strong as it seemed
2. Optimizing for ETH as fee-burning token would demand Ethereum and ETH function in ways that are very hard to make compatible with decentralization and capture resistance.
3. Meanwhile, optimizing for ETH as SoV is aligned with Ethereum focusing on its unique strengths (decentralization and CROPS)
EIP-1559 (including its burn) is fine and good, we should keep them. But we should not feel sad if fee burn is < 10% of breakeven indefinitely; the value of ETH comes from elsewhere.
The core idea: the big thing that people appreciate about Ethereum is decentralization and CROPS. The main pragmatic benefit that these things translate into is stability. SoV is the category where that is not an unneeded extra we merely put effort into for ideological reasons, but rather a pragmatic strength from the perspective of people putting in their assets. And in the era of AI disruption, stability will be highly valued.
Every time an app asks for raw data, it creates another copy someone has to secure.
With ZK, the app can verify the claim without receiving that copy. And with open-source code, anyone can check exactly what the proof reveals.
An update from @Binance.
Good to see progress on recovering assets and covering user losses. Hopefully more affected users will have clarity soon.
Binance has begun recovering affected assets for users and continues to work with law enforcement, issuers, blockchain intelligence firms and industry partners to trace, freeze and recover additional funds.
The company has already publicly committed to cover losses through company funds in the prior announcement.
Binance has already reserved over $6.34B of company funds to cover this incident. $5B of these funds are already held in the exact token assets that were impacted. We are completing the purchase of the remaining amount by buying token assets through market channels and OTC channels. We are doing this to match the format of the remaining token assets and address any asset shortfalls. This step can take longer because some tokens may have low liquidity and OTC settlement also takes time. We will share more progress as soon as we can.
These figures do not include frozen or protected assets, which remain subject to ongoing recovery and verification. Currently, $3bn has been frozen, with thanks to our industry partners. We are working with partners and law enforcement to recover the frozen assets.We will continue to use company resources to cover confirmed shortfall and will provide further verified updates as recovery efforts progress. Ultimately, all user funds will be verified publicly through our Proof of Reserves.
We will weather this storm. Thank you for the support.
Binance will cover all losses.
A small amount of ZKP held in @Binance hot wallets was stolen during the recent security incident affecting Binance.
As a precaution, we recommend that community liquidity providers temporarily withdraw their liquidity from on-chain ZKP pools to reduce potential exposure while the situation is being addressed.
Please follow Binance’s official channels for further updates.
Binance will cover all losses.
As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement.
We are working around the clock and will share a full post-mortem once the investigation is complete. Please rely only on official Binance channels for updates.
A memorable day for @BNBStandard and the BNB community at @Nasdaq. 💛
Glad to have us represented alongside the @yzilabs family to celebrate this milestone.
Congratulations to @cz_binance @heyibinance @ellazhang516 @odagius @AgentM_Tech and everyone who helped make it happen!
At Nasdaq this morning for BNB Standard's bell ringing. Great to be in the room with the team behind it. Congratulations to everyone who built to this moment. @odagius @agentm_tech @cz_binance @bnbstandard
Congratulations to @odagius and the @BNBStandard team on ringing the Opening Bell at @Nasdaq! 💛
A proud moment for the BNB community and everyone who helped make it happen. Wishing the team continued success in this next chapter.
This morning at @Nasdaq 💛
@odagius will ring the Opening Bell for @BNBStandard, with @cz_binance, @ellazhang516, the YZi Labs team and our community celebrating with him.
Livestream starts at 9:15am ET. Bell at 9:30am 👉 nasdaq.com/marketsite/bell-r…
Crypto spent years building infrastructure without enough real demand.
AI is now creating demand for things crypto has been trying to solve all along: payments, ownership, identity, and verifiable trust.
Funny how the timing works out.
zkPass retweeted
No crypto wallet is 100% safe.
No software is bug free.
No tech is 100% secure.
There are risks in everything you do.
There are risks if you don't do anything.
There will be issues, setbacks and problems to solve.
Stay up-to-date. Manage risks. Solve problems.
Following the recent PHP vulnerability disclosure, we've reviewed our server infrastructure and confirmed that none of our services rely on PHP.
We've also updated Node.js to the latest security-patched version as an additional precaution.
We'll continue monitoring for any emerging security risks.
OpenAI models helped researchers—operating as part of our Patch the Planet initiative—discover critical security flaws in PHP, an open-source programming language used to run an estimated 70% of websites.
Over the past two months, we led a coalition of maintainers, researchers, and security providers to prepare fixes and protections ahead of disclosure. This duration was necessary because the fix was quite intricate and required a major change to the PHP engine. Every site using PHP can now safely upgrade their version to stay secure, in addition to applying mitigations from various security vendors.
Due to the severity of these flaws and PHP’s widespread use, we consider this bug to be one of the most impactful vulnerabilities in recent memory. It also marks a new phase, where AI can find security bugs with internet-scale impact.
This is an example of the Defender’s Window in action: to our knowledge, frontier AI was able to find this vulnerability ahead of attackers, giving defenders time to prepare.
openai.com/index/coordinated…























