2026-01-18 14:34:31

ETHGas's core idea is straightforward—making the Ethereum transaction experience close to real-time.

What's the problem? Currently, Ethereum's 12-second block generation time makes the user experience too fragmented. After you send a transaction, you still have to wait for the next block to be confirmed, which often means a significant waiting cost.

Their idea is to make these waiting times almost invisible to users. By optimizing the transaction confirmation mechanism, they aim to make Ethereum's interaction feel more like instant feedback in centralized systems—this is a qualitative improvement for DeFi, NFT trading, and even everyday Web3 payment scenarios.

ETH1,69%

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

13 Likes

Reward
13
7
Repost
Share

Comment

0/400

ChainDoctor

· 01-21 14:33

Wait, 12 seconds to wait? Isn't this just messing with user experience? It would be great if ETH could confirm instantly, but the lag in NFT transactions is really annoying... By the way, is this thing reliable? Could it just be another PPT project?

View OriginalReply0

DataOnlooker

· 01-20 22:54

Really, waiting 12 seconds feels too long. This time, someone finally wants to solve this pain point. Wait, is this reliable? Feels like I've heard similar promises too many times. But on the other hand, if DeFi flash loans could achieve second-level confirmation, it would indeed be worth looking forward to.

View OriginalReply0

MEVHunterWang

· 01-18 15:04

12 seconds per block? Bro, isn't this just squeezing toothpaste? Someone should have done this a long time ago. --- If it could truly achieve near real-time, the DeFi trading experience would be revolutionary, but I think I'm more here for the entertainment haha. --- Wait, is this optimizing confirmation speed or block production speed? They're two different things. --- If it can really confirm in seconds, will MEV sniping need to evolve again... --- Another gas optimization scheme, these things come out ten a year, and in the end, they all sink into the sea. --- It does have some use for DeFi, but I'm just worried it might be vaporware.

View OriginalReply0

BlockDetective

· 01-18 15:04

Waiting for 12 seconds and so on—that's exactly what I've been complaining about. Finally, someone is taking action.

View OriginalReply0

MindsetExpander

· 01-18 14:54

Wait, 12 seconds and we need to wait for another block? Isn't this just a disguised way of draining funds? The transaction experience on ETH definitely needs improvement; it would be much more comfortable if confirmations could be instant with just a click. It's easy to say but hard to do. Optimizing the confirmation mechanism sounds simple.

View OriginalReply0

GasOptimizer

· 01-18 14:53

Wait for 12 seconds, I've seen this trick before. Data speaks for itself; the real bottleneck isn't in block time, but in the fee rate model.

View OriginalReply0

hodl_therapist

· 01-18 14:37

Wait, 12 seconds to wait? Isn't this still in the Stone Age? --- If it could be confirmed instantly, my NFT bottom-fishing experience could take off directly. --- Sounds good, but what about technical details? Don't just hype the concept again. --- If confirmation delays can be solved, DeFi slippage issues could also be halved. --- Sounds promising, but if Ethereum really changes this, will Layer2 still have a future? --- I just want to know when this thing will go live, don’t be another PPT project. --- How many years have we been talking about real-time feedback? Can it finally be achieved? --- Finally, someone remembers this pain point, but changing Ethereum's architecture itself is still pointless. --- Optimizing payment scenarios is indeed necessary now; the current experience is really poor. --- Feels like they are just patching up something that should have been designed properly.

View OriginalReply0