# High Counterwallet TX Fee

**URL:** <https://forums.counterparty.io/t/high-counterwallet-tx-fee/2448>\
**Category:** Development\
**Created:** [November 4, 2016, 12:55pm UTC](https://forums.counterparty.io/t/high-counterwallet-tx-fee/2448 "2016-11-04T12:55:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\
**Post date:** [November 7, 2016, 12:54pm UTC](https://forums.counterparty.io/t/high-counterwallet-tx-fee/2448/3 "2016-11-07T12:54:41Z")

</div>

By the way I think it’d be good to implement the recommended fee in CounterTools (the simple method `"Target confirmation time: 10|30|60 minutes"`) and then submit a PR to CW.

Reference: Counterwallet’s fee setting:

> <https://github.com/CounterpartyXCP/counterwallet/blob/develop/src/js/consts.js#L52>

And for Counterparty Server API:

> <https://github.com/CounterpartyXCP/counterparty-lib/blob/master/counterpartylib/lib/transaction.py#L471>

Defaults in Counterparty Server:

> <https://github.com/CounterpartyXCP/counterparty-lib/blob/master/counterpartylib/lib/config.py#L87>

@jdogresorg in #L88 of this last file, you can set your target estimate to 6 blocks if you want.  
Today when I was writing that [Bash script](https://forums.counterparty.io/t/using-web-api-to-fetch-recommended-transaction-fee/2462) I realized that 10 and 30 mins fees were exactly the same (based on several tests I did with the API)

---

_[View the full topic](https://forums.counterparty.io/t/high-counterwallet-tx-fee/2448)._
