- Notifications
You must be signed in to change notification settings - Fork51
Add support for signet#140
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Binaries can be found herehttps://github.com/tiero/nigiri/releases/tag/v0.4.0-rc.0 |
ethicnology commentedDec 11, 2024
What is the status of this work? |
It requires some little work to make it compatible with master. We have stopped on this direction, as the interest from the user wasnt there anymore, and we prefer to remain regtest only if no-one else needs signet to work I found lately best to use MutinyNet as live signet with explorer etc.. What would be your use case? run a private signer or a public accessible one like MutinyNet so to speak? |
ethicnology commentedDec 12, 2024
run a private, team wide, or a public signet, like mutiny, with all the tooling (esplora, electrs, mempool…) BTW nigiri is great thank you |
Uh oh!
There was an error while loading.Please reload this page.
This PR adds an additional
docker-compose.signet.yml
and a dedicatedbitcoin.signet.conf
for running Bitcoin insignet
mode.38333
and rpc on38332
--signet
flag is incompatible with--ci
because no need in continuous integration pipelines--signet
flag is incompatible with--liquid
because there is nosignet
for Liquid Network for the time beingTODO
Thiscloses#138