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
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QbRsM-0003Kq-GE
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jun 2011 06:34:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com;
helo=mail-vx0-f175.google.com;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QbRsK-000369-9P
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jun 2011 06:34:22 +0000
Received: by vxa37 with SMTP id 37so5767435vxa.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 27 Jun 2011 23:34:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.175.132 with SMTP id ca4mr9405845vdc.98.1309242854653; Mon,
27 Jun 2011 23:34:14 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.169.40 with HTTP; Mon, 27 Jun 2011 23:34:14 -0700 (PDT)
In-Reply-To: <DA6FEDE0-8C45-4416-B8BC-FDABC857A87A@heliacal.net>
References: <BANLkTi=zdn-ELG4xsVS7oyNQKO6dwtt99g@mail.gmail.com>
<DA6FEDE0-8C45-4416-B8BC-FDABC857A87A@heliacal.net>
Date: Tue, 28 Jun 2011 08:34:14 +0200
X-Google-Sender-Auth: 5r4r1tqJP2YRzHe3m99BgVu5JaI
Message-ID: <BANLkTik4m832G_C_P8+oXSt+6QA4QtpC7Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: solar <laszlo.hanyecz@heliacal.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.2 (-)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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
0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QbRsK-000369-9P
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
nathan.baulch@gmail.com
Subject: Re: [Bitcoin-development] [ANNOUNCE] BitCoinSharp
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, 28 Jun 2011 06:34:22 -0000
Sure.
On Tue, Jun 28, 2011 at 2:49 AM, solar <laszlo.hanyecz@heliacal.net> wrote:
> Great work on this guys! =C2=A0I have a small request though.. could you =
please include the recent fix to join a random #bitcoinXX channel on IRC (i=
nstead of #bitcoin)? =C2=A0It is in the c++ code that way, it's just a rand=
omly selected number from 00 to 99.
>
> Thanks,
> Laszlo Hanyecz
>
>
> On Jun 27, 2011, at 5:04 PM, Mike Hearn wrote:
>
>> This evening I'd also like to announce the BitCoinSharp project by
>> Nathan Baulch. It's big enough to deserve its own email, IMHO.
>>
>> Nathan has done a complete port of BitCoinJ into C#, thus opening the
>> world of Bitcoin up to .NET developers everywhere.
>>
>> You can browse the code here:
>>
>> =C2=A0http://code.google.com/p/bitcoinsharp/source/browse/
>>
>> Visual Studio SLN files are provided to help you get started. The
>> PingService example is a good place to start reading:
>>
>> =C2=A0http://code.google.com/p/bitcoinsharp/source/browse/src/Examples/P=
ingService.cs
>>
>> I'm hopeful that we've now covered nearly all the bases in terms of
>> languages and platforms. Everyone should be able to write interesting
>> Bitcoin apps no matter what their background or preferred toolchain.
>>
>> ------------------------------------------------------------------------=
------
>> All of the data generated in your IT infrastructure is seriously valuabl=
e.
>> Why? It contains a definitive record of application performance, securit=
y
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
|
