# Why do I need small amounts of Bitcoin to do things in Freewallet?

<mark style="color:yellow;">Counterparty builds directly on top of the Bitcoin network, and every Counterparty transaction is a Bitcoin transaction as well.</mark>&#x20;

This means that <mark style="color:red;">Counterparty transactions are the same as Bitcoin transactions</mark>, with some information attached through the OP\_RETURN function.\
\
Adam Krellenstein, co-founder of Counterparty, wrote about this functionality and labelled Counterparty as a 'metaprotocol' on top of Bitcoin in the [Counterparty Whitepaper](https://krellenstein.com/adam/get/counterparty-whitepaper_2024-03-29.pdf).

<figure><img src="/files/CymR8nBs25x7T24Ku8Dd" alt=""><figcaption><p>From: "Counterparty An Extension to Bitcoin by State-Machine Replication"</p></figcaption></figure>

Because of this, <mark style="color:yellow;">Counterparty transactions using Freewallet</mark> <mark style="color:yellow;"></mark>*<mark style="color:yellow;">**MUST**</mark>* <mark style="color:yellow;"></mark><mark style="color:yellow;">pay a small BTC fee to the Bitcoin miners for each Counterparty transaction</mark>. Beyond being a sign of commitment to the health of the Bitcoin network, this allows Counterparty transactions to be given a high priority and be confirmed quickly while maintaining the same security that Bitcoin has.

<mark style="color:yellow;">Every Counterparty transaction is a bitcoin transaction with more information encoded into the OP\_RETURN function</mark>. Many internal Counterparty transactions such as asset creation, issuance change, token locking etc. are transactions “sent to yourself” with this Counterparty information on layered on top of it.

<figure><img src="/files/xE4ERHBTfgCLSlWkieNB" alt=""><figcaption><p>A Counterparty transaction with OP_RETURN data attached (representing a named token creation transaction)</p></figcaption></figure>

<mark style="color:yellow;">The detailed OP\_RETURN data can be seen on Counterparty block explorers, while all BTC transactions can be viewed on a BTC block explorer.</mark> \
\
Freewallet specifically shows the OP\_RETURN data from the [tokenscan.io](https://tokenscan.io/) Counterparty block explorer. \
\
On xchain, all Bitcoin addresses are linked to the BTC data on the Bitcoin network.

<figure><img src="/files/HhtGxAM0Qrb6n06cGiMJ" alt=""><figcaption><p>The same transaction as above, but viewed on tokenscan.io</p></figcaption></figure>

<mark style="color:green;">If you are looking to save bitcoin it is recommended to use a Segwit addresses instead of Legacy if you plan to do many transactions.</mark>&#x20;

To learn more about viewing accessing your different types of addresses in Freewallet, check out: [Viewing, Creating and Importing Addresses](/freewallet.io-user-manual/freewallet-functions/viewing-creating-and-importing-addresses.md).

If you are looking to get a function done quickly it is needed to use the recommended high fee (or even higher) for the Bitcoin network to confirm it quickly. In the event you are not sure what BTC fee to use, please reference the [What BTC fee should I use?](/freewallet.io-user-manual/getting-started/what-btc-fee-should-i-use.md) section of the user manual.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://davestaxcp.gitbook.io/freewallet.io-user-manual/getting-started/why-do-i-need-small-amounts-of-bitcoin-to-do-things-in-freewallet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.