stacks-core
stacks-core copied to clipboard
local_peer table in peer DB not updating when setting local_peer_seed
Describe the bug
When updating the local_peer_seed
config property on a node with a pre-existing chainstate, the local_peer
table in the peer database does not get updated. Instead, the node continues using the private key of the original local_peer_seed
used when the node first started with an empty working directory.
Steps To Reproduce
- Start a stacks-node with an empty working directory
- Observe the entry in the
local_peer
table in the peer database - Update the
local_peer_seed
config property and restart the stacks-node - Observe the entry in the
local_peer
table in the peer database again. It's supposed to change with the updatedlocal_peer_seed
, but it doesn't
Expected behavior
The entry in the local_peer
table in the peer database should be updated on bootup if the local_peer_seed
in the config TOML has changed since the last boot.
Stacks-node version: 2.05.0.2.2