---
<center>![Milestones.jpg](https://ipfs.busy.org/ipfs/QmX489wFJHyoXKxiBCe2uZsq2CWuoJqeFRuoSrraP2SwYf)</center>

---

### Version 1.0.7 - One Open Item Remaining 
</br>
As of this writing, the next release of EOS only two open items and nine closed items.  Digging into the closed items, most are simple bug fixes/enhancements; one of the items really caught my eye though:-

* Round up fee when selling RAM

The RAM market for EOS definitely​ an interesting​ beast as the price is not set by what someone is willing to pay, like the token exchanges, it is set automatically by the system based on availability/demand​.  I go into more detail on RAM trading [here](https://steemit.com/bitcoin/@aclarkuk82/eos-ram-trading), but note that the system charges a 1% fee for both buying and selling RAM.

<center>What is the fee for?</center>
---

> Now that there is a RAM market, speculators may want to trade RAM price-volatility for profit. The EOS.IO system contract makes RAM non-transferrable and charges a 1% fee on trades. The result of this fee is to offset the natural inflation of tokens by taking them out of the market. These tokens are removed from circulation and are effectively destroyed.

---

I am expecting a lot of noise from the EOS naysayers shouting that this is an unfair change if this item gets out to the general population​, so I thought​ I would take some time to explain what it means an why it is not an issue.

As the title of the item states, Block One is​ changing the code to round up the fee when *selling* RAM.  Well, when we dig into the change details, we see that the code has been amended​ from a formula of *quant / 200* changed to *(quant + 199) / 200*, ( line 192 in delegate_bandwidth.cpp)

<center>*Old Code* </center>
<center>auto fee = tokens_out.amount / 200;</center>

<center>*New Code*</center> 
<center>auto fee = ( fee.amount + 199 ) / 200;</center>


</br>
The net result of this change seems to be that the lower amount of EOS you spend, (1 EOS minimum), the higher the fee.  Here is a table​ showing the fees for a few different amounts of EOS. 

---
<center>*Source shuke0327 on Github*</center>
| Quantity (EOS)  | RAM fee (EOS) |  RAM fee Rate  |
| ------------- |-------------| -----|
| 1     | 1 | 100% |
|10|1.045|10.45%|
|100|1.495|1.4950%|

---

### Summary
</br>
Conclusion, a complete non-issue as the buy RAM method​ already has the formula *(quant + 199) / 200* applied (line 111 in delegate_bandwidth.cpp), so the team is​ simply keeping fees the same across the two functions.  This is the beauty of open source, you are able to verify all the details needed to satisfy your curiosity. 

The question still remains is this the correct formula to use.  There is an ongoing discussion with the Github​ repo about this, a question was posted by,reply is awaiting.