4nk/anchorage_layer_simple
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Geo ⚡️ 2024-02-16 21:01:04 +01:00 committed by GitHub
parent 4a792770b2
commit 1c3465e23f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -41,7 +41,7 @@ The provided Dockerfile and scripts automate the process of setting up a custom
```docker run -d -p 38333:38333 -p 38332:38332 bitcoin-signet``` ```docker run -d -p 38333:38333 -p 38332:38332 bitcoin-signet```
The generate_signet.sh script will execute within the container, setting up the custom Signet and starting the Bitcoin node. The `generate_signet.sh` script will execute within the container, setting up the custom Signet and starting the Bitcoin node.
**NOTE**: the signet challenge parameter (pubkey) should be generated before building **NOTE**: the signet challenge parameter (pubkey) should be generated before building
the docker image. this can be done on your local machine. This approach would mean you would have a fixed public key for your Signet, which isn't such a big deal for testing. It's also possible to update the `generate_script.sh` script to dynamically create the bitcoin.conf after generating the public key. I ran into some issues trying to do this, you may have the time, so Knock yourself out and create a PR if you get it done. the docker image. this can be done on your local machine. This approach would mean you would have a fixed public key for your Signet, which isn't such a big deal for testing. It's also possible to update the `generate_script.sh` script to dynamically create the bitcoin.conf after generating the public key. I ran into some issues trying to do this, you may have the time, so Knock yourself out and create a PR if you get it done.