Topic: Bitcoin Core 0.9.2.1 has been released - page 2. (Read 27416 times)
Nice software, thanks so much.
first release which I used was 0.3.21 so thank you all for your ongoing hard work on this exciting piece of software.
Thanks to everyone who contributed to this release:
- Addy Yeow
- Altoidnerd
- Andrea D'Amore
- Andreas Schildbach
- Bardi Harborow
- Brandon Dahler
- Bryan Bishop
- Chris Beams
- Christian von Roques
- Cory Fields
- Cozz Lovan
- daniel
- Daniel Newton
- David A. Harding
- ditto-b
- duanemoody
- Eric S. Bullington
- Fabian Raetz
- Gavin Andresen
- Gregory Maxwell
- gubatron
- Haakon Nilsen
- harry
- Hector Jusforgues
- Isidoro Ghezzi
- Jeff Garzik
- Johnathan Corgan
- jtimon
- Kamil Domanski
- langerhans
- Luke Dashjr
- Manuel Araoz
- Mark Friedenbach
- Matt Corallo
- Matthew Bogosian
- Meeh
- Michael Ford
- Michagogo
- Mikael Wikman
- Mike Hearn
- olalonde
- paveljanik
- peryaudo
- Philip Kaufmann
- philsong
- Pieter Wuille
- R E Broadley
- richierichrawr
- Rune K. Svendsen
- rxl
- shshshsh
- Simon de la Rouviere
- Stuart Cardall
- super3
- Telepatheic
- Thomas Zander
- Torstein Husebø
- Warren Togami
- Wladimir J. van der Laan
- Yoichi Hirai
Thanks to everyone in the core team. Tip sent to op.
Hasnt this core been out for 34 decades already?
Next core 0.9.3 is already in RC2: https://bitcoin.org/bin/0.9.3/test/
Hasnt this core been out for 34 decades already?
Turns out my ISP had suddenly blocked port 8333. The addnode worked with a nonstandard port. Other alt coin wallets work just fine so I guess they use a different port. In future, it seems like a good idea to add nodes that have non-standard ports for the bitcoin default node list, to prevent connection errors. Also this would makes it more difficult for ISP's to censor bitcoin traffic.
ISP? or some crappy antivirus software?
on emule P2P network, for example ...
Code:
ed2k://|file|bitcoin-0.8.6-win32-setup.exe|11687960|6AA253134E3BE22C1D8FF7B2357D63E7|h=3WTJIMSY5C2XXXFM2YVR642C2HLSJZKW|/
ed2k://|file|bitcoin-0.9.0-win32-setup.exe|11219184|EB11AE4949129FEF4AC624AA83947CD9|h=IX5S7CHS2O6Y46EXYP7I5RJDU627HDHD|/
ed2k://|file|bitcoin-0.9.0-win64-setup.exe|12016968|D516AB3E06A41FF20BBAC7485D4AD8DB|h=A63WHMI2KRSKOWLK3ACREMFN66RQPZPV|/
ed2k://|file|bitcoin-0.9.1-win32-setup.exe|11217912|C0648D693B36DA98F086441808B47F28|h=5KVBWJX2DEQ27XSZPNMQUUP4NR42FZMZ|/
ed2k://|file|bitcoin-0.9.1-win64-setup.exe|12016520|C7DC589CE8A1E712FF992B2A7DBF0FEB|h=NSRNIB2TG4GYNR3VMIBQVELL654IMS7S|/
ed2k://|file|bitcoin-0.9.2.1-win32-setup.exe|11407544|CD151F833E4CFC8179E5A7B61902EFE7|h=XZBI6CI2GSNW3MT3R2KN75RYASG4UEWO|/
ed2k://|file|bitcoin-0.9.2.1-win64-setup.exe|12212672|43D6D668EB0FA1C8BF1387FBE4B17225|h=HXZBAF5SZJA63R35JQNBURFLY53YEMAG|/
why is bitcoin.org down right now?
where else can I download the bitcoin core wallet?
where else can I download the bitcoin core wallet?
Looks like linux statically built binary bitcoin-qt has no compatibility with Centos 6.5 Qt
Code:
bin/bitcoin-qt: symbol lookup error: bin/bitcoin-qt: undefined symbol: _ZN10QTextCodec11validCodecsEv
^ Thank you for the link. Just found this bit of info from it, which I just noticed in the OP as well 
Downgrading warnings
The ‘chainstate’ for this release is not always compatible with previous releases, so if you run 0.9 and then decide to switch back to a 0.8.x release you might get a blockchain validation error when starting the old release (due to ‘pruned outputs’ being omitted from the index of unspent transaction outputs).
Running the old release with the -reindex option will rebuild the chainstate data structures and correct the problem.
Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan the blockchain for missing spent coins, which will take a long time (tens of minutes on a typical machine).
Downgrading warnings
The ‘chainstate’ for this release is not always compatible with previous releases, so if you run 0.9 and then decide to switch back to a 0.8.x release you might get a blockchain validation error when starting the old release (due to ‘pruned outputs’ being omitted from the index of unspent transaction outputs).
Running the old release with the -reindex option will rebuild the chainstate data structures and correct the problem.
Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan the blockchain for missing spent coins, which will take a long time (tens of minutes on a typical machine).
Why are the two core versions not compatible with the same database?
Because things change in beta software.
https://bitcoin.org/en/release/v0.9.0
I've used this new 0.9.2.1 version for almost 2 months now. I accidentally opened up 0.8.6, and now when I open up the 0.9.2.1, all the blocks have to be reindexed which will take hours. I can't use Amory either, until all the blocks are reindexed 
Why are the two core versions not compatible with the same database?
Why are the two core versions not compatible with the same database?
Thank you for the great work
there is something else you can do I guess , taking off the download of Blockchain like Multibit .. because it takes for ever ... really !
there is something else you can do I guess , taking off the download of Blockchain like Multibit .. because it takes for ever ... really !
all P2P client is always in development since ... 15 years.
P2P is not a enterprise.
P2P work from alpha version to beta version ... flawless.
development take care of the "pollution" in network and cosmetics tricks usually.
development change critical fault.
version is marketing, no a "indicator" of progress.
P2P is not a enterprise.
P2P work from alpha version to beta version ... flawless.
development take care of the "pollution" in network and cosmetics tricks usually.
development change critical fault.
version is marketing, no a "indicator" of progress.
work , thanks
This is still in beta
so when the final version came out ??
This is still in beta
so when the final version came out ??
I rolled back as this hangs intermittently on OSX 10.9.4
Its like it sleeps..... And yes Prevent App Nap is ticked
I like the skinny font though.
Its like it sleeps..... And yes Prevent App Nap is ticked
I like the skinny font though.
is there any significant update??? 
OSX version is finally available
Maybe I'll tell my friends to be this good news
Thank you developer
Maybe I'll tell my friends to be this good news
Thank you developer
If you have backed up your wallet file once wild that be enough or so you have so it regularly and why?
It would be enough only if you nearly stop to send BTC from your wallet.
The problem is the so named "change" and the fact that the wallet has only a limited number of pregenerated priv-key/addresses for changes.
At the end (after 100 transactions if I well remember), you will receive your changes on new addresses that aren't saved on your backup copy.
https://en.bitcoin.it/wiki/Change
If you have backed up your wallet file once wild that be enough or so you have so it regularly and why?
Jump to: