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

Make signers config customizable #1530

Closed
hugocaillard opened this issue Aug 2, 2024 · 0 comments · Fixed by #1555
Closed

Make signers config customizable #1530

hugocaillard opened this issue Aug 2, 2024 · 0 comments · Fixed by #1555
Assignees
Labels
devnet Issue related to the devnet

Comments

@hugocaillard
Copy link
Collaborator

Context

The Stacks blockchain needs Signers to sign blocks in Nakamoto. For Nakamoto support, it's important that the Devnet setup has Signers and Stackers.
Two signers were setup in Clarinet in this PR #1384

At they time, the two signers were hard coded and non customizable.

They use the hard coded wallet_1 and wallet_2 private keys (default wallet in devnet.toml).

The stackers will then use one of these private keys (hard coded again) to submit their stacking orders.

Allow the Signers config to be customizable

Developers should be able to customize the signers config in the Devnet.toml. The config should allow 1 or multiple signers
It would also impact the stacking orders settings, we may want to add the ability to config the signer in key for the stackers.

For backward compatibility (existing Devnet.toml without signer configs), we should either provide a mechanism to add it on clarinet devnet start (promp the user "signers config not found, o you want to add the default one: ...") or have a default one in clarinet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devnet Issue related to the devnet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants