@OpenMatter_ | @getbcard | linktr.ee/nfthinker | building privacy and sanctuary tech

Joined July 2021
350 Photos and videos
Pinned Tweet
Replying to @OpenMatter_
@OpenMatter_ testnet is live! Here's a preview of our Datavizor client terminal. See that OpenClaw button? Yes, that's right, one-click deployment of your little molten friend. Deploy one or deploy a whole swarm and get native MPC and ZK protections for your agents. link below
1
8
419
Just spent the day at #TheAISummit London validating the @OpenMatter_ playbook. Everyone is building agents, but legacy security is failing them. When we show how we use post-quantum cryptography to mathematically gate AI execution, the reaction is unanimous: "You are the only company building this." PMF unlocked. 🔒
1
1
60
Chris B retweeted
Our statement on the UK government’s demand that all content on all devices sold or used in the country be scanned, on the presumption of nudity, using a dystopian combination of age verification and content scanning. This proposal will not safeguard children. It endangers us all. signal.org/blog/pdfs/2026-06…

739
8,550
41,333
2,728,018
Fee switch flipped. You are the product.
47
Chris B retweeted
Today a crazy quantum story just got wilder. On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures. But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first! As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise. Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours. Let's start with the rediscovery. Just two months after Google's paper, French quantum expert AndrĂŠ Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to AndrĂŠ, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure. Interestingly, AndrĂŠ missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice! The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond AndrĂŠ and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :) Part 2: neutral atoms and qday The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers. Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low. Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts. My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom". Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions. So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030. Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years. Part 3: post-quantum cryptography There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation. These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer. The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security. Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.
408
1,129
6,244
3,701,536
@reneedaos and the @openmatter_ team just open-sourced 31 modular agent skills mapping directly to rigorous I-O psychology, APA standards, and legal compliance frameworks. Autonomous agents are rapidly entering the workforce, but compliance cannot be an afterthought. These SKILL.MD files give frameworks like Claude Code and OpenClaw the baseline domain knowledge to audit algorithmic hiring tools and manage personnel selection safely. Fork the repository and integrate it into your workflows. Full repo link in the post below.
2
2
64
Robinhood granted AI agents autonomous trading powers via MCP… what could go wrong? Sure, they have dedicated wallets, hardcoded spending caps, and some transactions will require human-in-the-loop, but there are no cryptographic gates to prevent prompt injections, just semantic software rules sitting between a rogue agent and your funds. One properly manipulated input will bypass software guardrails and drain a portfolio in milliseconds. Financial agents require absolute logic. They need threshold secured credentials. They must rely on cryptographic execution to mathematically verify a trade before it ever happens. Have fun testing out the new agentic trading features. Just make sure you’re fully aware of the risks before giving it access to your full stack. gridthegrey.com/posts/robinh…
85
Downright wholesome privacy and opsec content.
Don't take cables from strangers.
52
Translating post-quantum cryptography and agentic execution into sharp, actionable intelligence is a rare skill. I am incredibly excited to welcome my good friend @HiroKennelly to the @OpenMatter_ team as our Staff Writer. This week he gives us the lowdown on the OpenMatter ZK Firewall Primer: AI agents are no longer just answering questions. They access databases, use tools, move information between systems, and increasingly make decisions on behalf of people and organizations. That creates a new problem: How do you verify what an AI agent actually did, rather than simply trusting logs, policies, or vendor assurances after the fact? In this week’s issue, he breaks down: • Why AI governance built on trust and auditing is no longer enough • How autonomous agents create new security and compliance risks • Why enterprises need mathematical verification instead of promises • How OpenMatter’s QuantumGuard establishes cryptographic proof that policies were followed before actions are executed Read the full article from the link below 👇
1
4
558
QuantumGuard Offers Proofs, Not Promises openmatter.substack.com/p/qu…

1
51
Chris B retweeted
24
62
385
10,255
@tugraz new Telescope report exposes a fatal flaw in TEEs. By monitoring a sibling CPU core, attackers bypassed Intel TDX boundaries to leak an RSA-2048 private key with 99.6% accuracy. The Problem: Hardware enclaves must reconstruct plaintext inside the CPU execution boundary to process it. This creates a microarchitectural honeypot vulnerable to machine-speed side channels. If the data exists in plaintext anywhere on the silicon, it can be leaked. The @OpenMatter_ Solution: We eliminate hardware trust entirely. OpenMatter's Masked Compute uses post-quantum MPC to keep data cryptographically sharded across nodes. Plaintext is never rebuilt in the CPU. Side channels get only noise. This is a massive paradigm shift for how the industry views multi-party computation. The first wave of Web3 infrastructure companies popularized MPC strictly for digital asset custody and threshold wallets. Using it solely for key signing is like buying the Ferrari Luce just to use that massive, polarizing glass canopy as a high tech greenhouse. Key signing (such as ECDSA or Ed25519 threshold signatures) is simply the multi-party generation of a static mathematical proof to unlock a wallet. True MPC is a general-purpose, Turing-complete secure execution environment. It allows multiple independent nodes to take encrypted inputs, run complex operational logic across those inputs, and output a verified result without any single node ever seeing the underlying data.
1
104
Here’s the @tugraz post detailing the TEE exploit. Crazy to think we’re putting all our trust in hardware vendors tugraz.elsevierpure.com/en/p…
111
This is why agents need encrypted keys and environment variables execution gating
🚨 TrapDoor supply chain attack hits npm, PyPI, and Crates-io. thehackernews.com/2026/05/tr… 34 malicious packages across 384 versions were used to steal crypto wallets, SSH keys, cloud credentials, and developer secrets from crypto, DeFi, Solana, and AI environments. The malware abused npm hooks, Python imports, and Rust build scripts for execution and persistence.
57
I’ve been using @AskVenice agentic mode to perform deep research on personal health and business initiatives. It’s far more effective at returning actionable insights than basic chat mode, and I feel 1m% safer than I would sending my data over to any of the mainstream AI orgs
If you haven’t tried the new agentic chat yet, use @VeniceAiPro’s referral code and take it for a spin. It’s free to try, and if you upgrade to Pro for higher limits and more powerful models, you’ll both receive $10 in credits.
10
5
63
4,243
We’ve been working on our agentic firewall for months. The NSA basically just rubber stamped it.
NSA is releasing security design considerations for AI-driven automation leveraging MCP which, while simplifying the integration of diverse capabilities into powerful agent workflows, requires caution. Learn more: nsa.gov/Portals/75/documents…
85
They say never meet your heroes, but Johnny 5 seemed genuinely happy to see me
3
67