# Token Issuance: Relationship between description length and BTC required

**URL:** <https://forums.counterparty.io/t/token-issuance-relationship-between-description-length-and-btc-required/3318>\
**Category:** Support\
**Created:** [June 29, 2017, 9:23pm UTC](https://forums.counterparty.io/t/token-issuance-relationship-between-description-length-and-btc-required/3318 "2017-06-29T21:23:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![JamesC](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/jamesc/32/745_2.png) [@JamesC](https://forums.counterparty.io/u/JamesC)\
**Post date:** [June 29, 2017, 9:23pm UTC](https://forums.counterparty.io/t/token-issuance-relationship-between-description-length-and-btc-required/3318/1 "2017-06-29T21:23:29Z")

</div>

Dear Community,  
I am new to counterparty, but am interested in better understanding how the BTC transaction fees relate to the length of the description in the asset being issued.

Is there a maximum number of bytes that can be stored in an amount of BTC? So if the description exceeds a certain byte amount, more unspent BTC transactions are needed to store the data?

I have tried issued various test assets with varying description lengths on the testnet, but am not sure of the true relationship to the underlying BTC op-return data and required BTC balance.

A big thank you in advance for any tips!