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

update signet script

Browse Source
This commit is contained in:
Elyan 2024-03-05 13:03:16 -08:00
parent 0c2c0e9fa5
commit 59e896c297
3 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.env
View File

@ -3,12 +3,12 @@ BLOCKPRODUCTIONDELAY=600
MINERENABLED=1 MINERENABLED=1
NBITS=1e0377ae NBITS=1e0377ae
PRIVKEY=cQ78Y7oUASnzbgK465VPug4CrfxJPe95ftsDqwMwTJU8j1NoY76C PRIVKEY=cQ78Y7oUASnzbgK465VPug4CrfxJPe95ftsDqwMwTJU8j1NoY76C
MINETO=tb1qg0w2x4z0seppjrpp5e6q6c9sggu5qy4jxmdvvl MINETO=tb1qhcuywsgshgs2ukv0ae2gw9egrfqx944qh6eurq
SIGNETCHALLENGE=5121021dc5794f479c961e47fd3ec343ecd7bb43c3abb991fb1e104f1e2403019e5e7551ae SIGNETCHALLENGE=5121021dc5794f479c961e47fd3ec343ecd7bb43c3abb991fb1e104f1e2403019e5e7551ae
# RPC Configuration # RPC Configuration
RPCUSER=easepay-signet RPCUSER=easepay-signet
RPCPASSWORD=2cdbbe44a6e91b2b39f0ac2bb0f67b4f$b57bc3759b99f1dc6c3c88f037cdd95151370c41246619a23a350abe4c4d36a0 RPCPASSWORD=Beautifulgirl456
UACOMMENT=CustomSignet UACOMMENT=CustomSignet

2
README.md
View File

@ -91,7 +91,7 @@ If MINERENABLED=1 and not provided, it will be generated. If provided, PRIVKEY m
2. Navigate to the root of the repository directory. 2. Navigate to the root of the repository directory.
3. Build the Docker image: 3. Build the Docker image:
`docker build -it bitcoin-signet . ` `docker build -t bitcoin-signet . `
## 4. Running the docker Image build in Step 3: ## 4. Running the docker Image build in Step 3:
To run the image without hitting some gotcha moment, i find it imperative to explain in more details the approach i took that got me here, Especailly for those trying to run a custom signet for the very first time. This repository is built to be highly customizable, which means you can swap a lot of things out and replace with your own implementation and it would still work. but some things you need to do after building the image would almost always remain the same. To run the image without hitting some gotcha moment, i find it imperative to explain in more details the approach i took that got me here, Especailly for those trying to run a custom signet for the very first time. This repository is built to be highly customizable, which means you can swap a lot of things out and replace with your own implementation and it would still work. but some things you need to do after building the image would almost always remain the same.

7
gen-bitcoind-conf.sh
View File

@ -40,6 +40,13 @@ rpcallowip=$RPCALLOWIP
whitelist=$WHITELIST whitelist=$WHITELIST
fallbackfee=0.0002" fallbackfee=0.0002"
# Add wallet auto-load configurations (outside of the [signet] section)
echo "wallet=easepay.wallet.hot.2.3.multisig"
echo "wallet=easepay.wallet.cold.first"
echo "wallet=easepay.wallet.cold.second"
echo "wallet=easepay.wallet.cold.third"
if [[ "$ADDNODE" != "" ]]; then if [[ "$ADDNODE" != "" ]]; then
echo $ADDNODE | tr ',' '\n' | while read node; do echo $ADDNODE | tr ',' '\n' | while read node; do
echo "addnode=$node" echo "addnode=$node"