<p>I am afraid the sent coins are irrevocably burned.</p>
<p>The reason is that P2TR addresses encode a (tweaked) public key, while P2WSH addresses encode a script hash. If someone would take a P2TR address so that it is interpreted as a P2WSH address with the same payload, you'd need find a script that hashes to the public key in the P2TR address. This is completely infeasible; if this were possible, SHA256 would be spectacularly broken.</p>
<p>This is <strong>not your fault</strong>, and you should demand your bitcoin back. P2TR addresses (like all addresses) have a checksum, and this checksum algorithm was even changed for the introduction of taproot. The fact that they accepted this address <em>at all</em> (even ignoring the misinterpretation as P2WSH) shows extreme incompetence on the side of the sender.</p>

CC BY-SA 4.0
2021-12-26T03:44:09.163Z
Thanks. I have the same opinion. But I'm a regular guy vs a huge company that doesn't even seen to have a headquarters or address to be able to take this to court.
Mario
CC BY-SA 4.0
2021-12-26T03:46:03.963Z
Chat support answers: https://ibb.co/tZq4txt https://ibb.co/YQMvd4y and transaction screenshot: https://ibb.co/Sfv36hS ( 3eeeb9f0f27abeddbd64c1a696c4a02107759d5853877b327cb783a68ee4559a )
Mario
CC BY-SA 4.0
2021-12-26T03:49:36.410Z
Absolutely agree that you should be fully reimbursed for their error. Websites should *never* modify the address they've been given from that which you provided.
meshcollider
CC BY-SA 4.0
2021-12-26T03:53:24.477Z
I've been trying for days to get some big influencer or something to retweet me to get CZ (Binance CEO) attention but nobody cares. I'll wait for the last shot and if they keep trying to shut me down I'll have to try and take this to court.
Mario
CC BY-SA 4.0
2021-12-26T16:35:41.307Z
I hope this will help get it a bit more attention: https://twitter.com/murchandamus/status/1475120106695008260
Murch
CC BY-SA 4.0
2021-12-26T16:44:31.547Z
@Murch thanks man I'll be forever grateful for that no matter how this issue ends.
Mario
CC BY-SA 4.0
2022-12-10T19:51:34.007Z
Note: the amount was eventually [refunded by Binance](https://twitter.com/murchandamus/status/1475821143219134469).
Jonathan Cross
CC BY-SA 4.0
2021-12-26T03:29:46.480Z
2021-12-26T19:57:41.257Z
2021-12-26T19:57:41.257Z
Pieter Wuille
<ol>
<li>A few days ago I requested a BTC withdrawal on Binance, I used a bc1p address and the request went through as usual without any issue or warning. (my first time using taproot address).</li>
<li>Binance checked the transaction as completed and provided Txn id.</li>
<li>I noticed the funds didn't arrive and went to check the Txn id and noticed my address wasn't listed as beneficiary but a completely different address had received the exact same amount as I requested.</li>
<li>Requested Binance chat support and They say taproot is not supported and Their system automatically transform/convert to a BC1Q (native segwit) address.</li>
<li>Since then Binance admit to have fixed withdrawal to not allow taproot addresses to be used.</li>
</ol>
<p>Of course all this is something beyond usual and They're trying to convince me it's my fault and I keep on fighting for They to assume Their responsibility.</p>
<p>Question 1: is it actually possible for them to convert a BC1P public address into a BC1Q address without having access to my private key or xpub? How?</p>
<p>Question 2: is it possible for me to recover the funds they sent to that address? How? (I'm currently waiting on Ledger support to see if They can help)</p>

CC BY-SA 4.0
2021-12-26T03:25:00.567Z
Well... the P2WPKH is bech encoding of a 20 byte hash.  P2WSH is bech encoding of a 32 byte hash.  Where as P2TR is encoding of a 32 byte key.  Are you sure your asking about a P2WPKH?  Because I can easily see how to convert a P2TR bech32 encoding to a P2WSH encoding since the are both essentially encoding 32 bytes.  But their meanings are so fundamentally different that I don't think it makes sense to do it.
Dan
CC BY-SA 4.0
2021-12-26T03:27:52.517Z
They're presumably misinterpreting it as v0 P2WSH address, which also has a 32 byte payload.
Pieter Wuille
CC BY-SA 4.0
2021-12-26T03:49:47.493Z
@PieterWuille here's a screenshot of the transaction and the Txn id.  https://ibb.co/Sfv36hS ( 3eeeb9f0f27abeddbd64c1a696c4a02107759d5853877b327cb783a68ee4559a ) I'm not into technical stuff. They simply said They've converted the bc1p address I provided to a bc1q address. I don't see the funds anywhere on my wallet and tried generating new address and balance is 0. Chat support answers: ibb.co/tZq4txt ibb.co/YQMvd4y
Mario
CC BY-SA 4.0
2021-12-26T03:50:09.780Z
@Dan here's a screenshot of the transaction and the Txn id.  https://ibb.co/Sfv36hS ( 3eeeb9f0f27abeddbd64c1a696c4a02107759d5853877b327cb783a68ee4559a ) I'm not into technical stuff. They simply said They've converted the bc1p address I provided to a bc1q address. I don't see the funds anywhere on my wallet and tried generating new address and balance is 0. Chat support answers: ibb.co/tZq4txt ibb.co/YQMvd4y
Mario
<address-generation><taproot><bech32-address><binance>
Is it possible to convert a taproot address into a native segwit address?
Mario
# Is it possible to convert a taproot address into a native segwit address?

(Asked by: username_0 on 2021-12-26)

1. A few days ago I requested a BTC withdrawal on Binance, I used a bc1p address and the request went through as usual without any issue or warning. (my first time using taproot address).
2. Binance checked the transaction as completed and provided Txn id.
3. I noticed the funds didn't arrive and went to check the Txn id and noticed my address wasn't listed as beneficiary but a completely different address had received the exact same amount as I requested.
4. Requested Binance chat support and They say taproot is not supported and Their system automatically transform/convert to a BC1Q (native segwit) address.
5. Since then Binance admit to have fixed withdrawal to not allow taproot addresses to be used.

Of course all this is something beyond usual and They're trying to convince me it's my fault and I keep on fighting for They to assume Their responsibility.

Question 1: is it actually possible for them to convert a BC1P public address into a BC1Q address without having access to my private key or xpub? How?

Question 2: is it possible for me to recover the funds they sent to that address? How? (I'm currently waiting on Ledger support to see if They can help)

**Tags:** address-generation, taproot, bech32-address, binance

> **Comments:**
> **username_1**: Well... the P2WPKH is bech encoding of a 20 byte hash.  P2WSH is bech encoding of a 32 byte hash.  Where as P2TR is encoding of a 32 byte key.  Are you sure your asking about a P2WPKH?  Because I can easily see how to convert a P2TR bech32 encoding to a P2WSH encoding since the are both essentially encoding 32 bytes.  But their meanings are so fundamentally different that I don't think it makes sense to do it.  
> **username_2**: They're presumably misinterpreting it as v0 P2WSH address, which also has a 32 byte payload.  
> **username_0**: @username_2 here's a screenshot of the transaction and the Txn id.  https://ibb.co/Sfv36hS ( 3eeeb9f0f27abeddbd64c1a696c4a02107759d5853877b327cb783a68ee4559a ) I'm not into technical stuff. They simply said They've converted the bc1p address I provided to a bc1q address. I don't see the funds anywhere on my wallet and tried generating new address and balance is 0. Chat support answers: ibb.co/tZq4txt ibb.co/YQMvd4y  
> **username_0**: @username_1 here's a screenshot of the transaction and the Txn id.  https://ibb.co/Sfv36hS ( 3eeeb9f0f27abeddbd64c1a696c4a02107759d5853877b327cb783a68ee4559a ) I'm not into technical stuff. They simply said They've converted the bc1p address I provided to a bc1q address. I don't see the funds anywhere on my wallet and tried generating new address and balance is 0. Chat support answers: ibb.co/tZq4txt ibb.co/YQMvd4y  

---

## 1 answers

### Answer by username_2 on 2021-12-26. Score: 32 | Accepted answer

I am afraid the sent coins are irrevocably burned.

The reason is that P2TR addresses encode a (tweaked) public key, while P2WSH addresses encode a script hash. If someone would take a P2TR address so that it is interpreted as a P2WSH address with the same payload, you'd need find a script that hashes to the public key in the P2TR address. This is completely infeasible; if this were possible, SHA256 would be spectacularly broken.

This is **not your fault**, and you should demand your bitcoin back. P2TR addresses (like all addresses) have a checksum, and this checksum algorithm was even changed for the introduction of taproot. The fact that they accepted this address *at all* (even ignoring the misinterpretation as P2WSH) shows extreme incompetence on the side of the sender.

> **Comments:**
> **username_0**: Thanks. I have the same opinion. But I'm a regular guy vs a huge company that doesn't even seen to have a headquarters or address to be able to take this to court.  
> **username_0**: Chat support answers: https://ibb.co/tZq4txt https://ibb.co/YQMvd4y and transaction screenshot: https://ibb.co/Sfv36hS ( 3eeeb9f0f27abeddbd64c1a696c4a02107759d5853877b327cb783a68ee4559a )  
> **username_3**: Absolutely agree that you should be fully reimbursed for their error. Websites should *never* modify the address they've been given from that which you provided.  
> **username_0**: I've been trying for days to get some big influencer or something to retweet me to get CZ (Binance CEO) attention but nobody cares. I'll wait for the last shot and if they keep trying to shut me down I'll have to try and take this to court.  
> **username_4**: I hope this will help get it a bit more attention: https://twitter.com/murchandamus/status/1475120106695008260  
> **username_0**: @username_4 thanks man I'll be forever grateful for that no matter how this issue ends.  
> **username_5**: Note: the amount was eventually [refunded by Binance](https://twitter.com/murchandamus/status/1475821143219134469).  

---

