stacks-core icon indicating copy to clipboard operation
stacks-core copied to clipboard

local_peer table in peer DB not updating when setting local_peer_seed

Open CharlieC3 opened this issue 2 years ago • 0 comments

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

  1. Start a stacks-node with an empty working directory
  2. Observe the entry in the local_peer table in the peer database
  3. Update the local_peer_seed config property and restart the stacks-node
  4. Observe the entry in the local_peer table in the peer database again. It's supposed to change with the updated local_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

CharlieC3 avatar Jun 09 '22 14:06 CharlieC3