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

Send block number instead of the epoch seed hash #5

Open
chfast opened this issue Mar 29, 2018 · 0 comments
Open

Send block number instead of the epoch seed hash #5

chfast opened this issue Mar 29, 2018 · 0 comments

Comments

@chfast
Copy link

chfast commented Mar 29, 2018

  1. The mining software has to search for the epoch number anyway, because that's needed to create light cache and DAG - the sizes of light cache and full DAG are functions of the epoch number.
  2. Epoch / block number has 4 bytes max, seed hash 32 bytes.
  3. Block number is better than epoch number, because:
    • you can estimate when the epoch change will occur,
    • it's more informational for users (e.g. you can log the current block number),
    • it's easier to explain in the spec what the block number is than what the epoch number is.

I recommend creating version 1.1.0 of the spec with this change.

@chfast chfast changed the title Sending seed hash instead of epoch number is stupid Sending seed hash instead of epoch number is unefficient Aug 8, 2018
@chfast chfast changed the title Sending seed hash instead of epoch number is unefficient Send block number instead of the epoch seed hash Aug 8, 2018
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

No branches or pull requests

1 participant