Live data from Hacker News

Scout: Securely Locate Peers Without Central Servers

blog.bittorrent.com

1–10 of 24 posts

Re: Scout: Securely Locate Peers Without Central Servers

#5
post #4

IPFS should be looking at this. They had a number of NAT traversal issues this might help with.

IPFS dev here -- judging from a quick look, Scout uses NAT-PMP and UPnP for NAT traversal, so it basically has the same occasional NAT issues as everybody else in the P2P space. By the way, sometimes NAT issues are the fault of routers handed out by ISPs. The quality of these is often less than ideal.

(A pretty cool approach to circumventing NAT issues is a proper routed overlay network, which we plan to implement in libp2p soon: https://github.com/ipfs/notes/issues/143)

Re: Scout: Securely Locate Peers Without Central Servers

#6
post #3

Oh, I wonder if this means that Bittorrent Inc's own clients (e.g. uTorrent) are helping maintaining the DHT store by default now.

uTorrent has implemented BEP44 (storing data in the DHT) for years, as has libtorrent. Those two clients combined make up a large majority of the bittorrent DHT so BEP44 support is quite reliable now.

Re: Scout: Securely Locate Peers Without Central Servers

#7
post #6
post #3

Oh, I wonder if this means that Bittorrent Inc's own clients (e.g. uTorrent) are helping maintaining the DHT store by default now.

uTorrent has implemented BEP44 (storing data in the DHT) for years, as has libtorrent. Those two clients combined make up a large majority of the bittorrent DHT so BEP44 support is quite reliable now.

Thanks!

Re: Scout: Securely Locate Peers Without Central Servers

#8
post #3

Oh, I wonder if this means that Bittorrent Inc's own clients (e.g. uTorrent) are helping maintaining the DHT store by default now.

At least according to Wikipedia references, BitTorrent Inc's own client had mainline DHT support since version 4.2 (~2005). uTorrent seems to have added support for mainline DHT some time before the acquisition as well. There's a good torrentfreak post from the 10 year anniversary that covers the history pretty well: https://torrentfreak.com/bittorrents-dht-turns-10-years-old-...

I'm guessing that your "by default now" may actually be in regards to BitComet and the v0.60 client that upset some folk?

Besides the BEP44 implementation magila mentioned, BitTorrent Inc. also assists with the DHT by operating a public bootstrap server at router.[bittorrent|utorrent].com, and provides the source too: https://github.com/bittorrent/bootstrap-dht

Re: Scout: Securely Locate Peers Without Central Servers

#9
post #5
post #4

IPFS should be looking at this. They had a number of NAT traversal issues this might help with.

IPFS dev here -- judging from a quick look, Scout uses NAT-PMP and UPnP for NAT traversal, so it basically has the same occasional NAT issues as everybody else in the P2P space. By the way, sometimes NAT issues are the fault of routers handed out by ISPs. The quality of these is often less than ideal. (A pretty cool approach to circumventing NAT issues is a proper routed overlay network, which we plan to implement in…

I should probably also mention that even if you implement the existing NAT traversal protocols correctly, these aren't satisfying solutions. We really need that damn time machine already, the End-to-End Principle should have been an End-to-End Law.

Re: Scout: Securely Locate Peers Without Central Servers

#10
The Kademlia/Bittorrent DHT protocol still requires an initial node to bootstrap access the DHT. In Bittorrent, a set of known-good nodes is encoded into the .torrent file (or clients can use previously-discovered nodes they might happen to know about, or router.bittorrent.com as a last-resort fallback).

How does Scout bootstrap?

Post reply on HN