Pages:
Author

Topic: Bitcoin Core 0.10.0 has been released - page 2. (Read 27238 times)

full member
Activity: 224
Merit: 100
March 31, 2015, 06:43:47 AM
i don't know why but since 3 days ago my Bitcoin Core 0.10.0 wallet is not connecting to more than 8 nodes while i was having more than 30 connections before. i didn't change anything in my modem/router config.

Could you go to the "Join the network" section on https://getaddr.bitnodes.io/ and check if you are accepting incoming connections?

is anyone else having the same problem?

Not for me.

thank you for your response.
i forwarded the port 8333 to my PC and now i'm connecting to more than 8 nodes and i'm accepting other connections. don't know why that wasn't needed before and it was working flawlessly.
legendary
Activity: 1120
Merit: 1000
March 30, 2015, 12:58:08 PM
i don't know why but since 3 days ago my Bitcoin Core 0.10.0 wallet is not connecting to more than 8 nodes while i was having more than 30 connections before. i didn't change anything in my modem/router config.

Could you go to the "Join the network" section on https://getaddr.bitnodes.io/ and check if you are accepting incoming connections?

is anyone else having the same problem?

Not for me.
full member
Activity: 224
Merit: 100
March 30, 2015, 12:26:01 PM
i don't know why but since 3 days ago my Bitcoin Core 0.10.0 wallet is not connecting to more than 8 nodes while i was having more than 30 connections before. i didn't change anything in my modem/router config.
is anyone else having the same problem?
legendary
Activity: 966
Merit: 1001
March 28, 2015, 10:31:39 PM
Thanks for this.
Has been waiting for this upgrades. is this stable one?
will link my node blockchain to here.

Yes. Core 0.10 is the latest stable version.
newbie
Activity: 3
Merit: 0
March 28, 2015, 04:55:19 AM
Thanks for this.
Has been waiting for this upgrades. is this stable one?
will link my node blockchain to here.
member
Activity: 110
Merit: 10
March 21, 2015, 09:54:44 AM
[...] If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.

This is the first time you mention your wallet.dat got corrupted. Maybe a general HDD problem?

maybe when he transfer file from usb to an hdd, while the core is still running(even simply copy-paste), happened to me once

I never transferred my wallet to a usb. My guess is that my pc was rebooted while 0.10.0 was running.
legendary
Activity: 1274
Merit: 1000
March 20, 2015, 11:58:42 AM

I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/."
How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic Huh
I checked Windows Firewall Inbound Rules and verified that I have port 8333 open.
I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do Huh TIA

Now I'm on the 4th day of being frozen at block 346578.

Looks like upgrading to 0.10.0 was very premature as it freezes up. I gave up and removed all trace of the thing. I reinstalled it and will not wait another 2 days to see if it's capable of syncing up. If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.

mine has  also become corrupted somehow and reindexing the blockchain is taking up 100% of the cpu for days now
i think the older version  0.9.3 was more stable

I also had to uninstall and reinstall core after 0.10.0 and re-d/l and re-sync the entire block chain.  There was definitely some issues with it, seems this has happened to several people.  I've had no syncing issues since doing the clean re-install.
legendary
Activity: 3206
Merit: 1069
March 20, 2015, 09:41:52 AM
[...] If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.

This is the first time you mention your wallet.dat got corrupted. Maybe a general HDD problem?

maybe when he transfer file from usb to an hdd, while the core is still running(even simply copy-paste), happened to me once
legendary
Activity: 1876
Merit: 1005
March 15, 2015, 02:04:21 PM
I downloaded new version 0.10.0 core and this is the best and most advanced wallet I ever saw. Especially it opens in mini window now which can be minimized and can do other things easily . Bitcoin was and will always be 2 steps ahead they other crypto currencies.
member
Activity: 110
Merit: 10
March 14, 2015, 03:57:58 PM
[...] If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.

This is the first time you mention your wallet.dat got corrupted. Maybe a general HDD problem?

I never said my BTC wallet was corrupted. As I understand it 0.10.0 alters it when it gets converted to headers first so one cannot use a 0.10.0 wallet in 0.9.x client. I used the same wallet when I reloaded the entire blockchain which took 3 days. It now works but I will not risk being a full node and I will only open it when I have to. I've emptied it and I'm going to use my CoinBase wallet from now on.
member
Activity: 112
Merit: 10
★Bitin.io★ - Instant Exchange
March 14, 2015, 02:46:19 AM
Mine too has become corrupt and needed reindexing. Sure it didn't take as long as downloading the whole blockchain but its still a painful process. Nothing else on the HDD had any issues.
legendary
Activity: 1316
Merit: 1000
Si vis pacem, para bellum
March 13, 2015, 05:15:55 AM

I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/."
How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic Huh
I checked Windows Firewall Inbound Rules and verified that I have port 8333 open.
I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do Huh TIA

Now I'm on the 4th day of being frozen at block 346578.

Looks like upgrading to 0.10.0 was very premature as it freezes up. I gave up and removed all trace of the thing. I reinstalled it and will not wait another 2 days to see if it's capable of syncing up. If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.

mine has  also become corrupted somehow and reindexing the blockchain is taking up 100% of the cpu for days now
i think the older version  0.9.3 was more stable
legendary
Activity: 1358
Merit: 1000
https://gliph.me/hUF
March 12, 2015, 11:32:27 AM
[...] If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.

This is the first time you mention your wallet.dat got corrupted. Maybe a general HDD problem?
member
Activity: 110
Merit: 10
March 12, 2015, 11:28:05 AM

I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/."
How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic Huh
I checked Windows Firewall Inbound Rules and verified that I have port 8333 open.
I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do Huh TIA

Now I'm on the 4th day of being frozen at block 346578.

Looks like upgrading to 0.10.0 was very premature as it freezes up. I gave up and removed all trace of the thing. I reinstalled it and will not wait another 2 days to see if it's capable of syncing up. If my wallet was not corrupted by 0.10.0 I would definitely have gone back to an earlier version.
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
March 12, 2015, 06:24:37 AM
I am a technical newbie so I want to ask this: I am a bitcoin Core user, is there a way to send your bitcoins from specified address from your wallet? Not just random one in BTC-Core? I did not see that option anywhere so I am asking, also if that is not possible which other wallet has this option?

Well technically transactions have no "send from" address, but I know what you are refering to and most block explorers show it like that. You can enable "coin control" to select the input you want to spend by hand.

-> Settings -> Options -> Wallet -> check Enable coin control features -> OK

This might require a restart, not sure its been a while since I enabled it and you only have to do this once.

Now if you go to the send panel you will see a new button labeled "Inputs..." if you click it a new window will open showing the available inputs in either a long list or ordered by address ("Tree mode"). I prefer tree mode, but keep in mind that this might result in odd behaviou as change addresses are not listed as a seperate Tree branch. In your case if you want to control the "from" address list mode is probably better.

You dont have to do this. If you dont care you could just not click on the "Inputs..." Button and it will selecte them automatically as if you never had coin control enabled in the first place.


Minor bug: Date of files on windows 64 bit version says 2013 year. Otherwise, it works.

Did you download the correct file? Mine shows

Code:
‎Freitag, ‎13. ‎Februar ‎2015 18:38:10

in the signature.

I downloaded the zip from the website. Let me check now.

https://bitcoin.org/bin/bitcoin-core-0.10.0/bitcoin-0.10.0-win64.zip

Yup, date shows as 2013-06-01 for all files in the zip archive, as of this posting.

Thats odd, does that match your system time? I just downloaded the same file (copy pasted the link) and it shows the same date (2013-06-01). The hash matches the signed hash though, so its probably related to the way the files are build..?



I was refering to the setup file earlier

legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
March 12, 2015, 03:47:27 AM
Minor bug: Date of files on windows 64 bit version says 2013 year. Otherwise, it works.

Did you download the correct file? Mine shows

Code:
‎Freitag, ‎13. ‎Februar ‎2015 18:38:10

in the signature.

I downloaded the zip from the website. Let me check now.

https://bitcoin.org/bin/bitcoin-core-0.10.0/bitcoin-0.10.0-win64.zip

Yup, date shows as 2013-06-01 for all files in the zip archive, as of this posting.

member
Activity: 110
Merit: 10
March 11, 2015, 08:22:05 PM

I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/."
How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic Huh
I checked Windows Firewall Inbound Rules and verified that I have port 8333 open.
I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do Huh TIA

Now I'm on the 4th day of being frozen at block 346578.
legendary
Activity: 1288
Merit: 1000
March 11, 2015, 08:20:05 PM
I am a technical newbie so I want to ask this: I am a bitcoin Core user, is there a way to send your bitcoins from specified address from your wallet? Not just random one in BTC-Core? I did not see that option anywhere so I am asking, also if that is not possible which other wallet has this option?
member
Activity: 97
Merit: 10
March 11, 2015, 03:04:07 PM
Nice! it gets better and better...
member
Activity: 110
Merit: 10
March 11, 2015, 11:29:22 AM

I upgraded to BitCoin Core 0.10.0 64-bit Windows very shortly after it was released. I've been running a full node since it finished syncing after 2 days. I've had a couple days when it reindexed the blockchain, or something, that took a few hours but worked fine after that finished. Now it's frozen at block 346578 and will not sync up. I just reinstalled 0.10.0 and it reindexed blocks but has remained frozen at block 346578. When I check at getaddr.bitnodes.io it says my address is unreachable. I changed it to my IP address instead the address it defaulted to and it now says "23.119.56.197:8333 /Satoshi:0.10.0/."
How can it be unreachable yet I have 10 connections in and 8 out with plenty of traffic Huh
I checked Windows Firewall Inbound Rules and verified that I have port 8333 open.
I sure need to receive my BTC deposits from the last 3 days of pool mining. What can I do Huh TIA
Pages:
Jump to: