Zach Hyatt
Zach Hyatt
Refer to existing [tuning options](https://docs.nano.org/running-a-node/ledger-management/#tuning-options) and expand into other known areas for troubleshooting bootstrap issues.
The confirmation time stats (either from [confirmation_history](https://docs.nano.org/commands/rpc-protocol/#confirmation_history) or average from [websocket confirmations](https://docs.nano.org/integration-guides/websockets/#confirmations)) can be misleading since they don't sample the time between the block being **sent** and the time of...
Possibly to the glossary, or other locations as appropriate.
Add an example for creating change blocks in our [external management](https://docs.nano.org/integration-guides/key-management/#external-management) guide. It's possible to imply from the [block specification](https://docs.nano.org/integration-guides/the-basics/#block-format) now but this should make it more explicit for wallet...
On the Configuration page https://docs.nano.org/running-a-node/configuration/ add a section, likely a collapsed box to keep it from overwhelming the page, for capturing configuration changes over time. This is needed because it...
Related to https://github.com/nanocurrency/nano-node/pull/2535
Pulling over and possibly expanding from https://github.com/cryptocode/raiblocks/wiki/Error-handling-in-the-node-using-std::error_code-and-std::expected. This is likely best for the Node Implementation section being added with the Living Whitepaper.
This will likely fit best in the Node Implementation section being added as part of the Living Whitepaper setup.
The Wireshark dissector spec for Nano has fallen out-of-date as protocol changes have occurred the past couple years, so an update is needed. - Current version: https://www.wireshark.org/docs/dfref/n/nano.html - Previous owner...
With the state block v2 changes to the signed block payload, hardware signing implementations will need to be modified to support this before the new block version is required for...