u/Vivid_Wolverine2469

Reverse Onus

In cases of a true fiduciary breach, the law applies the principle of a "reverse onus"

This means that the burden falls on the liquidators to prove that the hack did not cause the loss, rather than GNY having to prove the opposite

The liquidators are unable to provide this proof because Cryptopia itself caused the relevant information gap due to its failure to monitor and record system access. The legal rule clearly states that a wrongdoer who makes proof difficult or impossible must bear the risk of adverse factual findings.

Some people got test transaction last few days

For usdt, ada, tron

The liquidators did not just make a single error; they deliberately destroyed two vital layers of evidence.

They decommissioned and dismantled the Redis server, which acted as the live operational memory of customer interactions, and they also mutated the SQL database, which represents the persistent storage of balances, through an arbitrary "haircut". This dual destruction prevents any ability to conduct a technical audit. Legally and technically, they cannot reject your contemporaneous records on the pretext that they are unable to verify them, when they are the ones who destroyed the primary audit trails.

And support said its all lies lol , one of them threatens the community ( JAWA ) that he will delay the distribution for some people

This is how corruption works it seems he is paying from his pocket

Unfortunately we've mainly been focused on the distributions that have been happening recently, so there are no updates at the moment. Hopefully we'll hear something after these distributions are all done and dusted - we still have TRX, ADA and USDT to go, and then smaller 'follow up' distributions for any users that had to be removed at the last minute. 
** **
I would say probably about a month or so and we'll be able to re-focus on future distributions. Again, thanks a lot for your continued patience with this process,I realise that it must be very frustrating for you .

Notice : every month they say next month with unknown, misleading information Procrastination, Wolf and the turnover of support, once because of the system, and once because of the current distribution and their preoccupation, where is the fulfilment of the covenant and commitment to the provisions of the court since few years ago

Dear Cryptopia Account Holder,
We are writing to inform you that we intend to make a distribution to your submitted wallet address(es) in the upcoming week. This distribution will cover Cardano (ADA), Tron (TRX), and Tether (USDT).
If you missed the distribution of Bitcoin (BTC), Dogecoin (DOGE), and Litecoin (LTC), we expect to distribute any outstanding balances up to 100% of your accepted balance shortly thereafter.
According to our records, your wallet address(es) have previously received a distribution from the Cryptopia liquidation. As there has been no change to your registered wallet details, a test transaction will not be offered for this distribution.

Mr. Ruscoe, do you acknowledge that on May 24, 2019, you declared under oath to the United States Bankruptcy Court that all Bitcoin was pooled in a single 'master wallet' and could not be separated?" 

Do you also acknowledge that merely five days later, on May 29, 2019, you utilized 27 automated accounts to extract exactly 344 Bitcoin from that exact same commingled wallet, classifying it as 'Company funds'?

If the SQL database was accurate enough for you to calculate, isolate, and extract 344 Bitcoin for your own company, how can you stand before this Court today and claim that the exact same database is suddenly incapable of identifying community cryptographically verified balances?

Do you admit that your administration applied a one-way 'hashing' algorithm to the API keys, which programmatically destroyed the database's 'search index' and mapping keys?"

How do you legally justify closing the Plaintiff's support ticket and rejecting his claim for a 'lack of evidence,' when you are the ones who destroyed the automated validation system, and you personally ordered him to conceal that exact evidence? Is this not deliberate spoliation of evidence?

Since you have formally admitted that the internal audit logs justifying these deductions 'cannot be located,' wouldn't you agree as an auditor that altering final balances without transaction records constitutes a 'ledger mutation,' rendering your current database technically corrupt and legally invalid?"

If you failed so catastrophically to protect the master vaults from your own employee for over a year—and only discovered the theft because a customer notified you—by what technical logic do you now reject the Plaintiffs pristine receipts under the guise of your collapsed 'security protocols'?

Mr. David ian Ruscoe all of you will be reported in usa justice

Beside that sworn in your affidavit for restricted countries and your system should be ready for years

Stay tuned

The forensic evidence proves that the security issues were not caused by the users, but by the administration's own operational failures:

The criminal judgment R v Glaser proved that the administration failed to secure the custody layer, allowing an internal employee to steal 13.179 BTC from deposit wallets for over a year without the administration noticing. 

The administration intentionally modified the mapping keys (API keys) via a one-way mathematical "hashing" algorithm, which destroyed the database search index. 

This destruction is the direct technical cause of the administration's current inability to locate user records, which they now use as a pretext to deny claims

It is critical for all users to understand that Cryptopia did not operate as a decentralized, on-chain ledger platform.

The exchange operated as a centralized, off-chain SQL database

User balances did not represent possession of blockchain private keys; instead, they represented numeric entries on an internal SQL general ledger

The Private API Key served as the machine-to-machine command layer for the exchange, authenticating the user's specific account pathway on that SQL ledger