crypto.zero（😎→🤣→😌→🙂→😡→😣→🥶→👻）

@dominic_w 你别睡觉了，快来看看@Polymarket ，icp能不能帮助polymarket做链改x.com/devjoshstevens…

So, when you see me speak much less about "web3" and "crypto," you know why! In the view of DFINITY, the Internet Computer must pursue the root of everything, which is "frontier compute." This year, we'll see big wins. Thanks for following.

For more than 10 yrs, I've worked on "frontier compute." I've worked on this since the "world computer" vision was first mooted. Nowadays, the terms "crypto," "web3" and "blockchain" are inextricably linked to speculative assets. But this is 1 niche application of the tech. 🧵

@devjoshstevens @Polymarket @dominic_w 你在干什么呢，还没睡醒？来活了啊，快上！

This is my 3rd week as VP of Engineering DeFi at @Polymarket , and I'm going to be straight: the traction @Polymarket has seen has massively outpaced our infrastructure, and we haven't done nearly enough to scale to keep up. I hear you, and fixing this is our entire focus. We're a major company now, and we need to engineer like one. Here's exactly what we're doing: - Onchain data latency. We're working on making this near-instant so the experience is incredible. - Chain migration. We need more block space, cheaper gas and much smaller block times so settlement is instant. - Transactions are getting cancelled. We understand this is one of the most frustrating issues right now, and we have a complete fix coming very soon. - Massive focus on the website to make it faster, more responsive, and with better UX. - We added observability everywhere. Proper alerting so we catch issues ourselves, market makers should not be the ones telling us something is down. That's been unacceptable, and we know it. - E2e tests throughout, starting with the CLOB, so issues get caught in CI before anything ships. - CLOBv2 is not a rewrite. It won't improve performance or stability on its own; it's an upgrade that unlocks us to move fast right after. We'll do better with communication next time. - We are rebuilding the CLOB from the ground up. Most important thing we're doing. Without it, we can't be the best DeFi exchange in the world. We know it, we're on it, it's mission critical. - Unified TypeScript SDK for all APIs, which is shipping soon. - Unified API. One WS connection for everything, with a schema that's actually readable. - New Polymarket contract in the works that unlocks things that are simply impossible on the current protocol. - New hires: Head of QA Automation, Head of Dev Tooling, Head of Internal Tooling, Head of Data Engineering. - Smaller, dedicated teams. Fewer focus points per person, clearer ownership. People do what they're good at and are accountable for it. - Working closely with customer support to give them real debugging tools so any user issue gets properly diagnosed, not lost. - Proper communication with marketing and market makers so everyone knows what's coming and when, and MM can submit feature requests with a clear path to get them into engineering and shipped. - Working with 4 security teams daily to ensure we're super secure and that funds are always safe. - Perps incoming. Brand new contracts and a backend built from scratch in Rust. We're proud of this one. - A lot of other fixes are running in parallel right now. Starting next Friday, I will be posting weekly engineering updates. I joined because I genuinely believe in what @Polymarket is trying to do. @shayne_coplan built this so the world has somewhere to go to find out what's actually going to happen, not what the media thinks, not what a pundit says, but what thousands of people are willing to put money on. But right now, our engineering isn't living up to that. We've let people down, and I'm not going to dress that up. I came here to fix it, and that's exactly what we're going to do. The next few months are going to speak for themselves. Stay with us.

@furan86999 @LBankchinese 老板可以参与我们的活动，如果不清楚可以私聊我

@LBankchinese 組隊一起玩還能有獎勵，這活動挺實在的，趕緊找人衝一波。

LBank × Nobody Sausage 正在招募創始戰隊隊長 🌭 扭一扭，帶隊衝，贏到底！ 瓜分 7,777U 總獎勵池，等你來拿。 我們正在尋找： • 群主 • 社群營運者 • 在地 KOL 建立你的戰隊，推動成長，競逐獎勵。 立即申請 👇 forms.gle/LRzZYhpLBqbEYb… 如有任何問題，請加入我們的官方群組： t.me/LBank_en/69545…

@IPDefenseForum 我日你妈傻逼东西 ，草你吗张口就来，你他妈说了是就是了？收了钱就老老实实当婊子，别他妈乱搞舆情、舆论！老子现在评论你都是给了你流量

點燃導火線 中國助長伊朗飛彈與太空發射能力 ipdefenseforum.com/zh-hant/2026/0…

@massachain 马克龙是不是也要参会，你向马克龙推荐massa，让法国采用massa

Massa is live from EthCC 9 in Cannes ☀️ Our team is here throughout the week, connecting with builders, partners, and anyone curious about what we're building. If you're around and want to meet, talk about DeWeb, automation, or Gossip, our decentralized messenger, feel free to reach out. See you in Cannes! 👋🏼

@0xStudy 你跟@hashkey对比一下，hashkey千倍打底，上市前肖风疯狂站台宣传，千倍完成以后就删资料

都在说YZi投的Opinion 没人说USDai嘛 马勒戈壁 这YZi投了一些牛鬼蛇神，属于看一眼都要亏钱的类型了 随便一提众所周知的都数不完： Tea、Hemi、Corn、aPriori、无敌畜的Blum、Tabi、Tge完直接跑的Sidekick、巴比龙、无敌恶心的Xterio…数不过来了 也有几个好的 属于粪里淘金了 OPN反撸太多让USDai把所有iCO的YT都狠割一刀咋都没人在意了？🤣 玩的人越来越少是有原因的😅你们投资者吃爽了 贡献费用的玩家被当厕纸用

@cheems0x @LBank_Exchange @LBankchinese 速速进群参与，有usdt还有周边😎

@EcoinAx @LBank_Exchange @LBankchinese 元旦活动像是直接开新一局的节奏快进快出才带劲

圣诞活动结束了，周边也抽完了，接下来开始元旦活动，进tg群就可以参与活动，门槛低见效快，完事了就发奖👋👋👋 t.me/LBank_cn/408793 #lbank @LBank_Exchange @LBankchinese

最新一期活动t.me/LBank_cn/434147

#LBANK 你们可能不知道，我在到处找话痨玩家进群聊天，只要聊天就能抽取LBank专属周边，只要你们进了群，你们要啥就给我说🫡🫡

@xiaojiejie2002 我草他们的婊子妈，搞得谁线下要砍他们一样，接广告就是接广告，天天无脑乱发引流就很傻逼，最后韭菜亏完了他们删推特，畜牲行为

你妈比的 我发现有些人接广告就接广告 还被迫接了个广告 咋了谁强迫你赚钱了啊 不接这个广告甲方就弄死你呗 又要钱又要当白莲花 接ju这样的广告就大大方方的承受舆论 赚钱没毛病推特商业化也能接受 当又立真的是大过年给我看恶心了🤮

@heyibinance 开公司不用本人到场，一张身份证就能搞定？那还要本人干嘛？丢证就活该背债、被告、被造黄谣，流程跟摆设一样，最后全让普通人买单是吧？🤫🤫🤫

如果你在中国曾经身份证遗失过，可能不小心因此背上负债，也可能因此成为“被执行人”，如果你是一个女性，还可能因此被造黄谣，哪怕你在很多年以前已经在法院赢了官司。建议所有曾经丢过身份证的朋友都去对应的系统检索一下自己的信息。 感谢友商中文水军在2020年帮我查到这个问题，后来经过漫长的诉讼解决了我自己不知道的历史风险。 对于一直努力“建设BNBchain MEME”的玩家，花那么多钱养水军，雇佣供应商，不如直接用户发福利。

@dominic_w 总结 Jolt zkVM 本身技术非常优秀、是领域突破，这点完全认可。 但 Zero 用它来宣称“可替代 AWS、成为世界计算机”是严重误导。 100,000 倍计算开销 + 级联回滚风险 + 天文服务器需求→ 不可能实现通用链上云。 行业已经被一堆“世界计算机”营销搞混乱，需要把真实成本讲清楚。

Urm, this is very misleading: "Zero... provides a credible alternative to centralized cloud providers like AWS" At a high-level, all you need to know is that Zero works by proving hosted computation is correct. The proving overhead makes computation 100,000X more expensive. Zero uses the Jolt zkVM to run computations, and generate proofs that computation has been performed correctly. The 100,000X cost multiplier number comes from the Jolt project itself, as per this linked content from the fall of 2025: a16zcrypto.com/posts/article/… Factually-detached as marketing in our industry typically is, I feel duty bound to share the truth because harmful market confusion has now been caused by a succession of networks marketing themselves as "world computers" capable of providing onchain cloud, when they can't remotely do anything of the sort. Hosting computation and apps fully onchain on the Internet Computer network, by comparison, doesn't involve an insane overhead, which is why the network is actually being used for sovereign cloud, and as a self-writing cloud backend by Caffeine. We don't want people to get confused. LayerZero naturally fails to mention the 100,000X expense overhead and instead bamboozles readers with descriptions of its "QMDB" verifiable database, and lofty claims that Zero could potentially process 2 million TPS (transactions per second). Team posts generally also include some idealist blockchain polemic for good measure, to emphasize they are the real deal. But just focus on the 100,000X cost multipler. The claim that Zero can provide onchain cloud that rivals AWS doesn't pass the smell test! That does mean the Jolt zkVM ("zero knowledge virtual machine") developed by a16z Research, is anything less than very impressive. It delivers major advances in the field and can be accurately described as an incredible piece of work. I can even imagine the Internet Computer network using it for much more specific purposes in the future. But, "The Network is The Cloud" paradigm cannot remotely be delivered by Zero so long as it relies on Jolt to prove the correctness of compute, which adds this insane overhead (Jolt runs the compute at near native speed, and it's the generation of the proof that creates the massive overhead)... Example 1: If a database command takes 1 second to run on some machine, then if that machines runs the computation using Jolt, it will take longer than a whole day for the computation to complete! Example 2: If a single server machine is running at full utilization, then to run that workload on Jolt, we must offload its proving work to other server machines. Since dividing proving work amongst different servers introduces additional overhead, around an additional 125,000X server machines will be required to prove the computation taking place. You read that correctly! LayerZero claims the Zero L1 can process 2 million TPS of general-purpose cloud logic. If we assume a standard server/node handles 2,000 TPS of complex SQLite logic (for example, SQLite can be embedded inside a Wasm canister smart contract on the Internet Computer), LayerZero would need 1,000 servers just for execution. But to provide the Jolt proofs they promise, they would need an additional 125,000,000 servers (125 million servers) running at full capacity just to keep up. This would require an unimaginably large data center to be available for proving (one orders of magnitude larger than has ever been created before) and somehow the network would have to pay for that. LayerZero is aware of these issues, and so let's look at how they hope to get around them, and the sacrifices Zero makes, which sheds light on the validity of its deccentralization claims. LayerZero hopes to leverage two technical angles to make this scheme practical. Firstly, zkVMs like Jolt allow computation and proving to be separated. Essentially, the computation runs on Jolt first at near native speed, producing an "execution trace" as a side effect, then that trace is used to generate the proof in a separate process that can run afterwards (which proof creation adds the 100,000X computational cost overhead). Secondly, the job of creating the proof from the trace can be divided amongst different machines ("sharded"), to speed up proof generation. For example, dividing the work of proof generation among 10 machines might produce a 9X speedup (rather than a 10X speedup owing to the overhead of sharding). Note that although a speedup is achieved, the overall cost multiplier increases beyond 100,000X owing to the overhead involved with sharding/parallelization. Zero is composed of multiple "atomicity zones," which scale Zero's capacity horizontally. An atomicity zone is roughly analogous to an Internet Computer subnet. Each atomicity zone reaches "soft finality" first, which occurs when the computation completes. Then "hard finality" is achieved later when the proving/generation of the proof of correctness is complete. Let's assume that proving is offloaded to some other capacity within the network, so computation can proceed at near native speed, delivering soft finality fast, while the proving catches up in the background, providing hard finality later. Firstly, we can see that while computation can proceed ahead of proving in bursts, proving must generally keep pace with computation, otherwise it will fall further and further behind. Ultimately, that means that computation is like a high-speed car that can only drive as fast as a person in the back can draw a map of where it's going. Secondly, we see that Zero is probably relying on the idea that people will be happy with soft finality. This is why their SVID (Scalable Verifiable Information Dispersal) module essentially shares *claims* about the state of atomicity zones across the network, rather than proven state created by hard finality. Thirdly, we can see that Zero's idea about the network relying on sharing data for which only soft finality has been achieved is flawed. Why? Because different atomicity zones will wish to rely on the state/data of others in their own computations. This results in easy-to-understand phenomenon called "fan out." Let's say Zone A shares soft finality data with Zone B, which performs some actions, updating its own data, which is shared with Zone C. If Zone A cannot later produce a proof to show that its data was correct at the time it was shared with B, and it reached hard finality, then Zone A must rollback to the previous valid hard finality state—which in turn means that Zone B must rollback, and Zone C must rollback. In a global onchain cloud environment, one app can call another app, that can call another app, ad infinitum. This "fan out" makes reverting state near impossible, especially if proving falls well behind computation. According to the "Zero: Technical Positioning Paper," if a proof fails, the system will use on-chain governance (directed by voting by ZRO holders/validators) to manually "adjust protocol parameters" or "upgrade validator software" to fix the problem. Obviously, if this ever became necessary, implementing the fix will not be so easy, and will take the network down for a very long time indeed. So what is LayerZero thinking? My guess is that they assume by partnering with trusted centralized parties like Google and Citidael, and getting them to run atomicity zones, their soft finality will be reliable enough that state reversions won't ever be necessary. We saw something similar in Optimism, the so-called Ethereum L2, which was run on a tightly-controlled network of machines. It was possible to submit a fraud proof to the network showing that something had gone wrong, but there was no way to revert to the state in such a case. It really was truly optimistic! If this understanding is correct, it means Zero is really a network depending on trust in institutions, rather than the math of zkVM proving per se. Since the network will be relying on soft finality and trust in institutions, rather than the hard finality provided by proving, it's not clear what the benefit of using Jolt exactly is—if the real purpose is to attach Zero to the buzz around zero knowledge proofs, then potentially this will become one of the most expensive marketing exercises in history. But, you say, this SURELY cannot be true! Well, this is where I landed looking at how they claim Zero works—although my time is limited, and I could have made mistakes. I hope they let me know if I have. My guess is that LayerZero justifies the current design of Zero on the basis that hardware cavalry is coming to make their architecture work better in the future. Specialized zk hardware, such as ZK-ASIC or FPGA devices that can be installed into servers, much like the Bitcoin mining cards that do hashing, are in development by companies like Ingonyama, and might reduce the proving overhead to 1,000x - 5,000x if their claims are accurate. Obviously, that kind of overhead will still be far too high for Zero to provide onchain cloud that can rival AWS, but, if it enables them to ditch soft finality, removing the impossible-to-satisfy requirement that the network can run global state reversions across atomicity zones, Zero will be interesting as a solution for hosting DeFi. I wish them well.

冲他妈的，你不玩，我不玩，会所嫩模谁来玩！ ca: 0x29e7cf1cecc15409e44fca7012a5dcca7cf87777

@ETHGasOfficial 谢谢你的赠予😎😎ethgasfoundation.org/token/

😎😎让我看看是谁还没有Lbank足球？

@miaaibot here！

@Starknet 说实话，从你发空投的那一刻起，你就比同为zk系的zksync优秀多了，你至少是个懂感恩的，而zksync直接就是个畜牲😀😀

8 users yes. But all whales.

#LBank 我村长说了，在社群发周边发钱，就是真的发周边发钱，你们还不来玩？？

@BTCOld8 玩个奶子拉尔夫套死我了

这轮BSC的土狗 #memecoin 暂时告一段落了，但并不代表结束！ 这两天的下跌是整体行情的下跌，不光是BSC的盘子跌，SOL的整体流动性也在缩减，物极必反，之前SOL的AI 热潮和BSC的一姐风波太猛了 市场不可能一直疯狂，确实也该到冷静冷静的时候了，前天晚上Alpha的 #黑马 和 #老子 应该就是BSC最后收割的信号，不过别担心，在币圈，meme板块只会更新周期，不会永远沉寂 这一轮结束了，下一轮才会开始，币安总是一波接着一波搞事，等大家都觉得BSC没希望的时候，二圣就会再次出来带货，Alpha也会重启 目前阶段BSC建议尽量不要多关注老盘子，尤其是已经上了Alpha的盘子，土狗玩新不玩旧，新周期肯定会诞生新概念 玩二段也尽量选SOL的 百万级以上的标的，也别瞎抄底，等到明显的反弹信号再进场