小熊哥

[小熊哥 @_bearcookie]

@BTCBruce1 BOSS 请问MSX招聘Golang开发工程师嘛？我目前是在国内一家很知名的游戏中大厂，我拥有全栈开发经验包括丰富的微服务开发经验 和 前端开发经验~

[小熊哥 @_bearcookie]

@colinwu 很好奇是哪一家？

[小熊哥 @_bearcookie]

@JoeyJia11 @Gate_zh Golang工程师有木有

[小熊哥 @_bearcookie]

@yuexiaoyu 小鱼总太优秀了！吾辈楷模！

[小熊哥 @_bearcookie]

@ohyishi 老板后端招Golang嘛？

[小熊哥 @_bearcookie]

好硬核

[vitalik.eth @VitalikButerin]

Ethereum itself must pass the walkaway test.

Ethereum is meant to be a home for trustless and trust-minimized applications, whether in finance, governance or elsewhere. It must support applications that are more like tools - the hammer that once you buy it's yours - than like services that lose all functionality once the vendor loses interest in maintaining them (or worse, gets hacked or becomes value-extractive). Even when applications do have functionality that depends on a vendor, Ethereum can help reduce those dependencies as much as possible, and protect the user as much as possible in those cases where the dependencies fail.

But building such applications is not possible on a base layer which itself depends on ongoing updates from a vendor in order to continue being usable - even if that "vendor" is the all core devs process. Ethereum the blockchain must have the traits that we strive for in Ethereum's applications. Hence, Ethereum itself must pass the walkaway test.

This means that Ethereum must get to a place where we _can ossify if we want to_. We do not have to stop making changes to the protocol, but we must get to a place where Ethereum's value proposition does not strictly depend on any features that are not in the protocol already.

This includes the following:

* Full quantum-resistance. We should resist the trap of saying "let's delay quantum-resistance until the last possible moment in the name of ekeing out more efficiencies for a while longer". Individual users have that right, but the protocol should not. Being able to say "Ethereum's protocol, as it stands today, is cryptographically safe for a hundred years" is something we should strive to get to as soon as possible, and insist on as a point of pride.
* An architecture that can expand to sufficient scalability. The protocol needs to have the properties that allow it to expand to many thousands of TPS over time, most notably ZK-EVM validation and data sampling through PeerDAS. Ideally, we get to a point where further scaling is done through "parameter only" changes - and ideally _those_ changes are not BPO-style forks, but rather are made with the same validator voting mechanism we use for the gas limit.
* A state architecture that can last decades. This means deciding, and implementing, whatever form of partial statelessness and state expiry will let us feel comfortable letting Ethereum run with thousands of TPS for decades, without breaking sync or hard disk or I/O requirements. It also means future-proofing the tree and storage types to work well with this long-term environment.
* An account model that is general-purpose (this is "full account abstraction": move away from enshrined ECDSA for signature validation)
* A gas schedule that we are confident is free of DoS vulnerabilities, both for execution and for ZK-proving
* A PoS economic model that, with all we have learned over the past half decade of proof of stake in Ethereum and full decade beyond, we are confident can last and remain decentralized for decades, and supports the usefulness of ETH as trustless collateral (eg. in governance-minimized ETH-backed stablecoins)
* A block building model that we are confident will resist centralization pressure and guarantee censorship resistance even in unknown future environments

Ideally, we do the hard work over the next few years, to get to a point where in the future almost all future innovation can happen through client optimization, and get reflected in the protocol through parameter changes. Every year, we should tick off at least one of these boxes, and ideally multiple. Do the right thing once, based on knowledge of what is truly the right thing (and not compromise halfway fixes), and maximize Ethereum's technological and social robustness for the long term.

Ethereum goes hard.

This is the gwei.

[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.

[小熊哥 @_bearcookie]

@wangduanniao @bcgame 鸟哥 坚强坚强坚强坚强！

[小熊哥 @_bearcookie]

@lilyanna_btc 里里宝回归了

[小熊哥 @_bearcookie]

@PenngXiao 哈哈 这个给建议的人估计是没写过代码

[小熊哥 @_bearcookie]

@BitcoinNL @MagicNetMoney @billydollarcat $RUNECOIN is down close to -99% from it's all time high

[小熊哥 @_bearcookie]

@cryptobraveHQ @RiverdotInc @BitAgere BEVM又激起了我的恨意

[小熊哥 @_bearcookie]

@xiaoayi1997 好的 小姨～

[小熊哥 @_bearcookie]

@Sh1l1b34tRun3St @rune_coin 😂

[小熊哥 @_bearcookie]

@LeonidasNFT @Ness0x0 @okx @ElizabethOls0n 你就这点格局嘛，符文生态一起把蛋糕做大不是更好吗？🧐

[小熊哥 @_bearcookie]

@thehdr_btc @rune_coin You used to be the most faithful believer, and now you are like this.

[小熊哥 @_bearcookie]

@H790567H @lilyanna_btc 哈哈哈

[小熊哥 @_bearcookie]

@lilyanna_btc 里里宝回来啦~

[小熊哥 @_bearcookie]

@freak0618 好的。

[小熊哥 @_bearcookie]

@jackli727 杂种畜牲