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/3596 #3597

Merged
merged 5 commits into from
Mar 10, 2023
Merged

Feat/3596 #3597

merged 5 commits into from
Mar 10, 2023

Conversation

jcnelson
Copy link
Member

@jcnelson jcnelson commented Mar 1, 2023

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 the listunspent and importaddress 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:

[burnchain]
wallet_name = "name-of-your-wallet"

I have tested this with bitcoin 0.22.99.0.

@jcnelson jcnelson added the L1 Working Group Issue or PR related to improving L1 label Mar 1, 2023
@jcnelson jcnelson changed the title Feat/3595 Feat/3596 Mar 1, 2023
@codecov
Copy link

codecov bot commented Mar 1, 2023

Codecov Report

Merging #3597 (bcdbab4) into develop (cc2966b) will increase coverage by 0.94%.
The diff coverage is 4.68%.

@@             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     
Impacted Files Coverage Δ
testnet/stacks-node/src/tests/neon_integrations.rs 86.83% <0.00%> (+3.92%) ⬆️
...-node/src/burnchains/bitcoin_regtest_controller.rs 86.43% <40.00%> (+2.24%) ⬆️
testnet/stacks-node/src/tests/epoch_21.rs 96.13% <100.00%> (-0.01%) ⬇️

... and 54 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

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.

lgtm

@kantai
Copy link
Member

kantai commented Mar 1, 2023

Untagging myself as a reviewer, because this seems like a great PR for newer reviewers!

@kantai kantai removed their request for review March 1, 2023 18:21
@kantai
Copy link
Member

kantai commented Mar 1, 2023

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).

@igorsyl
Copy link
Contributor

igorsyl commented Mar 1, 2023

Untagging myself as a reviewer, because this seems like a great PR for newer reviewers!

@jo-tm seize the opportunity!

@jcnelson
Copy link
Member Author

jcnelson commented Mar 2, 2023

What is the "L1 Working Group" tag supposed to be for? Does it mean "Everything that isn't sBTC"?

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
Copy link
Contributor

igorsyl commented Mar 2, 2023

What is the "L1 Working Group" tag supposed to be for? Does it mean "Everything that isn't sBTC"?

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.

stacks-network/stacks#468

@jio-gl
Copy link
Contributor

jio-gl commented Mar 6, 2023

@igorsyl sorting out my GH notifications. will review this today as a new contributor (next time in 48 hours as per the contributor guide)

@igorsyl igorsyl requested a review from jio-gl March 6, 2023 18:16
@igorsyl igorsyl requested a review from jferrant March 7, 2023 18:15
Copy link
Contributor

@pavitthrap pavitthrap left a comment

Choose a reason for hiding this comment

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

lgtm

@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 Nov 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
L1 Working Group Issue or PR related to improving L1 locked
Projects
Status: Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

8 participants