You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
withd
being defined asd = max(H) / N
andN
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 timesN
to find a nonce that is below the difficulty threshold.The text was updated successfully, but these errors were encountered: