Web3Buidler.Tech

804 posts

Web3Buidler.Tech banner
Web3Buidler.Tech

Web3Buidler.Tech

@Web3BuidlerTech

https://t.co/7mkKvBNK5h 是一个聚焦 Web3 与 AI 融合创新的技术共建社区。 ⏰ 每周一下午 2 点线上分享: ▪️ Web3 一周要闻回顾与热点提纯; ▪️ 最新核心研报(Crypto + AI)深度精讲; ▪️ 前沿 AI Agent 技术与 Web3 实战解析。

Katılım Eylül 2022
101 Takip Edilen1.6K Takipçiler
Web3Buidler.Tech retweetledi
QuarkChain
QuarkChain@Quark_Chain·
QuarkChain has been invited to present on the main stage at @EthCC on April 2. @qc_qizhou, founder of QuarkChain, will present: “Scaling Ethereum L1: Achieving 10 GigaGas/s EVM Execution with Block-Level Access Lists” We’ll share what we learned from exploring the limits of Ethereum execution — and what it could mean for the next phase of L1 scaling. #EthCC #ScalingEthereum
QuarkChain tweet media
English
2
3
9
351
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
AI 正在重塑 Web3 的执行层,真正的 Builder 必须跟上节奏!⚡️ 未来,Web3BuidlerTech 每周一下午 2 点的线上分享,将在原有的新闻/研报精讲基础上,全面融入 AI 技术的深度解读。懂 Web3 也懂 AI,才是未来的赢家。🫡
Web3Buidler.Tech@Web3BuidlerTech

感谢大家参与 26/03/16 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周会议主要内容:区块链 & AI 快讯、Zerodev 讨论 Frame 交易和 Tempo 的区别、ACD 关于 Hegota 升级执行层头条的讨论、ERC-8183:AI Agents 的商业层,等等。 视频:youtu.be/ra-R3wWivoM

