Paweł Bylica

890 posts

Paweł Bylica

Paweł Bylica

@chfast

Warszawa, Poland Katılım Kasım 2008
520 Takip Edilen1.7K Takipçiler
Paweł Bylica
Paweł Bylica@chfast·
In the future, EVM will spend more time computing gas than computing.
English
4
3
41
2.7K
Paweł Bylica retweetledi
powdr labs
powdr labs@powdr_labs·
Announcing powdr-wasm! powdr-wasm is an optimized zkVM for WASM, built on top of @openvm_org and the novel 𝑐𝑟𝑢𝑠ℎ ISA. Early benchmarks already show 1.5x fewer trace cells & faster proof times compared to RISC-V (OpenVM). It also supports Go guests via WASI! 👇
English
7
12
91
12.9K
Adrian Brink
Adrian Brink@adrianbrink·
I get the overall vibe, but Ethereum isn't even friendly to developers as a protocol. We had an EIP-665 (eips.ethereum.org/EIPS/eip-665), which was implemented in every client to add ed25519 precompiles. However instead of doing the simple thing, someone proposed to generalize it (ethereum-magicians.org/t/precompile-f…); make it work for all curves. So as a result the former was abandoned and closed and then the latter was also abandoned and closed. The net result is that 8 years later, we still only have secpk1 and bn128 precompiles instead of at least also having ed25519, which everyone agrees is just better. So I get why people complain that this looks not focused enough on actual users, sure. But god the problem is that this is also not focused on any protocol user. There are a bunch of super low hanging fruits (like freaking precompiles) that would make deploying privacy tech 10x easier, but we haven't managed to improve the core protocol a single bit on that front for the last 8 years.
Ethereum Foundation@ethereumfndn

Today, the Foundation’s Board released the EF Mandate. This document, which was first intended for EF members, reaffirms the promise of Ethereum, and the role of EF within this ecosystem.

English
21
10
150
15.8K
Paweł Bylica
Paweł Bylica@chfast·
@big_tech_sux You just want the "stack too deep" to stay so you can point it out in every Solidity vs Vyper discussion.
English
1
0
1
51
sudo init vyper
sudo init vyper@big_tech_sux·
eip-8024 is a pretty useless eip, there are much better and more useful improvements for the evm like fixing the 70s memory model, why are the core teams prioritizing this!!
Franco Victorio@fvictorio_nan

New article on Cethology: a deep dive into EIP-8024, a proposal by @frangio_ to finally kill the "stack too deep" error. Why it happens, how the EIP addresses it, and why the solution is not as simple as it appears at first. @cethology/eip-8024-or-killing-the-stack-too-deep-error" target="_blank" rel="nofollow noopener">paragraph.com/@cethology/eip…

English
1
0
5
788
Justin Drake
Justin Drake@drakefjustin·
Today marks an inflection in the Ethereum Foundation's long-term quantum strategy. We've formed a new Post Quantum (PQ) team, led by the brilliant Thomas Coratger (@tcoratger). Joining him is Emile, one of the world-class talents behind leanVM. leanVM is the cryptographic cornerstone of our entire post-quantum strategy. After years of quiet R&D, EF management has officially declared PQ security a top strategic priority. Our journey began in 2019, with the "Eth3.0 Quantum Security" presentation at StarkWare Sessions. Since 2024, PQ has been central to the @leanEthereum vision. The pace of PQ engineering breakthroughs since then has been nothing short of phenomenal. It's now 2026, timelines are accelerating. Time to go full PQ: → PQ ACD: Antonio Sanso (@asanso) kicks off a bi-weekly All Core Devs PQ transactions breakout call next month. These sessions focus on user-facing security, covering dedicated precompiles, account abstraction, and longer-term transaction signature aggregation with leanVM. → PQ foundations: Today we are announcing a $1M Poseidon Prize to harden the Poseidon hash function. We are betting big on hash-based cryptography to enjoy the strongest and leanest cryptographic foundations. Check out our other $1M PQ initiative, the Proximity Prize. → PQ devnets: Multi-client PQ consensus devnets are live! Shoutout to pioneers @zeamETH, @ReamLabs, @PierTwo_com, @geanclient, @ethlambda_lean, as well as established consensus teams Lighthouse, Grandine, and soon Prysm. This incredible teamwork is coordinated by @corcoranwill via weekly PQ interop calls. → PQ workshops: Building on last year's PQ workshop in Cambridge (see photo), the EF is hosting another 3-day PQ event in October. Top experts from around the world will convene. In addition, a PQ day is set for March 29 in Cannes just ahead of EthCC. → PQ FV and AI: Last week Alex Hicks (@alexanderlhicks) ran a specialised maths AI for 8 hours, at a $200 cost. It one-shotted a formal proof one of the hardest lemmas in the foundations of hash-based snarks. Mind-blowing. Applied cryptography will never be the same. → PQ roadmap: A comprehensive breakdown of the EF's proposed PQ strategy will be shared soon™ on pq[.]ethereum[.]org. The roadmap targets a full transition in coming years with zero loss of funds and zero downtime. Stay tuned :) → PQ education: The ZKPodcast (@zeroknowledgefm) is producing a 6-part video series on Ethereum's PQ strategy. EF Enterprise Acceleration is also preparing material for enterprises and nation-states. Finally, Ethereum is now represented on the PQ advisory board that Coinbase announced yesterday. Believe in something. Believe in PQ security.
English
341
622
3.2K
1.2M
Paweł Bylica
Paweł Bylica@chfast·
@sina_mahmoodi Maybe keep this page in shape and up to date? #execution-clients" target="_blank" rel="nofollow noopener">ethereum.org/developers/doc…
English
1
0
0
126
Paweł Bylica retweetledi
Octant
Octant@OctantApp·
Solidity compilation is now 5x faster than it was in 2023. The @solidity_lang team has been grinding on backend modernization, and they're not stopping. Next on their list is killing "stack too deep" errors for good. This is the kind of work that doesn't make headlines but keeps Ethereum moving.
Octant tweet media
English
2
5
41
1.4K
Paweł Bylica retweetledi
Leo Alt
Leo Alt@leonardoalt·
Great post! On the security of autoprecompiles: we're working on multiple fronts: - optimizer & equiv checker in Lean - FV proving equiv of R5 code & generated circuits - simplifying the Rust code to a minimal core In the end autoprecompiles will enable better perf & security!
Cody Gunton@codytouchgrass

How do we minimize risk when integrating zkEVM proving into Ethereum L1? My latest blog post (link in thread) approaches this question by breaking down the risks into granular categories, making tradeoffs explicit. 1/7

English
0
2
15
1.2K
Paweł Bylica retweetledi
Robert
Robert@zhuboxuan2·
The fact drives a lot of talent away. You can just do things, but it must already be on Vitalik's todo list.
Dankrad Feist@dankrad

@uttam_singhk Vitalik does run the EF, actually. He chooses not to control some things.

English
1
2
15
5.6K
Paweł Bylica retweetledi
Chad Smith
Chad Smith@cs01_software·
Fans of the C language, embedded engineers, compiler engineers -- take a look at this RFC to bring null safety and modern type narrowing to the clang compiler! discourse.llvm.org/t/rfc-flow-sen…
English
1
9
38
2.8K
Paweł Bylica
Paweł Bylica@chfast·
Does the Fusaka upgrade still count as 100% uptime?
English
0
0
0
192
Paweł Bylica
Paweł Bylica@chfast·
@no89thkey zkVMs don't care how you execute EVM, this EIP makes no difference.
English
0
0
7
847
michael
michael@no89thkey·
EIP-7825 is one of the most underrated upgrades for the future of ZK proving and 100X Ethereum scaling. By capping each Ethereum transaction at ~16.78M gas, it removes the risk of a single “mega-transaction” consuming an entire block. That sounds small, but the implications for ZK systems are huge. ZKVMs generate proofs by replaying execution. Bigger single tx → bigger un-parallelizable unit of work → longer latency. Before 7825, one "ZK unfriendly" transaction could blow up the proof time because you cannot run parallel proving across multiple transactions. This easily breaks real-time proving which is needed for 100X Ethereum scaling. For any team working on fast ZKVMs, this was the nightmare scenario. 7825 fixes that. Now, every block is made of predictable, bounded work units, which makes proving schedulable and highly parallelizable. As long as we can prove a worst-case 16M gas tx fast enough (like <5s), we know we can prove basically any big blocks through parallel computing. In short: EIP-7825 made sure that Ethereum real-time proving becomes a pure money problem. As long as we can throw enough parallel computing power to the problem, we can get real-time Ethereum proving for even 100M, 200M gas blocks, TODAY. This upgrade may not look like the main event tonight, but it is actually a massive unlock for the ZK roadmap and the future of Ethereum scaling in 2026. Believe in somETHing.
Ethereum@ethereum

