Quote from: mwmanoh on January 28, 2018, 01:35:52 AM

Kraken does not care the issue is between them and Bithumb. Here is what their support said:

"Kieren (Kraken Support)
Jan 25, 23:40 PST

Hi,

As for why we don't post a bulletin that would be unprofessional since the issue at Bithumb would be temporary and we don't block clients from having free will on where to send their funds. It is always highly suggested clients research the exchange they send funds to before they send them.

Support documents: https://support.kraken.com/hc/en-us

Website Status: https://status.kraken.com/

Sincerely,
Kieren
Client Engagement Specialist"

Kracken and Bithumb probably split the stolen XRP. They both are crooks.

It's not fully kraken fault, all withdraw from kraken to home wallet and ALL another exchanges exept bithumb arrive without any problem. I guess problem in way how bithumb handle with transactions.

Single diffrence between xrp transactions sent from kraken and from another exchange is flag, kraken doas not add flag, rest exchange doas.

bittrex for example add flag:
This transaction arrived without problem:
STATUS:
This transaction was successful, and validated in ledger ... on December 30
DESCRIPTION:
This is a Payment transaction.
The payment is from rPVMhWBsfF9iMXYj3aAzJVkPDTFNSyWdKy to rsG1sNifXJxGS2nDQ9zHyoe1S5APrtwpjV.
The payment has a destination tag: ....
It was instructed to deliver .... XRP.
The actual amount delivered was .... XRP
The transaction's sequence number is ....
MEMOS:
The transaction has no memos.
TRANSACTION COST:
Sending this transaction consumed 0.000012 XRP.
FLAGS:
The transaction specified the following flags:
tfFullyCanonicalSig
AFFECTED LEDGER NODES:
It affected 2 nodes in the ledger:
MODIFIED NODES:

kraken doas not add flag:
this transaction still didn't arrive
STATUS:
This transaction was successful, and validated in ledger ... on January 4, 2018 .
DESCRIPTION:
This is a Payment transaction.
The payment is from rLHzPsX6oXkzU2qL12kHCH8G8cnZv1rBJh to rsG1sNifXJxGS2nDQ9zHyoe1S5APrtwpjV.
The payment has a destination tag: ......
It was instructed to deliver .... XRP.
The actual amount delivered was .... XRP
The transaction's sequence number is .....
MEMOS:
The transaction has no memos.
TRANSACTION COST:
Sending this transaction consumed 0.000031 XRP.
AFFECTED LEDGER NODES:
It affected 2 nodes in the ledger:
MODIFIED NODES:
.......

No clue what for bithumb may check this flag and think that transaction is invalid. It is my single assumption, since support doas not tell anything,
i realy hope that finnaly someone will deposite our money manualy.
But it should be bithumb support, since kraken obviously can't do anything with already sent and confirmed transactinos.