From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] IRC meeting Tuesday, Feb 14, 21:00 UTC
Date: Mon, 13 Feb 2012 21:49:03 -0500 [thread overview]
Message-ID: <CABsx9T3qct8zZJZtbF7p-qLhatif4ioBqWKNctHHf5=o7mSiRQ@mail.gmail.com> (raw)
Tomorrow, Feb 14'th at 21:00 UTC on #bitcoin-dev on Freenode IRC I'd
like to chat about:
Status of BIP 16 support (progress towards 50% hashing power).
Protocol change coming up Feb. 20 (checksums in version messages).
Duplicate coinbase issue (and requiring block height in the coinbase
as a solution).
Then when we're done talking tech we can all send each other bitcoins
with addresses that are cute Valentine's day messages...
--
--
Gavin Andresen
next reply other threads:[~2012-02-14 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 2:49 Gavin Andresen [this message]
2012-02-14 6:09 ` [Bitcoin-development] IRC meeting Tuesday, Feb 14, 21:00 UTC slush
2012-02-14 7:23 ` Wladimir
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='CABsx9T3qct8zZJZtbF7p-qLhatif4ioBqWKNctHHf5=o7mSiRQ@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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