3/⛽ Scale L1: 60M gas limit #pumpthegas 🎉 The gas limit increased to 60M (up from 45M), increasing transaction throughput by ~33%: x.com/nero_eth/statu… ‼️ More gas = more transactions, higher transaction complexity or lower fees 🛡️ 60M is safe, thanks to benchmarking, ModExp repricing & optimizations: nethermind.io/blog/measuring… ⚙️ Clients set their default to 60M. Update validator config manually: pumpthegas.org 🆙 Block proposers can increase by 0.0976% each block (per EIP-1559): gaslimit.pics Fusaka features: * Set default gas limit to 60M (EIP-7935) * Set upper bounds for ModExp (EIP-7823) * ModExp gas cost increase (EIP-7883) * RLP execution block size limit (EIP-7934) * eth/69 - history expiry and simpler receipts (EIP-7642) * Transaction gas limit cap of ~16.8M gas (EIP-7825) Note: devs/users of VERY large transactions should check they fit within Fusaka ~16.8M gas cap: blog.ethereum.org/2025/10/21/fus…

English
79
92
608
373.6K
Paweł Bylica
Paweł Bylica@chfast·
What time is it forking?
English
1
0
2
459
Paweł Bylica
Paweł Bylica@chfast·
@FUCORY If you focus on syntax then this is true. C++26 will finally have compile-time reflections, so you will be able express much more in the same language.
English
1
0
3
61
fucory
fucory@FUCORY·
The reason I say that is because the entire big idea of comptime is reusing your programming language as your metaprogramming language or your generic type language. The entire value of that is how incredibly simple it is to use and reason about Template metaprogramming lacks both the big idea and the simplicity value proposition
English
1
0
0
33
fucory
fucory@FUCORY·
TIL C++ has been adding zig comptime to the language
fucory tweet media
English
1
0
8
1K
fucory
fucory@FUCORY·
@chfast Comptime is definitely not template metaprogramming though
English
1
0
0
42
Paweł Bylica retweetledi
Solidity
Solidity@solidity_lang·
We’re thrilled to welcome @rodiazet to the Solidity team! Many of you already know his work from the Ipsilon team, where he contributed important features such as EOF support in the Solidity compiler, as well as earlier contributions during the Ewasm development efforts. With a strong background in compiler design, deep knowledge of EVM internals, and his ongoing work on evmone, a fast C++ EVM implementation and crucial part of the Solidity testing stack, he brings invaluable expertise to the team. On top of that, as an Ethereum core dev, he’s well versed in the protocol design process, including shepherding EIPs and contributing to core decision-making. This hire helps replenish team capacity following the personal and organizational changes earlier this year. Radek will strengthen the C++ side of the Solidity compiler, contributing to backend and optimizer features including SSA-CFG and ethdebug. We’re excited for what we’ll build together. Welcome aboard!
Radosław Zagórowicz@rodiazet

It’s been three years at the @ethereumfndn — easily the most rewarding professional journey I’ve had so far. Now it’s time for the next exciting step. I’m thrilled to be joining the @solidity_lang team and contributing to one of the most important parts of the @ethereum stack!

English
6
8
73
10.7K