From within the GUI, no, and this is intentional. There is no reason to use P2PKH addresses anymore. If you need backwards compatibility, then that's what the P2SH checkbox is for.
But if you really must have P2PKH addresses, you can configure Bitcoin Core to only use them by adding addresstype=legacy to your bitcoin.conf file. If you want your change to ...
Electrum does not support bitcoin core wallet files. What you can do is dump all the private keys using bitcoin core and then import them into electrum. So first make sure that the wallet.dat file is in bitcoin core's data directory and then launch bitcoin qt, go to window menu > console and unlock your wallet:
walletpassphrase your-wallet-passphrase 300
1) How can you run a full node wallet with electrum? what do you need? Or please link me to an understandable guide for that
This probably should be a separate question.
2) Do you have to be online always or can you set it up, fund your wallet, and leave it offline for months, and just from time to time use it for transactions?
You can use it only ...
1) Which secure full node wallet implementations exist? Currently I just know of bitcoin core. Is there not any other one with a GUI?
I don't know of any others, apart from forks of Bitcoin Core like Knots. See https://bitcoin.org for an overview of various types of wallet software.
2) Can you use a Ledger device with those full node wallets?
Running a pruning node simply means enabling the prune setting.
In Bitcoin Core, that can be done either in the bitcoin.conf file by adding a line "prune=N" (where N is a number in megabytes), or through the Qt GUI in the settings screen.
Electrum is not a full node, and never downloads or verifies blocks at all, so there is nothing to prune.
There is no ...
What other full node wallet apps are available to select from for bitcoin?
See https://bitcoin.org/en/choose-your-wallet for a reasonable list
Is it mandatory to have an own server when using a full node wallet
Not really. Some wallets have an API that allows other software to interact with the wallet but the wallets are generally usable directly for ...
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-...
You need to take a look at how fee_estimates.dat is written and interpreted. Basically it's composed of:
With CURRENT being "when writing", i.e. when stopping bitcoind.
Here is the method writing the file, and here is the method reading this file (at startup). I ...
It's possible to do this externally, but it's tricky to get right and a cause of loss of funds if you do.
You need to correctly identify transactions you can spend. This is relatively trivial with P2PKH addresses, but a little more involved if using more exotic script types. You need to understand rules like transaction maturity before considering a UTXO ...
The tlv_payload is a modification to the way onion packets are created between the 1.0 version and the 1.1 version (current working version) of the BOLT specs. The (optional) feature is named var_onion_optin in BOLT#9.
In V1.0 of the spec, there was a fixed structure for sending onion payloads to hops along a route, which contained a short_channel_id, a ...
Generation of blocks uses the proof of work algorithm that includes a nonce that ensures randomness, if we could somehow recreate all these things the whole system of cryptocurrency would break down. The short answer is no.
Follow this guide.
Download Electrum and verify the signature to prove it was not modified in transit. Create a new Standard Wallet and choose "Create a new seed". Electrum will give you a seed phrase which you should write down on paper.
If using Bitcoin-Qt, click Window -> Console.
If your wallet is encrypted, use this command to decrypt it for ...
In a sense, such a command would be trusting a third party: any putative answer would be that given by whoever supplied that code to you; and it may not be trustworthy - it could tell you it was 21 million, but behind the scenes actually use, say, 42 million.
The nearest you could do would be to download the source code from a proper source and, having ...
It appears that the answer is yes. I have not fully established that it was successful, but it looks like it's headed that way. Here are the steps I followed:
Shut down the pruned node.
Edit bitcoin.conf to change pruned=10000 to pruned=0
Update the startup script to point to the new 400GB volume that already has the blocks folder on it.
Copy everything ...
So how we can calculate txn fee before signing and sending txn for external addresses?
As a reference:
P2PKH P2SH-P2WPKH P2WPKH
Input : 592 WU 364 WU 272 WU
Output : 136 WU 128 WU 124 WU
All transactions include 40 WU by default. If your transaction spends a P2SH-P2WPKH or P2WPKH ...
"fundrawtransaction" and "walletcreatefundedpsbt" are wallet RPCs. They add inputs and change outputs from your wallet to aim for a specific feerate for the transaction.
These operations inherently require the relevant wallet. Change addresses are generated by the sender's wallet, and inputs have to come from the wallet of the sender. If you don't have that ...
Well "wallet" as storage of keys should always be under your control. There are online wallets for higher convenience, but as the old saying goes "not your keys, not your bitcoin". It's probably a bad term, but I'd rather say "local (SPV) node" instead of "wallet".
When you are sending there is no problem with malicious peers as the transaction is (usually) ...
You can use scantxoutset command which was introduced in Bitcoin Core 0.17. It scans the UTXO set for any UTXOs for the address (or output script) provided. It is faster than the rescan when you import a private key.
Type help scantxoutset to see the help.
If I understand correctly you can use this command getrawtransaction to get a transaction that is in your node's mempool i.e. an unconfirmed transaction.
However, if you are looking for a transaction that has been confirmed, you'll need to know the blockhash of the block in which that transaction resides.
> bitcoin-cli getrawtransaction "...
It looks like you have your block hashes in the wrong byte order. You have them in the display byte order, but the network actually handles block hashes in the reverse byte order, the zeroes are at the end.
I think the blocks that you are getting in response are going to be the first 500 blocks of the blockchain as well.
So what's happening is that a node ...
The transaction has been cleared on the blockchain
How did you know that? Did you query the corresponding transaction on an online blockchain explorer?
If you are happy to trust third party services (like the online blockchain explorer you had used), then generally speaking, (you believed that) you have already received these bitcoins.
You just have not ...
One thing to note is when you're syncing the blockchain, you're both downloading the blockchain and also validating all of the transactions. So that is also a possible bottleneck on your end that could be causing a slow sync.
I wonder how does Bitcoin Core manage its peers? Will it disconnect with slower nodes, and then turn to faster ones?
This question ...
Prior to segwit doing this securely required carrying around enormous prior transactions.
Prior to PBST there wasn't a standard serialization that covered all the interesting use-cases.
It's been possible to offline sign for years using the CLI and many people have been doing so.
More recently this PR adds a GUI for doing this using PSBT: https://github....
The wallet itself is still downloading the block and is 3 years and 29 months behind. Does this mean I must wait until this finishes before it shows up?
Yes, in order to understand the current state of the network (which includes the transaction that you received funds in), your node will need to work through the blockchain history. Otherwise, your node ...
You can specify the wallet options multiple times.
in your bitcoin.conf will load wallet01, wallet02, wallet03.
Finally, I got the spend transaction. I signed it with another wallet and tried broadcasting it.
This wallet filled the scriptSig instead of the witness.
Here is a step-by-step P2WSH multisig I made on regtest:
Generate two addresses:
$ bcreg1 getnewaddress
$ bcreg1 getnewaddress
If you want to implement your coin selection, the only alternative to calculating the fee manually I can think of is the following:
You select which inputs you want to be used in your transaction based on your coin selection algorithm.
You then proceed to lock every input that is not the one you selected. You can get the list of all inputs through ...