From: Michael Gronager <gronager@ceptacle•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] libcoin - fixed post Feb 20 version 0.2 bug.
Date: Fri, 24 Feb 2012 12:57:06 +0100 [thread overview]
Message-ID: <7AAF416E-57BC-4C79-949C-CD93AA3E26C8@ceptacle.com> (raw)
The bitcoin 0.2 protocol (the one with no checksums on version/verack) ended its life Feb 20th.
I had forgot to add the date check in libcoin, so after Feb 20th you might have seen some errors in the log file (and having trouble getting blocks) - the code is fixed now...
Also, there are a lot of updates for 0.6:
* New internal address classes: PubKeyHash and ScriptHash to support P2SH
* Adapted a lot of other code from the 0.6 branch
* Support for BitcoinQt: I am porting BitcoinQt to use libcoin - this required a couple of interface enhancements. More on this later...
(detail:
https://github.com/ceptacle/libcoin/commit/98531e971152d4fff41c30b14d58b9fd548b21db
)
Cheers,
Michael
reply other threads:[~2012-02-24 11:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7AAF416E-57BC-4C79-949C-CD93AA3E26C8@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox