Howard Wu

@johnnychen8188 I would `git pull` and try again. The logs seem to me like the node is running an older version.

I have added PR #2134 which checks for duplicate solutions or transactions on a per IP address basis. Feel free to check if this change fixes the issue and can...

Closing as the issue has been fixed with PR #2134.

@HarukaMa would you be open to share a code snippet or sample PR for how you are architecting this? We can then base a design around it

@ljedrz We also use thread pool approach in snarkVM to make things performant. Do you have recommendations on resource allocation between tokio and the threadpool to ensure snarkOS runs fairly?

Closing as most provers seem to have moved on to dedicated hardware. Please feel free to reopen if this continues to be a concern.

Note: We need to add a README section for this PR too.

This appears to be third party software. snarkOS does not offer a service install process.

> Validator will always get block locators when perform_handshake, however, there's no need to do it when peer is a Prover or a Client，right？ #2147 I've answered this in PR...

`Sync` already ensures that the client/prover will only request a `PuzzleRequest` with a specific set of peers if it deems them to be further on the canonical chain. Additionally, we...