

✓Sleep deprived with minor addiction to coffee. CEO @fhenix. Bringing encryption to Ethereum.


If you wouldn't share your bank balance with strangers, your DeFi positions shouldn't be public. @GuyItz, CEO of @fhenix, joins us to discuss: 🔹 CoFHE on @arbitrum 🔸 FHE + confidential DeFi 🔹 What onchain privacy enables RSVP 👇 x.com/i/spaces/1POMeNnmyEnyV…



mainnet checklist: ☑ make everything encrypted by default ☑ write a song about it ☐ ship it Encrypted by Default, October 21 @fhenix

Oct 21st. Save the date.


We have been building CoFHE for a while. What started as an idea to bring FHE-based privacy to blockchains is now a reality, and we’re ready for everyone to use it. Our strategy is simple: 1. Build CoFHE and drive adoption. That includes the infrastructure and SDK, together with standards like Dual Mode Token. 2. Lead the charge by building solutions on top of our infrastructure where we see the most urgent needs. More on that in a few weeks. 3. Scale across payments, stablecoins, and tokenized assets (and more) while making privacy integration seamless for users. Chapter one starts in October.

Introducing confidential shareholder voting on Obolos, powered by @fhenix Shareholders can vote on company resolutions, weigh their votes across different matters, and appoint legal proxies to vote on their behalf, all while keeping their choices confidential. See it in action below 👇

Today, another attack on TEEs was disclosed: DDRop. The attack shows how a relatively simple hardware technique can undermine the memory integrity guarantees behind Intel TDX and AMD SEV-SNP. And it costs only 200$ to build the device. In simple terms, DDRop manipulates how memory is accessed so that protected data can be altered or observed despite the safeguards meant to protect it. ddropattack.eu/ TEEs are useful. They can be practical, efficient, and a reasonable part of systems today. But they should not be confused with the long-term end state for privacy. Systems that need durable privacy guarantees should keep moving toward architectures where security is rooted in cryptography itself. FHE is one path toward that.

How I handle legal agreements today: 1. Build a strong legal AI agent. Make sure it’s grounded in the latest regulations (they change a lot these days), trained on your product, and understands the landscape you operate in. 2. Have it review agreements as they come in and flag the important issues. Use that output to negotiate the key changes directly with the counterparty. 3. Update the agreement based on what was agreed, and only then send it to your legal team for final review. Much more efficient and a lot cheaper.

Funny how quickly "crypto is dead" changes when BTC starts moving again. Regardless of where the market is, onchain trading keeps taking share, and privacy matters more as trading moves on-chain. Sedona building on Fhenix is exactly the kind of partnership we want @SedonaFi

Random thought about team growth: I used to hire team members to speed execution, only to learn it often had the opposite effect: too many people in decision-making, ownership got blurred, and managers spent more time on the team than on delivery. Faster execution doesn't require more headcount. In 90% of cases, the key factor is making sure there is real clarity on what needs to be done, and even more important, what should be stopped. Then the team will deliver.

CoFHE v0.8.0 just hit testnet and this one is a BIG upgrade: 1/ FHE computations are significantly faster 2/ inputs can now be verified end-to-end through onchain commitments 3/ transactions are more reliable + safer to handle 4/ every FHE computation is now fully traceable less friction. more reliability. much closer to production. Mainnet is getting very real 👀

This is exactly the thing that keeps me hyped - seeing projects that build on us without any support from our end. Capstone project using fhenix for sealed bid, presented today in blockchain rio.

I still believe in Ethereum, and Vitalik's vision that places privacy and post-quantum security front and center is encouraging, but what I want to see is how this all translates into actionable activities targeted at onboarding users and institutions. This is what really matters.