Bitcoin Forum
April 24, 2014, 01:09:37 AM *
News: Due to the OpenSSL heartbleed bug, changing your forum password is recommended.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Version 0.5.4 released  (Read 729 times)
Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 16, 2012, 01:21:02 AM
 #1

Bitcoin version 0.5.4 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.4/
NOTE: 0.5.4rc3 is being renamed to 0.5.4 final with no changes.

This is a bugfix-only release in the 0.5.x series, plus a few protocol updates.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

Stable source code is hosted at Gitorious:
  http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.4#.tar.gz

PROTOCOL UPDATES

  • BIP 16: Special-case "pay to script hash" logic to enable minimal validation of new transactions.
  • Support for validating message signatures produced with compressed public keys.

BUG FIXES

  • Build with thread-safe MingW libraries for Windows, fixing a dangerous memory corruption scenario when exceptions are thrown.
  • Fix broken testnet mining.
  • Stop excess inventory relay during initial block download.
  • When disconnecting a node, clear the received buffer so that we do not process any already received messages.
  • Yet another attempt at implementing "minimize to tray" that works on all operating systems.
  • Fix Bitcoin-Qt notifications under Growl 1.3.
  • Increase required age of Bitcoin-Qt's "not up to date" status from 30 to 90 minutes.
  • Implemented missing verifications that led to crash on entering some wrong passphrases for encrypted wallets.
  • Fix default filename suffixes in GNOME save dialog.
  • Make the "Send coins" tab use the configured unit type, even on the first attempt.
  • Print detailed wallet loading errors to debug.log when it is corrupt.
  • Allocate exactly the amount of space needed for signing transactions, instead of a fixed 10k buffer.
  • Workaround for improbable memory access violation.
  • Check wallet's minimum version before trying to load it.
  • Remove wxBitcoin properly when installing Bitcoin-Qt over it. (Windows)
  • Detail reorganization information better in debug log.
  • Use a messagebox to display the error when -server is provided without configuring a RPC password.
  • Testing suite build now honours provided CXXFLAGS.
  • Removed an extraneous line-break in mature transaction tooltips.
  • Fix some grammatical errors in translation process documentation.



Thanks to everybody who contributed code or helped test this release:

Luke Dashjr
Pieter Wuille
Wladimir J. van der Laan
Gavin Andresen
Matt Corallo
Philip Kaufmann
Alistair Buxton
Joel Kaartinen
Patrick Schneider
Vegard Nossum

1398301777
Hero Member
*
Offline Offline

Posts: 1398301777

View Profile Personal Message (Offline)

Ignore
1398301777
Reply with quote  #2

1398301777
Report to moderator
Unbeatable Service & Product Support
Grab Your Miners at GAWMiners.com
Order Before April 25th to receive
Double your Hashing Power for 1 week!

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1398301777
Hero Member
*
Offline Offline

Posts: 1398301777

View Profile Personal Message (Offline)

Ignore
1398301777
Reply with quote  #2

1398301777
Report to moderator
Etlase2
Hero Member
*****
Offline Offline

Activity: 756


View Profile

Ignore
April 16, 2012, 01:31:39 AM
 #2

Quote
Support for validating message signatures produced with compressed public keys.

Is this referring to ECDSA signatures that have the public key encoded in them so that the public key is not necessary? Or just some compression scheme for ECDSA? I thought most implementations of ECDSA already employed public key compression.

Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 16, 2012, 01:36:35 AM
 #3

Quote
Support for validating message signatures produced with compressed public keys.

Is this referring to ECDSA signatures that have the public key encoded in them so that the public key is not necessary? Or just some compression scheme for ECDSA? I thought most implementations of ECDSA already employed public key compression.
Bitcoin didn't use public key compression until 0.6; this just adds the minimum glue required to verify these 0.6-made signatures on text messages with the JSON-RPC "verifymessage" method.

Pages: [1]
  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!