Feat/remove signer 1 #134
Open
Feat/remove signer 1 #134
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
leahjlou
approved these changes
Jul 3, 2025
hugocaillard
force-pushed
the
feat/remove-signer-1
branch
from
b93d693 to
fc234ed
Compare
hugocaillard
requested a deployment
to
Development
GitHub Actions
Waiting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When we first implemented nakamoto support, we needed 2 signer.
In reality, one is enough, so this PR remove the signer-1 and only keeps signer-0. The might save some resources costs
It's nice that we have the setup to easily add a signer, or potential signer customisation in the future.