Namecoin already has an id/ and a/ (alias) namespace for such use:
{ "name" : "id/pichler", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 29397 },
{ "name" : "id/pigeons", "value" : "{ bitcoin:
1BekNv7ezkx8eAjdkrUta2BTp9bbxU9LGG, bitmessage:
BM-opfhTsUKdTezPiWFHxRQtM1ZMDvj
On 5/10/2013 8:39 AM, Gavin Andresen wrote:
> Bitcoin-Qt version 0.8.2 release candidate 1 is now available from:
>http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.2/test/
>
Testnet glitch, something broke...
Fired up 0.8.2rc, and where's the coins? Where's the blocks?
On 4/28/2013 8:55 PM, Peter Todd wrote:
> On Mon, Apr 29, 2013 at 03:48:18AM +, John Dillon wrote:
>> We can build this stuff incrementally I'll agree. It won't be the case that
>> one
>> in a thousand nodes serve up the part of the chain you need overnight. So
>> many
>> I am over engineerin
On 4/9/2013 4:09 AM, Peter Todd wrote:
> On Tue, Apr 09, 2013 at 12:42:12PM +0200, Mike Hearn wrote:
>> hack by changing the protocol. Nodes can serve up blocks encrypted under a
>> random key. You only get the key when you finish the download. A blacklist
> NAK
>
> Makes bringing up a new node dep
My first concern was that I and about everyone else only has TCP/UDP
port forwarding, but at least for the first:
UDT uses UDP to transfer bulk data with its own reliability control and
congestion control mechanisms. Multiple UDT flows can share a single UDP
port, thus a firewall can open only
On 3/12/2013 5:18 AM, Jorge Timón wrote:
> A related question...some people mentioned yesterday on #bitcoin-dev
> that 0.5 appeared to be compatible with 0.8.
> Was that only for the "fatal block" and would have forked 0.8 later
> too or is it something else?
> I'm having a hard time understanding
6 matches
Mail list logo
