Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UXGyt-0003Ck-15 for bitcoin-development@lists.sourceforge.net; Tue, 30 Apr 2013 20:16:55 +0000 X-ACL-Warn: Received: from masada.superduper.net ([85.119.82.91]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1UXGyr-0000tB-90 for bitcoin-development@lists.sourceforge.net; Tue, 30 Apr 2013 20:16:55 +0000 Received: from 199-83-222-22.public.monkeybrains.net ([199.83.222.22] helo=[192.168.1.119]) by masada.superduper.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UXGH8-0004vw-Lz; Tue, 30 Apr 2013 20:31:43 +0100 Message-ID: <51801C1A.7080805@superduper.net> Date: Tue, 30 Apr 2013 12:31:38 -0700 From: Simon Barber User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Andy Parkins References: <201304302027.10247.andyparkins@gmail.com> In-Reply-To: <201304302027.10247.andyparkins@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -2.9 (--) X-Spam-Score: -2.5 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1UXGyr-0000tB-90 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Fwd: Service bits for pruned nodes 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: Tue, 30 Apr 2013 20:16:55 -0000 And then the problem of what domain name to use - ideally a single name would be used so caches had the maximum chance to reuse content. To keep the network distributed perhaps the existing DNS seed mechanism could be used - a few names, each serving a random bitcoind's address. Put :8333 after the name, and enhance bitcoind to respond to HTTP and p2p caching would be used! Simon On Tue 30 Apr 2013 12:27:10 PM PDT, Andy Parkins wrote: > On Tuesday 30 April 2013 19:04:59 Jeff Garzik wrote: > >> The format currently used by bitcoind would be just fine -- >> blocks/blkNNNN.dat for raw data, size-limited well below 1GB. Just >> need to add a small metadata download, and serve the raw block files. > > That doesn't seem very generic. It's tied far too much to the current storage > format of bitcoind. > > Wouldn't it be better to add support for more bitcoin-protocol-oriented HTTP > requests? Then any client can supply the same interface, rather than being > forced to create blkNNNN.dat on the fly? > > http://bitcoind.example.com/block/BBBBBBBBBBBBBBBBBBBBBBB > http://bitcoind.example.com/tx/TTTTTTTTTTTTTTTTTTTTTTTT > http://bitcoind.example.com/block/oftx/TTTTTTTTTTTTTTTTTTT > http://bitcoind.example.com/peers > http://bitcoind.example.com/peer/nnn > > Essentially: block explorer's raw mode but in every bitcoind. The hardest > operation for light clients is finding out the block that contains a > particular transaction -- something that bitcoind already knows. > > I'd like to see support for HTTP POST/PUT of signed transactions and block > announcements too. > > > > Andy >