Neptune-Crypto/neptune-core

when guessing node is restarted, it does not begin guessing again until next block.

Open

#432 opened on Feb 14, 2025

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Rust (45 forks)auto 404
enhancementhelp wantedlow prioritymining

Repository metrics

Stars
 (110 stars)
PR merge metrics
 (PR metrics pending)

Description

Actually, I'm not certain. It might start guessing if a new block proposal is received for the current block.

But really, it should start guessing soon after the node is restarted and connected. That could mean:

  1. asking peers for block-proposal(s)
  2. storing best block-proposal locally, in case of restart.

For now, this is mostly a nuisance and seems low priority. But it should be fixed at some point.

The basic behavior I am seeing is:

  1. node is guessing on block 400
  2. node is shutdown, and restarted.
  3. block 401 has not been found yet.
  4. node remains inactive for a lengthy period, when it should start mining instead.

Contributor guide

Research direction
Investigate the node restart logic to understand why guessing does not resume immediately. Look at how block proposals are fetched and stored, and consider implementing a mechanism to request proposals from peers on startup.
Tech stack
rust
Domain
blockchain
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustBlockchain concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60