summaryrefslogtreecommitdiff
path: root/4e/4ecb1124a23d9e5b593c3a4ee8242a02024845
blob: edbe4008f0d7ce83e7abc9ed3770d1c04b5fc9d4 (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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@bitpay.com>) id 1XFiQt-00025L-Ou
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Aug 2014 11:34:03 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.223.179 as permitted sender)
	client-ip=209.85.223.179; envelope-from=jgarzik@bitpay.com;
	helo=mail-ie0-f179.google.com; 
Received: from mail-ie0-f179.google.com ([209.85.223.179])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XFiQs-000662-UP
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Aug 2014 11:34:03 +0000
Received: by mail-ie0-f179.google.com with SMTP id rl12so6280291iec.38
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 08 Aug 2014 04:33:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=wN+AncISkwUtywrrUioliMU6zg8yefUZ2Kk8dXl9MHg=;
	b=baFL3kGuurVSD+KCugP8uSQeZWA8088LJ5C8P5aGXjE/9AacYju24hP+NIpKeqbvkX
	DTmKZbEg3Dj0JNlIPVHF/Xk4btRnSywR2CI3M9yYEStDjtVHWVEj63zj2hUMSSrmfz2o
	KFMl+DUw8q94Wms6d0o55BDDBCDXlfog7aJ2E7yHroF8jOH3zL7Dm2K/VqNhP5/up3Ah
	5WaONqDP9ExtpCUSEXLAPeg2c+7T07dNrwx269pkLo2nFVyPSjyJVodD5b/ElJjs5TLL
	c78M0P/sBRFBZWOwJ9IJUWHh6EqwPOO6cplUjVtsMG/Cuw9+nfOTw9KAL7QMQqAdSUFq
	Q+bw==
X-Gm-Message-State: ALoCoQlMj2GAsSzZYSp0rHKG45WU/MGtiooPQSHOl1EeKWsgUo049TWNJlljDxAzjiJ4XvcvWpXc
X-Received: by 10.42.48.197 with SMTP id t5mr11572363icf.11.1407497637662;
	Fri, 08 Aug 2014 04:33:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.10.78 with HTTP; Fri, 8 Aug 2014 04:33:37 -0700 (PDT)
In-Reply-To: <CANEZrP245242JYDBBo72XVmKgEBO96QPjcJi8Jy2Dm_r90n1Bw@mail.gmail.com>
References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
	<CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com>
	<CA+s+GJD+9qpwFcVfHOCCsFYjmk7A0V=65vG-7jJ6D7jj4Pi_7g@mail.gmail.com>
	<CANEZrP245242JYDBBo72XVmKgEBO96QPjcJi8Jy2Dm_r90n1Bw@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 8 Aug 2014 07:33:37 -0400
Message-ID: <CAJHLa0N3xx1QZ==iSLYNsdgkBGoqN34+4eVtukkjn+3SrDhC7A@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
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 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: 1XFiQs-000662-UP
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related
	services
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: Fri, 08 Aug 2014 11:34:03 -0000

n Fri, Aug 8, 2014 at 6:01 AM, Mike Hearn <mike@plan99.net> wrote:
> What's wrong
> with the existing mechanism exactly?

It would be wrong to add NODE_INSIGHT, NODE_ELECTRUM_SERVER, etc. bits
even though you do have useful bitcoin-related APIs that exist on the
same system as bitcoind.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/