From: Wladimir <laanwj@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
Date: Thu, 8 May 2014 09:45:02 +0200 [thread overview]
Message-ID: <CA+s+GJDm=J6-SYr4KEZ70f46E3U61Yva36a-gccRFSiT5ia2-g@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgR0CtYeLmp8pmMFvtOyqrhNgz0U-BsfBQ7QRr3dM-7J9g@mail.gmail.com>
On Thu, May 8, 2014 at 2:47 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
>
> The tor network works based on a centralized (well, in theory,
> federated) trusted directory service. (More info in
> https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=dir-spec.txt).
Thanks!
> Much of data that is not related to relay related is just generated by
> probes, e.g. semi-trusted bandwidth authorities that measure node
> performance back to the directory authorities.
Right, so there is more involved than just adding having nodes provide
measuring points, a third-party is also performing tests on the nodes.
In a way it looks similar to how the Bitcoin DNS seeds work, trying to
find good and stable nodes, although more extensive.
Wladimir
next prev parent reply other threads:[~2014-05-08 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 19:12 Jameson Lopp
2014-05-07 19:46 ` Wladimir
2014-05-07 19:57 ` Jameson Lopp
2014-05-07 20:18 ` Wladimir
2014-05-07 20:25 ` Mike Hearn
2014-05-07 20:31 ` Charlie 'Charles' Shrem
2014-05-07 21:07 ` Wladimir
2014-05-08 0:47 ` Gregory Maxwell
2014-05-08 7:45 ` Wladimir [this message]
2014-05-08 10:08 ` Mike Hearn
2014-05-08 10:32 ` Wladimir
2014-05-07 20:28 ` Nelson Castillo
2014-05-08 11:22 ` Wladimir
2014-05-07 20:35 ` Jameson Lopp
2014-05-07 21:04 ` Charlie 'Charles' Shrem
2014-05-07 19:50 ` Mike Hearn
2014-05-07 20:00 ` Jameson Lopp
2014-05-07 20:12 ` Mike Hearn
2014-05-07 19:55 ` Pavol Rusnak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+s+GJDm=J6-SYr4KEZ70f46E3U61Yva36a-gccRFSiT5ia2-g@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox