Sei v6.4 is live on mainnet. Here's what it means for the SIP-3 transition: v6.4 adds the ability to disable inbound IBC transfers on Sei. IBC is Cosmos' interop protocol. Once activated via governance, users will no longer be able to bridge CosmWasm assets onto Sei. This… https://twitter.com/Sei_Labs/status/2043733269351674327/photo/1
中文: Sei v6.4 在 mainnet 上实时直播。对SIP-3过渡的意义如下: v6.4 增加了在 Sei 上禁用入站IBC传输的功能。IBC 是 Cosmos 的间接协议。通过治理激活后,用户将无法再将 CosmWasm 资产连接到 Sei 上。 这个......
In many multi proposer chains, a cartel that controls enough lanes can extract MEV from users. That was previously thought as the price of high throughput. Giga will use Sedna to prevent this https://twitter.com/Sei_Labs/status/2041605349967589835/photo/1
中文: 在许多多个提议链中,一个控制足够车道的贩毒集团可以从用户那里获取MEV。 这被认为是高吞吐量的代价。 Giga 将使用 Sedna 来阻止此功能
In multi proposer chains like Giga, a cartel that controls enough lanes can extract MEV from them. That's the price of high throughput. Today, most multi proposer chains handle this at the cost of good throughput. Giga will use Sedna https://twitter.com/Sei_Labs/status/2041593938461815217/photo/1
中文: 在像吉加这样的多个提案链中,一个控制足够车道的贩毒集团可以从这些链条中获取MEV。 这就是高吞吐量的代价。 如今,大多数多方案链都以高吞吐量为代价来应对这一措施。Giga 将使用 Sedna
We rebuilt https://seilabs.io/ to show what we're working on: from Giga to the projects we've been incubating We'll have a lot more going live in the coming months If you like solving hard problems, check the open roles https://twitter.com/Sei_Labs/status/2036817944274247804/video/1
中文: 我们重建了 来展示我们正在制定的工作:从 Giga 到我们一直在孵化的项目 在接下来的几个月里,我们将会有更多的直播 如果你喜欢解决难题,请查看开放角色
The typical mode for faster finality is to weaken the fault model. 5f+1 drops Byzantine tolerance from 33% to 20%. Ethereum's FCR adds a synchrony requirement. And rollup preconfs rely on a single sequencer. Giga preserves the fault model and redesigns everything else https://twitter.com/Sei_Labs/status/2034656395400990996/photo/1
中文: 快速终结的典型模式是削弱故障模型。 5f+1 将拜占庭式的容忍度从33%降至20%。以太坊的FCR增加了同步要求。卷轴前列靠单个音序器。 Giga 保留了故障模型,并重新设计了其他所有内容
Ethereum has never been fully asynchronous. But nothing consequential ever depended on a 13-second window before. The Fast Confirmation Rule changes that. FCR commits in ~13s but requires synchrony. Now there's an incentive to induce exactly the attack FCR assumes won't happen https://twitter.com/Sei_Labs/status/2033995265041125570/photo/1
中文: 以太坊从未完全异步。 但任何影响都取决于之前的13秒窗口期。 快速确认规则会改变这一点。FCR 以 ~13 s 提交,但需要同步。 现在有动机促使FCR认为不会发生攻击
Storage for @SeiNetwork has been redesigned for Giga. ReceiptDB will replace PebbleDB, which uses Parquet style storage for writes and DuckDB for reads. Faster writes and much faster reads means less waiting on history, quicker backfills, and more headroom for apps under load. https://twitter.com/Sei_Labs/status/2031372034073305117/photo/1
中文: @SeiNetwork 的存储功能已重新设计为 Giga。 ReceiptDB 将取代 PebbleDB,后者使用 Parquet 样式存储作为写作,DuckDB 用于读取。 更快的写入速度和更快的读取速度意味着等待历史的时间更少,返回速度更快,且加载后应用空间也更大。