exploration mode. ex: head of eng @fhenix , core eng @SecretNetwork
- Tweets 1,138
- Following 290
- Followers 873
- Likes 3,278
Fhenix goes mainnet this October.
For years, transacting onchain came with a tradeoff: participate in open, composable markets and, with it, surrender the privacy of your financial activity.
Dual mode turns what was once an inevitable tradeoff into a property of your asset itself.
For the first time, the same asset can be public when you want and confidential when you need- without sacrificing composibility or fragmenting liquidity.
The era of dual mode money is here, more soon.
149
61
377
31,662
so @grok-4.7-high consumed 10% weekly limit with a single prompt
now what?
2
5
132
Digital nomads be like: hotspot to your phone and place it in the single 10x10cm spot where it gets 1 bar of 5G when you sit to work in the mountains
>10cm to any direction the connection drops completely 😂
3
10
597
Tom Langer retweeted
the institutional behind-the-scenes is really where the magic of crypto is at. UX aside, it's also so much cheaper and faster
1
1
62
PERSONAL UPDATE
Last week was my last at @fhenix.
I've spent the last 7 years with this team, the last 3 of them at Fhenix, creating the new generation of onchain privacy infra. After this long, it is time for me to move on and go back to exploration mode!
Building CoFHE at Fhenix was incredible. We took an idea that seemed simple on paper but proved complex in practice - an FHE encryption layer for the EVM - and every day meant solving something nobody had hit before. That's the dream.
Besides, the true highlight was always the team I got to build it with, and I'm leaving the project in very good hands ❤️
WHAT'S NEXT?
idk! That's the good part. I want to explore and rediscover my interests and passions. I'm ready to leave the rutted path and let curiosity take the wheel again! The feel of freedom and opportunity is real, especially now. Either way, I can't imagine myself straying too far from software, web3, and privacy.
Excited for this next chapter, can't wait! 🚀
8
37
1,169
I actually use this extension a lot and loving it.
I love simple tools that saves you fractions of seconds here and there.
Now you can use EIPeek too - chromewebstore.google.com/de…
I got tired of trying to remember these arbitrary eip numbers, so I built a silly helper extension and I LOVE IT!
btw @StaniKulechov it changed to 8363
1
2
189
if ACD decides to go with 8130 - what happens with zkzk frames?
AA update: The Frame Transactions EIP was moved today to Scheduled status for the Hegotá upgrade. It was proposed as a headliner and moved in March of this year to Considered status. There was strong consensus that it was important to ship Account Abstraction in Hegotá even if the specific implementation was still up for debate.
There's been a lot of progress in the past few weeks as another implementation, EIP-8130, became a contender. This EIP is scheduled to be shipped on @base in September. It spurred productive conversation async and in a breakout this past Tuesday about the best way to not fracture standards across the ecosystem by shipping two incompatible Account Abstraction implementations between the L1 and L2s.
The crux of the issue is arriving at a shared transaction type that both preserves flexibility and future-proofness for the L1 and allows L2s to statically analyze transactions for performance and DoS-resistance reasons. At a minimum, we should make sure that the AA scheme we adopt for the L1 is flexible enough that 8130, or any future account system, can be built on top of it so that from the user's perspective the same account can work across L1 and L2s.
Authors of both EIPs, core devs, researchers, and testing teams have been working toward a solution that respects the imperative to get Account Abstraction in the next fork without delay but avoids fracturing ecosystem standards.
That said - Account Abstraction _will_ ship in Hegotá, so core devs decided today to move EIP-8141 from Considered to Scheduled today. This was made with the caveat that the version of Account Abstraction that ships in Hegotá may significantly change from what's on the Hegotá Meta EIP right now: potentially the EIP number, the transaction type, etc.
The move to Scheduled doesn't materially change the conversation that's been happening over the past few weeks or enshrine the current spec. When an EIP is proposed as a headliner and moved to Scheduled, it just signals an intention to make the fork schedule dependent on that feature being shipped. It's more common than not for the implementation to change significantly between being Scheduled and shipping.
Big appreciation to @_chunter of @base, @Offchain, @EthLabs_org, and client teams for moving the conversation forward. Progress is ongoing and can be followed at the AA breakouts on Tuesdays at 14:00 UTC or asynchronously on Forkcast.
97
Grok Build still has no `grok usage`
So I wrote a tiny CLI that reads the same auth token and hits the same billing endpoints the official client uses:
- plan tier
- usage %
- reset time
- `--json` for scripts
github.com/toml01/grok-usage
4
105
Hot take on the github downtime
Keeping software running is damn hard, especially when it’s lending free compute to any anon on the internet.
Sure the downtime yesterday was bad but github is still like 99.99% up year round.
Competition will be great but github is solid
2
7
342
in the most convenient timing lol
tl;dr: we present an interpolation attack on 28 out of 31 rounds of Poseidon in practical time via a novel technique for partial round skipping; see ia.cr/2026/1692. 🧵⬇
3
187
1/ It's interesting that post quantum TLS is a thing since 2024 and it is very likely your browser already supports it, but adoption is pretty slow, especially in banks and government sites.
You can check if you browse using PQ-TLS right now:
1
6
210
4/ encrypted credit number for later. Once quantum computers become viable, decrypts it and steals your money 🥲 Apply this logic to any sensitive information you send online - medical, bank statements, etc.
The good news is it's easy to defend
1
1
18
