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
I assume this is the origin of this equihash implementation port to c I have stumbled upon in several other projects?
If so, I believe my request is best directed and solved here.
Am I missing something, or does this port not verify the algorithm binding condition (strict (i.e. no duplication in indices) lexicographical ordering + leading zeroes in 'subsolutions')?
Given that several mining pool projects seem to have adopted this code, I could see there being potentially some problems depending on how their share payout is set up, if rogue miners decide to take advantage of amortization costs submitting solutions that wouldn't be accepted by the network, but this verifier code seems to allow.
The text was updated successfully, but these errors were encountered:
Hi,
I assume this is the origin of this equihash implementation port to c I have stumbled upon in several other projects?
If so, I believe my request is best directed and solved here.
Am I missing something, or does this port not verify the algorithm binding condition (strict (i.e. no duplication in indices) lexicographical ordering + leading zeroes in 'subsolutions')?
Given that several mining pool projects seem to have adopted this code, I could see there being potentially some problems depending on how their share payout is set up, if rogue miners decide to take advantage of amortization costs submitting solutions that wouldn't be accepted by the network, but this verifier code seems to allow.
The text was updated successfully, but these errors were encountered: