pull down to refresh
92 sats \ 3 replies \ @Signal312 OP 13 Nov \ parent \ on: Testing signet (or testnet) for a bitcoin educational project - good faucets? bitdevs
Interesting, thank you! Running a fork of bitcoin is a beyond my skill level right now.
So just using the regular signet didn't work for your purposes? I have an educational project in mind that would require many different users to get some signet coins, make some practice transactions, and view those transactions on a block explorer.
If you have any suggestions about how users could easily get the signet coins (or anything along those lines) I'd love to hear them.
Running a fork of bitcoin is a beyond my skill level right now.
Are you currently running a node? If so, running a fork is no different.
So just using the regular signet didn't work for your purposes? I have an educational project in mind that would require many different users to get some signet coins, make some practice transactions, and view those transactions on a block explorer.
I think I went straight for mutinynet since I needed to run lightning and I wasn't aware of any other signet with a lightning network. Also, mutinynet has 30s blocks so you don't need to twiddle your thumbs as much.
If you have any suggestions about how users could easily get the signet coins (or anything along those lines) I'd love to hear them.
Sorry, I only have experience with mutinynet. It has all you need: a working faucet (onchain and lightning), a block explorer, LNURL, a fedimint and a cashu mint (probably more than you need actually).
What do you want to do exactly? Do you only want to have an onchain wallet which can send and receive bitcoins but no lightning? Lightning might be overwhelming initially so onchain-only would make sense.
reply
Yes, this is just for on-chain. I'm planning on using Sparrow.
I'd like to have students be able to get some signet sats, make transactions with them, and then follow the transactions in mempool.space. Preferably without me needing to dole out the signet sats manually.
Maybe I should switch to testnet 4?