summaryrefslogtreecommitdiff
path: root/01/b8028bd115e7e802adacf4289cf11f084f1cc8
blob: 1437c5542a7f31365762d5039f63f7f2886397e5 (plain)
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <m@xk.io>) id 1UZlEe-0003X8-Rq
	for bitcoin-development@lists.sourceforge.net;
	Tue, 07 May 2013 16:59:28 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of xk.io
	designates 209.85.210.47 as permitted sender)
	client-ip=209.85.210.47; envelope-from=m@xk.io;
	helo=mail-da0-f47.google.com; 
Received: from mail-da0-f47.google.com ([209.85.210.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UZlEd-0003Qa-K3
	for bitcoin-development@lists.sourceforge.net;
	Tue, 07 May 2013 16:59:28 +0000
Received: by mail-da0-f47.google.com with SMTP id k13so440538dae.34
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 07 May 2013 09:59:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=x-received:date:from:to:message-id:subject:x-mailer:mime-version
	:content-type:x-gm-message-state;
	bh=1Ah5fsrlG4HS91ZUTCRJm6UFZy1Me2nrhISZ4XyWJLM=;
	b=VQHZ6oNxYMMr5alCovPNIXIYqgi4Ur4AdZyyaCpEeRBOyMfhCnqb9sYVzm6rXQWDRW
	1le6teCQNhmk2DzZPW6JcmKX0iT0idwWzQq0q6+nABX/8xPTDdeKdfaiSydrh6d4bRsA
	54qoiawx0NioOapHl5zYFsFGrIcoT29L7e+xzhxdc7hBxuU061rrIZ/O03lgsQSbn0G7
	d5xSSldXysf0mQOmvJDZy1FVtbKIDLHpNlAwvoEHwTS/mg+47jH2ulDMnnoOvIhrIVKa
	MmTa+xm0w9IVabCjNV4DdSLqJ4wOgfRw5NXrOdLUE4mvFKePujCI8KBvMJM69JKq4UFs
	zOUQ==
X-Received: by 10.66.161.227 with SMTP id xv3mr3749714pab.82.1367944638512;
	Tue, 07 May 2013 09:37:18 -0700 (PDT)
Received: from [192.168.1.4] (27-33-76-115.static.tpgi.com.au. [27.33.76.115])
	by mx.google.com with ESMTPSA id
	uf2sm28824762pbc.41.2013.05.07.09.37.16
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=RC4-SHA bits=128/128);
	Tue, 07 May 2013 09:37:17 -0700 (PDT)
Date: Wed, 8 May 2013 02:37:12 +1000
From: Max Kaye <m@xk.io>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <5E87867AB6214424BF99A460C56A1365@xk.io>
X-Mailer: sparrow 1.6.4 (build 1178)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="51892db8_4f4ef005_172"
X-Gm-Message-State: ALoCoQkw0IwqXBnhnLS27tj6wFjaHXmCi0ft2wCW5LvXy0c4uhwnwp1FKOLZaN0xttPNpWiu166N
X-Spam-Score: -0.5 (/)
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 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1UZlEd-0003Qa-K3
Subject: [Bitcoin-development] For Public Consideration: [Marketcoin | MKC]
 A P2P Trustless Cryptocoin Exchange
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, 07 May 2013 16:59:29 -0000

--51892db8_4f4ef005_172
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All, 

If any of you are interested, I've put forward a proposal for a P2P Trustless Cryptocoin Exchange. I don't have anyone around to bounce ideas off; my apologies if there's any gaping logical holes.

You can find details here:
https://bitcointalk.org/index.php?topic=198032.0

I'd really appreciate any insight any of you have on the matter. (And look forward to hopefully meeting a few of you at the conference).

Cheers,
Max

--51892db8_4f4ef005_172
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


                <div>
                    Hi All,
                </div><div><br></div><div>If any of you are interested, I=
've put forward a proposal for a P2P Trustless Cryptocoin Exchange. I don=
't have anyone around to bounce ideas off; my apologies if there's any ga=
ping logical holes.</div><div><br></div><div>You can find details here:</=
div><div><a href=3D=22https://bitcointalk.org/index.php=3Ftopic=3D198032.=
0=22>https://bitcointalk.org/index.php=3Ftopic=3D198032.0</a></div><div><=
br></div><div>I'd really appreciate any insight any of you have on the ma=
tter. (And look forward to hopefully meeting a few of you at the conferen=
ce).</div><div><br></div><div>Cheers,</div><div>Max</div>
            
--51892db8_4f4ef005_172--