You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the reported issue at Loopring/protocols#2591. When digging that issue, I also noticed that the dexwebapp do not show the right timestamp of the orders. See the following screenshot:
Initially, I thought the trades were out-of-order. But then I noticed the "second" value been over 60. I checked the latest trades with the api (https://api3.loopring.io/api/v3/trade?market=LRC-USDC&limit=200&fillTypes=mixed) and they are in synch. So, I think there's an issue on the way those timestamps are printed.
I would like to open a PR to fix that, but unfortunately I do not have enough time rn.
The text was updated successfully, but these errors were encountered:
Following the reported issue at Loopring/protocols#2591. When digging that issue, I also noticed that the dexwebapp do not show the right timestamp of the orders. See the following screenshot:
Initially, I thought the trades were out-of-order. But then I noticed the "second" value been over 60. I checked the latest trades with the api (https://api3.loopring.io/api/v3/trade?market=LRC-USDC&limit=200&fillTypes=mixed) and they are in synch. So, I think there's an issue on the way those timestamps are printed.
I would like to open a PR to fix that, but unfortunately I do not have enough time rn.
The text was updated successfully, but these errors were encountered: