<p>UPDATE: Crypto.com acknowledge the bug and refunded the full amount, at the time of writing this update the crypto.com team confirmed that they are working on fixing the bug and the defi wallet will hopefully be fixed ASAP.
Lesson learned; test every transaction even with wallet and address that you know are safe and already used in the past.</p>
<p>When scanning the QR code of a taproot address with the DefiWallet of crypto.com the app will correctly show the taproot address, not give any warning of unsupported format or other error message (screenshot from my second attempt to recreate the bug with different taproot address <a href="https://i.sstatic.net/yl95C.jpg" rel="nofollow noreferrer">https://i.sstatic.net/yl95C.jpg</a>), it will give a first confirmation with a reference transaction ID that the bitcoin transaction was broadcasted to the network with the correct recipient address, but in reality it will automatically convert the taproot address to a segwit address and send the bitcoin to this random generated address making the coin lost forever.</p>
<ol>
<li><p>taproot address generated from ledger - <a href="https://i.sstatic.net/KiwBE.jpg" rel="nofollow noreferrer">https://i.sstatic.net/KiwBE.jpg</a></p>
</li>
<li><p>first confirmation showing the correct taproot address scanned in the previous step with a reference transaction ID <a href="https://i.sstatic.net/MuVMa.jpg" rel="nofollow noreferrer">https://i.sstatic.net/MuVMa.jpg</a>  transaction ID: <a href="https://blockchair.com/bitcoin/transaction/c834fb3bc1e849b1e708b15728e55796adb7d44bf1b83b2b35dcaba4eb87b54b?from=crypto.com" rel="nofollow noreferrer">https://blockchair.com/bitcoin/transaction/c834fb3bc1e849b1e708b15728e55796adb7d44bf1b83b2b35dcaba4eb87b54b?from=crypto.com</a></p>
</li>
<li><p>After the transaction has been broadcasted to the network and it receives the first confirmation the defiwallet updates the home-screen showing the converted segwit address where it actually sent the bitcoin with the same transaction ID as reference, proving that the first confirmation screen is the result of a bug. <a href="https://i.sstatic.net/D4sLa.jpg" rel="nofollow noreferrer">https://i.sstatic.net/D4sLa.jpg</a> - <a href="https://i.sstatic.net/NreRT.jpg" rel="nofollow noreferrer">https://i.sstatic.net/NreRT.jpg</a></p>
</li>
<li><p>Video on my second attempt to recreate the bug and using a second bitcoin software wallet (trustwallet) to show that the problem is not my phone or some malicious software installed on the phone but the actual crypto.com defiwallet - <a href="https://streamable.com/91ksgg" rel="nofollow noreferrer">https://streamable.com/91ksgg</a></p>
</li>
<li><p>since my first chat with them the defiwallet has been under &quot;maintenance for bitcoin transaction&quot; - <a href="https://i.sstatic.net/osqWF.jpg" rel="nofollow noreferrer">https://i.sstatic.net/osqWF.jpg</a></p>
</li>
</ol>
<p>I understand something similar has already happened <a href="https://bitcoin.stackexchange.com/questions/111440/is-it-possible-to-convert-a-taproot-address-into-a-native-segwit-address">Is it possible to convert a taproot address into a native segwit address?</a> I have contacted the crypto.com support chat, I have sent them the same information and for the last 12 days they have been &quot;investigating&quot; the issue. I'm aware the coin are lost forever but the lack of response from crypto.com team is awful and I have no idea how many people have already lost and will lose their bitcoin because of crypto.com.<br />
my segwit address bc1q3exlju6gr6cwu3s3hxnjssjpxnmafnxtlms6cm</p>

CC BY-SA 4.0
2022-05-17T20:10:05.233Z
If what you say is true, I'm sorry for what happened to you, and I stand by my response in https://bitcoin.stackexchange.com/questions/111440/is-it-possible-to-convert-a-taproot-address-into-a-native-segwit-address: this is painfully incompetent, and you should demand your money back. That said, I don't think there is any new question here. It also sounds like they may be working on fixing it already.
Pieter Wuille
CC BY-SA 4.0
2022-05-17T20:24:20.927Z
Yes I believe the problem is the same experienced by the other guy, I have not found anything else apart from the previous post, I hope this post will help someone in the future if they happen to be in my same situation, this is more of a warning post than a question honestly, i've made peace with myself and think of the 0.21btc as a donation to the network.
froginspace
CC BY-SA 4.0
2022-05-17T20:30:02.770Z
@froginspace: You have good grounds in demanding that crypto.com reimburse you. That's what happened in the prior case with Binance. The error is solidly on the end of the service here.
Murch
CC BY-SA 4.0
2022-05-17T21:01:12.170Z
Note that we'll probably close this topic eventually either as a duplicate of the linked one, or because you didn't actually ask a question. But meanwhile I interpreted your post as a request for making some noise about this: https://twitter.com/murchandamus/status/1526668237529878528
Murch
CC BY-SA 4.0
2022-05-18T18:18:45.343Z
I am having a remotely similar dispute with an exchange, did you manage to solve this? Text me on twitter, maybe we can help each other: @pedr0fr
Pedro
CC BY-SA 4.0
2022-05-19T18:30:48.960Z
I’m voting to close this topic because it is a recount of events and not asking a question.
Murch
CC BY-SA 4.0
2022-05-22T01:38:25.507Z
@froginspace: Did you ever hear back from Crypto•com since?
Murch
<segregated-witness><address-generation><taproot><bech32-address>
crypto.com defiwallet sends bitcoin to random segwit address if a bitcoin taproot address is selected after confirmation of the correct address
froginspace
# crypto.com defiwallet sends bitcoin to random segwit address if a bitcoin taproot address is selected after confirmation of the correct address

(Asked by: username_0 on 2022-05-17)

UPDATE: Crypto.com acknowledge the bug and refunded the full amount, at the time of writing this update the crypto.com team confirmed that they are working on fixing the bug and the defi wallet will hopefully be fixed ASAP.
Lesson learned; test every transaction even with wallet and address that you know are safe and already used in the past.

When scanning the QR code of a taproot address with the DefiWallet of crypto.com the app will correctly show the taproot address, not give any warning of unsupported format or other error message (screenshot from my second attempt to recreate the bug with different taproot address <https://i.sstatic.net/yl95C.jpg>), it will give a first confirmation with a reference transaction ID that the bitcoin transaction was broadcasted to the network with the correct recipient address, but in reality it will automatically convert the taproot address to a segwit address and send the bitcoin to this random generated address making the coin lost forever.

1. taproot address generated from ledger - <https://i.sstatic.net/KiwBE.jpg>
2. first confirmation showing the correct taproot address scanned in the previous step with a reference transaction ID <https://i.sstatic.net/MuVMa.jpg> transaction ID: <https://blockchair.com/bitcoin/transaction/c834fb3bc1e849b1e708b15728e55796adb7d44bf1b83b2b35dcaba4eb87b54b?from=crypto.com>
3. After the transaction has been broadcasted to the network and it receives the first confirmation the defiwallet updates the home-screen showing the converted segwit address where it actually sent the bitcoin with the same transaction ID as reference, proving that the first confirmation screen is the result of a bug. <https://i.sstatic.net/D4sLa.jpg> - <https://i.sstatic.net/NreRT.jpg>
4. Video on my second attempt to recreate the bug and using a second bitcoin software wallet (trustwallet) to show that the problem is not my phone or some malicious software installed on the phone but the actual crypto.com defiwallet - <https://streamable.com/91ksgg>
5. since my first chat with them the defiwallet has been under "maintenance for bitcoin transaction" - <https://i.sstatic.net/osqWF.jpg>

I understand something similar has already happened [Is it possible to convert a taproot address into a native segwit address?](https://bitcoin.stackexchange.com/questions/111440/is-it-possible-to-convert-a-taproot-address-into-a-native-segwit-address) I have contacted the crypto.com support chat, I have sent them the same information and for the last 12 days they have been "investigating" the issue. I'm aware the coin are lost forever but the lack of response from crypto.com team is awful and I have no idea how many people have already lost and will lose their bitcoin because of crypto.com.  
my segwit address bc1q3exlju6gr6cwu3s3hxnjssjpxnmafnxtlms6cm

**Tags:** segregated-witness, address-generation, taproot, bech32-address

> **Comments:**
> **username_1**: If what you say is true, I'm sorry for what happened to you, and I stand by my response in https://bitcoin.stackexchange.com/questions/111440/is-it-possible-to-convert-a-taproot-address-into-a-native-segwit-address: this is painfully incompetent, and you should demand your money back. That said, I don't think there is any new question here. It also sounds like they may be working on fixing it already.  
> **username_0**: Yes I believe the problem is the same experienced by the other guy, I have not found anything else apart from the previous post, I hope this post will help someone in the future if they happen to be in my same situation, this is more of a warning post than a question honestly, i've made peace with myself and think of the 0.21btc as a donation to the network.  
> **username_2**: @username_0: You have good grounds in demanding that crypto.com reimburse you. That's what happened in the prior case with Binance. The error is solidly on the end of the service here.  
> **username_2**: Note that we'll probably close this topic eventually either as a duplicate of the linked one, or because you didn't actually ask a question. But meanwhile I interpreted your post as a request for making some noise about this: https://twitter.com/murchandamus/status/1526668237529878528  
> **username_3**: I am having a remotely similar dispute with an exchange, did you manage to solve this? Text me on twitter, maybe we can help each other: @pedr0fr  
> **username_2**: I’m voting to close this topic because it is a recount of events and not asking a question.  
> **username_2**: @username_0: Did you ever hear back from Crypto•com since?  

---

## 0 answers

