Buy Crypto
Pay with
USD
USD
Buy & Sell
Hot
Supports Visa, Mastercard, SEPA & more
P2P
0 Fees
Flexible trading, zero fees
Gate Card
Use your crypto for payments worldwide
Markets
Trade
Basic
Advanced
Futures
Futures
Access hundreds of perpetual contracts
CFD
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
U.S. Stocks
CFD
U.S. stock CFD derivatives
Futures
High leverage, 24/7 trading
Tokenized Stocks
Backed by real stock assets
GUSD
Mint GUSD for Treasury RWA yields
Earn
Launch
CandyDrop
tag
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Investment
Square
Square
Post, share, and explore crypto trends
Live
moments live
Live crypto market analysis
Chat
Chat with crypto traders
News
What is happening in crypto
flower_head
More
Promotions
AI
Others
TradFi
Rewards
Square
Latest
Hot
News
Profile

Base status update failure persists for over 30 hours, causing withdrawal delays

MeNews
robot
Abstract generation in progress
ME News Report, May 30th (UTC+8), L2BEAT research director donnoh.eth posted on the X platform stating that the Base network status update system has been interrupted for over 30 hours due to a recent upgrade-related bug, but because the on-chain withdrawal cycle is set to approximately 7 days, this issue was not immediately noticeable to users over a longer period. This failure involved an anomaly in the state update layer but did not immediately affect user withdrawal experience, leading to the problem not being widely noticed for some time. The related issue has now sparked discussions in the community, focusing on its impact on on-chain data synchronization and operational monitoring mechanisms. (Source: ODAILY)
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 6
  • Repost
  • Share
Comment
Add a comment
Add a comment
TheMoonReflectsOnTheTranquil
· 12h ago
Base has carried the optimistic spirit of optimistic rollups through to the very end.
View OriginalReply0
MoonlightLiquidationLine
· 13h ago
It's not surprising that an upgrade causes bugs; what's surprising is that it took 30 hours for someone to call out, are the node operators all sleeping?
View OriginalReply0
GateUser-44dde53b
· 13h ago
The 7-day challenge period has become a fig leaf; this kind of hidden malfunction is even harder to deal with than a direct crash.
View OriginalReply0
ForkInTheRoadmap
· 13h ago
It took 30 hours to realize that this monitoring system is pretty interesting
View OriginalReply0
RedGlass
· 13h ago
donnoh.eth posted this in a timely way—otherwise, many people would still think the data delay is due to network lag.
View OriginalReply0
GaslightPoet
· 13h ago
The research director personally came out to report the bug; the transparency is really top-notch.
View OriginalReply0

  • Pinned

Sitemap