An online open-source developer community focusing on Ethereum & Layer2. Official website: https://xitter.cf/t.co/aFPj7mxvac https://xitter.cf/t.co/eqGPrSztRh

Ethereum
Joined October 2017
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Dapp-Learning retweeted
vitalik.eth
@VitalikButerinOct 19
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable. Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread. Instead, the correct solution is... EIP-8288 maximalism. If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation. This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
vitalik.eth
@VitalikButerinOct 19
Replying to @lex_node
> we could still ultimately do Lattice stuff for accounts, wallets, etc. through a precompile if it is proved to be AI-secure The ideal route to support everyone's cryptography is imo through 8288. You make whatever signature you want locally, then STARK it, and then it gets included through the stark aggregator machine. Don't need any calldata onchain. Ethereum can then never add a new precompile again.
439
216
102
1,837
382,498
Dapp-Learning retweeted
🎉Devcon香港分会场|11月3日,相聚香港 以太坊基金会@ethereumfndn、ETHTAO @Ethtao_Ethtao 、Ethereum HK Hub @ethereumhkhub携手 Devcon 团队@EFDevcon ,将于 2026 年 11 月 3 日在香港举办 Devcon香港分会场。 ✨活动将围绕 Devcon 的核心议题,汇聚前沿研究、技术分享与社区讨论。我们诚邀亚洲华语社区的开发者、研究者与社区伙伴加入,交流想法、分享实践,一起在香港共庆以太坊生态盛会! 🤩更多重磅嘉宾将陆续公布。 👇注册信息 ⏰时间:11月3日 🔗注册地址:luma.com/cfthgx9l
1
15
2
24
3,123
还好我等小散的仓位有 "Satoshi's shield 保护
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
213
xiaohongshu.com/explore/6a7d… 签证状态查询看这个。
77
5. 想及时查看签证下来没,可以参考xiaohongshu.com/search_resul…。 Processed and Printed就表示通过了。有短信通知护照到达签证中心即可下单快递取护照。我这里只等了不到一周就下签了。 所以前后花了我一个月+一周拿到签证的。 想要参加devcon的同学尽快申请吧。 孟买见!
1
118
4 签证中心资料提交,录指纹,然后就是等消息了。这里广州签证中心比较坑的是, 说会到时候电话给你,然后邮寄,最后还是自己预约的快递上门取的护照。耽误了几天时间。
1
139
3 预约好时间后就可以去准备资料了,印度签证需要的资料最近也简化了很多,工作证明也不需要了(web3工作者福音)。 xiaohongshu.com/explore/6a75…可以参考这个教程。材料准备好就到时候去选择的签证中心交资料即可。尽量早点去,资料不齐的还可以有时间改。
1
216
2 申请表填写其实比较简单,去Devcon咱们直接申请旅游签比较省事,听说商务签拒签率高点。这里要提醒的是city,出生地什么的都要填省份,填错了交资料的时候会让重填,那就得现场改了。 申请表填好了就可以去BLS网站预约时间提交资料了,这个环节要排很长时间!!!
1
230
1好多想参加@EFDevcon同学咨询印度签证办理的问题, 这里分享下自己DIY的过程。 首先印度签证感觉没有网上说的比美签还难办,最麻烦的就是预约时间去签证中心提交资料,一般要排到一个月以后。 所以想尽快出签的同学, 可以先立即马上填申请表! 可以参考这个教程DIY: xiaohongshu.com/explore/6912…
2
1
4
2,472
I just got my @EFDevcon ticket — paid for with ETH! Next stop: Mumbai 🇮🇳 Join me at Devcon 8 from November 3–6, 2026 for four days of big ideas, technical depth, community, and the people building the future of open source technology. devcon.org/ticket/dapplearni…
3
6
363
《zkVM 最新进展与核心技术解析: Logup-GKR》by @dddjjjiie 精彩分享已上传, 欢迎点赞收藏订阅转发~~ 非常精彩,建议反复观看。 Youtube: p1 youtu.be/5-dGZvWd2dM p2 youtu.be/J4tf6QQLIjQ Bilibili: bilibili.com/video/BV1nBeS6F…
1
3
447
会议链接:meeting.tencent.com/dm/1enhI… 腾讯会议:946-981-016 分享材料:drive.google.com/file/d/1lQB…
68
DappLearning 分享会预告: 分享者:@dddjjjiie 标题:zkVM 最新进展与核心技术解析: Logup-GKR(zkVM Advances: A Deep Dive into Logup-GKR) 主要内容: 本次分享将深入浅出地介绍 LogUp-GKR 的核心原理、协议流程及其在ZKVM中的应用 会议时间:8:00pm, Sep 18th 会议语言:中文
1
1
1
4
278
有想去参加今年在孟买举行的 @EFDevcon 的同学注意了,社区有一些折扣和免费门票,欢迎留言和私信咨询。 两年才一次的以太坊开发者开会,不容错过哦,更多详情参考:devcon.org/en/
1
281
DappLearning 分享会预告: 分享者:@nicheddy 项目/社区:@DFArchon 标题:Aztec Network 介绍与开发经验分享( Aztec Network Intro ) 主要内容: - Aztec Network 介绍 - ZK 证明与 Noir 语言 - 开发经验分享 会议链接:meeting.tencent.com/dm/jHbkb… 分享材料:dive-into-aztec.netlify.app
1
1
4
457
Dapp-Learning retweeted
一夜之间,刷屏的桥水创始人 Ray Dalio,看涨黄金和比特币原文。 他认为这类并非由政府创造的资产,表现可能会相对更好,建议大家可以低配债券,超配黄金,并配置部分比特币。
60
144
13
470
235,355