On 05/27/2014 12:39 AM, Peter Todd wrote:
> On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach
> wrote:
>> You're very quick to point at others. Especially since they run
>> software that had the time to mature for about 30 years, and the
>> protocol didn't really change since then...
>
>> T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27 May 2014 01:12:05 GMT+03:00, Andreas Schildbach
wrote:
>You're very quick to point at others. Especially since they run
>software
>that had the time to mature for about 30 years, and the protocol didn't
>really change since then...
>
>The l
You're very quick to point at others. Especially since they run software
that had the time to mature for about 30 years, and the protocol didn't
really change since then...
The last time it didn't work, the bug -- non RFC-conformance -- was on
the bitcoin seeders side. ISPs do weird things with DN
Hi all,
The first version of the Bitcoin.org Developer Documentation is now
live. The main URL (below) provides a portal to two main documents, an
overview-level guide and a more detailed reference. The portal page also
links to individual sections of the documentation and noteworthy
off-site docu
On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote:
> Thanks for looking at the issue.
>
> Unfortunately, it still fails for me:
>
> $ nslookup testnet-seed.bitcoin.petertodd.org
> Server: 127.0.1.1
> Address: 127.0.1.1#53
>
> ** server can't find testnet-seed.
>
> it: I'd be much more likely to run an experimental gateway in another
> process on a node than experimental p2p code inside my production
> bitcoinds themselves.
>
Yes, it's certainly better to do that during the development phase. However
if it does turn out to be good and valuable then it'd
6 matches
Mail list logo
