Daniel Pham (perfogic)

Blockchain Engineer and Researcher | Core Builder Of Orbiton
I love building and learning new things about blockchain

[Thomas Coratger @tcoratger]

Ethereum is preparing for a post-quantum future.

The transition away from BLS signatures starts with a dedicated Post-Quantum (PQ) Public Key Registry.

https://t.co/H1UUFfUZqk

Here is a deep dive into the design space, XMSS, and how Ethereum will secure its validators. 🧵👇

[Daniel Pham (perfogic) @perfogic_]

@0xKoiner @LayerZero_Core Yes, definitely. Using a light client to verify data from block headers would help mitigate this type of attack, since block headers are continuously validated as part of the consensus process and cannot be easily forged. 😁

[Daniel Pham (perfogic) @perfogic_]

@runchao_han Awesome, Runchao 🔥, I'm testing it noww with codex 😆

[Daniel Pham (perfogic) @perfogic_]

Congrats, Professor Vincent. I also have a paper accepted at ICBC this year and am planning to attend. If all goes well with my visa, I’d be very glad to hear your keynote talk on Redbelly and follow the paper sessions as well.
I’ve been reading your book recently on blockchain scalability and learned a lot about consensus from it. Really looking forward to learn more! 😆

[binji @binji_x]

Ethereum is going post quantum.

https://t.co/wmNjRdkV8Z

[Daniel Pham (perfogic) @perfogic_]

@zksecurityXYZ Great post 💯💯

[zkSecurity @zksecurityXYZ]

KZG vs IPA vs FRI: which polynomial commitment should you use? https://t.co/Wob4F6FFC2

[Sabanaku77 @Sabanaku77]

After months of learning and research on Fully Homomorphic Encryption, I’m excited to share my FHE Handbook for Beginners.

https://t.co/4giutcwDAQ

It currently covers the foundational cyphertexts and the basic operations you need to understand schemes like TFHE.

I'm actively working on adding sections for Key Switching, External Products, and Bootstrapping.

Contributions are welcome!

#Web3 #cyptography #privacy #fhe #tfhe

[vitalik.eth @VitalikButerin]

Now that ZKEVMs are at alpha stage (production-quality performance, remaining work is safety) and PeerDAS is live on mainnet, it's time to talk more about what this combination means for Ethereum.

These are not minor improvements; they are shifting Ethereum into being a fundamentally new and more powerful kind of decentralized network.

To see why, let's look at the two major types of p2p network so far:

BitTorrent (2000): huge total bandwidth, highly decentralized, no consensus

Bitcoin (2009): highly decentralized, consensus, but low bandwidth - because it’s not “distributed” in the sense of work being split up, it’s *replicated*

Now, Ethereum with PeerDAS (2025) and ZK-EVMs (expect small portions of the network using it in 2026), we get: decentralized, consensus and high bandwidth

The trilemma has been solved - not on paper, but with live running code, of which one half (data availability sampling) is *on mainnet today*, and the other half (ZK-EVMs) is *production-quality on performance today* - safety is what remains.

This was a 10-year journey (see the first commit of my original post on DAS here: https://t.co/Fa0jKFgObW , and ZK-EVM attempts started in ~2020), but it's finally here.

Over the next ~4 years, expect to see the full extent of this vision roll out:

* In 2026, large non-ZKEVM-dependent gas limit increases due to BALs and ePBS, and we'll see the first opportunities to run a ZKEVM node
* In 2026-28, gas repricings, changes to state structure, exec payload going into blobs, and other adjustments to make higher gas limits safe
* In 2027-30, large further gas limit increases, as ZKEVM becomes the primary way to validate blocks on the network

A third piece of this is distributed block building.

A long-term ideal holy grail is to get to a future where the full block is *never* constituted in one single place. This will not be necessary for a long time, but IMO it is worth striving for us at least have the capability to do that.

Even before that point, we want the meaningful authority in block building to be as distributed as possible. This can be done either in-protocol (eg. maybe we figure out how to expand FOCIL to make it a primary channel for txs), or out-of-protocol with distributed builder marketplaces. This reduces risk of centralized interference with real-time transaction inclusion, AND it creates a better environment for geographical fairness.

Onward.

[Daniel Pham (perfogic) @perfogic_]

@abbas_tfu indie hacker time, broo

[Daniel Pham (perfogic) @perfogic_]

@abbas_tfu @get_optimum Gmum, Abbas 💪💪

[Daniel Pham (perfogic) @perfogic_]

@get_optimum Congrats! @MurielMedard 💯

[Daniel Pham (perfogic) @perfogic_]

@daniellehrner Hmm how u measure it, can i see the code ? On blog of Base in the comment, they show Reth have pretty good result compared to Geth

[Daniel Pham (perfogic) @perfogic_]

@SinhaSwarnabha Great Post, Swarna! I have learnt a lot about Turbine.
Since it is a tree and it distributes erasure piece, we totally can replace it with RLNC. The performance will rocket.

On DAS, i dont think they should implement it yet. Only if they want each node store only partial data

[Daniel Pham (perfogic) @perfogic_]

@FigoETH Thanks a lot @FigoETH 🫡

[Roberto Bayardo | bayardo.eth @roberto_bayardo]

@daniellehrner Benchmarking is hard. Base had to pretty much give up on geth which exhibited (1) too much disk usage and (2) bad block building outliers which regularly stalled the chain. Reth solved both problems. https://t.co/xn5RZTtwoM

[patrickogrady.xyz @_patrickogrady]

With @tempo, what you can see is just as impressive as what you don't.

In each round of consensus, Tempo validators emit a set of BLS12-381 threshold signatures that can be verified against a static network key (maintained across validator set changes) 🔐

[Daniel Pham (perfogic) @perfogic_]

@protolambda 👀👀