historic-blockhashes #2427
historic-blockhashes #2427
Conversation
zmitton
force-pushed
the
historic-blockhashes
branch
2 times, most recently
from
8e11f3f
to
a0afd75
Compare
zmitton
force-pushed
the
historic-blockhashes
branch
from
a0afd75
to
1388a97
Compare
|
There has been no activity on this pull request for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
There was a problem hiding this comment.
Along with the suggested changes, this EIP also needs all of the sections found in the template: https://raw.githubusercontent.com/ethereum/EIPs/master/eip-template.md
Is there still interest in this over https://eips.ethereum.org/EIPS/eip-2935 ? If not, it may be worthwhile to consolidate effort into one of the two.
micahzoltu suggested changes Co-authored-by: Micah Zoltu <micah@zoltu.net>
|
I posted this nearly a year ago after aggregating the best research from multiple other EIPs (themselves over 3 years old). Didn't receive so much as a single comment until now. Might as well just close this one because Vitalik has written one now which will probably actually be payed attention to. |
|
@zmitton do you have any feedback on how this process can be improved? It is really unfortunate this EIP received no traction when you authored it. Did you share this with anyone in the community (e.g. twitter, eth magicians, etc)? |
|
I guess my suggestion is that the person assigned to review it, does so. It was clear there was interest, so that means it should get moved to the next step of the process, or given a reason why not? |
|
We have a had a problem historically of editors not proactively reading EIPs, which meant the only way to get them through the process was to find and pester an editor to read your EIP and review it. We have gotten better and started to work through the backlog, but editors are still greatly understaffed so this generally continues to be a problem. |
I believe the contract implementation strategy is what held this up (EIP #210). Lets keep it simple. We won't have to worry about complex "stuffing" processes this way. And clients already have this data, so it should be relatively easy.