# EIP

EIP stands for **e**conomic **i**mprovement **p**roposal and basicly includes three main changes. (See the [details](https://steemit.com/steem/@steemitblog/improving-the-economics-of-steem-a-community-proposal))


- Convergent linear rewards curve instead of linear rewards curve

- 50/50 author/curation rewards distribution

- Free downvote pool

I personally like all these changes. 

The current economical mechanics clearly doesn't work as it's expected. We have almost zero organic curation, people tend to sell their votes instead of curating, and nobody uses their downvotes. (because it costs your VP and potential profit.)

I understand that the authors may be frustrated with the idea of fewer author rewards. However, if these changes bring a better curation, %50 of the new system's potential rewards would be bigger than %75 of the old rewards.

We're doing nothing to improve the current economic status for a long time. These changes won't fix everything in one night, but it's a good start.

# SPS

I've [reviewed the initial SPS](https://steemit.com/steem/@emrebeyler/notes-on-steem-proposal-system) four months ago. Not much changed since then.

STEEM is an open-source project and there is a consensus between multiple entities. We have lots of interested parties about the project and blockchain.

As an open-source contributor, maintainer I see everyday people contribute to projects voluntarily. and that happens on every scale. 

My dream is to see official steem repositories getting contributions in a non-profit and healthy way.  Steemit inc. recently taking a friendly behaviour to community contributions and thats a really good step.

I see SPS as an additional incentive for people to work for the benefit of the network. That's why I support that it should be funded with donations instead of inflation sources.

# [Vote window to 1 minute instead of 15 minutes](https://steemit.com/hf21/@steemitblog/hf21-addition-vote-window-change)

It was painful to wait for 10-15 mins  to upvote a post because it was not efficient to do it. The current parameters on that topic actually favor automated curation or other bot solutions. This is a good and simple touch to have at HF21.

# [Increasing Custom JSON limits to 5](https://steemit.com/hf21/@steemitblog/hf21-recommendation-raising-custom-json-limit)

A good change for app developers and user experience. 

I was always curious if apps handling that possible race condition before. I was playing Steemmonsters and Drugwars heavily a couple of months ago and they both broadcast custom jsons from my account. Pretty sure I hit that limitation a couple of times. Also, this also removes the burden on application accounts if they need to broadcast custom jsons regularly.

***

I support the proposed changes for the upcoming hard-fork.

I might criticize that we're having lots of changes for a single hard-fork, however, I also imagine it's a hard thing to poke every exchange and 3rd party to update their nodes every time we have a hard-fork.  That's should be quite an operation.