Topic: Bitcoin Core 0.16.0 Released (Read 8304 times)
Bitcoin Core 0.16.1 has been released: https://bitcointalksearch.org/topic/bitcoin-core-0161-released-4476057
Soo i know, or i think i know what HD wallets are, so i make a new receive address and send btc to that address. But then delete the new wallet with the new receiving address and replace with backup wallet that did not have the new receive address, would the btc i sent to the new address be in the original wallet? Seeing they both use the same seed?
Yes, but the same would be true for a non-HD wallet, because the "new" receiving address would probably already be in the keypool of the old backup copy of the wallet.
Could someone with the new receive new address be able to see the original btc balance on blockchain explore?
There is no way to for an observer to connect the different addresses in your wallet unless you help them by spending from multiple addresses at once for example.
Soo i know, or i think i know what HD wallets are, so i make a new receive address and send btc to that address. But then delete the new wallet with the new receiving address and replace with backup wallet that did not have the new receive address, would the btc i sent to the new address be in the original wallet? Seeing they both use the same seed?
Hope i made that question clear..
Icon
PS
Could someone with the new receive new address be able to see the original btc balance on blockchain explore?
Hope i made that question clear..
Icon
PS
Could someone with the new receive new address be able to see the original btc balance on blockchain explore?
I have just installed bitcoind 0.16 in Linux. How can I get the seed of the HD wallet ?
I dont have nor want bitcoin-qt, only bitcoin-cli
Use the dumpwallet RPC command. Do bitcoin-cli dumpwallet I dont have nor want bitcoin-qt, only bitcoin-cli
I have just installed bitcoind 0.16 in Linux. How can I get the seed of the HD wallet ?
I dont have nor want bitcoin-qt, only bitcoin-cli
I dont have nor want bitcoin-qt, only bitcoin-cli
This is a great news, but am a kind of person that ask a lot of questions. I want to know the principle of working of Bitcoin Core version 0.16.0. Does it entails POW
Of course, Bitcoin uses PoW. Bitcoin Core is the reference implementation for Bitcoin, it is not an altcoin.
This is a great news, but am a kind of person that ask a lot of questions. I want to know the principle of working of Bitcoin Core version 0.16.0. Does it entails POW
Is this version available for mobile?
No, Bitcoin Core is not a mobile application. What happen if send BTC from legacy address to SegWit address?
The typical thing happens, your Bitcoin are transferred from a legacy address to a Segwit address. The address types really don't matter; the network doesn't care and such transactions are possible due to the soft forking nature of Segwit. You can even do it the other way around, segwit address to legacy address. It doesn't matter.
Hi, Thanks for info.
I will update bitcoinnode on my vps ubuntu.
SegWit addres - default..
Dear friends adk me:
What happen if send BTC from legacy address to SegWit address?
I will update bitcoinnode on my vps ubuntu.
SegWit addres - default..
Dear friends adk me:
What happen if send BTC from legacy address to SegWit address?
On one on our computers, on which we use Bitcoin Core, we are behind a NAT. Before 0.16, we had 8 incoming connections at most, but lately, we're seeing 16 incoming connections. Certainly speed things up. Thank you, I guess? Is this a documented new feature?
There was no such change that does that. Seeing your incoming connection count increase is normal behavior.
On one on our computers, on which we use Bitcoin Core, we are behind a NAT. Before 0.16, we had 8 incoming connections at most, but lately, we're seeing 16 incoming connections. Certainly speed things up. Thank you, I guess? Is this a documented new feature?
i got a question, can i add 2 datapaths to the config so i could store 2 copies of the blockchain in 2 difference locations from 1 node thats running?
No, you cannot do that.
i got a question, can i add 2 datapaths to the config so i could store 2 copies of the blockchain in 2 difference locations from 1 node thats running?
Icon
Icon
No noticeable performance differences from 0.15.1 on Win7 x64 machine with overclocked i7-4700MQ CPU, 8GB RAM and 256GB SSD. Running with block pruning enabled. And I am really sensitive to any performance drops, like I am able to distinguish between RAM running at stock speeds vs. XMP profile loaded and timings tightened. So I suspect the problem is due to blockchain maintenance or some other thing going on.
Sure, there's no reason you can not. You can use the connection instead of the addnode to ensure that you are connected to your local node and synchronized only from that node.
got a question, can i addnode= from local LAN that's running a full node to my spv wallet to sync from alot faster then say using the internet? Reason i run 2 copies is i hate copying that 150 gb of data over my network ~ 30 mins to backup the entire blockchain 
Icon
yes you can! Icon
Will Bitcoin Core adopt Lightning Network?
It is. The press reported mid of march that already 1000 mainnet nodes are ready for the lightning network. Forgive me my critics, but i think a lot users except too much from the lighting network. Since it transforms the scalability problem into a liquidity problem, it has a really limited use case. But yes, it gets support.
Hi all!
I am trying to rescue some BTCs from "wallet.dat corrupt, salvage failed"... I have tried many different things without success. Pywallet, for example, doesn't find anything at all in this wallet.dat. But it found some keys in another wallet.dat...
Please make a post in tech support, not here. Support requests are off topic for this thread. I am trying to rescue some BTCs from "wallet.dat corrupt, salvage failed"... I have tried many different things without success. Pywallet, for example, doesn't find anything at all in this wallet.dat. But it found some keys in another wallet.dat...
Hi all!
I am trying to rescue some BTCs from "wallet.dat corrupt, salvage failed"... I have tried many different things without success. Pywallet, for example, doesn't find anything at all in this wallet.dat. But it found some keys in another wallet.dat...
Anyway, now I'm trying to take a clear, unmodified copy of wallet.dat which is corrupted from the Bitcoin Core's point of view and try to -salvagewallet it.
Here is the log:
Why can't Bitcoin Core can't simply rename wallet.dat? Under Windows there is completely same problem...
Here are all the permissions and users:
How to make a -salvagewallet option work as it should?
p.s. even when I start bitcoind without GUI witl a -salvagewallet option, even when I start it under sudo - it still can't rename wallet.dat...
I am trying to rescue some BTCs from "wallet.dat corrupt, salvage failed"... I have tried many different things without success. Pywallet, for example, doesn't find anything at all in this wallet.dat. But it found some keys in another wallet.dat...
Anyway, now I'm trying to take a clear, unmodified copy of wallet.dat which is corrupted from the Bitcoin Core's point of view and try to -salvagewallet it.
Here is the log:
Code:
2018-04-25 05:36:49 Bitcoin Core version v0.16.0 (release build)
2018-04-25 05:36:49 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-04-25 05:36:50 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-04-25 05:36:50 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-04-25 05:36:50 WalletParameterInteraction: parameter interaction: -salvagewallet=1 -> setting -rescan=1
2018-04-25 05:36:50 Using the 'sse4' SHA256 implementation
2018-04-25 05:36:50 Using RdRand as an additional entropy source
2018-04-25 05:36:50 Default data directory /home/kazna/.bitcoin
2018-04-25 05:36:50 Using data directory /home/kazna/.bitcoindata
2018-04-25 05:36:50 Using config file /home/kazna/.bitcoindata/bitcoin.conf
2018-04-25 05:36:50 Using at most 125 automatic connections (1024 file descriptors available)
2018-04-25 05:36:50 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-04-25 05:36:50 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-04-25 05:36:50 Using 2 threads for script verification
2018-04-25 05:36:50 Using wallet directory /home/kazna/.bitcoindata
2018-04-25 05:36:50 init message: Пpoвepкa кoшeлькa(oв) ...
2018-04-25 05:36:50 scheduler thread start
2018-04-25 05:36:50 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-04-25 05:36:50 Using wallet wallet.dat
2018-04-25 05:36:50 CDBEnv::Open: LogDir=/home/kazna/.bitcoindata/database ErrorFile=/home/kazna/.bitcoindata/db.log
2018-04-25 05:36:50 Failed to rename wallet.dat to wallet.dat.1524634610.bak
2018-04-25 05:36:50 Shutdown: In progress...
2018-04-25 05:36:50 scheduler thread interrupt
2018-04-25 05:36:50 Shutdown: done
2018-04-25 05:36:49 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-04-25 05:36:50 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-04-25 05:36:50 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-04-25 05:36:50 WalletParameterInteraction: parameter interaction: -salvagewallet=1 -> setting -rescan=1
2018-04-25 05:36:50 Using the 'sse4' SHA256 implementation
2018-04-25 05:36:50 Using RdRand as an additional entropy source
2018-04-25 05:36:50 Default data directory /home/kazna/.bitcoin
2018-04-25 05:36:50 Using data directory /home/kazna/.bitcoindata
2018-04-25 05:36:50 Using config file /home/kazna/.bitcoindata/bitcoin.conf
2018-04-25 05:36:50 Using at most 125 automatic connections (1024 file descriptors available)
2018-04-25 05:36:50 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-04-25 05:36:50 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-04-25 05:36:50 Using 2 threads for script verification
2018-04-25 05:36:50 Using wallet directory /home/kazna/.bitcoindata
2018-04-25 05:36:50 init message: Пpoвepкa кoшeлькa(oв) ...
2018-04-25 05:36:50 scheduler thread start
2018-04-25 05:36:50 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-04-25 05:36:50 Using wallet wallet.dat
2018-04-25 05:36:50 CDBEnv::Open: LogDir=/home/kazna/.bitcoindata/database ErrorFile=/home/kazna/.bitcoindata/db.log
2018-04-25 05:36:50 Failed to rename wallet.dat to wallet.dat.1524634610.bak
2018-04-25 05:36:50 Shutdown: In progress...
2018-04-25 05:36:50 scheduler thread interrupt
2018-04-25 05:36:50 Shutdown: done
Why can't Bitcoin Core can't simply rename wallet.dat? Under Windows there is completely same problem...
Here are all the permissions and users:
How to make a -salvagewallet option work as it should?
p.s. even when I start bitcoind without GUI witl a -salvagewallet option, even when I start it under sudo - it still can't rename wallet.dat...
Jump to: