Repository navigation
docs(run-a-node): fix 0.3.1 mining defaults, pow_status warning, catalogue refresh - #553
Merged
Merged
Conversation
…logue refresh Fixes #552. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kashepavadan
force-pushed
the
fix-552-run-a-node-031
branch
from
October 9, 2026 18:30
f6e413b to
1d0d1de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #552.
powexample now shows whatgenerate_user_configwrites in 0.3.1 (max_threads: 1,max_tickets_per_block: 1,threshold: 2000000000). It also explainsmax_threads(null= one thread per core) andthreshold: auto-claim pays a target until its balance reaches the threshold, then stops mining once every target has. Checked againstservices/pow/src/service.rsandDEFAULT_POW_CLAIM_THRESHOLDinnodes/node/binary/src/cli/config/init.rsin logos-blockchain.pow_statuswarning: removed the "blockchain module0.3.0" qualifier, and addedpow_claimable_rewards(seeblend/info,pow/statusandpow/rewards/claimablenever respond while the node is Bootstrapping (0.3.1) logos-blockchain/logos-blockchain#3780). I made the same change todocs/blockchain/get-started/run-a-logos-blockchain-node-from-cli.md, which had the same warning.logosctl catalog refreshstep before the install, so it now also says to run it even when the daemon was already running.npm run buildpasses. I didn't run Vale locally.🤖 Generated with Claude Code