scripts: improve regtest setup #2844
Draft
Conversation
This file contains 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
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.
Use PIN remote in webdev. You might have to eject software keystore and reconnect after sending the first tx. to the wallet so that the tx shows up, after that all txs will show up immediately (no idea why).
Set
export DOCKER_REGTEST=1in case you are using it with therun_regtest.shscript.Source
lib.shorexample.shfrom theregtestfolder so thataccount0.jsoncan be imported intobitcoin-clicorrectly (I used a relative path because this is a WIP)