1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1Rx8S6-00054U-Ac
for bitcoin-development@lists.sourceforge.net;
Tue, 14 Feb 2012 02:49:10 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=gavinandresen@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rx8S5-00049h-Jr
for bitcoin-development@lists.sourceforge.net;
Tue, 14 Feb 2012 02:49:10 +0000
Received: by wgbdr12 with SMTP id dr12so5302491wgb.10
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Feb 2012 18:49:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.137.210 with SMTP id y60mr198317wei.14.1329187743499; Mon,
13 Feb 2012 18:49:03 -0800 (PST)
Received: by 10.223.112.199 with HTTP; Mon, 13 Feb 2012 18:49:03 -0800 (PST)
Date: Mon, 13 Feb 2012 21:49:03 -0500
Message-ID: <CABsx9T3qct8zZJZtbF7p-qLhatif4ioBqWKNctHHf5=o7mSiRQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Rx8S5-00049h-Jr
Subject: [Bitcoin-development] IRC meeting Tuesday, Feb 14, 21:00 UTC
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2012 02:49:10 -0000
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
|
