Bitcoin Forum
December 06, 2016, 08:09:22 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 3 4 5 6 »  All
  Print  
Author Topic: Bitcoin version 0.3.24 released  (Read 21483 times)
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
July 08, 2011, 09:35:32 PM
 #1

Bitcoin v0.3.24 is now available for download at
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.24/

This is another bug fix release.  We had hoped to have wallet encryption ready for release, but more urgent fixes for existing clients were needed -- most notably block download problems were getting severe.  Wallet encryption is ready for testing at https://github.com/bitcoin/bitcoin/pull/352 for the git-savvy, and hopefully will follow shortly in the next release, v0.4.

Notable fixes in v0.3.24, and the main reasons for this release:

F1) Block downloads were failing or taking unreasonable amounts of time to complete, because the increased size of the block chain was bumping up against some earlier buffer-size DoS limits.
F2) Fix crash caused by loss/lack of network connection.

Notable changes in v0.3.24:

C1) DNS seeding enabled by default.
C2) UPNP enabled by default in the GUI client.  The percentage of bitcoin clients that accept incoming connections is quite small, and that is a problem.  This should help.  bitcoind, and unofficial builds, are unchanged (though we encourage use of "-upnp" to help the network!)
C3) Initial unit testing framework.  Bitcoin sorely needs automated tests, and this is a beginning.  Contributions welcome.
C4) Internal wallet code cleanup.  While invisible to an end user, this change provides the basis for v0.4's wallet encryption.

Full changelog ("git shortlog v0.3.23.."):

Dawid Spiechowicz (1):
      added polish translation

Doug Huff (1):
      Add OSX App bundle and correct build instructions to reflect reality.

Eric Hosmer (3):
      Updated Visual C++ makefile.
      Further updated Visual C++ makefile.
      Add keystore.h to makefile.vs's header list.

Gavin Andresen (3):
      Boost unit-testing framework.
      Block-chain lock-in at 134444
      Do not use comma as thousands separator

Giel van Schijndel (2):
      rpc server: send '403 Forbidden' to rejected clients
      rpc: don't send 403 when using SSL to prevent DoS

Han Lin Yap (3):
      Double check translation and improved a translation string
      Update swedish translation
      Consistent Bitcoin example address

James Burkle (1):
      Edited init.cpp to include a check that -datadir exists

Jeff Garzik (6):
      FormatFullVersion: build fix related to recent translation improvement
      doc/release-process.txt: minor updates
      CWalletTx::GetAmounts(): pass NULL for CKeyStore*, rather than false     t
      Enable DNS seeding by default.
      Bump version to 0.3.24.
      Bump OSX version to 0.3.24 (missed in previous commit)

Joerie de Gram (1):
      Fix connection failure debug output

Jordan Lewis (Cool:
      Only include irc.h when needed
      Only include db.h when we have to.
      Only included rpc.h when necessary
      Only include net.h when we have to
      Only include init.h when we have to
      Only include strlcpy.h when we have to
      Remove some globally unused headers from headers.h
      Only include certain boost headers if necessary.

Matt Corallo (Cool:
      Update translations and remove obsolete translations.
      Add new DNSSeed dnsseed.bluematt.me.
      Only use dnsseeds and static seeds when not on testnet.
      Make UPnP default on Bitcoin but not on Bitcoind.
      Give more detailed error messages for connection failure.
      Added a couple minor things to match newer build process.
      Revert "Make UPnP default on Bitcoin but not on Bitcoind."
      Enable UPnP by default on bitcoin, but not on bitcoind (on gitian)

Pieter Wuille (6):
      move wallet code to separate file
      CWallet class
      Bugfixes walletclass
      Fix segfault when creating new wallet
      Limit response to getblocks to half of output buffer size
      Fix synchronization of default key

Shane Wegner (1):
      Fix missing includes needed for Boost 1.46.

Stéphane Gimenez (1):
      Fix AddressBook syncrhonization between a CWallet and CWalletDB

Wladimir J. van der Laan (1):
      add GetTotalBlocksEstimate() function, move magic number to constant

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

4909c17a1cc025c6f6c88d036f0b487c51c510f6  bitcoin-0.3.24-linux.tar.gz
58531249230f769fdc755822b41e0f18ba59512c  bitcoin-0.3.24-src.tar.gz
d4b5425eff673551a326d5326b92a06359dc1a3d  bitcoin-0.3.24-win32-setup.exe
520aed70ee28a0a91ed49dd983639cb1fab2a93c  bitcoin-0.3.24-win32.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIVAwUBThd13todwg8tvwyoAQKnVhAAnQzWKk5HrY5eMIprWwtsFZL0VOxAV2nV
Kn8NISmYk7PtfhzRm2sf0YYr369e7NtKAzdVNTRl+9m4RwQ6HhvzrChWG3OXxueA
AYg2JkS3oXbU2p4zOQT0/0ILp7iiHGhXCrEyd3bU5KkWOJhUnV0lS3ZzsELf8sab
I5MYQsrpZ9HZUI13e1ak/E0cub2gvxl+4D5Eg7EkNP71APR1MXGGzcfF7vlDYf4/
j1JTtkrBVZU6yFi8fNUxMQ/8G/0vyWLOOoCxaSvl5u5kssbI4rklhTA+BaqE1apx
xZN9Re0KjQ8cZiLQnVG9RhJsPhWe5tJRGqnKmaKF0gDELihFw9JLBDQkeSlhkhGx
wYtOfMClTDbd2qj5+dmvIrJPmDYHpGvmEO6xPsiv0qaNMZ1X/yMd9pp7nyCYosWB
u/vcPF0i4I27SDgRZ1TCPSgJgDQ4gEwKgzO69HywJw4KSkJq5MdecJDGRqTaYaf2
QI757pBXzFF3qORECSt5QIOjV1+bUc+1pB6450OfrZ+fTMMyWGF8t9t+TMAOwqoR
E0AMx2V+g+w6AXtpar4vsh0erexissREf6g1tW5ogy21Cv91MbIGZA9lUKNeU0Np
OgYSTNd5DvlbF7VpRZemSIz9gGWayqEi0G1oBQDo6DFcjeCS0okrIWPep4o1uoYz
xhxoauT2XEM=
=hgmn
-----END PGP SIGNATURE-----


Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
1481054962
Hero Member
*
Offline Offline

Posts: 1481054962

View Profile Personal Message (Offline)

Ignore
1481054962
Reply with quote  #2

1481054962
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
supersonic3974
Member
**
Offline Offline

Activity: 70


View Profile
July 08, 2011, 09:36:42 PM
 #2

Is there a certain procedure for updating a wallet without loosing the BTC in it?
Chick
Member
**
Offline Offline

Activity: 70


View Profile
July 08, 2011, 09:37:24 PM
 #3

yay

CydeWeys
Full Member
***
Offline Offline

Activity: 154


View Profile
July 08, 2011, 09:42:25 PM
 #4

Is there a certain procedure for updating a wallet without loosing the BTC in it?

Make a backup before installing a new version just in case it doesn't work.
URSAY
Legendary
*
Offline Offline

Activity: 1708



View Profile
July 08, 2011, 09:58:18 PM
 #5

These installs seem to be getting more complex.  I'll stick with 0.3.21.  Sad
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
July 08, 2011, 10:01:16 PM
 #6

These installs seem to be getting more complex.  I'll stick with 0.3.21.  Sad

To what does this refer?

The installation procedure is unchanged since 0.3.21 (or before).

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
marcus_of_augustus
Legendary
*
Offline Offline

Activity: 2086



View Profile
July 08, 2011, 10:16:14 PM
 #7


Thanks for this Jeff.

Serge
Legendary
*
Offline Offline

Activity: 1050


View Profile
July 08, 2011, 10:33:52 PM
 #8

Nice, guess I'll be upgrading my 0.3.21 sometime soon
datguywhowanders
Member
**
Offline Offline

Activity: 112



View Profile
July 08, 2011, 10:37:38 PM
 #9

Can we get an official Mac OS X binary up on the sourceforge and Bitcoin.org?

Donations Welcome: 163id7T8KZ6MevqT86DjrBF2kfCPrQsfZE
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 08, 2011, 10:54:55 PM
 #10

thanks for the great work.
Steve
Hero Member
*****
Offline Offline

Activity: 868



View Profile WWW
July 08, 2011, 11:07:54 PM
 #11

Very nice!

(gasteve on IRC) Does your website accept cash? https://bitpay.com
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
July 08, 2011, 11:35:14 PM
 #12

Can we get an official Mac OS X binary up on the sourceforge and Bitcoin.org?

It is coming soon.  OSX builds are always delayed a day or so, because they are not integrated into our gitian build process like linux/windows.


Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Veldy
Member
**
Offline Offline

Activity: 98



View Profile
July 08, 2011, 11:41:38 PM
 #13

These installs seem to be getting more complex.  I'll stick with 0.3.21.  Sad

They are not any more complex than before, what do you think has made it "more complex"?  Just install and be done with it.  If worried about your wallet [which you should be], copy it aside, or in my case, I just take it as a good time to encrypt and back it up.  I can always recover it and it is a process I do anyway.

If you have found my post helpful, please donate what you feel it is worth: 18vaZ4K62WiL6W2Qoj9AE1cerfCHRaUW4x
datguywhowanders
Member
**
Offline Offline

Activity: 112



View Profile
July 09, 2011, 12:15:22 AM
 #14

Can we get an official Mac OS X binary up on the sourceforge and Bitcoin.org?

It is coming soon.  OSX builds are always delayed a day or so, because they are not integrated into our gitian build process like linux/windows.



Thanks Jeff!

I like to keep up with the most recent version, but I'm unfortunately not sophisticated enough to build from source on OS X. I tried, but I failed miserably.

Donations Welcome: 163id7T8KZ6MevqT86DjrBF2kfCPrQsfZE
walidzohair
Full Member
***
Offline Offline

Activity: 185


View Profile
July 09, 2011, 02:04:33 AM
 #15

should not that be pushed to the natty repos. (Ubuntu in general) to update automatically with the update manager ?
pandemic
Sr. Member
****
Offline Offline

Activity: 418


View Profile
July 09, 2011, 03:45:57 AM
 #16

So, what's the plan with this new version? send btc from old wallet into the new one? Convert the wallet.dat file?

What's the new file that we have to back up and encrypt to keep safe/secure?
error
Hero Member
*****
Offline Offline

Activity: 574



View Profile
July 09, 2011, 03:55:11 AM
 #17

So, what's the plan with this new version? send btc from old wallet into the new one? Convert the wallet.dat file?

What's the new file that we have to back up and encrypt to keep safe/secure?

Why would you have to do anything different?

15UFyv6kfWgq83Pp3yhXPr8rknv9m6581W
Alex Beckenham
Full Member
***
Offline Offline

Activity: 154


View Profile
July 09, 2011, 04:19:37 AM
 #18

Can someone complete the following line? I don't get it.

Gavin Andresen (3):
      Boost unit-testing framework.     make -f makefile.{unix,osx,mingw} test_b
      Block-chain lock-in at 134444
      Do not use comma as thousands separator     Using the comma as thousands s

haydent
Full Member
***
Offline Offline

Activity: 154



View Profile
July 09, 2011, 04:35:46 AM
 #19

mine was fine, wallet survived install

2x Gigabyte 6950 OC @ 920/450 w/ ati tray tools (1 shader modded) - 760Mhs on ozco.in 0% fee aus pool
btc: 1HS5Brzcsh7XkJn566XYbvfpa2JuBRBdss
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
July 09, 2011, 05:14:25 AM
 #20

Can someone complete the following line? I don't get it.

Gavin Andresen (3):
      Boost unit-testing framework.     make -f makefile.{unix,osx,mingw} test_b
      Block-chain lock-in at 134444
      Do not use comma as thousands separator     Using the comma as thousands s


That is referring to this git commit:

Quote
Do not use comma as thousands separator

Using the comma as thousands separator causes problems for parts of the world
where comma == decimal point.  Germans sending 0,001 bitcoins are unpleasantly
surprised when that results in 1 BTC getting sent.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Pages: [1] 2 3 4 5 6 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!