Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we include multiple implementation suggestions? #36

Open
bmann opened this issue Mar 26, 2019 · 3 comments
Open

Should we include multiple implementation suggestions? #36

bmann opened this issue Mar 26, 2019 · 3 comments
Labels
Implementation Tech, EIP talk, code

Comments

@bmann
Copy link
Contributor

bmann commented Mar 26, 2019

Evan Van Ness has suggested a different implementation of block rewards https://www.evanvanness.com/post/183629647376/a-simple-way-to-fund-more-public-goods-in-ethereum

Should this group broadly speaking work towards a block rewards proposal that can have multiple implementation suggestions and then push forward the one that has the most support?

Or should Evan’s proposal be turned into a separate EIP that is “competitive” with 1789?

Even with the latter, this group could have different people working on both but collaborating in different ways.

@owocki
Copy link

owocki commented Mar 26, 2019

Should this group broadly speaking work towards a block rewards proposal that can have multiple implementation suggestions and then push forward the one that has the most support?

this is the way i'm leaning. @lrettig ?

@lrettig
Copy link
Collaborator

lrettig commented Mar 26, 2019

I agree, for now let's explore multiple options here. I think it'll become clear over time if there is one "winner" that has the most support, or if we want to split the initiative and develop several proposals. It's also fairly likely that, like the issuance reduction/delay of the difficulty bomb in Constantinople, we may end up with an array of proposals that are very similar except for a few parameters.

I'd also point out that my EIP-1789 proposal should actually be compatible with all of these ideas since the beneficiary is set to null to begin.

@pet3r-pan pet3r-pan added the Implementation Tech, EIP talk, code label Apr 2, 2019
@glauseWilde
Copy link

✋ raises hand to lead a proposal. Initial draft #41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Implementation Tech, EIP talk, code
Projects
None yet
Development

No branches or pull requests

5 participants