# My transaction is too low of an "Effective Fee Rate"

<mark style="color:yellow;">This issue happens specifically with longform asset descriptions when minting a token, but also has been seen when doing very longform Broadcasts using Counterparty.</mark>

This issue has been discussed at length in the [Freewallet Telegram](https://t.me/freewallet_io) chat and has two open issues ([Issue#190](https://github.com/jdogresorg/freewallet-desktop/issues/190) and [Issue#197](https://github.com/jdogresorg/freewallet-desktop/issues/197)) in the Freewallet Desktop Github Issues section.

The issue has to do with mempool.space specifically showing you the correct Fee rate you chose in Freewallet when looking up your minting or Broadcast transaction, but the "Effective Fee Rate" shows as something much less.

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2FCKATYeffymEPNDpgxa9t%2Feffectivefee2.png?alt=media&#x26;token=ebf4a889-cd92-4ac0-933b-96e92a331560" alt=""><figcaption></figcaption></figure>

<mark style="color:red;">This will cause your transaction to most likely be stuck with too low of a fee</mark>.

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2F6kh9xDT2fmgvZplLl7Ry%2Feffectivefee1.png?alt=media&#x26;token=0a52816b-b521-4006-8daf-726ae898d3a8" alt=""><figcaption><p>Setting the UTXO Usage settings to Only Confirmed when broadcasting or minting descriptions in Freewallet</p></figcaption></figure>

One fix was introduced by Jdog by adding a "UTXO Usage" button in the settings and make sure it is set to "Only Confirmed" when adding a description to a token or including a significant amount of text in a Counterparty Broadcast.

Another fix, that is most commonly used by the community is:&#x20;

* The next time you attempt to broadcast a significant amount of data in a Broadcast or add a longform IPFS or Arweave description, <mark style="color:red;">simply use three times the recommended High fee setting</mark> (yes it will be expensive).

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2FgWUSjsTzzjkbyLylHULz%2Feffectivefee4.png?alt=media&#x26;token=d47fdb03-2d94-4e34-a74c-98596640f160" alt=""><figcaption><p>A sample recommendation of the High fee setting when minting a token shown in Red Boxes</p></figcaption></figure>

Above is the recommended setting for a High fee at this time, which happens to be 0.00011264 BTC at 44.0 sat/vb.

<figure><img src="https://3285406617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHOAdveIkUtULHe7q3v2%2Fuploads%2FdXeOJNro6DM1l4Xy5xu5%2Feffectivefee5.png?alt=media&#x26;token=20d0f4ad-5253-425e-b051-3d181219c8fd" alt=""><figcaption><p>Custom fee which is 3 times the previous estimate and shown in the Blue Boxes</p></figcaption></figure>

When minting a token with a long description, or a creating a longform Broadcast, use three times what Freewallet recommends instead. This will now show as a Custom fee, and you can simply input 0.00034 into the Fee entry manually.

If you are reading this, you probably have a transaction that is too low of a fee in the mempool already, so it is best to reference the steps explained in [Help! I used too small of a fee and my transactions is not confirming!](https://davestaxcp.gitbook.io/freewallet.io-user-manual/troubleshooting-issues/help-i-used-too-small-of-a-fee-and-my-transaction-is-not-confirming) section of this 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/troubleshooting-issues/my-transaction-is-too-low-of-an-effective-fee-rate.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.