btc资讯
  • NEW!
    NEW!  Connect Ideas Across Notes
    Save time and share insights. With Paragraph Citation, you can quote others’ work with source info built in. If someone cites your note, you’ll see a card showing where it’s used—bringing notes closer together.
    Got it
        • Sharing URL Link copied
        • /edit
        • View mode
          • Edit mode
          • View mode
          • Book mode
          • Slide mode
          Edit mode View mode Book mode Slide mode
        • Customize slides
        • Note Permission
        • Read
          • Owners
          • Signed-in users
          • Everyone
          Owners Signed-in users Everyone
        • Write
          • Owners
          • Signed-in users
          • Everyone
          Owners Signed-in users Everyone
        • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invite by email
        Invitee

        This note has no invitees

      • Publish Note

        Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

        Your note will be visible on your profile and discoverable by anyone.
        Your note is now live.
        This note is visible on your profile and discoverable online.
        Everyone on the web can find and read all notes of this public team.

        Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

        Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

        Explore these features while you wait
        Complete general settings
        Bookmark and like published notes
        Write a few more notes
        Complete general settings
        Write a few more notes
        See published notes
        Unpublish note
        Please check the box to agree to the Community Guidelines.
        View profile
      • Commenting
        Permission
        Disabled Forbidden Owners Signed-in users Everyone
      • Enable
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Suggest edit
        Permission
        Disabled Forbidden Owners Signed-in users Everyone
      • Enable
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
      • Emoji Reply
      • Enable
      • Versions and GitHub Sync
      • Note settings
      • Note Insights New
      • Engagement control
      • Make a copy
      • Transfer ownership
      • Delete this note
      • Insert from template
      • Import from
        • Dropbox
        • Google Drive
        • Gist
        • Clipboard
      • Export to
        • Dropbox
        • Google Drive
        • Gist
      • Download
        • Markdown
        • HTML
        • Raw HTML
    Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
    Menu
    Options
    Engagement control Make a copy Transfer ownership Delete this note
    Import from
    Dropbox Google Drive Gist Clipboard
    Export to
    Dropbox Google Drive Gist
    Download
    Markdown HTML Raw HTML
    Back
    Sharing URL Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Customize slides
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # ETH十年争论的拐点:以太坊或将终结不可能三角之争? <div style="background:#fff8e1;border-left:4px solid #F0B90B;padding:12px 16px;margin:0 0 24px;border-radius:0 6px 6px 0;color:#555;font-size:14px;line-height:1.7;">📋 在以太坊诞生的第一个十年里,不可能三角就像是悬在每一位开发者头上的物理定律——你可以在去中心化、安全和可扩展性中任选其二,但绝不可能三者兼得,下面我们就来聊聊贯穿以太坊十年的老大难问题,随着 PeerDAS 与 ZK 技术,终于要迎来曙光了么</div><div id="content"> <p style="text-align:center"><img alt="以太坊前景分析" height="375" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/973/f_29469973_1.jpg" width="750"/></p> <p>「不可能三角」这个词,大家听得耳朵生茧了吧?</p> <p>在以太坊诞生的第一个十年里,「不可能三角」就像是悬在每一位开发者头上的物理定律——你可以在去中心化、安全和可扩展性中任选其二,但绝不可能三者兼得。</p> <p>然而站在 2026 年初的时间点回望,我们会发现它似乎正在逐步变为一个可以通过技术进化来跨越的「设计门槛」,正如 1 月 8 日 Vitalik Buterin 指出的颠覆性观点:「相比降低延迟,提升带宽更安全可靠,<strong>借助 PeerDAS 与 ZKP,以太坊扩展性可提升数千倍,且与去中心化并不冲突」。</strong></p> <p style="text-align:center"><img alt="以太坊前景分析" height="325" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/974/f_29469974_1.jpg" width="800"/></p> <p>那曾被视为不可逾越的「不可能三角」,在 2026 年的今天,真的有望随着 PeerDAS、ZK 技术与账户抽象的成熟,而消散么?</p> <h2>一、「不可能三角」为何长期无法攻克</h2> <p>我们需要先回顾一下由 Vitalik Buterin 提出的「区块链不可能三角」这一概念,它曾专门用来形容公链在安全性、可扩展性和去中心化三者间难以兼得的困境:</p> <ul><li>去中心化,意味着低节点门槛、广泛参与、无需信任单一主体;</li><li>安全性,意味着系统在对抗作恶、审查与攻击时仍能保持一致性;</li><li>可扩展性,意味着高吞吐、低延迟与良好的用户体验;</li></ul> <p>问题在于,这三者在传统架构下往往相互掣肘,譬如提升吞吐,通常意味着提高硬件门槛或引入中心化协调;降低节点负担,则可能削弱安全假设;坚持极端去中心化,又难免会牺牲性能与体验。</p> <p>可以说,过去 5-10 年,从早期的 EOS 到后来的 Polkadot、Cosmos,再到极致性能追求者 Solana、Sui、Aptos 等,不同公链给出的答案并不相同,有的选择牺牲去中心化换取性能,有的通过许可节点或委员会机制提升效率,也有人接受性能受限,优先保证抗审查与验证自由。</p> <p>但共同点是,<strong>几乎所有扩容方案都只能同时满足其中两项,必然牺牲掉第三项。</strong></p> <p>或者换种说法,几乎所有方案都在「单体区块链」的逻辑下反复拉锯——想要跑得快,就得节点强;想要节点多,就得跑得慢,这似乎成了一道死命题。</p> <p>如果我们暂时放下对单体 - 模块区块链优劣的争论,认真回顾 2020 年以太坊从「单体链」全面转向「以 Rollup 为中心」的多层架构发展路径,以及近期 ZK(零知识证明) 等配套技术的成熟,其实就会发现:</p> <p><strong>「不可能三角」的底层逻辑,过去 5 年,已经在以太坊模块化的日拱一卒中,慢慢重构了。</strong></p> <p>客观而言,以太坊是通过一系列工程实践,将原本的制约因素逐一解耦,至少在工程路径上,这个问题不再只是哲学讨论。</p><div style="background:#e8f5e9;border:2px solid #66bb6a;border-radius:8px;padding:16px 18px;margin:24px 0;font-size:14px;line-height:1.8;"> <p style="margin:0 0 8px;font-size:15px;font-weight:bold;color:#333;">🌐 币安 Web3 钱包 · 一站式管理链上资产</p> <p style="margin:0 0 10px;color:#555;">内置 DEX 聚合器、跨链桥、DeFi 收益,支持50+主流公链,私钥自托管安全透明。</p> <ul style="margin:0 0 10px;padding-left:20px;color:#444;"> <li>🔗 Web3 钱包邀请链接:<a href="https://web3.binance.com/referral?ref=MW7E7Y08" rel="sponsored" target="_blank">立即体验(邀请码 MW7E7Y08)</a></li> <li>💱 现货账户同步开通享手续费减免:<a href="https://accounts.binance.com/register?ref=B2345" rel="sponsored" target="_blank">注册币安现货(邀请码 B2345)</a></li> <li>📖 完整 DeFi 教程:<a href="https://www.bitaigen.com/binance" rel="sponsored" target="_blank">币安12大专题教程</a></li> </ul> <p style="margin:0;font-size:12px;color:#888;">✅ Web3 + 现货双账户联动,链上链下资产统一管理</p> </div> <h2>二、「分而治之」的工程化解决思路</h2> <p>接下来,我们将拆解这些工程化细节,具体来看在 2020–2025 的五年实证中,以太坊是如何通过多条技术线并行推进,来消解这个三角制约。</p> <p><strong>首先是通过 PeerDAS 实现与数据可用性的「解耦」,解放了可扩展性的天生上限。</strong></p> <p>众所周知,在不可能三角中,数据可用性往往是决定可扩展性的第一道枷锁,因为传统区块链要求每个全节点下载并验证全部数据,在保证安全的同时也限制了扩展上限,这也是为什么上轮(或者说上上轮)周期 Celestia 这种「邪修」式 DA 解决方案会迎来大爆发。</p> <p>而以太坊给出的方向不是让节点更强,而是改变节点验证数据的方式,其中就以 PeerDAS(Peer Data Availability Sampling)为核心解决思路:</p> <p>它不再要求每个节点下载全部区块数据,而是通过概率抽样的方式验证数据是否可用——区块数据被拆分并编码,节点只需随机抽样部分数据,如果数据被隐瞒,抽样失败概率会迅速放大,这就使得数据吞吐量可以显著提升,但普通节点仍能参与验证,也意味着它不是通过牺牲去中心化换性能,而是通过数学与工程设计,大幅优化了用于实现验证的成本结构。</p> <p>而且 Vitalik 特别强调,PeerDAS 已经不再是路线图中的设想,而是真实部署的系统组件,也意味着以太坊在「可扩展性 × 去中心化」这一边已经迈出实质性一步。</p> <p><strong>其次则是 zkEVM,试图通过零知识证明驱动的验证层,解决「每个节点是否必须重复执行所有计算」的问题。</strong></p> <p>其核心思路是让以太坊主网具备生成、验证 ZK 证明的能力。换言之,每个区块执行后,都能输出一份可验证的数学证明,使其他节点无需重复计算即可确认结果的正确性,具体来说,zkEVM 的优势集中在三方面:</p> <ul><li>验证更快:节点无需重演交易,只需验证 zkProof 即可确认区块有效性;</li><li>负担更轻:有效降低全节点计算与存储压力,让轻节点与跨链验证器更易参与;</li><li>安全性更强:相比 OP 路线,ZK 的状态证明在链上实时确认,抗篡改能力更高,安全边界更清晰;</li></ul> <p>前不久,以太坊基金会(Ethereum Foundation, EF)正式也发布 L1 zkEVM 实时证明标准,标志着 ZK 路线首次正式写入主网层级的技术规划,在未来一年内,以太坊主网将逐步过渡到支持 zkEVM 验证的执行环境,实现从「重执行」到「验证证明」的结构性转变。</p> <p>Vitalik 的判断是 zkEVM 在性能与功能完备性上,已经初步达到了可用于生产的阶段,真正的挑战集中在长期安全性与实现复杂度,而根据 EF 公布的技术路线,区块证明延迟目标控制在 10 秒以内,单个 zk 证明体积小于 300 KB,且采用 128-bit 安全等级、避免 trusted setup 及计划让家用设备也能参与证明生成,以降低去中心化门槛。</p> <p><strong>最后,除了上述两项,还有基于 2030 年前的以太坊路线图(如 The Surge、The Verge 等),围绕提高吞吐、重构状态模型、调高 Gas 上限、改进执行层等多维展开。</strong></p> <p>这些都是在跨越传统三角限制中的试错与积累路径,它更像是一条长期主线,致力于实现更高的 blob 吞吐、更清晰的 Rollup 分工、更稳定的执行与结算节奏,以此为未来的多链协同与互操作打基础。</p> <p>重要的是,这些并非孤立升级,而是被明确设计为相互叠加、相互补强的模块,这也恰恰体现了以太坊对不可能三角的「工程态度」:不是像单体区块链那样寻找一招制胜的魔法解法,而是通过多层架构调整,重新分配成本与风险。</p> <h2>三、2030 愿景:以太坊的终局形态</h2><div style="background:#fff;border:2px solid #e53935;border-radius:8px;padding:16px 18px;margin:24px 0;font-size:14px;line-height:1.8;"> <p style="margin:0 0 8px;font-size:15px;font-weight:bold;color:#333;">🔒 选择合规交易所 · 资产安全第一</p> <p style="margin:0 0 10px;color:#555;">币安持有多国牌照,资产专业机构托管,建立用户保护基金(SAFU),历经多轮市场周期零用户资产损失。</p> <ul style="margin:0 0 10px;padding-left:20px;color:#444;"> <li>🛡️ 在币安安全存储资产:<a href="https://accounts.binance.com/register?ref=B2345" rel="sponsored" target="_blank">注册币安(邀请码 B2345)</a></li> <li>🌐 Web3 自托管(私钥归自己):<a href="https://web3.binance.com/referral?ref=MW7E7Y08" rel="sponsored" target="_blank">币安 Web3 钱包</a></li> <li>📖 安全使用完整指南:<a href="https://www.bitaigen.com/binance" rel="sponsored" target="_blank">币安安全教程</a></li> </ul> <p style="margin:0;font-size:12px;color:#888;">✅ 开启2FA · 使用官方渠道 · 保管好私钥助记词</p> </div> <p>即便如此,我们仍需保持克制。因为「去中心化」等要素并非静止的技术指标,而是长期的演化结果。</p> <p><strong>以太坊其实是在一步步用工程实践探索不可能三角的约束边界</strong>——随着验证方式(从重算到采样)、数据结构(从状态膨胀到状态到期)与执行模型(从单体到模块化)的变化,原有的权衡关系正在发生位移,我们正在无限接近那个「既要、又要、还要」的终点。</p> <p>在近期讨论中,Vitalik 也给出过一个相对清晰的时间框架:</p> <ul><li>2026:伴随一些执行层 / 构建机制的改进,引入 ePBS 等方向后,不依赖 zkEVM 的 Gas 上限可以先行提高,同时为「更广泛运行 zkEVM 节点」创造条件;</li><li>2026–2028:围绕 Gas 定价、状态结构与执行载荷组织方式的调整,使系统能在更高负载下保持安全运行;</li><li>2027–2030:随着 zkEVM 逐步成为验证区块的重要方式,Gas 上限可能进一步提高,长期理想目标则指向更分布式的区块构建;</li></ul> <p style="text-align:center"><img alt="以太坊前景分析" height="592" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/975/f_29469975_1.jpg" width="800"/></p> <p>结合最近的路线图更新,我们可以窥见 2030 年前以太坊的三个关键特征,它们共同构成了对不可能三角的最终解答:</p> <ul><li>极简的 L1:L1 成为一个稳固、中立且只负责提供数据可用性和结算证明的底层,它不再处理复杂的应用逻辑,从而保持了极高的安全性;</li><li>繁荣的 L2 与互操作:通过 EIL(互操作层)和快速确认规则,碎片化的 L2 被缝合成一个整体,用户感知不到链的存在,只感受到十万级别的 TPS;</li><li>极低的验证门槛: 由于状态处理和轻客户端技术的成熟,即使是手机也可以参与验证,这确保了去中心化的基石稳如泰山;</li></ul> <p>有意思的是,就在本文撰写之际,Vitalik 再度强调了一个重要的测试标准——「离场测试」(The Walkaway Test),重申以太坊必须具备自主运行的能力,即使所有服务提供商(Server Providers)都消失或遭到攻击,DApp 依然能运行,用户资产依然安全。</p> <p>这句话其实<strong>把这个「终局形态」的评价尺度,从速度 / 体验重新拉回到以太坊最在意的那件事——即系统在最坏情况下,是否仍然可信、仍然不依赖单点。</strong></p> <h2>写在最后</h2> <p>人总是要用发展的眼光看问题,尤其是在 Web3/Crypto 这个日新月异的行业。</p> <p>笔者也相信,很多年后,当人们回想起 2020-2025 关于不可能三角的激烈争论,或许会觉得它就像是在汽车发明前,人们在严肃讨论「马车如何才能同时兼顾速度、安全与载重」。</p> <p>以太坊给出的答案,不是在三个顶点之间做痛苦的选择题,而是通过 PeerDAS、ZK 证明和精妙的经济博弈设计,构建一个既属于所有人、又极其安全且能承载全人类金融活动的数字基础设施。</p> <p>客观而言,每朝这个方向迈进一步,都是踩在「不可能三角」这段往事的终点之上。</p> <p>到此这篇关于ETH十年争论的拐点:以太坊或将终结不可能三角之争?的文章就介绍到这了,更多相关以太坊前景分析内容请搜索Bitaigen(比特根)以前的文章或继续浏览下面的相关文章,希望大家以后多多支持Bitaigen(比特根)!</p><div style="background:#fffde7;border:2px solid #F0B90B;border-radius:8px;padding:16px 18px;margin:24px 0;font-size:14px;line-height:1.8;"> <p style="margin:0 0 8px;font-size:15px;font-weight:bold;color:#333;">🏆 币安 Binance · 全球最大加密货币交易所</p> <p style="margin:0 0 10px;color:#555;">全球交易量第一,500+交易对,中国大陆可直接访问,通过专属链接注册享 <strong>20% 手续费永久减免</strong>。</p> <ul style="margin:0 0 10px;padding-left:20px;color:#444;"> <li>📖 完整使用指南(2026最新):<a href="https://www.bitaigen.com/binance" rel="sponsored" target="_blank">12大专题教程</a></li> <li>🇨🇳 中国区专属注册通道:<a href="https://basebiance.com/binancecn" rel="sponsored" target="_blank">立即注册</a></li> <li>📱 安卓APK直接下载:<a href="https://basebiance.com/binanceapkcn" rel="sponsored" target="_blank">点击下载</a></li> <li>🌐 官网注册(邀请码 <strong>B2345</strong>):<a href="https://accounts.binance.com/register?ref=B2345" rel="sponsored" target="_blank">accounts.binance.com</a></li> </ul> <p style="margin:0;font-size:12px;color:#888;">✅ 手续费减免20% · 新用户福利 · 安全合规运营</p> </div> </div>

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully