Open bonomat opened 1 year ago
A custom signet is quite easy to setup, however we should think about how we want to use it? After looking into it I see the following options
Fork nigiri and add support for a custom signet chain. I got this working prototypical, but there is a lot of stuff in nigiri we do not really need for a custom signet. However if we plan to work with regtest and signet (and potentially liquid) in parallel that might be the way to go.
e.g.
nigiri start -signet
nigiri faucet 0.1
However, we would need to maintain a fork of nigiri and nigiri-chopsticks
Similar to nigiri - create a docker-compose with electrs, esplora and bitcoin (signet).
e.g.
docker-compose up
curl --data-binary '{"jsonrpc": "1.0", "method": "sendtoaddress", "params": ["tb1qlsp47mzmzzncwrp0gr4wvrqhn3s0dupf8hnwr4", 0.1]}' -H 'content-type: text/plain;' http://admin1:123@127.0.0.1:38332/
This could be done with nigiri fork or a custom setup, but on a remote server accessible from the outside. We setup the signet node only once and point our configuration to signet statically.
I am rather in favor of the remote option as I see signet more as an alternative to testnet than to regtest.
It would also help in the beta testing as we could easily fund the testers.
However, we could also go for the local and remote option.
I am rather in favor of the remote option as I see signet more as an alternative to testnet than to regtest.
I agree, it would replace the testnet setup.
I'm in favor of docker-compose or vanilla docker containers as we can't use nigiri on our VMs.
So far, we used regtest or testnet for testing.
We should evaluate how easy it is to setup a bitcoin signet including additional services like a blockexplorer and electrs.