> For the complete documentation index, see [llms.txt](https://davestaxcp.gitbook.io/freewallet.io-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://davestaxcp.gitbook.io/freewallet.io-user-manual/troubleshooting-issues/i-sent-dispensed-an-xcp-asset-to-a-wrapped-segwit-address-address-beginning-with-3.md).

# I sent/dispensed an XCP asset to a Wrapped Segwit Address (address beginning with "3")

At the moment on a protocol level, Wrapped Segwit Addresses (or addresses beginning with "3") are supported by Counterparty <mark style="color:yellow;">but Freewallet does not support signing those transactions at this time.</mark>

Another developer by the name of JP Janssen (JPJA) [has developed an OP\_Return builder for Wrapped Segwit addresses](https://jpja.github.io/Electrum-Counterparty/), but at the moment this is experimental. You can read more about this open-source process on the [Electrum-Counterparty Github page](https://github.com/Jpja/Electrum-Counterparty).

JP has also even developed a process to [Reverse Engineer Counterparty transactions](https://jpjanssen.com/how-to-reverse-engineer-counterparty-txs/).

It is recommended to [get into contact with JPJA](https://twitter.com/jp_janssen) to better help experiment with these advanced technical processes.

If you find yourself in a situation that an XCP asset has been sent to a Wrapped Segwit Address and you are looking to access this token, <mark style="color:red;">it would be best at this time to wait until a further release of Freewallet that supports Wrapped Segwit Addresses so they can be used for all Counterparty functions.</mark>