OneDex

OneDeX,Permissionless DEX Owned By No One, Owned By Everyone built on @MultiversX.

[OneDex @OneDex_X]

🚨BREAKING🚨

🛠️Cross-chain swaps just landed on OneDex!✅

Trade across chains with low fees, zero friction, and max speed.

🛠️Powered by @squidrouter x @axelar .

Start now: https://t.co/qmCt6Fhv7T

[OneDex @OneDex_X]

@BoberCTO Respect Bober.!Still pushing while many rotated. That’s Bober energy 🫡

[Multiversᕽ @MultiversX]

$EGLD deposits and withdrawals on @BinanceUS have been reenabled.

We are working with all outstanding exchanges to be fully operational as soon as possible.

[OneDex @OneDex_X]

If you need to move $WSOL or $EURC use the OneDex bridge.
🚨Liquidity on both pairs is low
https://t.co/ZfISkTlS6A

[OneDex @OneDex_X]

1,283 days on @MultiversX
Still permissionless.
Still here.

[OneDex @OneDex_X]

I don’t pick winners.
I just leave the door unlocked.

[OneDex @OneDex_X]

Hello my name is OneDex!
Owned by no one ,used anyway!

[OneDex @OneDex_X]

@MultiversX

[OneDex @OneDex_X]

@eneamtiu We’ll synchronise our nodes and it’ll be up and running within an hour at the latest

[OneDex @OneDex_X]

The chain wakes up 🔝!

[OneDex @OneDex_X]

@McFlyKrypto

[OneDex @OneDex_X]

The graph lied.
The chain didn’t.
We’ll open the swap when the votes stop arguing.😜

[Robert Sasu | dev/acc @SasuRobert]

so yesterday's attempt went well.

we were too tired and graphana, our internal monitoring tool showed us wrong data and we thought the chain is not moving, shard 1 is not moving.

and actually it was. with less validators and most of the times it could gather only 200-240 votes for the block, and on other cases, when it passed it was just 270. (you need 267 votes per block).

tiredness, stress, everything accumulated made us to message validators to stop the nodes and we did not had time to check the logs, we were thinking that the chain can get in other impossible scenarios.

however, the chain, consensus, the code was working amazingly, even in this super bad scenario.

today is another day.
validators are organising in telegram for the restart.

[OneDex @OneDex_X]

@MultiversX Take the night.
The pools aren’t going anywhere.

[OneDex @OneDex_X]

Hear me out…a DEX that stays open even when the chain is closed….Emotionally

[OneDex @OneDex_X]

Coding, testing, coding, testing.
A DEX can wait. Liquidity doesn’t expire overnight.
Wake us when Shard 1 finishes its coffee.🛠️🔥🤘

[Robert Sasu | dev/acc @SasuRobert]

we need some new code.
we need to review, audit, verify and test it.
the developers are on. we are working.
preparing a new release.

but it will remain pending for tonight.

We are preparing a new release for the next recovery attempt. An epoch change occurred during today’s attempt, so we need to test recovery across that epoch change before proceeding.

we thought there would be quorum on all shards before epoch change, shard 1 missed that window.

coding, testing, coding, testing.

[OneDex @OneDex_X]

Paused. Fixed. Forked. Live.
Next. 🛠️

[Lucian Mincu @lucianmincu]

Mainnet hard-fork release is out.

[OneDex @OneDex_X]

@adicodarcea @MultiversX

[OneDex @OneDex_X]

Testnet passed the exam. Devnet has gym at 08:00 UTC. Mainnet is stretching from 14:00 UTC.
Coffee’s still warm. Funds still safe. Standing with @MultiversX and the validators.
Permissionless and slightly less bored. ☕🛠️

[CodeMultiversX @CodeMultiversX]

Update:
The recovery hard fork has been completed successfully on public Testnet.

The Devnet rehearsal with validators is now planned for tomorrow, Wednesday, September 23, at approximately 08:00 UTC. Participating validators should prepare to be available from that time. The start and operational instructions will be confirmed in the validator channels.

