Ciao Pigi, of course you know Bitcoin and Bitcoin Cash are two separate currencies, so if you send Bitcoin to your Bitcoin Cash address, or vice-versa, your wallet won't receive the transaction correctly.
I think that Kraken staff will need to manually sweep the funds from the incorrect receiving wallet, into the correct wallet.
Here's how: since you sent BTC to a BCH wallet, Kraken staff will have to export the BCH private keys from "your Kraken BCH wallet", and import them into "your Kraken BTC wallet" (recovering those BTC into your Kraken BTC wallet).
Even if the user has mistakenly sent the BTC to a BCH address, I'm interested on how the kraken support will act (no response, transfer funds by adding an increased fee, etc...)
The user in the italian board has published the transaction:
https://blockchain.info/tx/434f06efd0de5fa85447e2c4946e806aa719747217539890833f5cc45c9b223eThe transaction has 2 outputs, the second is still unspent, so i think that the blocked funds are currently here:
https://blockchain.info/it/address/14fYNe2SBiXxtG3xCq4dP1Jfhv49gihnuvKraken currently holds the related private key; I assume, by taking an additional fee, that is entirely possible for the technical support to recover the BTC.
This issue has been resolved by a client's ticket and the funds are not considered recoverable. Please note also that Kraken does not, as was suggested earlier, "have to export the BCH private keys from "your Kraken BCH wallet", and import them into "your Kraken BTC wallet" - there is no obligation on Kraken's part to do so (and indeed it may not be possible to do so). Even if it were possible (as has been covered earlier in this discussion), "we are unable to bear the cost or logistics required to rescue your funds" as has been indicated. The cost of covering every mistaken transaction is excessive in a realm where transactions are designed to be irreversible and security of the funds and the transactions is paramount.
In many cases, it is assumed that Kraken can give a client a private key (so as to either retrieve BCH mistakenly sent to an XBT address or to so that the client can retrieve XBT mistakenly sent to a BCH address). Please note that is not correct.
Furthermore, a summary of Kraken's security (though not a complete source of information about how client information is secured and protected, as Kraken goes well beyond what we can disclose) is here:
https://www.kraken.com/security/practicesPlease note also that clients were advised of Kraken's position on BCH before and after the fork:
1)
https://blog.kraken.com/post/1150/bitcoin-cash-and-a-critical-alert-for-bitcoin-margin-traders/ "Kraken will not be held responsible for any circumstances that result in the loss of BCH." (July 27, 2017)
2)
https://blog.kraken.com/post/1183/bitcoin-cash-and-a-critical-alert-for-margin-traders-part-2-2/ "Warning: only send BCH deposits to BCH deposit addresses when they become available (do NOT send any BCH to XBT deposit addresses)" August 1, 2017
3)
https://blog.kraken.com/post/1191/kraken-enables-bitcoin-cash-bch-deposits-and-withdrawals/ "Make sure you only deposit BCH to BCH-specific deposit addresses - Remember that Kraken has asset-specific deposit addresses and any funds sent to an address that isn’t specific to the asset will not be credited. Bitcoin Cash (BCH) deposits should only go to BCH-specific deposit addresses, and regular Bitcoin (XBT) deposits should only go to XBT-specific addresses. Any BCH sent to a XBT deposit address will not be credited and any XBT sent to a BCH deposit address will not be credited." - August 7, 2017
Please note also, that when a client is logged into Kraken, you have to check a box stating that you’ve reviewed the address and we’re not liable for your mistake.
Thank you for your comment regarding the issue of funds mistakenly sent to another asset address.