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

fix transfer invariant, credits to @holiman for finding the edge case #916

Merged
merged 2 commits into from
Apr 14, 2019

Conversation

protolambda
Copy link
Contributor

@protolambda protolambda requested a review from JustinDrake April 14, 2019 09:15
@JustinDrake JustinDrake merged commit be86f96 into dev Apr 14, 2019
@protolambda
Copy link
Contributor Author

@holiman Yes, thought about it, and asked Justin if allowing self-transfers (but with adjusted rules) would be better. Essentially, the beacon-chain is just a system chain, and the possibility of not having transfers for phase-0 is still up for discussion. Hence the choice for a more straight-forward fix to get the edge-case over with, in a simple way. If we would want beacon transfers for actual more eth1-like functionality, I'm sure we would go for the other more complete solution you mentioned.

JustinDrake added a commit that referenced this pull request Apr 14, 2019
@djrtwo djrtwo deleted the fix-self-transfer branch April 17, 2019 23:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants