Hasu⚡️🤖 retweeted
Complete acquittal.
For two and a half years, our family and friends rearranged their lives around this case to see a day like today.
Thank you to our lawyers, the amici, and all who stood up for us when it mattered most.
In the end, it’s a good story when the good guys win.
Excellent news: The Peraire-Bueno brothers have been acquitted. Congratulations to them and their defense teams!
Coin Center filed an amicus brief challenging the SDNY’s “honest validator” theory of wire fraud. In Ethereum, “honest” validation has a specific technical meaning. It does not create an open-ended legal duty to meet prosecutors’ expectations of fair play.
Had the SDNY’s theory prevailed, the government could use wire fraud law to impose its own code of conduct on Ethereum validators, backed by criminal penalties. Anyone participating in an open network would have to wonder whether prosecutors might later declare their behavior “dishonest” and haul them into court.
Hasu⚡️🤖 retweeted
Yesterday we finally went live with our newest research report with @SteakhouseFi and @tokenterminal: Understanding Onchain Vaults.
We at @block_stories spent the last few months deep in the vault trenches to better understand:
- How vaults work and how they differ from one another
- What's driving their growth
- What risks they carry and how those risks can be managed
- How different organizations, from fintechs to asset managers, can use vaults to grow their businesses, with real-world examples from Fasanara Capital, @coinbase, and @circle
- What could fuel the next leg of growth
You can find all our findings in the report, condensed into 30 pages.
Thanks again to the whole Steakhouse fam for teaming up with us, and especially to @0xMiracle_ for working so closely with us and sharing so much of his vault wisdom.
Also a huge shoutout to the great team at Token Terminal, whose data powers the entire report.
I genuinely think that if you're a fintech, institutional allocator, or asset manager, this report is a great resource to get up to speed on this emerging vertical and, most importantly, better understand the opportunities that vaults could open up for your business.
And if you're rather crypto-native, I hope it delivers value to you as well.
You can grab it here: blockstories.io/vault-report
in absence of other information, always judge a plan by its outcomes. say what you want about the mandate, it was successful in 1) executing a badly necessary downsizing at the EF, 2) purging unwanted political elements, and 3) increasing ecosystem diversity at the same time.
if someone had promised all of these in one swoop a year ago, we'd have called them a genius
correct, this is the stablecoin trilemma (made up term, dont think anyone ever wrote this down):
between three properties of
1) crypto-backed/immutable
2) solvent
3) scalable,
a stablecoin can only choose 2 of 3.
old-dai, lusd chose 1+2 (sacrifice scalability)
usdt, usdc choose 2+3 (sacrifice immutability)
terrausd and its many clones chose 1+3 (sacrifice solvency)
note that the three choices not equal:
- a stablecoin that isnt solvent fails its single most important test.
- give that money's utility scales with its network, sacrificing scalability is a large price that ultimately dooms the coin to failure
- immutability, then, is arguably the least-bad thing to sacrifice, because ("the only free lunch") it can be at least partially addressed with diversification. you also become less vulnerable with scale (see tether being a huge holder of t-bills giving it a certain political immunity)
this is completely ridiculous
besides the already huge list of 200,000 affected contracts in ethereum/repricing-impact, i found multiple methodological issues that make it miss many more.
it affects deployment and operation of several high profile protocols, not just some random devs misusing opcodes that were given to them.
i shared my findings privately with chainsecurity and i refuse to participate in this clownery
We should continue towards Glam activation asap.
A lot of research went into Glam's strategy to increase opcode gas prices for state creation.
It seems fair to say that the timing of this debate is irrelevant as to its correctness or rightness for eth and our users... Yet, why did some of us (eg. quoted author who is an ef board member) only start looking in detail at Glam EIPs eg. after testnet forks started? This isn't a personal attack, it's an observation that there's a collective responsibility-- for OP, for me, for all of us-- to steward fork strategy at the right times in the process.
imo ethereum's commitments to apps do not extend to gas pricing, or to total ETH fee levels, or to USD fees. And also not to opcode pricing or gas introspection that depends on those prices. We guarantee maximally credibly neutral, maximally live access to the correct state transition function. Those guarantees imply that we always use a neutral pricing mechanism to clear congestion wherever possible. However, pricing opcodes can't use a neutral mechanism, we need to pick magic number opcode gas prices. Some of our best people researched this extensively and picked updated magic numbers, and that's something imo we should stick with now and continue our larger plans that are on track to grow to global ubiquity.
The good news and practical reality may be that the explosion of blockspace supply from 60M to 200M gas limit seems likely to absolutely crater the L1 gas price. It will take time for demand to grow to meet the new supply, including from net new entrants (eg. GENIUS and institutions), induced demand from lower prices, and the coming next gen of return-to-mainnet-type eth native apps.
By the time L1 blockspace demand catches up, we will be exploding supply again as we get closer to the full lean eth vision. That's eth's vision: postquantum and postAI ETH SoV, supported by ethereum's hypergrowing capacity, which is supported by best-in-class security and formal verification.
Looking back, it's unfortunate that we provided these affected contracts with a footgun that has put them in the situation where they were *able* to rely on fake guarantees that ethereum never promises (afaik, essentially just gas introspection). We're sorry.
imo it's time to roll forward on this. Let's do what we can in an appropriately scoped capacity for the affected contracts, then activate Glam asap, and continue our excellent progress towards global ubiquity.
Hasu⚡️🤖 retweeted
Congrats to the @usewisp_io team on making it to the App Store! 👏
Spotted Wisp at #135 in the free Productivity chart. Top 100 next? 👀
I don’t think there will be one AI harness for everything. Sometimes you need speed, sometimes a specific workflow, and sometimes privacy comes first.
There will always be overlap and tradeoffs. But some things we work on simply shouldn’t become a public record or be easily accessible to others.
That’s where @usewisp_io comes in. I’m already trusting the team with my own data, and I’m excited to see more people get access to it.
Hasu⚡️🤖 retweeted
[ ZOOMER ]
THE CFTC APPROVES LISTING OF US EQUITY PERPETUALS IN THE US: PRESS RELEASE
if you think about it, its likely that the optimal incentive composition in any type of service/performance based industry is a mix of performance-based incentive (e.g. a tip) and stable salary.
employers reducing wages is not a problem but a good thing, as intense competition in the market causes these savings to move as price improvements to customers
It's so easy to get caught up in the FUD, especially if terminally online and caught in the X algo death loop
The reality is, if you zoom out, we got extreme validation with the perp dex usecase via NYSE + Hyperliquid this week
Slow and steady we win
Hasu⚡️🤖 retweeted
It's Friday midnight, slides for @Blockworks DAS Asia are finished.
This slide needed to be simplified, sad because it's great like that. An earlier (even more arcane) version was sourcing @conksresearch equity repo which you can read here :
conks.plumbing/p/plumbing-no…
Hasu⚡️🤖 retweeted
- ATHs in options volumes
- 8x YoY volume growth
- 5x YoY fees growth
- ~90% onchain options market share
Incredible to see people discover Derive v2 after nearly 3 years in production. But v3 is near, and it is lightyears better than v2.
We have taken all of the learnings of 5.5 years operating at the bleeding edge of internet finance and poured it into v3. It incorporates everything we’ve learned from traders, market makers, builders, and the markets themselves. I can't wait to show you what we've built.
In the meantime, please keep the feedback coming (traders, builders and MMs) - we aren't perfect but we will work hard to address issues as quickly as we can.
Grateful to all those who have believed in us to this point, we have much more to prove.
Hasu⚡️🤖 retweeted
Today I am excited to announce the launch of Senepol.
@Senepol_ky is the latest business to emerge from @SteakhouseFi, sitting alongside our vault curation business and Grove Labs.
At Senepol, we provide directorship and governance services for projects in the digital assets space. I will be leading the initiative from the Cayman Islands with my talented colleague @tavia_te.
Our philosophy is “by builders, for builders,” and that captures how we think. Senepol is the culmination of what we have learned at Steakhouse over the past few years. We know firsthand how quickly the crypto landscape evolves, and how much work it takes to keep pace with new developments at the intersection of tech and finance.
If you are a project team and that sounds like a good fit, let’s talk.
To keep up with our updates and learn more, please follow us at the page below.
Today, we’re launching Senepol.
Senepol provides directorship and governance services for digital asset foundations and related token structures in the Cayman Islands.
Senepol is backed by Steakhouse Financial. Over the past few years, the Steakhouse team has developed deep expertise across vault curation, protocol development, and complex cross-border transactions, giving it direct operational experience with the structures that underpin onchain finance.
Senepol is a natural outcome of that work. As onchain finance continues to grow, we’re excited to bring what we’ve learned at Steakhouse to our clients.
If you’re building something ambitious, we’d love to hear from you.
senepol.ky/
it's really hard to sustain speculation (buying with the intent to sell it higher) for multiple weeks, let alone months. should be obvious that RH chain has tremendous potential, but this wasn't what drove the early spike
wild stuff
There's some confusion about what, exactly, was exploited here.
I've seen claims that this was a long-standing bug, exploited after the "fix" was pushed to the open source repo but before that fix could be rolled out in production.
That does not appear to be true.
Instead, it seems that the fix *was* deployed, but inadvertently introduced a new bug which was subsequently exploited.
Most of the network was still running official releases, none of which contain the new bug. Those nodes correctly rejected the block containing the exploit and stalled at height 4050335.
The timeline is roughly as follows:
• 2016-07-12: Range proof caching added
• 2017-11-08: Range proofs extended to support assets
• 2019-03-19: Range proof cache key "simplified", dropping asset & script fields. introduces Bug A.
• 2026-09-01: Bug A "fixed" by extending cache key to include asset + script. introduces Bug B.
• 2026-09-06: Bug B exploited, reserves drained, chain split.
The original "Bug A" allows some limited cache poisoning because the cache key doesn't commit to the asset and script, allowing a cached result for a range proof for one asset to be applied to a different asset or context.
Exploiting this in practice looks quite difficult, since the amount must match the primer and the proof must be genuine.
The 2026 "fix" added those missing fields to the cache key, producing a format like:
"proof | amount | asset | scriptpubkey"
But this unfortunately made the key easier to manipulate and exploit:
The four fields are concatenated without separators or length indicators.
Since both the proof and the scriptpubkey are variable length, an attacker can stretch the proof and shrink the script to produce the exact same cache key from different proofs, amounts, assets and scripts.
This lets an attacker smuggle arbitrary confidential output amounts and junk proofs past the range proof checker without proper validation, which breaks the guarantees that prevent hidden inflation.
On-chain evidence suggests that this second bug is what was exploited:
Two primer transactions each created an op_return with carefully constructed scriptpubkey and valid range proof for a (presumably) zero value output.
blockstream.info/liquid/tx/2…
blockstream.info/liquid/tx/7…
This produced a cache key like:
"<valid proof> | <valid amount> | <L-BTC> | OP_RETURN <negative amount> <L-BTC> OP_RETURN"
The exploit transaction then created a large negative op_return output with an invalid range proof:
blockstream.info/liquid/tx/f…
The invalid proof is padded with bytes corresponding to the primer's valid amount and asset fields, aligning the actual amount and asset fields with the same bytes from the primer's opreturn payload:
"<valid proof> <valid amount> <L-BTC> OP_RETURN | <negative amount> | <L-BTC> | OP_RETURN"
The exploit transaction could then include a second output crediting the attacker with a large positive value, balanced out by the fake negative amount.
Because the success was already cached, the invalid proof was never actually checked and the transaction was accepted as valid by nodes running versions of the software vulnerable to bug B.
Although the amounts are blinded, this is the only output with an invalid range proof anywhere in the peg-out's recent ancestry, so this must be where the inflated coins were created.
And since the padding only produces a cacheable key under the new format, it must have been the newer bug that was exploited.



































