Quote from: Kraken-Septimus on January 09, 2018, 09:10:44 PM

Quote from: Ilanoh on January 09, 2018, 04:53:08 PM

Hello, how do you explain that this issue happen only when sending from kraken,
Can you as the owner of the wallet make a statement against this practice, if it is bithumb that is at fault, at ripple management? Since it is centralized maybe they can help us, and you by the same occasion.

Hi Ilanoh. It's hard to say what happened in this instance. When we're on the receiving end of a transaction, what's typically happened is a client has either omitted or made an error on the destination tag. Each exchange would have a different recovery process for these, so that's why we suggest contacting their support.

I do think this is worth at least raising the issue via some sort of ticket or whatever process you have with your developers so they can look into it. Looking at my Kraken => Bithumb TX vs. my offline wallet => Bithumb TX, the only difference appears to be in the different flags, and the last ledger sequence.

For reference, here's my two transactions, where the first is the missing one from Kraken and the second is the successful one from my offline wallet.

https://xrpcharts.ripple.com/#/transactions/4C6DBD6B514ECC1E21E8ECF5B0E44A8B587729931D8F7D1DCC338D59B88BDE5F
https://xrpcharts.ripple.com/#/transactions/4C489B9055D7594533B7F9FF16A3985DEEC65B5A8E2D43858FB775BDA1A2C9CA