This update is not required for my client to receive full SegWit support of bitcoin network when it will be activated in the future?
For now I am using older Core version and want to know if version 0.11 will be still supported and fully compatible.
Topic: Bitcoin Core 0.13.1 Released - page 4. (Read 13211 times)
i want to ask something about pruning, how much time can pass before i need to resync again after pruning with a wallet?, what i mean is, if i have two wallet, and i sync first with both of them, then i do pruning with one, let's say the main one, and i prune the other again after one month, do i need to resync again?
That is not how pruning works. Pruning is not wallet specific. You will probably need to resync when you switch wallets, but I think it is dependent on how many days of blocks are kept when you pruned.that what i was talking about, there is a way we can know how many days pass until we need to resync again after pruning? maybe some command line?
i want to ask something about pruning, how much time can pass before i need to resync again after pruning with a wallet?, what i mean is, if i have two wallet, and i sync first with both of them, then i do pruning with one, let's say the main one, and i prune the other again after one month, do i need to resync again?
That is not how pruning works. Pruning is not wallet specific. You will probably need to resync when you switch wallets, but I think it is dependent on how many days of blocks are kept when you pruned.that what i was talking about, there is a way we can know how many days pass until we need to resync again after pruning? maybe some command line?
Ticket is open, we will see!
https://github.com/bitcoin/bitcoin/issues/9056
https://github.com/bitcoin/bitcoin/issues/9056
And again the same behavior after the 24 h Internet disconnect tonight.
I think we have to open a new ticket
I think we have to open a new ticket
I have tried since Okt. 28
And again the same behavior after the 24 h Internet disconnect tonight.
I think we have to open a new ticket
That's strange. You should open up an issue on Github. Please make sure that you properly describe your issue in the used format. I think we have to open a new ticket
And again the same behavior after the 24 h Internet disconnect tonight.
I think we have to open a new ticket
I think we have to open a new ticket
Looks like there is a bug if you have a disconnect from the internet.
Most of the german internetproviders have an automatic 24h disconnect. Im running on 0.13.1 for two days now and after every reconnect it stucks with 8 connections and on bitnodes the node is showed open but down.
restarting core solves the problem until the next reconnect.
Somebody else notes this?
Most of the german internetproviders have an automatic 24h disconnect. Im running on 0.13.1 for two days now and after every reconnect it stucks with 8 connections and on bitnodes the node is showed open but down.
restarting core solves the problem until the next reconnect.
Somebody else notes this?
It was after a disconnect I got all the problem to continue resync.
Looks like there is a bug if you have a disconnect from the internet.
Most of the german internetproviders have an automatic 24h disconnect. Im running on 0.13.1 for two days now and after every reconnect it stucks with 8 connections and on bitnodes the node is showed open but down.
restarting core solves the problem until the next reconnect.
Somebody else notes this?
Most of the german internetproviders have an automatic 24h disconnect. Im running on 0.13.1 for two days now and after every reconnect it stucks with 8 connections and on bitnodes the node is showed open but down.
restarting core solves the problem until the next reconnect.
Somebody else notes this?
Will this version resync faster then the older one?
No. This version does not contain such improvements.Quote
News: Latest stable version of Bitcoin Core: 0.13.0 [Torrent]. This is not changed yet. Do it means that you don't know if 0.13.1 is stable?
No. That has just not been updated yet. It usually takes a few days.
Will this version resync faster then the older one?
News: Latest stable version of Bitcoin Core: 0.13.0 [Torrent]. This is not changed yet. Do it means that you don't know if 0.13.1 is stable?
News: Latest stable version of Bitcoin Core: 0.13.0 [Torrent]. This is not changed yet. Do it means that you don't know if 0.13.1 is stable?
i want to ask something about pruning, how much time can pass before i need to resync again after pruning with a wallet?, what i mean is, if i have two wallet, and i sync first with both of them, then i do pruning with one, let's say the main one, and i prune the other again after one month, do i need to resync again?
That is not how pruning works. Pruning is not wallet specific. You will probably need to resync when you switch wallets, but I think it is dependent on how many days of blocks are kept when you pruned.
i want to ask something about pruning, how much time can pass before i need to resync again after pruning with a wallet?, what i mean is, if i have two wallet, and i sync first with both of them, then i do pruning with one, let's say the main one, and i prune the other again after one month, do i need to resync again?
I have problem with my Bitcoin Core, both 0.13.0 and 0.13.1. After 34 weeks processing blocks on disk I'm getting fatal error again and again. It says I have to look into debug.log but cannot find it.
By the way. when I install I got 2 shortcut, bitcoin qt and bitcoin qt -testnet. Why?
By the way. when I install I got 2 shortcut, bitcoin qt and bitcoin qt -testnet. Why?
0.13.1 (and 0.13.0) don't support MAC OS X 10.7 ... you must have an 10.8 or earlier.
Sorry, Lauda, just telling cannot install 0.13.1, so I have no debug.log.
Make your anti-virus software ignore it, and report a false detection. As said, open a thread for your own issues. When trying to install 0.13.1 my protection program tells its unsafe and delete the install file.
Your protection program is the one at fault, and you're probably using something half-baked. Bitcoin Core tends to be falsely identified by such. I have problem with my Bitcoin Core, both 0.13.0 and 0.13.1. After 34 weeks processing blocks on disk I'm getting fatal error again and again. It says I have to look into debug.log but cannot find it.
This would be thread hijacking. Create your own thread after you've found the debug.log here: Technical SupportIt's going to create a new wallet even If I add the old backup of wallet.dat in the appdata folder ?
No. If you have a wallet.dat in your Datadir, it will not create a new wallet. If I got this right , this Segregated witness soft fork is implemented but will only be activated in 15th November ?
No. That's the signaling start day. Activation will likely happen in December or later.Quote
That does that mean for lightweight wallets btw ?
Nothing special.Quote
IIRC Bitcoin Core 0.13.0 or 0.12.x added HD wallet feature , If I want to upgrade now , should I take the wallet.dat I have and make a backup of it or that wouldn't do much as the wallet became HD ?
If you have a SD wallet, it will remain SD. Only wallets created using version 0.13.0 or later are HD.It's going to create a new wallet even If I add the old backup of wallet.dat in the appdata folder ?
I have problem with my Bitcoin Core, both 0.13.0 and 0.13.1. After 34 weeks processing blocks on disk I'm getting fatal error again and again. It says I have to look into debug.log but cannot find it.
It's in the same path of your wallet.dat C:\Users\admin\AppData\Roaming\Bitcoin where admin is your username
If I got this right , this Segregated witness soft fork is implemented but will only be activated in 15th November ?
No. That's the signaling start day. Activation will likely happen in December or later.Quote
That does that mean for lightweight wallets btw ?
Nothing special.Quote
IIRC Bitcoin Core 0.13.0 or 0.12.x added HD wallet feature , If I want to upgrade now , should I take the wallet.dat I have and make a backup of it or that wouldn't do much as the wallet became HD ?
If you have a SD wallet, it will remain SD. Only wallets created using version 0.13.0 or later are HD.
If I got this right , this Segregated witness soft fork is implemented but will only be activated in 15th November ? what does that mean for lightweight wallets btw ? IIRC Bitcoin Core 0.13.0 or 0.12.x added HD wallet feature , If I want to upgrade now , should I take the wallet.dat I have and make a backup of it or that wouldn't do much as the wallet became HD and all addresses have one private key now ?
Jump to: