Futures
Access hundreds of perpetual contracts
TradFi
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
Launch
CandyDrop
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
The BSC mainnet is about to initiate the Fermi hard fork upgrade, which is an important network optimization.
Upgrade details are as follows:
⏰ Activation time: January 14, 2026, 02:30 AM (UTC)
✅ Compatible versions: v1.6.4, v1.6.5
All validators and block producers must complete client updates before the hard fork trigger, otherwise they may experience validation or block production issues. This is crucial for maintaining network stability. If you are running a BSC node, it is recommended to complete the upgrade preparations a few days in advance to avoid disconnection risks during the hard fork. Detailed upgrade steps and technical instructions have been published; please refer to the official documentation to complete the process.
The upgrade time is again around 2 a.m., this timing is a bit tough.
Brothers running nodes, remember to prepare in advance, don't be caught off guard.
Wait, are v1.6.4 and v1.6.5 compatible? Which version should I upgrade to now?
What exactly did Fermi optimize this time? It feels like every time they say it's an important optimization, but the actual changes are not significant.
How does the Fermi upgrade optimize the system? Can it make gas cheaper?
Validators are going to start messing around again. Mark January 14th on your calendar so you don't oversleep.
Before the upgrade, check the nodes in the next few days. Don't want to be as clumsy as last time.
2026 is still so far away, it's really not too early to be reminded now.
---
Everyone, please update your clients before January 14th, or you might really get disconnected.
---
v1.6.4 should be enough, why insist on upgrading to a new version?
---
Upgrade early for a better experience; delaying might really cause issues.
---
Every hard fork is a gamble, hoping no bugs appear.
---
With BSC's frequency, it feels like it will never end.
Speaking of which, the Fermi upgrade really can't be delayed. It must be completed before January 14th, or don't blame me if you go offline
BSC keeps upgrading so frequently, it feels like there's no peace for a year
Remember v1.6.4 and v1.6.5, only these two versions are usable
It's never too early to get started, don't wait until 2:30 AM that day and suddenly find yourself falling behind the network haha
---
Brothers, hurry up and update, or you won't be able to mine blocks later.
---
Why is it always so rushed? Can't the advance notice be a month earlier?
---
Problems for v1.6.5 users are not significant; it mainly depends on how quickly validators respond.
---
Another hassle, so annoying.
---
A week before the hard fork should be enough to prepare; no need to be too nervous.
---
What can Fermi optimize this time? Is it just another gimmick?
---
Node enthusiasts are trembling; it's time for duty again.
---
Upgrading at 2 a.m. UTC, the time zone folks are suffering.
---
The risk of disconnection is real; I’ve been burned before.
Upgrade early or just wait to get disconnected, everyone
Fermi upgrade, it feels like the same routine every time
Which is more stable, v1.6.4 or v1.6.5? Has anyone tried?
Operations and maintenance are really exhausting, need to prepare in advance
Mid-January at this point is quite awkward
BSC's infrastructure awareness is still there, but proper execution is the key
Validators are going to be busy again
The most annoying thing about node upgrades is the strict timing
Can we fix all the issues at once, instead of constant small tweaks
Quickly check the node version to avoid going offline later.
Mid-January 2026, note it down.
Early preparation is never wrong; this is basic validator operation.
Fermi optimization... Sounds like a performance adjustment. Looking forward to subsequent feedback.
---
Nodes that are unprepared before a hard fork, get ready to be kicked out of consensus. I’ve already scheduled this on my end; efficiency is the key to competitiveness.
---
By the way, what exactly will this optimization change? Saying "network optimization" is too vague; we need to see whether it’s about consensus or gas calculation to assess the risks.
---
Can staking yields still be guaranteed? Will there be any interruption during the upgrade... That’s what operators care about most.
---
A few days in advance? I suggest preparing the test environment a week ahead, don’t leave it until the last minute.
---
It’s always UTC time, I have to convert every time, so annoying. But this time, the compatible version range isn’t too broad, which is actually a good thing—limiting the version range reduces variables.
---
Can I just look at the official documentation? Well, it depends on how well the documentation is written... Some official manuals are truly disastrous.