SUI (SUI)

I'm one of the people most directly responsible for this outage. I take Sui outages extremely personally and am incredibly disappointed that this happened. I'll echo what @EvanWeb3 said: Moving fast is no excuse for outages. This outage was caused primarily by an edge case in gas smashing introduced by address balances. However, we did not ship this feature carelessly. We spent over 6 months testing address balances and tried as hard as we could to exercise every edge case and combination of features we could think of. Unfortunately, we were bitten by an edge case that we did not discover during testing. Again, this is not an excuse - it shows that our testing strategy was inadequate, despite how much effort we put into it. We did not have a systematic way to enumerate or discover all possible edge cases. We will be re-examining our approach in light of this. But I do want to emphasize that we did not ship this feature carelessly or in a rush. We made mistakes, but we were absolutely not operating in "move"

I'm one of the people most directly responsible for this outage. I take Sui outages extremely personally and am incredibly disappointed that this happened. I'll echo what @EvanWeb3 said: Moving fast is no excuse for outages. This outage was caused primarily by an edge case in gas smashing introduced by address balances. However, we did not ship this feature carelessly. We spent over 6 months testing address balances and tried as hard as we could to exercise every edge case and combination of features we could think of. Unfortunately, we were bitten by an edge case that we did not discover during testing. Again, this is not an excuse - it shows that our testing strategy was inadequate, despite how much effort we put into it. We did not have a systematic way to enumerate or discover all possible edge cases. We will be re-examining our approach in light of this. But I do want to emphasize that we did not ship this feature carelessly or in a rush. We made mistakes, but we were absolutely not operating in "move"

I'm one of the people most directly responsible for this outage. I take Sui outages extremely personally and am incredibly disappointed that this happened. I'll echo what @EvanWeb3 said: Moving fast is no excuse for outages. This outage was caused primarily by an edge case in gas smashing introduced by address balances. However, we did not ship this feature carelessly. We spent over 6 months testing address balances and tried as hard as we could to exercise every edge case and combination of features we could think of. Unfortunately, we were bitten by an edge case that we did not discover during testing. Again, this is not an excuse - it shows that our testing strategy was inadequate, despite how much effort we put into it. We did not have a systematic way to enumerate or discover all possible edge cases. We will be re-examining our approach in light of this. But I do want to emphasize that we did not ship this feature carelessly or in a rush. We made mistakes, but we were absolutely not operating in "move"

I'm one of the people most directly responsible for this outage. I take Sui outages extremely personally and am incredibly disappointed that this happened. I'll echo what @EvanWeb3 said: Moving fast is no excuse for outages. This outage was caused primarily by an edge case in gas smashing introduced by address balances. However, we did not ship this feature carelessly. We spent over 6 months testing address balances and tried as hard as we could to exercise every edge case and combination of features we could think of. Unfortunately, we were bitten by an edge case that we did not discover during testing. Again, this is not an excuse - it shows that our testing strategy was inadequate, despite how much effort we put into it. We did not have a systematic way to enumerate or discover all possible edge cases. We will be re-examining our approach in light of this. But I do want to emphasize that we did not ship this feature carelessly or in a rush. We made mistakes, but we were absolutely not operating in "move"

$SUI back to back down. $SOL down multiple times in recent history. $KAS down 0 times, POW record set and big developments to come. Food for thought.

E173: Raoul Pal - Why I won't sell, why AI Agents' TAM is infinite and why it's it all so f*cking obvious @raoulGMI is back on When Shift Happens for a fun episode full of swearing and well needed hopium while the industry is in full crisis and depression. This time we cover the race to AGI, why crypto got left behind while Nasdaq ran, and why Raoul thinks the worst of that correction is over. We also get into what he's actually buying (moar $SUI and some $ZEC), his framework for valuing layer ones, and why he thinks most traders are just burning energy. Timestamps: Introduction Traveling Non-Stop & Kast Card Discussion Why Steak & Eggs Seems Expensive But $1000 NFTs Don’t What Raoul’s Been Up To The Past 4 Months Why The Stock Market Never Ceases To Grow What Is The Economic Singularity? Partnerships: @Trezor @Bitwise Is It Still Early To Invest In AI? Is Crypto Superior To AI Investment Wise Crypto’s Reasons For Going Up Forever Bitcoin Going From $126k - $60k Is A Nasty Correction Are Earl

What are you doing now? Testing $SUI engagement 🌊 https://t.co/VAFrbKV1Lp

$SUI back to back down. $SOL down multiple times in recent history. $KAS down 0 times, POW record set and big developments to come. Food for thought.

Sui is moving from a performance narrative to an ecosystem depth story. @SuiNetwork’s architecture gives the base layer, but the more important shift is what is forming on top DeFi liquidity, stablecoin capacity, trading activity, and app infrastructure. A metrics-led deep dive into Sui 🧵