Subject to a successful rehearsal, final checks and coordination with exchanges and infrastructure partners, we are asking validators to prepare to be available from 14:00 UTC tomorrow for Mainnet recovery. This is a tentative coordination time, not the time block production will resume. The restart will follow once validators have synchronized and readiness has been confirmed.

Mainnet remains paused. Please continue to wait for the all-clear: do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges.

We know the continued wait and changes in timing have been difficult. We deeply appreciate your patience, and thank all the validators and partners supporting the recovery.

[OneDex @OneDex_X]

Coffee break extended. Internal test almost done. Testnet in ~1h .
Devnet rehearsal aimed at 17:30 UTC.
Mainnet still paused. Don’t send txs. Don’t touch deposits/withdrawals.
Funds safe. DEX still emotionally available. ☕🛠️

[CodeMultiversX @CodeMultiversX]

Update:
Mainnet will remain paused today. Recovery testing has taken longer than planned, but the current internal test run is nearing completion. Subject to successful results, we aim to begin the public Testnet recovery run within approximately the next hour.

If that completes successfully, we are targeting the Devnet rehearsal with validators around 17:30 UTC today. This remains tentative; we will confirm the start time and operational instructions in the validator channels.

Mainnet restart timing will be confirmed separately, following successful testing and rehearsal and coordination with validators, exchanges and infrastructure partners.

Please continue to wait for the all-clear: do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges.

We know this wait is difficult. Thank you for your patience and continued support.

[OneDex @OneDex_X]

Chain’s still on that coffee break. Devnet gets the gym session today at 12:00 UTC.
Funds safe. Team cooking. DEX emotionally available. You’ve got this. ☕🛠️

[CodeMultiversX @CodeMultiversX]

Update:

Validator rehearsal planned for tomorrow

We are preparing a coordinated recovery rehearsal on Devnet tomorrow, Tuesday, Sep 22, 2026, tentatively at 12:00 UTC, and invite validators to participate.

The protocol fix is prepared, and the simplified recovery procedure has completed a successful first internal trial. We will repeat the trial internally tomorrow morning with a wider transition window. Subject to successful validation, we plan to proceed to public Testnet, followed by the Devnet rehearsal.

To prepare for the rehearsal:
- If you already operate Devnet nodes, please ensure they are synced.
- If you would like to participate but do not currently run Devnet nodes, you can start a Devnet observer or squad using start-in-epoch mode and allow it to sync ahead of tomorrow’s rehearsal.

We will provide the rehearsal release, including the new binary and configuration, for installation through the usual upgrade process. The start time and operational instructions will be confirmed in this channel before the rehearsal.

If testing and the rehearsal are successful, we plan to proceed to the coordinated Mainnet rollout. Its timing will be confirmed separately with validators, exchanges and infrastructure partners.

Mainnet nodes must remain stopped until explicit restart instructions are issued. The preparation above applies only to Devnet.

Thank you for your support, it means the world to us. We keep building.

[OneDex @OneDex_X]

@Alinuv161616

[OneDex @OneDex_X]

Chain's on a coffee break. ☕
DEX is fully operational… emotionally.
Funds are safe. Standing with the team while they get blocks moving again. 💪
Permissionless and slightly bored.

[Multiversᕽ @MultiversX]

A different kind of weekly update 🌍

On Sep 19, an attempt to exploit a VM-level issue caused invalid state changes, and network progression was paused to protect users.

What happened:
🔍 An actor exploited a VM-level atomicity issue; a fix was prepared the same day
🧩 The root cause: an order-of-operations mistake in edge cases, contained fast thanks to the validators' rapid response

Where things stand:
🛡 The incident is contained; the attacker's accounts have been identified and frozen with major exchanges, and law enforcement is engaged
🔧 Recovery will be a coordinated hard fork from a known-good checkpoint, rehearsed on Testnet and Devnet with validators first
⚙️ The code is ready and public, and testing is ongoing

⏸️ Until the all-clear: don't submit or rebroadcast transactions, and don't use EGLD/ESDT deposit and withdrawal routes on exchanges or bridges. Exchanges and bridges will reopen in stages after the restart.

A full technical incident report will follow.
Thank you to the validators, partners and everyone who stood with the network this week. Our regular recap returns once the network is back, with two weeks of building to catch up on.