Hello,
Due to the recent network load, I decided to switch the order time from 24 hours to 72 hours. A lot of users wrote over the email about their transactions not being processed, as they arrived after 24 hours from order creation. All the reported cases were resolved either thanks to the LoG or by checking whether the deposit address belonged to MCM and doing the analysis described above.

To prevent this from happening, on 05.02.2021 13:53 UTC, I decided to update order validity time from 24 hours to 72 hours, 3 days. Answering multiple emails about transactions lost due to order termination was not something I have time to do. The change was not yet propagated to the frontend, as I was not sure whether it is a temporary or permanent solution. The LoG is generated independently of the frontend, this is why it was available for full 72 hours instead of the 24 hours the frontend page was available for.

After reading the TryNinja post, not having much time at the moment, I decided to shut down the backend immediately in case something serious have happened. The backend was effectively offline from 22.02.2021 06:33 UTC to 23.02.2021 14:05 UTC, when I made sure no leaks are present.

No security was compromised. Each order is assigned unique id, it consists of 18 alpha-numeric lowercase characters, this gives us 36 ^ 18 possible combinations, roughly 1 and 28 zeros so you can imagine the number. This is enormous value, even when compensating for multiple orders being available at any time and considering finding the order id of single of them as a success, the chances of guessing and testing the order id is almost nonexistent.

The LoG generated by TryNinja is valid and confirms the transaction was successful.

As for @Cowboy310 I will post a response in his thread directly.