FHENIX MAINNET IS LIVE!!!
CONGRATULATIONS TO TEAM AND TO EVERYONE THAT MADE IT POSSIBLE.
ThIS CALLS FOR CELEBRATION TO ANOTHER ERA OF ENCRYPTION 🔥🤝
(willox*) retweeted
The Next Evolution of EVM Privacy
EVM compatibility made blockchain development more accessible. Developers can build decentralized applications using familiar tools, established standards, and Solidity.
But accessibility alone doesn't solve every challenge.
One important limitation remains: sensitive information can become exposed during smart contract execution.
Imagine building a DeFi application where financial positions remain encrypted. Or creating governance systems where users can participate without publicly revealing their votes.
This is where Fully Homomorphic Encryption (FHE) becomes interesting.
@Fhenix is exploring how FHE can bring confidential computation into EVM environments through its CoFHE coprocessor.
The approach creates new possibilities:
- Smart contracts processing encrypted inputs.
- Confidential financial applications.
- Private governance mechanisms.
- More privacy-focused onchain experiences.
What's particularly interesting is the developer experience. Solidity developers can explore confidential computation without abandoning the familiar EVM development environment.
The bigger opportunity isn't simply adding privacy to existing applications.
It's expanding what developers can build when sensitive information doesn't need to be exposed during computation.
EVM brought programmability to blockchain.
FHE could take that programmability toward a more confidential future.
Fhenix is working at the intersection of both.
@Asterix54907294 @deivonchain @0xkeksgiven
🤝 Paid partnership
save the date: Nov 9
bring some CoFHE and interesting questions that @GuyItz will happily answer
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 👇
xitter.gq/i/spaces/1POMeNnmyEnyV…
(willox*) retweeted
𝙏𝙝𝙚 𝙋𝙡𝙖𝙮 𝙉𝙤𝙗𝙤𝙙𝙮 𝙎𝙖𝙬 ⚽
82nd minute. Nil-nil.
Every defender in the stadium is watching the ball.
The No. 10 is watching the space.
The playmaker checks the shoulder once, then again. No one else notices what's being read: a gap forming between two centre-backs, a striker about to make a run. Nothing has happened yet, but the playmaker already knows how it ends.
The ball arrives. No shot. No dribbling for the cameras.
One touch, one pass, weighted so perfectly it seems to hesitate, and the striker is through.
GOAL!⚽
The crowd chants the striker's name. The playmaker is already walking back to the halfway line.
Nobody saw the play that made the goal.
That's the job.
𝙁𝙝𝙚𝙣𝙞𝙭 𝙒𝙤𝙧𝙠𝙨 𝙏𝙝𝙚 𝙎𝙖𝙢𝙚 𝙒𝙖𝙮.🔐
Onchain, everything is visible, so the moment an app tries to keep something private, the whole stadium can see it: the bid, the balance, the strategy. Fhenix is the player nobody sees, using fully homomorphic encryption so apps can compute on data while it stays encrypted. Users never notice the machinery. They just notice the team finally scores.
Some players score the goals. Others make the goals possible.
(willox*) retweeted
Just tried encrypting and decrypting tokens on Fhenix mainnet
Two weeks in Fhenix has already recorded:
$526,787 total shielded and unshielded volume.
What's exciting is experiencing confidential transactions firsthand.
Encrypt, decrypt and switch between public and private token modes without leaving Ethereum or Arbitrum.
Privacy is no longer just an idea. It's happening on chain
@fhenix
Try it: genesis.fhenix.io/
(willox*) retweeted
In mid-September, we made the decision to allocate a large chunk of our dev resources towards auditing and further improving protocol security. This included additional audits of both the codebase and our operations, AI-enabled pentesting, red teaming, and more.
Public mainnet is now right around the corner, and the trading API is being rolled out to a small set of whitelisted alpha testers before being publicly launched this month.
We remain on track for this year’s TGE and major partnership announcements that we alluded to in our tokenomics update. Expect to hear much more from us beginning later this month!
gfhenix
A business can benefit from moving money onchain without making every financial detail part of its public record.
Think about a company paying contractors, settling invoices or managing its treasury.
The transactions may need the speed and accessibility of blockchain infrastructure, but the company may not want competitors tracking its payment amounts, balances or financial activity.
This is one area where Fhenix @fhenix mainnet could make a difference.
With Dual Mode assets, the same asset can support public and confidential activity.
A business can use public functionality where transparency is useful and confidential functionality where sensitive financial information needs protection.
The role of FHE is important here.
It allows applications to perform computations on encrypted information without first exposing the underlying values.
That creates room for more practical financial applications, from business payments to confidential DeFi operations.
What I find valuable is the possibility of bringing sensitive financial activity onchain without treating complete public visibility as the only option.
Fhenix mainnet makes that direction more tangible.
@fhenix
🤝 Paid partnership
gfhenix
Fhenix @fhenix mainnet going live is an important step toward giving onchain assets more flexibility.
What stands out to me is Dual Mode. The same asset can operate publicly or confidentially, without users needing to move into a completely different token.
That opens up more possibilities for payments, DeFi and everyday onchain activity.
Some actions need public visibility, while others involve financial details users may prefer to keep private.
With encrypted computation, applications can work with protected data without exposing the underlying information during computation.
I’d like to see this used in payment apps and DeFi products where users can choose what information they make visible.
Privacy shouldn't mean leaving the ecosystem or sacrificing useful functionality.
It should be another option built into how assets work.
A new chapter for onchain finance.
@fhenix
(willox*) retweeted
$526,787 in total volume on @fhenix mainnet in just 2 weeks
Shielded or unshielded, your choice.
Any token can switch between public and confidential on Ethereum & Arbitrum without leaving its chain.
Privacy isn't an add-on
Try Genesis
genesis.fhenix.io
@deivonchain
(willox*) retweeted
Huge congrats to Succinct’s Rahul Dalal, one of the cryptographers behind FlashProve, @AnthropicAI’s provable inference system built on zkSNARKs.
Why: Today, AI runs on a “just trust me” model. Users can’t verify that a response came from the model they chose, or that an attacker didn’t tamper with it along the way. As AI takes on higher-stakes work, that create tension for users, labs, and regulators alike.
What: Researchers from Anthropic, EPFL, MIT, and @SuccinctLabs built FlashProve, a system that lets a model provider commit to a specific model and then prove each response was produced by it, without revealing the weights. Under the hood, it uses zkSNARKs, the same cryptographic technology Succinct uses to secure $13.5B in deposits on Ethereum L2s.
So What: FlashProve proved Llama 4 Maverick, a 400B-parameter LLM, at 110 tokens/sec on a single H100 GPU, with ~19 MB proofs. That puts proving at roughly 70 to 95x the cost of running the model. The previous standard for the same model was ~0.02 tokens/sec.
What’s Next: FlashProve is still a research prototype, but it’s a step change toward the question we asked with Flock earlier this year: how close can proving get to computing? The closer it gets, the less reason there is to release any output without a proof attached.
Congrats again to Rahul and the FlashProve team, and great to see @Starknet, @Mantle_Official (proven by Succinct), and several zkML projects cited.
(willox*) retweeted
Should engineers continue working in isolation?
Even the most brilliant engineers should be subject to regular independent audits. There should also be systems in place to review their work continuously, rather than relying solely on their expertise.
At the end of the day, some of the simplest vulnerabilities are the ones that catch even the most experienced teams off guard.
I don't necessarily believe this script, but it's becoming an increasingly familiar pattern.
Perhaps it's time we rethink our approach to security in this space. Security shouldn't depend solely on the competence of individual engineers. It should be built around continuous reviews, independent oversight, and accountability.
(willox*) retweeted
Very cool to see ZKPs being applied for provable inference.
Even cooler that Rahul Dalal from @SuccinctLabs is a co-author.
They were able to achieve surprisingly low overhead: < 100x for Llama4!
New Anthropic research: progress on provable inference for large language models.
Here, we introduce FlashProve. Building on established cryptographic techniques, FlashProve allows developers to verify whether a given response came from a given AI model. It’s substantially more efficient than prior open-source methods for doing so.
These proofs have a range of applications. They can, for instance, make it harder for attackers to hijack a chat, or enable safety evaluators to verify that the model they’re testing is the same one being served to customers.
For our full write-up, see here: anthropic.com/research/prova…
Further progress in provable inference will likely be an important part of improving trust in AI deployment. To that end, we're open-sourcing FlashProve’s code, here: github.com/anthropics/FlashP…
We’re grateful to our collaborators: Alessandro Chiesa, @GiacomoFenzi, @gwberg95, @miranda__christ, Rahul Dalal (rdalal.github.io) and Ben Mayer (@transmissions11).
(willox*) retweeted
I got a girl pregnant in 2020 and my parents made me take a Board to SPAR with the inscription "I GOT A GIRL PREGNANT AND THIS IS MY PUNISHMENT" on the Board.
You can Google it.. You will see the image.


































