Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add chain_id to signer config #5314

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Conversation

hstove
Copy link
Contributor

@hstove hstove commented Oct 15, 2024

This adds an optional chain_id field to the signer's config. If present, it is used in the /v3/block_proposal endpoint.

@hstove hstove requested review from a team as code owners October 15, 2024 00:18
@hstove hstove requested review from obycode and jferrant October 15, 2024 00:19
@hstove
Copy link
Contributor Author

hstove commented Oct 15, 2024

I've updated regtest-env with this PR (hirosystems/stacks-regtest-env#49) and confirmed it's working well

@hstove hstove linked an issue Oct 15, 2024 that may be closed by this pull request
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

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

I should have realized in my earlier PR that my integration test in nakamoto_integrations.rs did not include the real signers. Can we also add an integration test in testnet/stacks-node/src/tests/signer/v0.rs that uses a custom chain id? Maybe a variant of multiple_miners_with_nakamoto_blocks?

Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

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

Fine to add the integration test in a separate PR.

@wileyj wileyj added this pull request to the merge queue Oct 15, 2024
Merged via the queue into develop with commit b0a1b84 Oct 15, 2024
1 check passed
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add chain_id to signer config
6 participants