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
{{ message }}
This repository has been archived by the owner on Mar 12, 2022. It is now read-only.
Simply discarding work received by clients is wasteful. Even if we don't reward those, we can still compare their work value with the available one and replace if higher.
A more conscious approach is to save multiple work values, and when work is requested, use the one immediately above the current active difficulty. This creates a soft dependency on more node functionality. If broken, we can rely on the service to request what they think is an appropriate difficulty. We can also use always that mode, which puts the burden of tracking active difficulty on the services.
The text was updated successfully, but these errors were encountered:
Suggested by @zhyatt (thanks!).
Simply discarding work received by clients is wasteful. Even if we don't reward those, we can still compare their work value with the available one and replace if higher.
A more conscious approach is to save multiple work values, and when work is requested, use the one immediately above the current active difficulty. This creates a soft dependency on more node functionality. If broken, we can rely on the service to request what they think is an appropriate difficulty. We can also use always that mode, which puts the burden of tracking active difficulty on the services.
The text was updated successfully, but these errors were encountered: