We're continuing to work on the mining pool API specification, plan is to release an early version by next Monday.
Thank you for all the interest in starting mining pools. More details to follow (and we will respond to individual emails) but the basic requirements to receive the reward will be
We'll follow up by email to everyone who indicated interest with more information on each of those requirements
No final decision has been made yet, but there will likely be a HARD FORK of testnet2 where we'll introduce some changes to the difficulty adjustment algorithm. We have not set a date yet but be aware that ALL nodes on the network must switch to the latest version of snarkOS at the time of the fork if they want to participate in the rewards program.
Merges:
Ledger::update_block_requests refactoring series.Ledger::update_block_requests. The endg goal of this series is to arrive at the same final outcome as #1372, with more intermediate steps and extended modularity.FromBytes implementation for BlockLocators; it reduces the number of allocations, lookups, and removes checks form non-emptiness that would always return true.stderr the text PoSW difficulty target is not met. Thank you, xbeastx for your contribution!stdout.Decoder::decode impl for Message. This removes an intermediate vector allocation whenever a network message is received.Activity:
Mining Pool:
Infrastructure is done. Need to add some nonsense bytes to what we are hashing to avoid some exploits. Avoid allowing to resubmit their own work in their own name enabling them to reap duplicate rewards.
We have the option to defer updating the reward mechanism to make sure it’s favorable for the pool and the worker.
Fabiano has offered up some people who can test the pool, and that’s the next step.
There’s a draft PR open, and there’s already a community member who is posting bugs for us in the mining pool impl that Jules has created.
We need to set up the pool servers. Fabiano and crew can help with this.
We can do this on testnet2 right now.
Workers have to swap out their difficulty targets, there’s an API change in snarkVM, Howard reverted it, so we have to wait. The set_difficulty_target is the detail that needs to be considered here.
https://github.com/AleoHQ/snarkVM/pull/529
Niklas: Going to work on getting Prometheus back into the codebase.
Lukasz: Communicating with Howard and the details of my changes and going over the changes.
Fabiano: Working with Max on the CUDA server. We ran into an issue w/ snarkVM that’s causing a crash. Making some progress on scaling the network dynamically. Tried tweaking some of the parameters on the miners to see if we can get more perf, but we haven’t been able to get to a point where we can get better perf. We’re blocked on CUDA until we can figure out if snarkVM can really run. The inner snark fails to verify when CUDA is used for multi-scalar multiplication.
Fabian: No update.