Hot answers tagged

12

Testnet is really heavy (hundreds of gigabytes), there is a lighter alternative to that now: signet. There is also a local-only network called regtest, which I put in its own section. Finally, I'll explain txindex, which is a useful option to have your own mini block explorer. Signet To use it, first start bitcoind with the option: bitcoind -signet It will ...


8

I will assume that you want to get set up on the default Signet that is administered by Kalle Alm and AJ Towns. (You can also set up your own custom Signet network and administer it yourself but the following instructions won't apply.) Signet was merged into Bitcoin Core in PR 18267 in September 2020 and was first included in the 0.21 release. Build ...


7

The main difference between signet and regtest is that signet is an actual network, as opposed to a sandboxed environment. In regtest, the network topology is entirely manual. You spin up nodes, and manually establish connections between them. You have exact control over what blocks are mined and when. This is great for testing things like consensus logic, ...


6

Signet is more comparable to testnet than it is to regtest. Regtest is for private use and testing things. Even if signet were available, it is still useful to have your own blockchain for testing where you can generate coins, blocks, forks, and reorgs at will. It allows tests to run quickly and for a specific set of conditions to be tested. There is no ...


6

Bech32 addresses are defined in BIP 173. This slide is taken from Pieter Wuille's presentation on bech32 at SF Bitcoin Devs in March 2017. Different prefixes A list of address prefixes on the Bitcoin wiki is here. bc is representing Bitcoin (mainnet) Testnet bech32 addresses start tb Signet (both default Signet and custom Signets) bech32 addresses also ...


4

This was answered by individuals on IRC. It is perfectly fine to run any number of c-lightning nodes for any combination of networks as long as you keep home directories (--lightning-dir) and (--bind-addr, --addr) bindings distinct. For different networks (i.e. mainnet, testnet, signet etc) c-lightning already has subdirectories so there is no need to ...


4

I don't think there is a clear answer to this yet. I suspect many are waiting to see whether Signet proves an effective replacement for testnet. (Signet is not yet merged into Bitcoin Core as of the time of writing in August 2020.) There has been discussion on the Bitcoin dev mailing list and in the Bitcoin Core repo about a testnet reset at multiple points. ...


3

It is absolutely possible, running parallel networks will be even added as a GUI option in the next RaspiBlitz release (FOSS bitcoin - lightning node package) which will also make C-lightning available. See the issue about the parallel networks: https://github.com/rootzoll/raspiblitz/issues/2290 Here is a screenshot demonstrating running 5 LN nodes (3 C-...


3

As Pieter said in the comments there are Taproot test vectors that have recently been merged into BIP 341. You can also find additional P2TR spends on signet, testnet on block explorers e.g. mempool.space. Any transaction that is spending from a tb1p address is a Taproot spend (tb1q is SegWit version 0 and tb1p is SegWit version 1 as discussed here). ...


3

first install the software(bitcoin-qt) by following the steps: sudo apt-add-repository ppa:luke-jr/bitcoincore sudo apt-get update sudo apt-get install bitcoin-qt run: bitcoin-qt -testnet since testnet is huge, as @Janus Troelsen suggest, there is a lighter version(signet): bitcoin-qt -signet click on the Receive button in the screenshot to get the ...


3

You can use testnet, it is a separate chain: https://en.bitcoin.it/wiki/Testnet


2

The way Signet will likely address this is to have two classes of Signet full nodes. The first class of Signet full nodes will stay on a stable Signet version and only update once the proposed soft fork is activated on mainnet. The second class of Signet full nodes will run experimental Signet versions and as a result will need to update every time a new ...


2

You could enable -fallbackfee (as darosior says) but the easiest or quickest way to resolve this is to set a fee. In this example we are setting a fee of 1 satoshis per byte. ./bitcoin-cli sendtoaddress "bc1q09vm5lfy0j5reeulh4x5752q25uqqvz34hufdl" 0.1 "" "" false true 1 sat/B If you do ./bitcoin-cli -regtest help sendtoaddress ...


2

bitcoind uses transactions it relays (and later see as mined) to estimate the feerate to set for transactions its wallet creates. On regtest, you don't relay then mine enough transactions so bitcoind's estimation buckets are not filled enough to give a reliable estimate. Without such an estimate the wallet, out of safety, prefer not to create any transaction ...


2

This is a draft answer (incomplete). To get set up on Signet ie sync the Signet chain and claim some Signet Bitcoin, follow these instructions. (You can run a Signet node in parallel with your mainnet node, ie same hardware) You now have funds at a non-P2TR (i.e. SegWit v0, bech32) Signet address. Now you need to generate a P2TR address to send funds to so ...


1

There is currently no realm byte defined for testnet and signet. At least lseed.bitcoinstats.com and lseed.darosior.ninja don't support testnet nor signet.


1

generatetoaddress doesn't actually have a restriction on which networks it operates on. You can use it on mainnet, it will just not find any blocks. The way that it is implemented is that it just tries the nonce range for a single block, and if none of those block proposals are valid, then it exits. So if the difficulty is low enough that it is possible to ...


1

You can't create blocks yourself for the global signet; it requires signatures by the parties running that signet. You can create your own signet, though, where you yourself are the signer. The tooling around this is still a work in progress, as far as I know.


1

Of course Taproot isn't activated at all so all nodes would have treated my transaction as an anyone-can-spend and my transaction would easily have made it into a block. No, the new output types for soft forks are constructed in a manner that they are non-standard for old nodes and thus do not get included in the mempool by old nodes, and therefore also not ...


1

You could enable -fallbackfee as it says in the error message but the easiest or quickest way to resolve this is to set a fee. In this example we are setting a fee of 1 satoshis per byte. ./bitcoin-cli sendtoaddress "bc1q09vm5lfy0j5reeulh4x5752q25uqqvz34hufdl" 0.1 "" "" false true 1 sat/B If you do ./bitcoin-cli -regtest help ...


1

No there isn't. Regtest is not designed to test mining ASICs and the motivation for such a RPC seems limited given regtest is for local testing. However, if you want to experiment with mining on a network with limited network hash rate you could either try mining on the default Signet administered by Kalle Alm and AJ Towns or you could set up your own custom ...


Only top voted, non community-wiki answers of a minimum length are eligible