AramaicAllspice 2025-03-13

Thread 🧵🧵 (1/x) I’m looking into some of the awesome information provided in the post here: https://talk.neptune.cash/post/1/34

I found a commit from March 7 2025 that seems to be related

commit dce5113b4748d7f3e9dab8f74f817fd4c1a4e2a6 Author: sword-smith thor@neptune.cash Date: Fri Mar 7 14:56:14 2025 +0100

feat(rpc_server): Support external PoW guesser programs

Add two endpoints, one for exporting the PoW puzzle and one for receiving a PoW puzzle solution. With these endpoints, external programs like GPU hashers and mining pools can receive a PoW puzzle (challenge) that they can work on.

In the current implementation, the node’s wallet secret is used as the guesser digest in the block header, meaning that the guesser-reward will go to the wallet handled by the client.

AramaicAllspice
2025-03-13

With this change, main_loop now has two ways of handling a self-guessed block, one from the client’s own guesser, and one from the RPC server. For this reason, the handling of a self-guessed block is factored out to a separate function in main_loop, and this function gets ia test.

All block proposals that are exported in this way are stored in RAM such that a correct guess will be rewarded, even if the node has received a new, more favorable, block proposal in the meantime.

GlobalState gets a new field for the current best block proposal and for the exported block proposals. This new field is called mining_state.