中文
0
0
0
34
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
感谢大家参与 26/03/16 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周会议主要内容:区块链 & AI 快讯、Zerodev 讨论 Frame 交易和 Tempo 的区别、ACD 关于 Hegota 升级执行层头条的讨论、ERC-8183:AI Agents 的商业层,等等。 视频:youtu.be/ra-R3wWivoM
YouTube video
YouTube
中文
1
1
3
475
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
每周一下午 2 点,Web3Buidler.Tech 联合 ETHPanda 带来以太坊中文周会! 本周的会议主要内容包括:区块链快讯、Zerodev 讨论 Frame 交易和 Tempo 的区别、ACD 关于 Hegota 升级执行层头条的讨论、量子时代你的助记词怎么办、ERC-8183:AI Agents 的商业层,等等。 欢迎大家来参加!
Web3Buidler.Tech tweet media
中文
1
0
0
81
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
感谢大家参与 26/03/09 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周的会议主要内容包括:区块链快讯、Vitalik 谈共识层的路线图、Vitalik 清迈对话:人工智能大爆发,Crypto 该为何而战、以太坊 2029 Strawmap 指南,等等。 视频:youtu.be/lJyb0GW7f78
YouTube video
YouTube
中文
0
1
1
414
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
每周一下午 2 点,Web3Buidler.Tech 联合 ETHPanda 带来以太坊中文周会! 本周会议主要内容包括:区块链快讯、Vitalik 谈共识层的路线图、Vitalik 清迈对话:人工智能大爆发,Crypto 该为何而战、以太坊 2029 Strawmap 指南、没有护城河的困局:Optimism 为何留不住 Base,等等。 欢迎参加!
Web3Buidler.Tech tweet media
中文
0
0
0
69
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
感谢大家参与 26/03/02 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周的会议主要内容包括:区块链快讯、Base 将过渡离开 OP Stack,增强网络独立性、Vitalik 谈以太坊扩容、ERC-5564:以太坊隐秘时代已至,等等。 视频:youtu.be/gx8obUT0cJ0
YouTube video
YouTube
中文
1
2
3
596
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
每周一下午 2 点,Web3Buidler.Tech 联合 ETHPanda 带来以太坊中文周会! 本周的会议主要内容包括:区块链快讯、Base 将过渡离开 OP Stack,增强网络独立性、Vitalik 谈以太坊扩容、ERC-5564:以太坊隐秘时代已至、DUE:稳定币真实使用图谱,等等。 欢迎大家来参加!
Web3Buidler.Tech tweet media
中文
1
0
0
86
Web3Buidler.Tech retweetledi
vitalik.eth
vitalik.eth@VitalikButerin·
A very important document. Let's walk through this one "goal" at a time. We'll start with fast slots and fast finality. I expect that we'll reduce slot time in an incremental fashion, eg. I like the "sqrt(2) at a time" formula (12 -> 8 -> 6 -> 4 -> 3 -> 2, though the last two steps are more speculative and depend on heavy research). It is possible to go faster or slower here; but the high level is that we'll view the slot time as a parameter that we adjust down when we're confident it's safe to, similar to the blob target. Fast slots are off in their own lane at the top of the roadmap, and do not really seem to connect to anything. This is because the rest of the roadmap is pretty independent of the slot time: we would need to do roughly the same things whether the slot time is 2 seconds or 32 seconds There are a few intersection areas though. One is p2p improvements. @raulvk has recently been working on an optimized p2p layer for Ethereum, which uses erasure coding to greatly improve on the bandwidth/latency tradeoff frontier. Roughly speaking: in today's design, each node receives a full block body from several peers, and is able to accept and rebroadcast it as soon as it receives the first one. If the "width" (number of peers sending you the block) is low, then one bad peer can greatly delay when you receive the block. If width is high, there is a lot of unneeded data overhead. With erasure coding, you can choose a k-of-n setup, eg: split each block into 8 pieces so that with any 4 of them you can reconstruct the full block. This gives you much of the redundancy benefits of high width, without the overhead. We have stats that show that this architecture can greatly reduce 95th percentile block propagation time, making shorter slots viable with no security tradeoffs (except increased protocol complexity, though here the performance-gain-to-lines-of-code ratio is quite favorable) Another intersection area is the more complex slot structure that comes with ePBS, FOCIL, and the fast confirmation rule. These have important benefits, but they decrease the safe latency maximum from slot/3 to slot/5. There's ongoing research to try to pipeline things better to minimize losses (also note: the slot time is lower-bounded not just by slot latency, but also by the fixed-cost part of ZK prover latency), but there are some tradeoffs here. One way we are exploring to compensate for this is to change to an architecture where only ~256-1024 randomly selected attesters sign on each slot. For a fork choice (non-finalizing) function, this is totally sufficient. The smaller number of signatures lets us remove the aggregation phase, shortening the slots. Fast finality is more complex (the ultimate protocol is IMO simpler than status quo Gasper, but the change path is complex). Today, finality takes 16 minutes (12s slots * 32 slot epochs * 2.5 epochs) on average. The goal is to decouple slots and finality, so allow us to reason about both separately, and we are aiming to use a one-round-finality BFT algorithm (a Minimmit variant) to finalize. So endgame finality time might be eg. 6-16 sec. Because this is a very invasive set of changes, the plan is to bundle the largest step in each change with a switch of the cryptography, notably to post-quantum hash-based signatures, and to a maximally STARK-friendly hash (there are three possible responses to the recent Poseidon2 attacks: (i) increase round count or introduce other countermeasures such as a Monolith layer, (ii) go back to Poseidon1, which is even more lindy than Poseidon2 and has not seen flaws, (iii) use BLAKE3 or other maximally-cheap "conventional" hash. All are being researched). Additionally, there is a plan to introduce many of these changes piece-by-piece, eg. "1-epoch finality" means we adjust the current consensus to change from FFG-style finalization to Minimmit-style finalization. One possible finality time trajectory is: 16 min (today) -> 10m40s (8s slots) -> 6m24s (one-epoch finality) -> 1m12s (8-slot epochs, 6s slots) -> 48s (4s slots) -> 16s (minimmit) -> 8s (minimmit with more aggressive parameters) One interesting consequence of the incremental approach is that there is a pathway to making the slots quantum-resistant much sooner than making the finality quantum-resistant, so we may well quite quickly get to a regime where, if quantum computers suddenly appear, we lose the finality guarantee, but the chain keeps chugging along. Summary: expect to see progressive decreases of both slot time and finality time, and expect to see these changes to be intertwined with a "ship of Theseus" style component-by-component replacement of Ethereum's slot structure and consensus with a cleaner, simpler, quantum-resistant, prover-friendly, end-to-end formally-verified alternative.
Justin Drake@drakefjustin

Introducing strawmap, a strawman roadmap by EF Protocol. Believe in something. Believe in an Ethereum strawmap. Who is this for? The document, available at strawmap[.]org, is intended for advanced readers. It is a dense and technical resource primarily for researchers, developers, and participants in Ethereum governance. Visit ethereum[.]org/roadmap for more introductory material. Accessible explainers unpacking the strawmap will follow soon™. What is the strawmap? The strawmap is an invitation to view L1 protocol upgrades through a holistic lens. By placing proposals on a single visual it provides a unified perspective on Ethereum L1 ambitions. The time horizon spans years, extending beyond the immediate focus of All Core Devs (ACD) and forkcast[.]org which typically cover only the next couple of forks. What are some of the highlights? The strawmap features five simple north stars, presented as black boxes on the right: → fast L1: fast UX, via short slots and finality in seconds → gigagas L1: 1 gigagas/sec (10K TPS), via zkEVMs and real-time proving → teragas L2: 1 gigabyte/sec (10M TPS), via data availability sampling → post quantum L1: durable cryptography, via hash-based schemes → private L1: first-class privacy, via shielded ETH transfers What is the origin story? The strawman roadmap originated as a discussion starter at an EF workshop in Jan 2026, partly motivated by a desire to integrate lean Ethereum with shorter-term initiatives. Upgrade dependencies and fork constraints became particularly effective at surfacing valuable discussion topics. The strawman is now shared publicly in a spirit of proactive transparency and accelerationism. Why the "strawmap" name? "Strawmap" is a portmanteau of "strawman" and "roadmap". The strawman qualifier is deliberate for two reasons: 1. It acknowledges the limits of drafting a roadmap in a highly decentralized ecosystem. An "official" roadmap reflecting all Ethereum stakeholders is effectively impossible. Rough consensus is fundamentally an emergent, continuous, and inherent uncertain process. 2. It underscores the document's status as a work-in-progress. Although it originated within the EF Protocol cluster, there are competing views held among its 100 members, not to mention a rich diversity of non-EFer views. The strawmap is not a prediction. It is an accelerationist coordination tool, sketching one reasonably coherent path among millions of possible outcomes. What is the strawmap time frame? The strawmap focuses on forks extending through the end of the decade. It outlines seven forks by 2029 based on a rough cadence of one fork every six months. While grounded in current expectations, these timelines should be treated with healthy skepticism. The current draft assumes human-first development. AI-driven development and formal verification could significantly compress schedules. What do the letters on top represent? The strawmap is organized as a timeline, with forks progressing from left to right. Consensus layer forks follow a star-based naming scheme with incrementing first letters: Altair, Bellatrix, Capella, Deneb, Electra, Fulu, etc. Upcoming forks such as Glamsterdam and Hegotá have finalized names. Other forks, like I* and J*, have placeholder names (with I* pronounced "I star"). What do the colors and arrows represent? Upgrades are grouped into three color-coded horizontal layers: consensus (CL), data (DL), execution (EL). Dark boxes denote headliners (see below), grey boxes indicate offchain upgrades, and black boxes represent north stars. An explanatory legend appears at the bottom. Within each layer, upgrades are further organized by theme and sub-theme. Arrows signal hard technical dependencies or natural upgrade progressions. Underlined text in boxes links to relevant EIPs and write-ups. What are headliners? Headliners are particularly prominent and ambitious upgrades. To maintain a fast fork cadence, the modern ACD process limits itself to one consensus and one execution headliner per fork. For example, in Glamsterdam, these headliners are ePBS and BALs, respectively. (L* is an exceptional fork, displaying two headliners tied to the bigger lean consensus fork. Lean consensus landing in L* would be a fateful coincidence.) Will the strawmap evolve? Yes, the strawmap is a living and malleable document. It will evolve alongside community feedback, R&D advancements, and governance. Expect at least quarterly updates, with the latest revision date noted on the document. Can I share feedback? Yes, feedback is actively encouraged. The EF Protocol strawmap is maintained by the EF Architecture team: @adietrichs, @barnabemonnot, @fradamt, @drakefjustin. Each has open DMs and can be reached at first.name@ethereum[.]org. General inquiries can be sent to strawmap@ethereum[.]org.

English
324
266
1.7K
336.9K
Web3Buidler.Tech retweetledi
CM
CM@cmdefi·
以太坊基金会发布了L1扩展路线图草案strawmap,这条路线应该是市场期望已久的,不依靠L2,而是直接在主网扩展。 strawmap有5个阶段目标: (1) fast L1: 秒级确认 (2) gigagas L1: 约10K TPS (3) teragas L2: 约10M TPS (4) post quantum L1: 抗量子密码学 (5) private L1: 原生隐私 以下总结: 首先科普一下,目前以太坊每个slot 12秒,第一阶段fast L1的关键词就是short slots,意思就是把这个时间缩短到几秒内完成。 slot可以理解为整个共识层的一个时间单位,如果以太坊是一个时钟,那么slot就是切割时间的刻度,目前每个刻度固定是12秒,每12秒,从全网验证者中选出一个「提议者」来打包一个区块。32个slot组成1个epoch。所以这是决定以太坊速度的基础单位。 第2、3阶段是大幅提升L1和L2的TPS,靠zkEVM、实时证明、数据可用性采样,这是以太坊长期以来一直在宣传的技术,不过多赘述了。 第4目标,抗量子威胁,这个值得说一说,我们先要了解原来以太坊签名是ECDSA,在签名的时候用私钥进行一次复杂的数学运算(椭圆曲线数学运算),那么攻击者想要破解,必须从公钥反向推导出私钥,以目前经典计算机的能力是完成不了的。但量子计算机的出现,可能就会打破这个局面,因为核心这就是一个解题的过程。 以太坊目前的方案是改用Hash-based签名,它不再是一个数学问题,而是类似于一个用碎片还原照片的问题,它有极强的单向性,这种“找原像攻击”(pre-image attack)目前没有任何计算机能快速做到这一点。 第5目标,原生隐私,V神惺惺念念的隐私,这个阶段把隐私从可选项变成以太坊L1自带的功能,支持shielded ETH转账,原理是主网上增加一个shielded pool,类似保险箱功能,你把普通ETH存入pool,就变成了 shielded ETH,而在链上只记录有人存了X金额的ETH,不记是谁存的,你要转账时,通过零知识证明来告诉链我有足够的shielded ETH,我要转给哪个地址,就行了。自由与隐私的终极平衡。
CM tweet media
中文
15
11
63
8.4K
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
感谢大家参与 26/02/09 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周的会议主要内容包括:区块链快讯、Vitalik 谈如何设立创作者代币、a16z: 人工智能为什么需要加密货币,等等。 视频:youtu.be/hbzx206jnQ4
YouTube video
YouTube
中文
0
1
2
414
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
每周一下午 2 点,Web3Buidler.Tech 联合 ETHPanda 带来以太坊中文周会! 本周的会议主要内容包括:区块链快讯、Vitalik 谈如何设立创作者代币、a16z: 人工智能为什么需要加密货币,等等。 更多内容请参加分享。 会议链接:meeting.tencent.com/dm/ujh2yfBJnwh9 #腾讯会议:731-5548-9154 欢迎大家来参加
Web3Buidler.Tech tweet media
中文
0
0
0
57
Web3Buidler.Tech retweetledi
EthStorage
EthStorage@EthStorage·
🇹🇭 EthChiangmai 2026 EthStorage co-founder @qc_qizhou participated in @ETHChiangmai 2026 as a Hackathon Judge and Summit Panelist. He joined the panel “Cypherpunk as a Survival Skill: What It Takes to Live Permissionlessly”, contributing to discussions with builders and the broader Ethereum community. Thanks to the EthChiangmai team and everyone who made the event possible 🙏
EthStorage tweet mediaEthStorage tweet media
English
0
2
6
569
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
感谢大家参与 26/02/02 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周的会议主要内容包括:区块链快讯、ERC-8004 在以太坊主网上线、TheDAO 化身以太坊安全基金、L1-zkEVM 2026 路线图、ACD 会议简报,等等。 视频:youtu.be/wys_pZA1VlA
YouTube video
YouTube
中文
0
1
2
886
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
每周一下午 2 点,Web3Buidler.Tech 联合 @ETHPanda_Org 带来以太坊中文周会! 本周的会议主要内容包括:区块链快讯、ERC-8004 在以太坊主网上线、TheDAO 化身以太坊安全基金、L1-zkEVM 2026 路线图、ACD 会议简报、再访 Vitalik:拒绝末日剧本,等等。 会议链接:meeting.tencent.com/dm/ujh2yfBJnwh9
Web3Buidler.Tech tweet media
中文
0
0
1
87
Web3Buidler.Tech
Web3Buidler.Tech@Web3BuidlerTech·
感谢大家参与 26/01/26 期 @Web3BuidlerTech 联合 @ETHPanda_Org 带来的每周简报,我们的分享已上传! 本周的会议主要内容包括:区块链快讯、梳理 Vitalik 最近的长推、IOSG 内部备忘录(上):2026,如何押注主流资产?等等。 视频:youtu.be/4GFUBvrInOQ
YouTube video
YouTube
中文
0
1
1
927