Skip to content

Add work_server_use_peers field to config#5017

Merged
pwojcikdev merged 8 commits intonanocurrency:developfrom
h45hc47:work_server_use_peers_config_field
Mar 16, 2026
Merged

Add work_server_use_peers field to config#5017
pwojcikdev merged 8 commits intonanocurrency:developfrom
h45hc47:work_server_use_peers_config_field

Conversation

@h45hc47
Copy link
Copy Markdown
Contributor

@h45hc47 h45hc47 commented Jan 28, 2026

Currently, if local work generation disabled and used external work server, there is a need to add "use_peers": true to all requests, which is not very convenient.
So i add field work_server_use_peers: <bool> to node config to specify it and redefine it in request if needed.

@gr0vity-dev-bot
Copy link
Copy Markdown

gr0vity-dev-bot commented Jan 28, 2026

Test Results for Commit 0c85100

Pull Request 5017: Results
Overall Status:

Test Case Results

Last updated: 2026-03-16 17:47:35 UTC

@pwojcikdev
Copy link
Copy Markdown
Contributor

This makes sense. I think using work peers should be the default (if they are available), but this can be done as a next step.

@h45hc47
Copy link
Copy Markdown
Contributor Author

h45hc47 commented Feb 2, 2026

Yeah, sounds right. Done.

@h45hc47 h45hc47 force-pushed the work_server_use_peers_config_field branch from 0ef94e8 to 22dc975 Compare February 2, 2026 20:35
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new configuration field work_server_use_peers to allow setting a default value for the use_peers parameter in work server RPC requests, eliminating the need to specify it in every request when using an external work server.

Changes:

  • Added work_server_use_peers boolean configuration field with default value false
  • Implemented serialization and deserialization in TOML config
  • Modified work_generate RPC handler to use the config value as default when use_peers is not specified in the request, with special logic to auto-enable when work peers are configured

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File Description
nano/node/nodeconfig.hpp Added work_server_use_peers boolean field declaration with default value false
nano/node/nodeconfig.cpp Added serialization and deserialization of work_server_use_peers field in TOML config
nano/node/json_handler.cpp Modified work_generate handler to use config field as default for use_peers parameter with auto-detection logic

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@h45hc47
Copy link
Copy Markdown
Contributor Author

h45hc47 commented Feb 19, 2026

I would also like to clarify is there an approximate release date for update 29.0?

@pwojcikdev pwojcikdev merged commit fa5fed3 into nanocurrency:develop Mar 16, 2026
28 checks passed
@pwojcikdev
Copy link
Copy Markdown
Contributor

@h45hc47 We don't have a strict schedule for launching V29. I think we still have a few work in progress items left to merge like database index PR. I'd say roughly 1-2 months for feature cutoff, then one month of testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants