feat: make chain_id configurable

[obycode]

Description

Applicable issues

• fixes #

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[jcnelson]

Approving, but please test this (or add tests) before merging to confirm that once the PeerDB is connected, the LocalPeer you load out of it has a network_id equal to chain_id.

[obycode]

Approving, but please test this (or add tests) before merging to confirm that once the PeerDB is connected, the LocalPeer you load out of it has a network_id equal to chain_id.

Are there any existing tests that might be a good setup for this that you could point me to?

[kantai]

Are there any existing tests that might be a good setup for this that you could point me to?

You could add an assertion to any of the neon or nakamoto integration tests by querying /v2/info

[obycode]

You could add an assertion to any of the neon or nakamoto integration tests by querying /v2/info

Cool, I was thinking about adding an integration test with this any way.

[jcnelson]

Approved pending CI

[blockstack-devops]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.