mw

block plumber🧑‍🔧 | @SuiNetwork 🌊 | @Mysten_Labs | views are my own

[mw @mwtian]

AGI test for Claude: figuring out which command is safe to run

[mw @mwtian]

@pikapikasui Is "db-path:" in the full node config correctly pointing to the snapshot? This should be a more detailed guide: https://t.co/voOu4NZLIZ

[mw @mwtian]

An unfortunate event but we learned a lot from it.

[Sui @SuiNetwork]

Yesterday, Sui experienced a prolonged disruption due to an internal divergence in validator consensus processing causing a network stall for approximately six hours.

The team identified the issue, implemented a fix, and validators elected to upgrade to it so normal consensus could resume, bringing the network back to fully operational performance.

While this interruption was unintended, it confirmed Sui’s safety-focused architecture did what it was designed to do: protect the network. We thank you for your patience.

Read our post-mortem on the incident: https://t.co/TjvwY2vaBw

[mw @mwtian]

Work paying off!

[0xEvan @EvanDeKim]

⚡📉 Under the hood, @SuiNetwork's Mysticeti consensus commits have gotten a lot faster and more stable this year:

- p95 decreased 20% (114ms -> 90 ms)
- p99 decreased 27% (156ms -> 114ms)
- p50 decreased 5% (70ms -> 67ms)

[mw @mwtian]

In DAG consensus like Mysticeti, every validator can be a proposer at every round, in the sense of contributing egress bandwidth and transactions to be committed.
Leader is equivalent to proposer in linear consensus. But leader in DAG consensus makes less sense. "Anchor" is a more accurate term to describe the block(s) helping to select other blocks to commit from previous rounds. Non-DAG consensus probably doesn't have an equivalent consensus. The Mysticeti paper has described using multiple anchors per round. This is a better illustration: https://t.co/JledHgAK0q. Currently Sui consensus uses one anchor per round, and we are working on using multiple anchors. This is both for latency reduction and front run mitigation.
With MCP consensus (DAG or otherwise), besides next round leader, any validator can front run transactions in block B even from the current round, if the validator can submit transactions to commit together or earlier than B. There is a project to address the issue on Sui as well.

[mw @mwtian]

@opiateful @SuiNetwork It’s now clear that the latency from clicking “Swap” on a dex to seeing the wallet pop up is taking longer than from approving in the wallet to on-chain finalization. We do plan to analyze and optimize the end-to-end experience further.

[mw @mwtian]

Mysticeti v2 will become the default for Sui transactions in the upcoming release 1.60.

[Sui @SuiNetwork]

Mysticeti v2 just dropped ⚡️

Sui’s consensus engine leveled up - integrated validation, smarter transaction flow, and up to 35% lower latency.

Faster. Lighter. Smarter.

Full breakdown 👇
https://t.co/16sYBS4mjf

[Sui Group Holdings (SUIG) @officialSUIG]

SUI Group Partners with Ethena and the Sui Foundation to Launch suiUSDe and USDi, the First Native Sui Stablecoins
https://t.co/QrIp22N23I

[Sui Group Holdings (SUIG) @officialSUIG]

$SUIG 🌊
has been welcomed to
@NasdaqExchange

[kklas @kklas_]

We've enabled closing of Cetus positions yesterday and now the USDC and suiUSDT vaults are unpaused as well!

Thanks to the 90% liquidity recovery on relevant Cetus pools, the vault (lender) liquidity is now fully covered and withdrawable, while LP users will claim the remaining portion through Cetus compensation (on Cetus app). So effectively, Kai is now entierly free of bad debt!

These past 2.5 weeks have been incredibly intense, and we couldn’t have gotten through it without the patience, support, and trust of the Kai community. Thank you all for standing by us — it truly means a lot.

We’ve got a bit of cleanup left over the next day or two—then it’s full steam ahead with the new features we had lined up (delayed only by the Cetus incident). We’re excited to finally share them with you!

[Cetus🐳 @CetusProtocol]

💪 1st stage — back to the TOP 10 DEX list of all chains by daily trading volume. 🌊🌊

#Cetus 🐳

[mw @mwtian]

@irvinxyz @SuiNetwork time and venue plz!

[Cyn @CQ_Neverland]

One of the most common questions we get on the @SuiFoundation ecosystem team is:

"What kind of support do builders get on @SuiNetwork?"

This thread dives into one of our top priorities for 2025: helping early-stage teams fundraise.👇

[mw @mwtian]

@ronanyeah lol

[mw @mwtian]

@guinnessstache @EmanAbio @Mysten_Labs @SuiNetwork @WalrusProtocol @DeepBookonSui One example, Walrus uses Sui for metadata management and coordination. Walrus would be harder to build without Sui. Also, this is a Deepbook frontend served by Walrus Sites: https://t.co/i1NczyjW3B

[mw @mwtian]

NFT season on Sui feels like back to 2023! Also there is Tako from @7k_ag_ : https://t.co/4ow2ojd9Oo

[𝕮𝖍𝖔𝖈𝖔𝖑𝖆𝖙𝖊 ☠︎ @chocolate_xo3]

gSui
Happy good friday!
These are NFT mints you should look out for;

@TheQuntz
Mint date : 18th April.
Time: 4pm UTC

@SuiPugwif
Mint date : 21st April
Time : TBA

@Blork_sui
Mint date: 20th April
Time : TBA

@WATwalrus
Mint date: TBA
Time: TBA

@SUIHEADS_NFT
Mint date : 21st April
Time : 12am UTC

@theordersui
Mint date : April 26th
Time : 6pm UTC

@lofitheyeti
Mint date : TBA
Time : TBA

@VOXXinc
Mint date : 23rd April
Time : TBA
It’s NFT szn, make sure not to miss out on these mints!🫵🤎

[mw @mwtian]

@Suilluminati_ They look super nice!

[mw @mwtian]

Upgraded Ledger device, Sui app and Ledger live to the latest versions. Great to have native support for Sui!

[Ledger @Ledger]

It’s official – @SuiNetwork is now LIVE on Ledger Live Mobile!

Send, receive, and manage your SUI on the go—anytime, anywhere. 🌍

Self-custody meets true mobility with Ledger’s industry-leading security.

No compromises. 🔐

Just power, protection, and full control in your pocket.⚡

[mw @mwtian]

@_StudioMirai @_smbrian @_smkotaro wow what have i missed!

[mw @mwtian]

I'm seeing this error in my broswer:

Access to fetch at 'https://t.co/IQm0ar8IQo' from origin 'https://t.co/P3NhPrW9q4' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

It seems the ika fullnode is misconfigured or down right now. I think it is best to see if there are updates from ika discord.