# Storage Fees improvements ( and few random ideas on the way )

**URL:** <https://forum.flow.com/t/storage-fees-improvements-and-few-random-ideas-on-the-way/5104>\
**Category:** Product & Ideas\
**Created:** [August 14, 2023, 11:59am UTC](https://forum.flow.com/t/storage-fees-improvements-and-few-random-ideas-on-the-way/5104 "2023-08-14T11:59:35Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![bluesign](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/bluesign/32/1359_2.png) [@bluesign](https://forum.flow.com/u/bluesign)\
**Post date:** [August 17, 2023, 7:54pm UTC](https://forum.flow.com/t/storage-fees-improvements-and-few-random-ideas-on-the-way/5104/11 "2023-08-17T19:54:53Z")

</div>

> [@TheOneSock](#):
>
> If storage is 1FLOW per MB  
> I can create a resource with a byte array that is 100MB long.

We charge writes ( not for space ) if you paid 100 FLOW to 100 MB then gave it to me, I write 100MB another data, I pay 100 FLOW too. And resource has 200 FLOW now ( in feeVault )

Actually first idea was to put it into tx fees directly ( but that does not allow redeem )

If somehow resource namespace is also implemented ( little off topic ) then writes will be minimal ( when resource doesn’t mutate, just owner change for example ), and fees will be minimal too

---

_[View the full topic](https://forum.flow.com/t/storage-fees-improvements-and-few-random-ideas-on-the-way/5104)._