Paweł Bylica

899 posts

Paweł Bylica

Paweł Bylica

@chfast

Warszawa, Poland Katılım Kasım 2008
526 Takip Edilen1.7K Takipçiler
Ben {chmark} Adams ⟠
Ben {chmark} Adams ⟠@ben_a_adams·
@InstLatX64 Keccak1600 does want a cursed number of registers so likes to spill to stack (also problematic for SIMD). Not sure if by design or accident but APX should help a lot there (and for other stack spilling algos)
English
1
0
7
643
Paweł Bylica
Paweł Bylica@chfast·
@gakonst Just use LLVM's musttail marker. #call-instruction" target="_blank" rel="nofollow noopener">llvm.org/docs/LangRef.h…
Dansk
0
0
1
172
Georgios Konstantopoulos
how can we stabilize tail call optimization in rust ASAP? we're happy to help fund it if necessary. can anyone connect me to the right people please?
English
6
0
38
9.4K
Paweł Bylica
Paweł Bylica@chfast·
@gakonst This is the Global Seed Vault on the picture. It has no code.
English
0
0
1
186
Paweł Bylica retweetledi
Somnath Banerjee
Somnath Banerjee@somnergy·
Last week we trespassed into the realm of RTP with 2 GPUs, this week we broke the 8 second barrier with zilkworm-airbender @eth_proofs Next-stop: Avg latency less than 10 seconds
Somnath Banerjee tweet media
English
0
5
12
572
Paweł Bylica
Paweł Bylica@chfast·
@leonardoalt Some time ago AI had successfully corrupted my 2 independent git projects.
English
0
0
0
81
Leo Alt
Leo Alt@leonardoalt·
AGI
Leo Alt tweet media
5
0
14
1.2K
Paweł Bylica retweetledi
Daniel Lemire
Daniel Lemire@lemire·
Fil-C is a C/C++ compiler that builds C/C++ projects into a binary with "complete memory safety". It is a great project by @filpizlo. In part because it is so easy to do, I am going to make sure that all the production-quality projects I manage support Fil-C directly. For the most part, this means skipping over direct assembly calls. You can still have the assembly calls, but you need some alternatives code path when building with Fil-C. As a side benefit, running the code with Fil-C serves as a sanitizer: if there is any bad memory business going on, Fil-C will just crash you out. Interestingly, Fil-C has no escape hatch. It is a totalitarian approach.
Daniel Lemire tweet media
English
18
89
778
48.4K
Paweł Bylica retweetledi
How To AI
How To AI@HowToAI_·
Researchers just proved that every single elementary function, sin, exp, log, sqrt, comes from one single binary operator. It is like finding the “God Particle" for calculus. In computer science, every complex program breaks down to a single logical operator: the NAND gate. It is the fundamental building block of all digital reality. But for continuous math, physics, engineering, machine learning, we thought we needed a massive toolbox. Addition. Subtraction. Trigonometry. Logarithms. Every scientific calculator and neural network has to juggle all of them. Until today. But this paper proved that every single mathematical function can be generated by a single, bizarre binary operator. eml(x,y) = exp(x) - ln(y). Combine that with the number 1, and you can build everything. Pi. The square root. Sine and Cosine. Arithmetic. It is all just the exact same operator, repeating over and over again in a binary tree. Nobody anticipated this existed. It was found by systematic exhaustive search. But the implications for AI are massive. Instead of an AI struggling to combine different mathematical rules to discover a new scientific law, it can just use a single, uniform architecture. One trainable circuit. One repeatable node. We thought the language of the universe was complex. It turns out, it's just one equation repeating in the dark.
How To AI tweet media
English
251
1.1K
6.3K
570.6K
Paweł Bylica
Paweł Bylica@chfast·
In the future, EVM will spend more time computing gas than computing.
English
5
3
43
2.8K
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
14
98
15.6K
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
16.1K
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
53
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
842
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
340
725
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
128
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
40
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
14
1.3K
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