create account

A Proposed Solution to EOS RAM Allocation by bancor-network

View this thread on: hive.blogpeakd.comecency.com
· @bancor-network · (edited)
$19.13
A Proposed Solution to EOS RAM Allocation
<center>![eos_bancor.png](https://cdn.steemitimages.com/DQmYGEJaGMWeTNWjvWyjjBk3PZSWAo8Z1ZEEALoqk84jbrr/eos_bancor.png)</center>
***Authored by Eyal Hertzog, Bancor Co-founder & Product Architect***

Following the BP conference call on Mon, July 2nd, I would like to share some thoughts regarding the EOS RAM model and the balance between free market price speculation and the need for dApp developers to have access to affordable RAM for the success of the network.

The main reason speculation can be harmful in this particular case is that unlike many other tokens - RAM is “backed” by a scarce resource (memory) which cannot be practically rented. An analogy would be a real estate market in which property rentals are not possible. In such a market, real estate speculators will essentially own empty properties, adding upward pressure to prices, while decreasing the overall resource utilization as many properties remain expensive and empty.

One solution that was proposed during the call is to continuously burn EOS tokens from the RAM contract (e.g. 10% a month). This would theoretically drive the prices down at rate of a 11.11% per month assuming there were no other trades. As Dan Larimer mentioned in the call, this solution represents a form of “rent” costs on the RAM that is being used.

Speculation would still make sense, but in fewer cases. Currently, if someone speculates that even just a few big dApps are able to afford the current price, the rational strategy would be to hold RAM for the long term, until some dApp eventually coughs up the cost and the value rises. We think this incentive structure could be problematic for the ecosystem.

Clay Shirky coined the term “Low Cost of Failure” which he describes as the main driver behind the success of user-generated content platforms such as Blogger, YouTube, Reddit, etc. It is the low cost of failure that allows the long tail of users to participate in an ecosystem. And it is this long tail of users that increases creativity, access and distribution. One of the main benefits of blockchain technology is its ability to dramatically reduce the cost of failure for online transactional and financial networks. In this case, a potential killer app on the EOS ecosystem may simply die for not being economically viable due to RAM costs, while at the same time most of the available RAM is not even in use, but is held by speculators for future profit.

By changing the RAM contract to burn EOS at a constant rate, speculation becomes riskier. Speculators must predict that dApps (or additional speculators) will buy RAM at a certain rate, rather than simply anytime in the future. This would have a similar effect to continuously adding RAM to the contract; however, adding RAM is labor intensive and could take some time for testing and community readiness. 

**This calculator & chart demonstrates a 10% EOS burn rate in the RAM contract: 
[EOS RAM Bancor Calculator](https://docs.google.com/spreadsheets/d/1O3rPlq0GCOopljSEsQmlYws_w4LmhhJ-wvsnWztnFE8/edit#gid=766594341)
[Chart](https://docs.google.com/spreadsheets/d/1O3rPlq0GCOopljSEsQmlYws_w4LmhhJ-wvsnWztnFE8/edit#gid=1365260655)**

An additional step could be to issue RAM “futures”, which could be traded in the same way, and represent the next 64G of RAM that will be added in the future. Since this RAM is not actually being used, no “rent” should be charged for it until it is added to the active pool. This would allow speculators to still speculate on the future price, without paying rent, and without preventing dApp developers from having affordable access to the resources they need to build on the network.

We look forward to discussing this and other topics with BP teams and the greater EOS and blockchain communities, and welcome any feedback and improvements on this proposed solution.

To liquidity and beyond, 
The LiquidEOS Team

## Community
LiquidEOS Telegram: [@BPLiquidEOS](https://t.me/BPLiquidEOS)
Bancor Telegram: [@Bancor](https://t.me/bancor)
Medium: https://blog.bancor.network/
Twitter: https://twitter.com/Bancor
BitcoinTalk: https://bitcointalk.org/index.php?topic=1789222.0
Reddit: https://www.reddit.com/r/Bancor/
Steemit: https://steemit.com/@bancor-network
GitHub: https://github.com/bancorprotocol/contracts
Facebook: https://www.facebook.com/bancor/
YouTube: https://www.youtube.com/c/BancorProtocol
Instagram: https://www.instagram.com/bancornetwork/
LinkedIn: https://www.linkedin.com/company/17986744/
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
properties (23)
authorbancor-network
permlinka-proposed-solution-to-eos-ram-allocation
categoryeos
json_metadata{"tags":["eos","ram","bancor","liquideos"],"image":["https://cdn.steemitimages.com/DQmYGEJaGMWeTNWjvWyjjBk3PZSWAo8Z1ZEEALoqk84jbrr/eos_bancor.png"],"links":["https://docs.google.com/spreadsheets/d/1O3rPlq0GCOopljSEsQmlYws_w4LmhhJ-wvsnWztnFE8/edit#gid=766594341","https://docs.google.com/spreadsheets/d/1O3rPlq0GCOopljSEsQmlYws_w4LmhhJ-wvsnWztnFE8/edit#gid=1365260655","https://t.me/BPLiquidEOS","https://t.me/bancor","https://blog.bancor.network/","https://twitter.com/Bancor","https://bitcointalk.org/index.php?topic=1789222.0","https://www.reddit.com/r/Bancor/","https://steemit.com/@bancor-network","https://github.com/bancorprotocol/contracts","https://www.facebook.com/bancor/","https://www.youtube.com/c/BancorProtocol","https://www.instagram.com/bancornetwork/","https://www.linkedin.com/company/17986744/"],"app":"steemit/0.1","format":"markdown"}
created2018-07-04 14:05:24
last_update2018-07-08 07:30:06
depth0
children23
last_payout2018-07-11 14:05:24
cashout_time1969-12-31 23:59:59
total_payout_value14.410 HBD
curator_payout_value4.720 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length4,478
author_reputation261,250,673,969
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,391,687
net_rshares8,219,334,128,616
author_curate_reward""
vote details (48)
@akumara ·
Great proposition. Really like how fast Eyal and the Bancor team have addressed this issues, considering all that is going on right now!
properties (22)
authorakumara
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180717t075612095z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-17 07:56:12
last_update2018-07-17 07:56:12
depth1
children0
last_payout2018-07-24 07:56:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length136
author_reputation1,762,959,386
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id64,962,355
net_rshares0
@bitemycrypto ·
I think this is an interesting proposition, setting the RAM contract to burn EOS at a constant rate could be a good solution.
👍  
properties (23)
authorbitemycrypto
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180707t012524268z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-07 01:25:27
last_update2018-07-07 01:25:27
depth1
children0
last_payout2018-07-14 01:25:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length125
author_reputation6,585,590,255
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,722,803
net_rshares609,745,344
author_curate_reward""
vote details (1)
@chrissolutions ·
Imo, this whole RAM issue was not well thought out.  If developers are impeded by RAM price it will adversely effect the long term success of EOS.
properties (22)
authorchrissolutions
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180714t065309560z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-14 06:53:15
last_update2018-07-14 06:53:15
depth1
children0
last_payout2018-07-21 06:53:15
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length146
author_reputation-7,450,157,794
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id64,618,222
net_rshares0
@dan ·
Removing EOS from the market maker will only increase volatility as the market maker doesn't set the price of RAM, it responds to the market price of RAM.
👍  , ,
properties (23)
authordan
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t160322475z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 16:03:21
last_update2018-07-04 16:03:21
depth1
children4
last_payout2018-07-11 16:03:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length154
author_reputation155,470,101,136,708
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,406,221
net_rshares4,248,958,848
author_curate_reward""
vote details (3)
@bobinson · (edited)
@dan In short, the market will decide whether EOS can be used for developing dApps or just for speculation ? Honestly I am confused like many others on the RAM aspect and how its possible to develop dApps where everything is controlled by market forces. This reminds of the flood in Taiwan few years ago which has resulted in high RAM prices. But EOS seems to behave like a flood any day and anytime and market decides it ? A dApp's RAM requirement on the other hand is independent and unlike a platform like AWS which has a fixed baseline price of the RAM and then spot pricing depending on the market conditions EOS has no way to ensure basic RAM requirements of the dApps at this point in time. Please enlighten us if this is not the scenario.
👍  
properties (23)
authorbobinson
permlinkre-dan-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180705t082651961z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1","users":["dan"]}
created2018-07-05 08:26:57
last_update2018-07-05 08:27:24
depth2
children0
last_payout2018-07-12 08:26:57
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length746
author_reputation55,343,141,313,811
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,494,348
net_rshares576,818,926
author_curate_reward""
vote details (1)
@lukestokes ·
Based on the algorithm, is removing the EOS in the system used for the market mathematically different than adding RAM? If RAM isn't actually being used, wouldn't it make sense to remove from the EOS side of things first, until we see more real-world applications using RAM effectively?
👍  
properties (23)
authorlukestokes
permlinkre-dan-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t225812352z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 22:58:12
last_update2018-07-04 22:58:12
depth2
children2
last_payout2018-07-11 22:58:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length286
author_reputation554,601,966,217,919
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,446,210
net_rshares0
author_curate_reward""
vote details (1)
@gold84 ·
That's an interesting point @lukestokes ! Great question that help everyone think about the possibility of placing RAM aside until its usage is needed.

Regards, @gold84
properties (22)
authorgold84
permlinkre-lukestokes-re-dan-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180711t165255403z
categoryeos
json_metadata{"tags":["eos"],"users":["lukestokes","gold84"],"app":"steemit/0.1"}
created2018-07-11 16:52:54
last_update2018-07-11 16:52:54
depth3
children0
last_payout2018-07-18 16:52:54
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length169
author_reputation20,903,401,478,476
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id64,310,543
net_rshares0
@yuhjtman ·
Yes, it is different
properties (22)
authoryuhjtman
permlinkre-lukestokes-re-dan-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180712t071311026z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-12 07:13:12
last_update2018-07-12 07:13:12
depth3
children0
last_payout2018-07-19 07:13:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length20
author_reputation2,122,549,867,239
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id64,377,170
net_rshares0
@drop-bear-beryl ·
The "futures" contract idea would be useful to allow speculation without resource hoarding.  This, however, opens another door to abuse.   Speculators would play the commodity against the derivative for gains.
👍  
properties (23)
authordrop-bear-beryl
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180705t062749990z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-05 06:29:12
last_update2018-07-05 06:29:12
depth1
children0
last_payout2018-07-12 06:29:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length209
author_reputation219,931,714
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,483,299
net_rshares5,339,355,669
author_curate_reward""
vote details (1)
@iamsubbu ·
we can implement it in a slab model, if ram is consumed by 10% then ram fee should be 1%, if it crosses 20%, ram fee should be 2%. it continuous for every 10%, so that the speculators maintain the price at lower but still gain in ram speculation. this makes win-win situation for both speculators and dapp devlopers
properties (22)
authoriamsubbu
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180707t151432474z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-07 15:14:33
last_update2018-07-07 15:14:33
depth1
children1
last_payout2018-07-14 15:14:33
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length315
author_reputation8,740,731,126
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,792,145
net_rshares0
@abhi3700 · (edited)
Now, here the RAM would actually be not used bcoz of fee based on consumption.

Probably, it should be other way round.
If someone doesn't use RAM and just holds it, then a penalty would be charged.
properties (22)
authorabhi3700
permlinkre-iamsubbu-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180708t205631699z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-08 20:56:36
last_update2018-07-08 20:57:54
depth2
children0
last_payout2018-07-15 20:56:36
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length198
author_reputation1,411,436,389,304
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,943,293
net_rshares0
@jarib ·
$0.03
How about you ask the Dapps, the ones building on EOS, our opinion? It feels like everyone has a voice on the network but us. This is a horrible solution as we will have to pay a continuous fee on the reserved RAM for our application. I'd rather pay for RAM at $7 dollars and own it than see the RAM I have reserved devaluate at 11% a month bleeding us slowly. Maybe I'm missing something?
👍  , , , , , , ,
properties (23)
authorjarib
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t184223136z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 18:42:24
last_update2018-07-04 18:42:24
depth1
children0
last_payout2018-07-11 18:42:24
cashout_time1969-12-31 23:59:59
total_payout_value0.024 HBD
curator_payout_value0.002 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length389
author_reputation240,980,358,372
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,424,216
net_rshares12,866,336,317
author_curate_reward""
vote details (8)
@jetiknight ·
$0.02
How about not allowing people to speculate on RAM, but instead only allow developers looking to use RAM to buy RAM?  The more developers buy RAM to airdrop and create Dapps on EOS the more valuable the available RAM becomes, but atleast the RAM is being used in a way that in return provides value to the EOS chain and tokens. RAM skyrocketed by 2000% at it's peak and all we've seen are 7 airdrops, a few folks make an amazing speculative trade but the majority of the community become concerned about the price of future airdropping & development. This could also lead to BP's buying RAM as a way of leveraging control over the chain as well. Let folks speculate on the coin, not the hardware used to establish value to the  coin.
👍  , ,
properties (23)
authorjetiknight
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t234931378z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 23:49:30
last_update2018-07-04 23:49:30
depth1
children2
last_payout2018-07-11 23:49:30
cashout_time1969-12-31 23:59:59
total_payout_value0.017 HBD
curator_payout_value0.002 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length732
author_reputation436,974,542,842
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,450,140
net_rshares10,257,791,271
author_curate_reward""
vote details (3)
@abhi3700 ·
But how to detect those people (non-developers) and stop them from buying?
properties (22)
authorabhi3700
permlinkre-jetiknight-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180708t204618546z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-08 20:46:21
last_update2018-07-08 20:46:21
depth2
children1
last_payout2018-07-15 20:46:21
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length74
author_reputation1,411,436,389,304
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,942,489
net_rshares0
@chrissolutions ·
Simple.  Register your project to be allowed to buy resources.
properties (22)
authorchrissolutions
permlinkre-abhi3700-re-jetiknight-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180714t032936829z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-14 03:29:39
last_update2018-07-14 03:29:39
depth3
children0
last_payout2018-07-21 03:29:39
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length62
author_reputation-7,450,157,794
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id64,604,016
net_rshares0
@mughat · (edited)
The optimal solution is to allow RAM owners to let others use it for a fee (1% might get burned) creating a rental market. 

This way you can choose between owning or renting. Having both options is better than limiting options to only "renting".
👍  , ,
properties (23)
authormughat
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t165105973z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 16:51:06
last_update2018-07-04 16:51:27
depth1
children0
last_payout2018-07-11 16:51:06
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length246
author_reputation3,032,027,493,503
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,411,788
net_rshares6,736,467,276
author_curate_reward""
vote details (3)
@samupaha ·
> The main reason speculation can be harmful in this particular case is that unlike many other tokens - RAM is “backed” by a scarce resource (memory) which cannot be practically rented. An analogy would be a real estate market in which property rentals are not possible.

There is a way to rent RAM. Or to be exact, it's owning+renting combined.

Users will buy and sell RAM like they do now. But if they have more than certain amount (that's needed for basic account), they will need to pay rent for the RAM.

Obvious problem is: What happens when the account doesn't have any tokens for paying the rent? RAM can't be taken away because it can store important information.

Solution: Accounts can go in debt. When the account receives tokens next time, the debt is automatically paid.

This is not perfect solution. There could be accounts that never pay their debt. But owning that kind of account is pretty stupid because you can't do any business with it. If people try to avoid paying rent by using other tokens than EOS core token (which would be used to automatically pay the debt), we can freeze the account when it has too much debt. The rent debt must be paid before the account can do any transactions again.

This would create quite good incentives to minimize the usage of RAM.
properties (22)
authorsamupaha
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t152610780z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 15:26:12
last_update2018-07-04 15:26:12
depth1
children0
last_payout2018-07-11 15:26:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,290
author_reputation43,637,433,899,367
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,401,842
net_rshares0
@steemitboard ·
Congratulations @bancor-network! You have completed the following achievement on Steemit and have been rewarded with new badge(s) :

[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/posts.png)](http://steemitboard.com/@bancor-network) Award for the number of posts published

<sub>_Click on the badge to view your Board of Honor._</sub>
<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>


To support your work, I also upvoted your post!


**Do not miss the last post from @steemitboard:**
[SteemitBoard World Cup Contest - Round of 16 - Day 4](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-round-of-16-day-4)

---
**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**
Collect World Cup badges and win free SBD
Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)

---

> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
properties (22)
authorsteemitboard
permlinksteemitboard-notify-bancor-network-20180704t172214000z
categoryeos
json_metadata{"image":["https://steemitboard.com/img/notify.png"]}
created2018-07-04 17:22:12
last_update2018-07-04 17:22:12
depth1
children0
last_payout2018-07-11 17:22:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,409
author_reputation38,975,615,169,260
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,415,233
net_rshares0
@todor ·
$0.20
Burning tokens from the RAM contract is a good solution IMO. It's a form of renting without the drawbacks of real renting.

Wondering if you discussed simply raising the RAM trading fees?
👍  
properties (23)
authortodor
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t142722521z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 14:27:24
last_update2018-07-04 14:27:24
depth1
children1
last_payout2018-07-11 14:27:24
cashout_time1969-12-31 23:59:59
total_payout_value0.148 HBD
curator_payout_value0.048 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length187
author_reputation204,236,824,747
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,394,220
net_rshares85,751,393,142
author_curate_reward""
vote details (1)
@napkin ·
that would not change much because people will just hold onto it and thus decreasing the supply like it is happening now
👍  
properties (23)
authornapkin
permlinkre-todor-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t144655523z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 14:46:54
last_update2018-07-04 14:46:54
depth2
children0
last_payout2018-07-11 14:46:54
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length120
author_reputation662,858,917,292
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,396,721
net_rshares609,061,897
author_curate_reward""
vote details (1)
@tom74 ·
This sounds like TRUE CAPITALISM at work. As a person who enjoys history, this journey with EOS is awesome. Property rights in the digital age. INHO, maybe the right Dapp paying whatever the cost for the RAM will overcome the bull run. Why is all this free publicity bad again? I hear the argument that it is stifling innovation. I just contend there may be just as much pressure in this mess pushing people to choose this platform. In the end, I feel that Dan made a product and if it is half as good as his others, I will enjoy being an early investor. When the right Dapp lands on EOS, that is when the fun will begin.
👍  , ,
properties (23)
authortom74
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180704t184307357z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-04 18:43:06
last_update2018-07-04 18:43:06
depth1
children1
last_payout2018-07-11 18:43:06
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length621
author_reputation48,066,228,162
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,424,298
net_rshares6,805,196,570
author_curate_reward""
vote details (3)
@drop-bear-beryl ·
It is a fascinating journey.  Perhaps the greatest achievement of EOS thus far is incentivizing the masses to learn about free markets.
👍  ,
properties (23)
authordrop-bear-beryl
permlinkre-tom74-re-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180705t063202523z
categoryeos
json_metadata{"tags":["eos"],"app":"steemit/0.1"}
created2018-07-05 06:33:18
last_update2018-07-05 06:33:18
depth2
children0
last_payout2018-07-12 06:33:18
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length135
author_reputation219,931,714
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,483,691
net_rshares6,145,825,062
author_curate_reward""
vote details (2)
@ursapolaris ·
This is not a good solution. Might as well start calling RAM Gas.
👍  , , ,
properties (23)
authorursapolaris
permlinkre-bancor-network-a-proposed-solution-to-eos-ram-allocation-20180705t065043140z
categoryeos
json_metadata{"tags":["eos"],"community":"busy","app":"busy/2.5.0"}
created2018-07-05 06:50:42
last_update2018-07-05 06:50:42
depth1
children0
last_payout2018-07-12 06:50:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length65
author_reputation206,594,607
root_title"A Proposed Solution to EOS RAM Allocation"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id63,485,345
net_rshares6,580,882,434
author_curate_reward""
vote details (4)