Bybit has confirmed that its Avalanche infrastructure will support the network’s v1.15.0 upgrade, giving AVAX users one less exchange-compatibility issue to worry about during the transition.
The September 22 notice covers both AVAX and Avalanche C-Chain support.
When a blockchain ships a network upgrade, exchanges have to update the software that connects deposits, withdrawals and internal wallet systems to the chain.
If they do not, customer transfers can stall even while spot trading remains available.
Bybit says it is updating its validator and node infrastructure for the Avalanche v1.15.0 release while maintaining trading during the synchronization process.
That makes this primarily an infrastructure story.
Users are not being asked to migrate tokens, claim a new asset or swap AVAX into a different contract.
The Bybit notice is also useful for what it does not say.
There is no token redenomination, supply-cap change or new asset created as part of the exchange support process.
The work is about keeping Bybit’s backend aligned with the upgraded Avalanche network.
For users, that should translate into continued exchange support once node synchronization is complete.
For Avalanche, exchange adoption of a network release is one of the quieter but necessary steps in moving new software into production at scale.
This article was written by the News Desk and edited by Samuel Rae.
—
Blog powered by G6
Disclaimer! A guest author has made this post. G6 has not checked the post. its content and attachments and under no circumstances will G6 be held responsible or liable in any way for any claims, damages, losses, expenses, costs or liabilities whatsoever (including, without limitation, any direct or indirect damages for loss of profits, business interruption or loss of information) resulting or arising directly or indirectly from your use of or inability to use this website or any websites linked to it, or from your reliance on the information and material on this website, even if the G6 has been advised of the possibility of such damages in advance.
For any inquiries, please contact [email protected]
