Omid Malekan@malekanoms · X· 3 天前AI 评分 32Omid Malekan 质疑 Canton 未能实现去中心化和无停机运行，认为许可制网络难以做到这两点。引用帖称，Canton 主网升级期间拓扑冻结 24 小时、交易暂停，BitGo 维护事件持续 25 小时；Malekan 提醒，机构和监管者必须关注结算基础设施由谁叫停、修改和控制，以免面临系统性风险与监管套利。
The Canton people seem to believe that tweeting about desirable features like "decentralized" or "no downtime" is more important than actually achieving them.
Here is a good thread on why Canton doesn't achieve either. This is not surprising - permissioned networks simply can't.
Of course the bag holders, compromised VCs, pump and dumpers, and Suit Simps won't care about any of this—and that's their right.
But institutional users, and even more importantly regulators, have to care about these drawbacks, lest they face systemic risk and regulatory arbitrage.
From the thread:
"For institutions choosing settlement infrastructure, the questions are who can halt it, who can change it, and who owns it. On Canton the answer to all three is the same short list."
Canton says its consensus swap had "almost no downtime" and "nobody noticed." Two things worth unpacking: what the downtime actually was, and whether "decentralized network" is the right description. Thread, with on-chain data. 1/ Per Digital Asset's own operator notice, mainnet was topology-frozen for 24 hours (no new parties, validators or package vetting) and transactions paused at the Saturday 13:00 UTC cutover. BitGo kept a maintenance incident open for 25 hours and blocked Canton wallet initializations. The devnet run of the same upgrade hit a bug that pushed mainnet from Aug 8 to Oct 10. That is a maintenance window. Ethereum has produced a block roughly every 12 seconds since July 2015, through every upgrade, with no halt and no window. For 24/7 settlement, that difference is the product.在 X 查看被引用的帖子
来源：Omid Malekan· x.com