SUI (SUI)

$0.7719  -6.48%  24H

Индекс социальных настроений (SSI)

Рейтинг пульса рынка (MPR)

Посты из X

  • Kyle Chassé 🐸 Influencer Regulatory_Expert C
     290.20K  @Kylechasse

    Sui went down three times in 48 hours this week. I'm not going to pretend that's nothing. But here's what the bears aren't saying : No funds lost Validators coordinated full recovery every time And the network hit a 2026 TPS high of 1,539 the same week. A gas bug is a software problem. Software problems get patched. Shit happens. What a team does next matters more.

     10  10  588
    Оригинал >
    Тренд SUI после выпуска
     Бычий
    Although the Sui network experienced three outages, there were no fund losses; the team recovered quickly and achieved high TPS, and the issue can be fixed.
  • MartyParty TA_Analyst Influencer C
     243.72K  @martypartymusic
    Mark Logan D
     336  @technicaldebtor

    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

     382  69  44.63K
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    Sui experienced downtime due to a gas smash edge case, insufficient testing, and short‑term confidence was shaken.
  • Decode TA_Analyst Influencer B
     69.10K  @decodejar

    Three major outages in the last few days, and Sui's not looking particularly good here. People are comparing to Solana's early problems but they were largely capacity issues, whereas Sui is breaking at the consensus layer. These are much more serious problems. Furthermore, the 1.72 update that caused these problems passed through testnet without this fatal bug being caught. Two issues I see are the overall fragility of the network design where all validators are required to run the exact same software version, so a single bug will simultaneously take out the entire network, and second, the gap in quality assurance that allowed this edge case to reach production in the first place. Not a good look.

     41  4  2.26K
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    A fatal vulnerability in SUI's consensus layer caused multiple outages, revealing network fragility.
  • 0xPain FA_Analyst DeFi_Expert B
     7.40K  @0xPain__
    Mark Logan D
     336  @technicaldebtor

    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

     382  69  44.63K
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    Sui experienced an outage due to a gas smash edge case, and the team admitted insufficient testing.
  • ⚡Shane_S⚡ FA_Analyst Influencer A
     1.99K  @shanesek1

    Ah yes, RP... crypto's resident snake oil salesman.

    Alex 👽 FA_Analyst Influencer B
     11.68K  @AlexesNakamoto

    Raoul Pal’s investment track record is truly unmatched: 🚩 2020: Calls BlockFi & Silvergate "most trusted" 🚩 2021: Calls Terra Luna "risk-free" 🚩 2025: Goes "massively overweight" SUI ❓ May 2026: Just announced he bought Zcash https://t.co/ocGJM2f4wj

     5  1  218
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    Raoul Pal accused of misleading, recently bought ZEC
  • BL Dev Founder B
     6.44K  @_smbrian

    Sui successfully advanced to epoch 1,144 just now, and the Random object is now functional. Been a busy few days for core team and validators, hope everyone can get some well-deserved rest now.

     78  4  2.42K
    Оригинал >
    Тренд SUI после выпуска
     Бычий
    SUI has entered epoch 1,144, and the Random object feature is live
  • Philose 🦭 OnChain_Analyst DeFi_Expert B
     6.00K  @Philose
    Mark Logan D
     336  @technicaldebtor

    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

     382  69  44.63K
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    SUI's network failure due to insufficient testing raises doubts about short-term reliability
  • Dragnipur「🦑」 OnChain_Analyst DeFi_Expert B
     2.98K  @_Dragnipur_

    Pretty cool that this guy just straight-up said what happened. This is what communication should look like. And if anyone in the comments says something mean, just remember: that’s your problem, not mine. :*

    Mark Logan D
     336  @technicaldebtor

    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

     12  0  699
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    SUI experienced downtime due to a gas conflict; the team acknowledges the mistake and will improve testing.
  • yuppi.sui Community_Lead Educator A
     9.01K  @yuppidotsui
    Mark Logan D
     336  @technicaldebtor

    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

     382  69  44.63K
    Оригинал >
    Тренд SUI после выпуска
     Медвежий
    SUI network outage caused by edge case of address balances, team acknowledges mistake and will improve testing
  • tehMoonwalkeR FA_Analyst DeFi_Expert C
     132.98K  @tehMoonwalkeR

    "Address Balances is by far the biggest change to Sui's execution model that we have shipped, and we don't have any plans to ship anything this large and disruptive again. It was a necessary change to make $Sui into what it should be, but we don't seek out huge disruptive changes like this for the sake of it. Now that the feature is out we will be redoubling our efforts to make Sui the most reliable L1"

    Mark Logan D
     336  @technicaldebtor

    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

     15  2  2.52K
    Оригинал >
    Тренд SUI после выпуска
     Нейтрально
    Sui experienced a brief outage due to the address balances feature, and the team will strengthen testing to improve reliability.