Nebulas’ Swap.NextDAO will be upgraded to version 1.1 and will fix an issue related to the use of nUSDT. At that time, users who have provided liquidity will be required to move their assets to the latest version.
Beginning on January 26th, Beijing time, the nUSDT related services in Swap failed. This issues involves the swapping and sending of nUSDT as well as the addition or removal of liquidity for nUSDT-related pairs (nUSDT-NAS, nUSDT-NAX).
The current bug will cause the failure of nUSDT related services but does not affect the security of users’ assets. Users who have pledged LP can continue to obtain and receive benefits. NAS-NAX pairs and Link services are also not affected.
When the Swap smart contract processes a transaction, it determines when the transaction occurred and at that point, the on-chain transaction count increases sequentially. The current contract uses a transaction timestamp. Some transactions did not use the correct timestamp when submitting the transaction on January 25th, Beijing time. As a result, the transaction timestamp was significantly higher than the current timestamp, and the new transaction time verification failed. Details will be further announced after version 1.1 goes live.
Swap contract address
Update to fix the problem:
The nextDAO team communicated with the Nebulas development team and a solution has been extrapolated. In the upcoming version 1.1 release, the timestamp used by the contract will be replaced with the block timestamp to ensure that the transaction sequence always matches the on-chain time thereby permanently solving this issue.
Asset migration for affected users:
This affects all users who have added liquidity via the current swap.nextDAO 1.0 version (including nUSDT-NAX, nUSDT-NAS, NAS-NAX):
- Holders of LP tokens: You will need to remove all liquidity from the pools....
To keep reading, please go to the original article at:
Nebulasio - Medium