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, ...
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 ...
No, there does not such thing as initialfreecoins=10000000. However mining on regtest is not resource hungry and nearly instant. It's the only way to get coins.
To get coins on regtest you first need a address to mine those coins to. An address can be created with
bitcoin-cli -regtest getnewaddress.
To mine and payout to this address use with <address&...
Regtest and testnet are different networks. They are not compatible with each other.
Regtest is a private local network which is used solely for testing. It is primarily used for the regression tests, hence the name regtest.
Testnet is the public testing network which is very similar to mainnet, the main network. It has a different genesis block and has ...
accounts method was deprecated in v0.17 and was removed since v0.18. accounts was replaced by label and it provides more flexibility as compared to before such as setting label on any address, not just receiving address. It also irons out issues raised in the past. If you are used to using accounts to mimic separate wallets, you now have an option to use ...
Addresses are not public keys. You cannot give createmultisig addresses because it cannot know what public keys your addresses refer to, if any. To get the public keys, you need to first do getaddressinfo <address>. That will give you a pubkey you can give to createmultisig.
I want to know why the two tools are giving different results
Bitcoin Core uses hardened derivation to derive child private keys from the master private key. You can check the embedded link for more details, but in summary it means that the software uses parent private keys within the hash function to generate child private keys. This compares to non-...
the problem is in your call of charged there you are passing the argument --ln-path ~/.lightning assuming that you run lightning in your home directory thus you have to set ln-path to /tmp/l1-regtest/.
Now you say that this also did not work. So before I give you a solution let me explain what is actually going on. charged talkes to lightningd via an rpc-...
Since you say you are changing your OS clock, I am assuming you are using Bitcoin Core's built in miner for regtest. This miner will try to not produce invalid blocks.
To avoid the time-too-old failure, it will take the maximum between the median time + 1, and the network adjusted time (which is basically OS time). So when you set the clock too far back, it ...
I downloaded the bitcoin core source code,
changed the regtest node address parameters to be like the mainnet in the file src/chainparams.cpp.
Then compiled it, run the node on regtest and it worked like magic!
The createmultisig RPC takes as input public keys, not addresses. As you created those addresses yourself, their public keys are in your wallet. createmultisig however is a utility RPC (which operates independently of the wallet), so it has no access to that information.
You can call the getaddressinfo wallet RPC on those addresses to obtain their public ...
I don't know the listaccounts, getaccount and setaccount commands inside the Bitcoin core 18.1.
I think you have used the wrong commands with the bitcoin 18.1, perhaps the equivalents are:
listaccounts -> getwalletinfo
setaccount -> importaddress
But before you use this command look the official documentation rpc framework
The issue is public key compression, as noted in your edit. The original code does not handle compressed public keys.
#here we retrieve the public key data generated from the supplied private key ...
The error gets resolved when I use OP_10 instead of 030a0000 to push the number 10 on the stack.
It appears that the bitcoin optimizes the size of the scripts. So to push any number from 2 to 16, OP_2 - OP_16 should be used and for numbers greater than 16 we should give minimum required bytes in the script.
OP_10 (5a) -> Correct
01 0a -> non-...
Simnet is only available for btcd (bitcoin node) and lnd (lightning node) afaik, while regtest is also available for bitcoind (bitcoin node), lnd and eclair (lightning nodes). The two modes are similar, according to documenation of LND:
Simnet is similar to regtest in that you'll be able to instantly mine blocks as needed to test lnd locally
Both also ...