From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1T0uUK-0007cU-R6 for bitcoin-development@lists.sourceforge.net; Mon, 13 Aug 2012 13:15:20 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f53.google.com; Received: from mail-wg0-f53.google.com ([74.125.82.53]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1T0uUI-0001Tp-Jb for bitcoin-development@lists.sourceforge.net; Mon, 13 Aug 2012 13:15:20 +0000 Received: by wgbfm10 with SMTP id fm10so2608453wgb.10 for ; Mon, 13 Aug 2012 06:15:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.94.164 with SMTP id dd4mr18535542wib.1.1344863712433; Mon, 13 Aug 2012 06:15:12 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.139.134 with HTTP; Mon, 13 Aug 2012 06:15:12 -0700 (PDT) In-Reply-To: <5028AFBE.8070104@justmoon.de> References: <5028AFBE.8070104@justmoon.de> Date: Mon, 13 Aug 2012 15:15:12 +0200 X-Google-Sender-Auth: xxKhldPI29nXnWT0_Mak3-B26t0 Message-ID: From: Mike Hearn To: Stefan Thomas Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.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 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 X-Headers-End: 1T0uUI-0001Tp-Jb Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] BIP: Custom Services X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2012 13:15:20 -0000 I think it's pretty reasonable, although people will want to use node flags to get into the addr broadcasts anyway. That said, I suspect (based on previous discussions) that there would be quite some pushback against putting extra functionality into the core Bitcoin network. Most likely people will re-use the code with different peer discovery seeds and bootstrap similar but unrelated P2P networks for doing new applications. For instance, what if we want to do the language translation app I've talked about a few times before? You need a way to floodfill broadcast invalid transactions to interested parties. The pubsub mechanism in the Bitcoin protocol was an interesting way to do that, but I think it got removed. To broadcast to interested nodes now, you'd have to find them via addr broadcasts and then connect directly. And if you're going to do that, you may as well just form an entirely independent network. More elaboration of the use cases might therefore be useful.