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

Define a suitable difficulty function to find a nonce for POPS-VRF #195

Closed
fasmat opened this issue Nov 28, 2022 · 2 comments
Closed

Define a suitable difficulty function to find a nonce for POPS-VRF #195

fasmat opened this issue Nov 28, 2022 · 2 comments
Assignees

Comments

@fasmat
Copy link
Member

fasmat commented Nov 28, 2022

In #175 it is proposed to introduce a difficulty function that is used to check if a smesher has performed a suitable amount of computational cost. The difficulty function implemented in spacemeshos/post#67 is the following:

H(nonce ++ VRFpk ++ PositioningATX ) < d with d being defined as d = max(H) / N and N being the number of labels computed for the PoST initialization.

This definition for the difficulty function seems sub-optimal, since only about 63% of VRFpk will find a nonce during PoST initialization. ~ 2% of VRFpk will need to compute hashes for more than 4 times N to find a nonce that is below the difficulty threshold.

@pigmej pigmej added the genesis label Nov 29, 2022
@fasmat fasmat changed the title Defining a suitable difficulty function to find a nonce for POPS-VRF Define a suitable difficulty function to find a nonce for POPS-VRF Nov 29, 2022
@pigmej
Copy link
Member

pigmej commented Nov 30, 2022

That needs further discussions. Currently the ball is on @selfdual-brain side.

@pigmej
Copy link
Member

pigmej commented Dec 7, 2022

Will be closed by: spacemeshos/post#91

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Spec available (on-going review)
Development

No branches or pull requests

3 participants