
Buy At Hello
274 posts



⭐️ 以太坊生态正发生一件重要却极少被社区讨论的事情:最广泛使用的智能合约语言 Solidity 即将「分叉」为强调稳定性的 Classic Solidity,以及完全重构、仍处于原型阶段的 Core Solidity。 这两个语言都是由 Solidity 团队维护。他们认为,由于 Solidity 早期参考方案的局限性影响了其设计,以及随着近 10 年的演变带来了许多 技术债,同时缺失部分语法特性(比如 generics),强行在现有系统中修复或者增加这些特性,风险极高。 而 Solidity 作为智能合约语言,安全性/稳定性比功能特性更重要。 所以他们才认为同步开发两个语言才是最佳的选择。所以 Core Solidity 会从零开始构建,原生支持新的特性,引入标准库,并形成新的语言规范。 目前 Solidity 的版本号为 0.8.30,而接下来将发布的 0.9 版本将会是从 Classic Solidity 迁移到 Core Solidity 的第一步。暂时还不会引入重大新特性,但主要目标是移除弃用功能、偿还技术债。后续的 0.10 版本还会移除更多过时元素,部分语法将演进为 Core Solidity 风格。 👂对于这件事,社区怎么看? 1️⃣ Paradigm 的@gakonst 认为,目前的Solidity已经「基本没有问题」,当前最优先要解决的问题不是新的语法或语言特性,而是编译器本身,如何让编译速度和 Gas 优化效果提升 100 倍。他很担心 Solidity 会重演当年 Python 2 升级到 Python 3 时的那种生态割裂。 2️⃣ 有开发者表示,同时维护两种语言会非常困难 ,对第三方工具(third-party tooling)来说也是如此。 3️⃣ 论坛中有人问,开发社区最主要的抱怨之一是(Solidity)编译速度太慢,并询问如何从设计层面改进编译速度或者采用增量编译类的技术。Solidity团队回复说,未来会考虑增加 增量编译 和 并行化,不过还在长期路线图中,没有具体时间。 其他讨论就更少了,论坛里就两个人进行了讨论。 考虑到 Solidity 已加入 Argot,且原团队负责人 Daniel Kirchner 目前处于休假状态,所以我也挺担忧语言的长期维护性,和他们是否真的做出了对于生态最佳的决策,所以更多的讨论是很有必要的。 不过幸好,在以太坊上你还可以用 @vyperlang 等其他智能合约语言。 来源:soliditylang.org/blog/2025/10/2… 参与讨论:forum.soliditylang.org/t/call-for-fee…



Goodbye EVM, Hello RISC-V Ethereum is about to change its engine. ________________________ For Dummies: If you’re an ordinary Ethereum user, here’s the key point: your wallet address will not change. - Your 0x... address stays the same. - Your ETH, tokens, and NFTs remain exactly where they are. - Your MetaMask or any other wallet will keep working. What does change is everything under the hood: - Transactions become cheaper (up to 100× lower fees). - Ethereum becomes faster (thousands of transactions per second). - Rollup withdrawals become quicker (hours instead of a week). - Security becomes stronger (fewer risks of protocol-level bugs). _____________________________ For ten years, Ethereum has been powered by the EVM — the Ethereum Virtual Machine. It was revolutionary, enabling smart contracts, DeFi, and NFTs. But in a future built on zero-knowledge proofs (ZK-proofs), the EVM has become the bottleneck. What’s wrong with the EVM? - Slow in ZK: zkEVMs don’t prove the EVM directly; they prove an interpreter of the EVM that itself compiles to RISC-V. This adds an extra layer and results in a 50–800× slowdown. - Overcomplicated: precompiles (hardcoded cryptographic functions) bloat the protocol and have caused near-consensus failures. Vitalik has called them “horrible.” - Outdated design: a 256-bit stack-based machine, chosen a decade ago, is inefficient for most real-world and ZK operations compared to modern 32/64-bit register machines. In short: the EVM was brilliant for its time, but it carries heavy technical debt that becomes unsustainable in a ZK-native world. RISC-V RISC-V is not a product, but an open standard for processors — a universal alphabet of instructions: simple, modular, and free. It already powers real chips and is the default backend for most zkVMs (9 out of 10). Adopting RISC-V gives Ethereum: - Massive speedups: direct proving without an interpreter layer. - Cheaper fees: ~100× lower proving costs, making transactions far cheaper. - Better developer experience: smart contracts in Rust, Go, C++, even Python, thanks to LLVM. - Stronger security: backed by a precise, machine-readable spec (SAIL), unlike the ambiguous Yellow Paper. - Hardware acceleration: paths for ASICs and FPGAs already being tested (Succinct SP1, Nervos, Cartesi). Migration Path @VitalikButerin outlines a gradual 3-step plan: - Precompile replacement — new cryptographic functions implemented as RISC-V programs, replacing fragile EVM precompiles. - Dual VM era — contracts can be deployed as either EVM or RISC-V, with full interoperability via system calls. - Rosetta strategy — the EVM itself becomes a contract running inside the RISC-V VM, ensuring backward compatibility while simplifying the core protocol. What does this mean for the ecosystem? - Optimistic rollups: break. Their fraud proofs rely on re-executing EVM on L1. Without the EVM, they must rebuild from scratch or change models. - ZK rollups: win big. Already standardized on RISC-V, they can integrate seamlessly with L1. Polygon, zkSync, Scroll, StarkNet all benefit (though StarkNet continues with Cairo). - Developers: no longer limited to Solidity and Vyper. They can reuse mainstream tooling, compilers, debuggers, and libraries. Users: transactions become cheaper, rollups finalize faster (hours not days), and Ethereum scales to ~10,000 TPS (Gigagas L1). Ethereum is evolving from a smart contract VM into a verifiable trust layer for the entire internet. As Vitalik puts it: “The finish line includes… ZK-snarking everything.” By adopting RISC-V, Ethereum aligns with the ZK-proving ecosystem, eliminates long-standing inefficiencies, and unlocks a new era where developers can bring the full power of mainstream software to the blockchain — and users benefit from faster, cheaper, and safer applications.








换了一些 SOL 到 FTM: 1. SOL 主升浪吃到了 2. 并行 EVM 在 @monad_xyz 出来以前只有 SEI 和 FTM 能可以出 Devnet / Testnet,其他的都是概念选手,全流通和低流通,你会选择谁呢 3. FTM 从 Multichain 事件中逐渐走出来(看起来会发一条用 $FTM 作为 native token 的新并行 EVM 链),类似于 SOL 的 FTX 时刻以后半年 4. 鄙人对 AC,曾经是宗教一般的爱,而 AC 对 FTM,亦是宗教一般的爱。只要有牛市、只要 AC 出来搞事,你只管梭哈,剩下都交给命运





