defi @ethereumfndn · ex-governance architect, makerdao · ceo, element/DELV · freedom tech

bWFkZSB5b3UgbG9vaw==
Pinned Tweet
1/ Today the EF is sharing a bit more about how it's approaching DeFi going forward:
66
72
509
281,109
Glad to see that Ethereum L1 will have a new strong prediction market contender that is dedicated to decentralization, and being ethical and not corposlop, and to actually trying to do interesting and meaningful things with this class of economic primitive. firefly.social/post/x/210212…
404
347
3,064
827,711
Three months ago, we put this idea out to the ecosystem. Today it starts getting built! @cp0xdotcom was selected to build the neutral, open-source DeFi risk data aggregator we announced this summer. Excited to see it take shape and be built in the open with the ecosystem 👇
The @ethereumfndn has awarded cp0x a grant to build an open-source tool for comparing DeFi risk assessments. We are starting work and invite the community to contribute ideas, data, corrections and code here or on github: github.com/cp0x-org/defi-dna
1
6
33
1,346
The EF Protocol Cluster's 15th AMA begins in 24 hours Ready to learn about Ethereum's potential futures? Ask away! → Submit questions now: teddit.net/r/ethereum/commen… → Answers roll in on Sep 16 at 2pm UTC
The EF Protocol teams are hosting a Reddit AMA on September 16. This is your chance to ask EF Protocol researchers and devs directly. Submit your questions about post-quantum Ethereum, L1-zkEVM, formal verification, the future of state, finality, privacy, and more now! 🔗↓
8
15
88
8,900
CSL retweeted
A general Glamsterdam update 🔈🔊 Ethereum’s next upcoming hard fork, Glamsterdam, is already in its Plataberget Testnet phase with Sepolia targeted for October. Some of the updates might affect the functionality of your protocol/app, so please have a look - and deploy on testnet to ensure compatibility. Important Links: • Summary - blog.ethereum.org/2026/08/17… • You can point your LLM to this to understand all EIPs scheduled - forkcast.org/upgrade/glamste… • A more detailed custom explanation: docs.fileverse.io/document/p… Some highlights: 1. Fixing Solidity's Stack Too Deep Error EIP-8024 - adding 3 new opcodes in the EVM to make it easier for the solidity compiler to handle more than 16 variables at a time 2. Larger Contract Size EIP-7954: increases the maximum deployed contract size from 24KiB to 64KiB and the maximum initcode size from 48KiB to 128KiB. 3. Gas repricings EIP-8007: a coordinated bundle of gas cost changes aimed at a ~200M gas floor. Any tooling or contract that hardcodes a maximum gas limit will be affected, especially around new state creation and calldata. 4. ETH Transfer emit a log EIP 7708 - Similar to ERC20 transfers, ETH transfer also follows the same spec for emitting events now. 5. ePBS EIP-7732 (Enshrined Proposer-Builder Separation): a new builder API flow and PTC (payload-timeliness) checks. Infrastructure which depends on the block production and validation pipeline should expect to be affected. PS: If you identify bugs or issues with the specification, the best place to raise these is in the Ethereum R&D Discord server. If you'd rather not use Discord, the article mentions other avenues where you can interact with core devs.
4
19
79
4,635
Live now: exploring the Kohaku CLI, how it makes Ethereum privacy tools easier to use, and demoing private transactions across Railgun, Tornado Cash, and more With @jchaskin22 and @kassandraETH of the @ethereumfndn nitter.net/i/broadcasts/1AKEmvkag…
12
36
154
26,683
Trezor now supports clear signing via ERC-7730. In May, the Ethereum Foundation’s Trillion Dollar Security Initiative shared the activities of the Clear Signing Working Group. Today, legible transactions are expanding to more hardware devices. Understanding what you sign is critical to safely transact on Ethereum. We appreciate the working group driving this effort and encouraging more wallets and dapps to participate. Check out clearsigning.org/contribute/ for ways to contribute.
Smart contract transactions can be complex.  Clear Signing makes them easier to understand. Your Trezor decodes supported EVM transactions and shows the action, tokens, amounts, and destination on its trusted screen. See it. Verify it. Sign with confidence.
15
23
216
12,261
🚨 3 decisions just landed for Glamsterdam. AllCoreDevs Consensus #186: → EIP-8037 cross-frame state gas fix approved for Glamsterdam, with all EL clients to implement and deploy on DevNet-8. → Consensus-specs parent-hash equality check approved as a spec fix, addressing the critical bug that could halt the network. → Sepolia Glamsterdam fork set for October 6, 2026. Hoodi’s date will be decided later. 🔗 eipsinsight.com/calls/acdc/1… #Ethereum #ACDC #Glamsterdam
2
11
647
withdraw multiple tornado cash notes borrow from aave and re-shield all in one atomic user op that wasn't possible before kohaku @kassandraETH takes us through it live:
7
9
65
6,911
Devcon is built for the Ethereum ecosystem, with the Ethereum ecosystem. The Supporters Program gives aligned teams a way to help make Devcon possible while showing up as active participants in the community. It's more than a sponsorship, it's an invitation to participate.
10
15
157
8,917
we will finally kill "stack too deep" the next @ethereum update brings both: 1) the ability to deploy larger contracts 2) lets compilers fix "stack too deep" eth dev is going to rip in Q4
46
88
512
87,447
Heads-up for anyone maintaining L1 contracts: → The Glamsterdam upgrade will include gas repricings (EIP-8037, EIP-8038) that shift state creation and access costs. → Most contracts are unaffected, but a small set may break or degrade without updates. Affected contracts rely on assumptions the new schedule changes, such as hardcoded gas values. Full context in the overview: blog.ethereum.org/2026/08/24…
17
73
360
45,487
📢 Call for Presentations: The Ethereum Foundation is sponsoring the 1st Workshop on Privacy-Preserving Technologies (WPPT 2026), an affiliated workshop of Asiacrypt 2026 in Hong Kong this December. Have recent or ongoing work on ZK, MPC, FHE, PIR, private identity, blockchain privacy, deployed privacy systems, and more? We’d love to hear from you. See the website for the full list of topics. Submit a ≤3-page abstract by Sept 25 (AoE). privacypreserving.tech/
18
42
230
28,020
CSL retweeted
We have some difficult news to share. Unfortunately, one of our shipping providers has experienced a data breach that exposed sensitive order data. This affects new customers in the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal who received an order within the 90 days prior to August 8th, 2026. The data exposed: - Full names - Shipping addresses - Phone numbers - Email addresses The incident affects 11,742 customers with full exposure (name, email, phone number, shipping address) and 1,947 customers with partial exposure (name, city, email). The breach is limited due to Trezor’s strict 90-day data storage policy (we were also able to negotiate the same terms with fulfillment partners, who follow the same policy). All affected customers have been contacted separately by email. Our systems and devices remain secure, but affected customers could experience an increase in phishing attempts. NEVER enter your wallet backup on a website or share it with anyone, and only check for updates on official Trezor channels. We are deeply sorry to the community and those affected. We are investigating this situation and will post updates on our blog: trezor.io/blog/news/recent-c…
2,060
2,247
8,319
7,654,478
🚨 The Devcon 8 speaker application deadline has been extended to August 12! We’re still looking for talks on: - practical privacy - censorship-resistant networks - open & verifiable infra - applied cryptography - self-sovereignty - security & tools that give users more control
This could be you on the Devcon stage in Mumbai👀 The ideas shared at Devcon can shape what Ethereum builds next. Bring your work, your questions and ideas to the global Ethereum community. Only a few days left to apply - apps close Aug 6! devcon.org/en/speaker-applic…
6
14
105
21,256
I think this is another reminder of why we need to do a better job explaining the EIP and Ethereum upgrade process to the broader community. Dear @MikeSilagadze, I understand the concerns, but there’s no need to panic just yet. A few notes that may help: - The proposal "Tapered Issuance Burn" is added as a new pull request 48 hours prior to the next ACDC call. - It doesn’t even have an EIP number yet (the number referenced is already assigned to another proposal). - Being proposed for inclusion (PFI) doesn’t mean it’s going to be on the mainnet. It simply means the authors are asking for the proposal to be discussed with Core Devs. - If authors get an opportunity to share, it will be a "PFI - Proposed For Inclusion" to Hegota, an upgrade which will be on Ethereum mainnet after Glamsterdam, (which is expected approximately in the next 3-4 months). - If the proposal moves forward, there will still be months of discussion, implementation, testing, and community feedback before anything could ever reach mainnet. - August 6th is the deadline to submit Hegota and thus this PR with a proposal: github.com/ethereum/EIPs/pul… - Here is the Pull Request to Hegota PFI github.com/ethereum/EIPs/pul… If anyone disagrees with the proposal, now is actually the best time to say so. Ethereum’s process is designed for exactly this kind of feedback. I’d encourage everyone to share their thoughts where the authors and core developers can see them: Join Discussion: ethereum-magicians.org/t/eip… The earlier the feedback comes in, core devs can make an informed decision. I hope this helps!
This is so disappointing on every level. EIP released with 48 hours notice for comments. Realistically 4 months before it goes live. For a major network economics change with far reaching implications for all of DeFi. Every builder on Ethereum opposes this. Why is this a focus? None of the reasoning makes any damn sense. This will self evidently push out solo stakers who aren't subsidized by the EF or others. It will essentially guarantee that the only ones staking are large centralized entities with zero cost of capital where users passively hold their ETH. Why? It will obviously kill a huge chunk of DeFi which is built around the staking ecosystem. Seven of the top 10 DeFi protocols with face a capital exodus. Why? Is the idea that a 0.8% reduction in issuance is somehow going to help ETH price? People who stake ETH don't sell it. This change will halt any new ETH getting staked and realistically will result in tens of billions of $ of ETH getting unstaked and entering into the market, not to mention the implosion of the core Ethereum use case. Why? Is the concern that liquid staking tokens, which intermediate about a quarter of staked ETH, displace ETH as money? This reasoning betrays a cash-accounting level of understanding of the economy, as if only M1 counts as real money. LSTs serve as valuable building blocks, and in fact implement a lot of user protections that would not be appropriate to do at the network level. At a near zero cost of 10-15 bps. I say this as a builder on Ethereum, not as someone who stands to benefit from staking issuance. I don't have much at risk here. Almost all of @ether_fi revenue is now coming from vaults and payments, staking is a small (and shrinking) part of our business. This is bad for decentralization, this is bad for Ethereum adoption, and this is bad for the credibility of the network to roll things out this way. This reinforces the Ethereum critics' position that the network is run by a small group of insiders with no regard for the actual users and builders on the chain. I can say that neither I nor any builder I know was asked for feedback on this before it went live. Any nation state or large institution looking at this will justifiably have a dramatic loss of confidence in the governance and stability of Ethereum.
10
22
141
9,866
when was your first ever POAP?
when was your first ever POAP?
4
15
1,029
CSL retweeted
Private Multiplayer Docs Live on ddocs.new 𓅢 One share link. All the permissions u need. >E2E encryption for your content >ZK proofs for your collaborators
11
28
106
12,158
Transaction outcomes should be guaranteed. Nothing more, nothing less. Setting invariants and guaranteeing execution integrity is the most impactful promise for user safety. Joining ACD tomorrow along with @forshtat to make sure we have the building blocks to do this natively
A guide to changing the transaction signing experience from “sign some bytes and pray to all the gods”, through “sign some inputs and hope for correct outcomes”, all the way to “sign desired outcomes and sleep easy”. Mirror: forshtat.com/posts/trustless…
Article

Architecture for Trustless Clear Signing on Ethereum

TLDR A guide to changing the transaction signing experience from "sign some bytes and pray to all the gods", through "sign some inputs and hope for correct outcomes", all the way to "sign desired

4
21
2,978