-
Notifications
You must be signed in to change notification settings - Fork 671
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/3596 #3597
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3597 +/- ##
===========================================
+ Coverage 30.46% 31.40% +0.94%
===========================================
Files 297 298 +1
Lines 275498 276125 +627
===========================================
+ Hits 83917 86717 +2800
+ Misses 191581 189408 -2173
... and 54 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Untagging myself as a reviewer, because this seems like a great PR for newer reviewers! |
Meta: What is the "L1 Working Group" tag supposed to be for? Does it mean "Everything that isn't sBTC"? In which case, I'd suggest that we just delete it as tag (because "Everything that isn't sBTC" is conveyed by the lack of an sBTC tag). |
@jo-tm seize the opportunity! |
Right now, I've taken it to mean "things that improve the UX of the Stacks blockchain". This includes both developer UX (i.e. refactoring) as well as performance and reliability improvements. It does not include CI, devops, or docs. |
|
@igorsyl sorting out my GH notifications. will review this today as a new contributor (next time in 48 hours as per the contributor guide) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
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. |
This PR addresses #3596 by enabling using a custom existing
bitcoind
wallet name when mining, instead of the default one ("") created by Stacks when it boots up for the first time. This is pertinent for thelistunspent
andimportaddress
RPC calls that the node makes (h/t @MaksimalistT for bringing this up).To use this feature, you will need to add 'wallet_name' to the '[burnchain]' section as follows:
I have tested this with bitcoin 0.22.99.0.