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

Update deposit data #25

Merged
merged 4 commits into from
Apr 14, 2019
Merged

Update deposit data #25

merged 4 commits into from
Apr 14, 2019

Conversation

NIC619
Copy link
Collaborator

@NIC619 NIC619 commented Mar 21, 2019

What was wrong?

ethereum/consensus-specs#780

How was it fixed?

  • Remove deposit_timestamp
  • Change the size of deposit_input to 176 bytes
    • 176 = 48 + 32 + 96

Cute Animal Picture

@@ -5,7 +5,7 @@
SECONDS_PER_DAY: constant(uint256) = 86400
MAX_64_BIT_VALUE: constant(uint256) = 18446744073709551615 # 2**64 - 1

Deposit: event({data: bytes[528], merkle_tree_index: bytes[8]})
Deposit: event({data: bytes[184], merkle_tree_index: bytes[8]})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JustinDrake @djrtwo @vbuterin do we want to fix the deposit data length tightly? I think allocating a bigger size is more future-proof.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the gas impact either way?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No impact if declared larger for future proof. More gas is charged only if there are more bytes to be logged.

@NIC619 NIC619 changed the base branch from master to dev March 26, 2019 14:07
@hwwhww hwwhww merged commit 9854cfd into ethereum:dev Apr 14, 2019
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