user130929: 
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).
Binance checked the transaction as completed and provided Txn id.
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.
Requested Binance chat support and They say taproot is not supported and Their system automatically transform/convert to a BC1Q (native segwit) address.
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)

user208: 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.

130929: <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>
 208: <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>
