There are two methods to prove a transaction:

- The Letter of Guarantee. A digitally signed proof of your transaction, which indisputably guarantees the funds sent to the deposit address are going to be transferred to specified destinations, according to the settings. Even if MCM made the mistake and lost the PKs to the deposit address, it would be forced to process the order as per LoG. It is a guarantee and a very powerful tool in user's hands.

- The address belonging to MCM. It is possible for me to confirm whether the address belongs to MCM or not. In the past there were cases when the order was not processed properly and after confirming the deposit address is owned by MCM, as well as the ownership of input address used for the transaction, I was able to return coins safely.

In this case, the address does not belong to MCM, nor the user is able to present valid Letter of Guarantee. They claim the "server crashed" when trying to download LoG, yet they have "verified the PGP" on the "secure incognito mode of google chrome" and still proceeded to send substantial sum of money nonetheless. This is at the very least very strange.

There are several attacks on MCM users I am aware of, it is possible the victim fell for one of them:
- fake websites using MCM look
- tor exit nodes changing deposit addresses and the address in LoG when accessing clearnet address through HTTP
- browser addons changing the deposit address on real website
- compute programs changing the deposit address when in clipboard

It is also possible it is the malicious actor who wants to harm MCM reputation. This concerns me especially since we just had another case when the user claimed the funds were transferred to different address. Very shortly after my explanation on how it is possible to find the outgoing transaction from MCM using the disclosed information and knowing that addresses belong to MCM, they posted the txid without demonstrating any prior technical knowledge required for such blockchain analysis. Perhaps the attacker wanted to double down using the FUD created by TryNinja post, which debunked their first attempt.