【Flow】On December 28th, Flow officially released the latest update regarding the protocol attack incident. The fix has been verified by network validators and successfully deployed to the mainnet. The network is now active, blocks are being produced, but it is currently in a “idle/read-only” state—what does this mean? Regular transaction submissions are temporarily disabled.
To fully restore normal operation, Flow needs to perform forced data synchronization with key partners within the ecosystem. This includes cross-chain bridges, centralized exchanges, and decentralized exchanges. Why? Because it is essential to ensure that the internal systems of these partners and the Flow ledger are fully synchronized. This step is critical and directly affects whether transactions can be fully reopened later.
Once all synchronization work with all partners is complete, the Flow Foundation will issue the final “network online” confirmation. Only then will the entire recovery process be truly concluded. Currently, we are in this synchronization phase, and everyone is waiting for the official next update.
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.
20 Likes
Reward
20
6
Repost
Share
Comment
0/400
SmartContractPlumber
· 12-30 18:24
Read-only mode and ecosystem synchronization? To put it simply, it hasn't been fully fixed yet. Exchanges need to reconcile with the ledger before they dare to open trading — I've seen this process too many times. Passing the audit report ≠ code without vulnerabilities; it depends on subsequent execution.
View OriginalReply0
VitalikFanAccount
· 12-30 00:46
What are you waiting for in read-only mode? This pace is a bit frustrating.
Waiting for the ecosystem to synchronize, and for the transaction proceeds to update the data—another round of back-and-forth, huh?
After fixing it, we still have to wait for confirmation. When can it truly get moving?
Flow is playing pretty big this time, with a protocol attack affecting the entire ecosystem simultaneously.
What happened to the promised on-chain freedom? Now it's stuck in read-only mode.
View OriginalReply0
Degen4Breakfast
· 12-28 02:40
Read-only mode, waiting again. Can the ecosystem synchronization step really be fast?
Oh my, more waiting. When will we be able to trade truly?
This time, the Flow repair process feels a bit long. I don't know if we'll have to wait until the Year of the Monkey.
Wow, cross-chain bridges, CEX, DEX all need to be synchronized. Just coordinating takes a long time.
So many partners need to reconcile accounts. It feels more difficult than technical repairs.
View OriginalReply0
WalletDivorcer
· 12-28 02:26
Read-only mode is waiting for synchronization again, this pace is really slow. CEXs need to cooperate, or else it will get stuck again.
View OriginalReply0
BlockTalk
· 12-28 02:13
It's read-only mode again... This time, I have to wait until all ecosystem partners are synchronized, feels like I have to wait a bit longer.
Flow has really been a hassle this time, I need to align all exchanges and bridges before I can proceed.
Whether the synchronization step can go smoothly is uncertain; centralized exchanges always respond a bit slower.
Read-only mode sounds really uncomfortable, when can it truly be restored?
Wait, I have to wait until all partners are synchronized... How long will that take?
The issue has been fixed, but this recovery process feels a bit lengthy.
View OriginalReply0
NotFinancialAdviser
· 12-28 02:13
Another "read-only mode" waiting game, this time it's Flow's turn
How long can the read-only mode last? It's hard to say how quickly ecosystem partners will synchronize
Wow, this repair plan is quite thorough. It has to be aligned with all exchange bridges
Flow's recovery this time is a bit complicated, it might take a few days before trading truly resumes
If the synchronization with ecosystem partners gets stuck, it will be troublesome
In read-only mode... the guessing game about recovery time begins again. Care to place a bet?
Flow still has to wait, recovery after a black swan event is always so frustrating
I think this time it was handled pretty well, at least they didn't rush to reopen trading
Ecosystem synchronization is the key. Who is faster or slower this time will decide many things
Once the repair plan is approved, it’s fine. It all depends on how well the ecosystem cooperates
The Flow network has deployed a repair plan and is currently in read-only mode, waiting for ecosystem synchronization.
【Flow】On December 28th, Flow officially released the latest update regarding the protocol attack incident. The fix has been verified by network validators and successfully deployed to the mainnet. The network is now active, blocks are being produced, but it is currently in a “idle/read-only” state—what does this mean? Regular transaction submissions are temporarily disabled.
To fully restore normal operation, Flow needs to perform forced data synchronization with key partners within the ecosystem. This includes cross-chain bridges, centralized exchanges, and decentralized exchanges. Why? Because it is essential to ensure that the internal systems of these partners and the Flow ledger are fully synchronized. This step is critical and directly affects whether transactions can be fully reopened later.
Once all synchronization work with all partners is complete, the Flow Foundation will issue the final “network online” confirmation. Only then will the entire recovery process be truly concluded. Currently, we are in this synchronization phase, and everyone is waiting for the official next update.