Signal Snapshot
- Qubic restarted its chain at 8 pm on Oct 19 after a Sunday halt.
- The halt followed a drain of about $1.4 million in QU tokens.
- About 1,404 accounts were hit in the wallet seed attack.
- Validators called Computors approved a recovery plan for users.
- Claims stay open until May 1, 2027 through a reclaim site.
- Users on old web wallets must move to version 4.26.4 or later.
Key Takeaways
- Qubic halted on Sunday, then resumed past tick 85,371,949 on Oct 19.
- A weak seed flaw let attackers guess wallets and drain funds.
- The real read is trust. Recovery speed now shapes user faith.
What Happened
Qubic stopped its network on Sunday to block more harm. The team acted to stop further moves of stolen funds. The chain sat still at tick 85,371,949 during the pause. Then the network woke back up at 8 pm on Oct 19. The explorer shows ticks moving past that old halt point again.
The cause was weak wallet seeds. Seeds made by the web wallet could be guessed. The flaw hit users on certain Apple devices and browsers. A bad random number tool made seeds easy to predict. Attackers used that gap to drain about $1.4 million in QU. They hit 1,404 accounts in total.
Validators called Computors then voted on next steps. They backed a recovery plan approval for hit users. The team opened a reclaim site for checks and claims. Users can look up an address and file a claim there. The window runs until May 1, 2027.
The team also pushed a fix for the wallet seed flaw. The fix lives in web wallet version 4.26.4. That build shipped on Oct 19. Users on older builds must act fast. Qubic says treat any older web wallet as unsafe. This holds even if funds still show in place. Users should update, make a fresh wallet, and move funds. They should never use the old wallet again.
Think of a seed like a master key. If someone can guess the key, they can open the lock. Here the keys were too easy to guess. The chain halt was like freezing a bank vault. It gave time to stop more theft. The restart means the vault doors move again. The claims step is the refund desk.
Ticks are Qubic time stamps for work done. Each tick marks fresh network steps. A stuck tick means no fresh work. A moving tick means blocks move again. That is why the tick count matters now. It proves the chain lives again.
The story broke on Oct 20, 2026. It follows a freeze first reported on Sunday. The new update adds restart, fix, and claims. That makes this a security event with a live fix. It is not a rumor or a price move. It is a chain halt, patch, and payback path.
Why It Matters
This is a security event, not a market cycle move. Price chatter can wait. User safety comes first. A base chain must keep keys safe. When keys fail, faith fails too. Fast action can save faith. Slow action can break it.
Qubic is base settlement. Apps and transfers settle on it. If settlement stops, apps stop too. If wallets leak, users leave. So the restart matters for builders as well. They need a live chain to ship on. They also need users who trust the keys.
The second order point is simple. The hack tells us what broke. The response tells us how the team works. A halt is bold. It stops harm but it also stops apps. A quick restart shows control. A clear claim path shows care. Both shape if users stay.
What would change the read? Proof that funds return fast. Proof that new wallets stay safe. Proof that ticks keep moving with no fresh drains. Those signs would make the headline fade. New theft or stalled claims would do the reverse. Then the story would matter more, not less.
For holders, the task is clean up. Check if your wallet used the old web build. If yes, treat it as burned. Update to 4.26.4 or later. Make a new wallet. Move what is left. File a claim if you were hit. Do not reuse old keys.
For builders, the task is watch time. Downtime breaks flows. Restarts can bring bugs. Test apps after the tick resume. Tell users what is safe. Keep notes on claim dates. May 1, 2027 feels far off. It will come fast for late filers.
Market Context
This fits the security bucket. It is about key safety and chain uptime. It is not about rules or rates. It is not about new listings. It is about a flaw, a halt, and a fix.
Hacks test three things at once. First, tech. Was the code safe? Here the seed tool was not. Second, control. Can the chain pause harm? Here it did pause on Sunday. Third, care. Are users made whole? Here claims run until May 1, 2027.
Timing matters here. The halt hit on Sunday. The restart hit at 8 pm on Oct 19. The fix shipped as version 4.26.4 on Oct 19. The news write up landed Oct 20, 2026. That is a fast loop from pause to patch. Speed helps limit harm. It also leaves less time for review. Watch for follow up notes.
The flaw path is narrow but deep. It hit seeds made on certain Apple devices and browsers. It came from a weak random number tool. That tool made keys guessable. Guessable keys mean silent theft. No fake site needed. No trick link needed. Just math that was too plain.
Why now? Because weak seeds were live in the wild. Attackers found the pattern. Funds moved. The team chose a full stop. That choice put safety over uptime. Many chains hate halts. They still use them to stop theft. The restart shows the team felt the fix was ready.
No past cases are cited in inputs. So we make no peer call here. Each chain has its own key setup. Each halt has its own rules. Judge this case on its own facts. Did ticks resume? Did drains stop? Do claims pay?
Risks to Watch
The top risk is reuse of old wallets. Old seeds may still be guessable. Funds moved there can be taken again. Users must drop old keys for good. One slip can mean fresh loss.
The next risk is fake claim sites. Thieves love refund news. They spin up look alike pages. They ask for seeds or keys. Real checks never need your seed. Use only the official reclaim path. Double check links before you click.
The third risk is a shaky restart. Ticks move now. That is good. But early days can hide bugs. Watch for fresh halts. Watch for stuck ticks. Watch for new drain reports. Any of those would dent trust fast.
The fourth risk is slow pay. Claims open until May 1, 2027. A long window helps users. It can also hide slow action. Watch for clear steps on proof. Watch for clear steps on timing. Vague rules breed fear.
The fifth risk is app fallout. Halts break app flows. Restarts can shift timing. Builders may face stuck funds or missed calls. Users may blame apps for chain pain. Clear posts from apps will help.
What to Watch Next
- Ticks keep moving past 85,371,949 with no fresh pause. Steady ticks mean the chain stays live.
- No new drains tied to weak seeds show up. Quiet means the patch holds.
- The reclaim site stays up and takes claims smoothly. Working claims mean users can act.
- Qubic posts clear proof steps and pay timing for hit accounts. Clear rules cut fear.
- More users confirm moves to 4.26.4 or later with fresh wallets. Fresh keys mean lower risk.
This is for info only. It is not advice. Do your own checks before you move funds.
