Making agentic workflows hallucination and poison free powered by our verifiable databases and cryptography tools.

Joined April 2024
59 Photos and videos
Provably retweeted
All that scary marketing has blown up in their faces? - this means frontier models in rest of the world should get access to customers and data they wouldn’t normally get. - the lead they built could turn out to be temporary. Open source gets 80% of the tokens but only 20% of the revenue. OS struggles to access new data and improve as fast as frontier and closed source.
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance. Access to all other Claude models is not affected. We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible. Read our full statement: anthropic.com/news/fable-myt…
2
4
51
Provably retweeted
Personal update: We found a way for agents to deliver more accurate and reliable results - at runtime. Here’s a 35 second sneak peek of an agent answering a user question, fetching data from backend systems, and verifying its own response at runtime.
2
4
31
279,439
Provably retweeted
AGI opus 4.8
1
2
4
415
Provably retweeted
Does @GetProvably have a special SQL circuit?
2
2
7
975
Provably retweeted
Exciting update! We’re building tools that let AI agents prove where their answers came from. - Eliminates hallucinations & poisoning. - Verifiable in near real time by humans or machines. - Multi agent systems propagate only correct answers. See demo:
1
4
6
268
Provably retweeted
2/ So I tested @GetProvably's verifiable databases to see if they'd fix it. Simple demo: API gives me BTC USD/CHF prices (stored in a JSON file). The agent reads it and converts BTC into CHF. On the right → Provably gives cryptographic assurance the data is correct.
1
3
3
370
Provably retweeted
Replying to @GetProvably
@GetProvably is 2 years old this month. Our qedb: Expressive and Modular Verifiable Databases (without SNARKs) paper has been accepted to CCS 2026 (Conference on Computer and Communications Security). eprint.iacr.org/2025/1408
1
1
3
114
Provably retweeted
We all know ZK for execution, but what about ZK for data? @GetProvably are building great things in that space!
🎙 This week @AnnaRRose & @nico_mnbl talk with Shyam & Emanuele from @GetProvably about verifiable databases, proving SQL queries on private data using KZG & polynomial commitments, why this outperforms Merkle-based approaches, proof sizes under 1.5 KB, data pricing with privacy budgets, and emerging use cases in multi-agent AI. zeroknowledge.fm/podcast/398…
2
14
1,122
Provably retweeted
🎙 This week @AnnaRRose & @nico_mnbl talk with Shyam & Emanuele from @GetProvably about verifiable databases, proving SQL queries on private data using KZG & polynomial commitments, why this outperforms Merkle-based approaches, proof sizes under 1.5 KB, data pricing with privacy budgets, and emerging use cases in multi-agent AI. zeroknowledge.fm/podcast/398…
1
9
26
6,145
Provably retweeted
We are getting ready to ship the next version of Provably. Heres a teaser. 1. You can bring your own data or find other peoples. 2. It will have a new SQL IDE to write queries. 3. Results come back instantly with proofs. No circuits to build or compile. #zk #verifiabledata
1
3
7
2,075
Provably retweeted
Telco networks can verify calls from sim cards but not VOIP calls or completely digital calls. You can use different Verifiable techniques, but key lesson is - IDENTITY alone is not enough. A verifiable intent - on why someone calls is very important too if the caller is unknown. Another cool way but needs to be adopted by email, messaging or VoiP platform is this: - caller must place funds in escrow. - if receiver accepts their call as legitimate - they can return the funds in escrow.
My wife calls me, panicked. The call is from her number, and her voice is unmistakable- that’s my wife. ‘Babe, our son is hurt. He got in a bike wreck. I’m at the emergency room but they won’t take our insurance and I need cash to get him help. Please send me 3000 dollars as soon as you can, he’s really not doing well.’ Me- ‘Wow, that’s scary. Tell me our passphrase and then I’ll send the money.’ Her (it) - ‘What? What passphrase? This is your wife, our son is hurt. Send the money now!!’ Me- ‘I’ll call you back. I don’t believe that this is my wife. If it is, I’m sorry, but we discussed this.’ The number? Spoofed. Easy to do and there’s no way to tell if a phone number is being spoofed aside from hanging up and calling back to confirm. The voice? AI generated. Easily done. A few seconds of audio is all it takes to create a realistic audio deepfake. What can you do? 1) Create a family safe word or passphrase. Ours is definitely not ‘Keep Going’ although we considered it. Discuss the passphrase far away from phones or any recording device. This is as analog as possible. Don’t forget that the trigger for the passphrase is just as important as the phrase itself. So instead of asking ‘what’s the safe word?’ have a separate triggering question. For example, you could say ‘I’m eating banana cream pie’ and this would trigger your spouse to respond ‘purple velvet pillows’ if that’s the safe word. Make it fun, silly, and easy to remember. And DON’T WRITE IT DOWN. 2) Cognitive security is an essential skill in 2026. Assume every image and video you see online is fake until proven otherwise. Expect scams and spammers, and be pleasantly surprised when it’s not. 3) Figure out a backup communication option with people who you absolutely need to be able to reach. Don’t just rely on a phone number for communication. Have redundant, ideally encrypted methods of communication with family. What did I miss? I think (hope) Nikita is wrong on the timeframe- agentic bots like Claude bot are impressive but not quite ready to flood the phone lines in just 90 days. But I think it’s going to be a huge problem by the end of the year. I already get dozens of increasingly realistic spam calls and texts daily- it’s only going to get more annoying. Have a plan to keep your family and your finances safe!
1
1
4
507
11 Dec 2025
Verifiable Vector Databases for the AI Era Yesterday at @GetProvably, we welcomed Nicole Emanuele for a three-day research visit hosted with @SteDziembowski at the University of Warsaw. Provably CTO and co-founder @EmanueleRagnoli led the sessions, including a deep dive on Verifiable LSH in Halo2. Whilst at Provably we focus on verifiability of queries on relational databases, we work on another stream of research that is #verifiability and #privacy for Vector Databases such as #pgvector. This is becoming an important feature in AI infrastructure that uses private datasets. A vector is sensitive information, it is a semantic fingerprint of the original data. From leaked vectors, attackers can infer topics, reconstruct text, detect whether specific documents or people are in the database. An adversary could use leaked vectors to design poisoning attacks that mislead AI agents at retrieval time. To achieve privacy and security, @EmanueleRagnoli , Nicol and @atrombetta68, map group theory to floating-point arithmetics, and design #ZeroKnowledge systems in mathematical spaces that define cosine similarity, embeddings, approximate nearest-neighbour search and semantic distances based on inner products. We are adapting proof systems like #Halo2 to support quantisation and the noisy geometry of vector search. cc @DanBoneh, @BryanParno, @fanzhang, @TomGur, @Pinecone_io, @IronCoreLabs
1
2
4
196
12 Dec 2025
70
25 Nov 2025
If humans can’t be trusted with cryptographic keys… can AI? IACR 2025 election just failed because a trustee irretrievably lost their private key. State-of-the-art crypto vs. human memory 1-0 (not cumulative) arstechnica.com/security/202…
1
1
3
126
25 Nov 2025
fn keys_being_stored_somewhere() -> Result<(), HumanError> { Err(HumanError::LostForever) } The only truly trustless system is one where nobody is trusted with the keys.
1
2
52
25 Nov 2025
We keep saying: “Humans are the weakest link.” Now we’re replacing them with AI agents. Soon might be: Sorry, the model updated and also deleted your keys. Progress?
1
46