btlink is a peer-to-peer web hosting implementation. It uses constructs provided by BitTorrent and the BitTorrent DHT to handle DNS and serve websites. It supports domain certificates, subdomains, origin isolation and CORS. btlink can be progressively integrated, starting from no user integration at all, to having users run their own private gateway on their device for maximum control, with a range of options between. The current implementation makes use of the ubiquitous HTTP(S) proxy and proxy auto-config support to extend the web experience at the system level to include native btlink handling.
btlink defines a HTTP(s) addressing scheme for BitTorrent. This means no special cases for each application: All applications on a configured device will work transparently with btlink without any changes in code, and without knowing that some domains are served from a peer-to-peer network.
btlink is the working name, due to the combination of BitTorrent, HTTP URL "links" and the plan to implement something similar to DNSLink. Alternative names might invoke something to do with swarms and webs, due to the overlap in terminology there in the use of BitTorrent and HTTP. Shelob, or the Flood for example. Less BitTorrent-specific names like distweb are an option if other backing data platforms are supported (like IPFS, or blockchains).
Dotted lines represent flows that aren't implemented yet. In some cases that may mean there are multiple paths for the same question, the dotted one is intended in the future.
flowchart TD
regularWeb[Send request to regular web]
gatewayDomain[Is gateway domain?]
subgraph user [User HTTP Client]
start[User initiates HTTP request]
checkPAC[User has proxy auto-configuration?]
btlinkTLD
dnslinkHost
proxyDomain[Host matches a proxy domain?]
proxy[Send request to proxy]
end
start --> checkPAC
checkPAC --> |No| proxyDomain
checkPAC --> |Yes| btlinkTLD
btlinkTLD ==> |No| proxyDomain
btlinkTLD[Host ends with .btlink?] -.-> |No| dnslinkHost[Domain has btlink DNSLink entry?]
dnslinkHost --> |No| proxyDomain
dnslinkHost --> |Yes| proxy
btlinkTLD --> |Yes| proxy
proxyDomain --> |No| gatewayDomain
proxyDomain --> |Yes| proxy
gatewayDomain --> |No| regularWeb
gatewayDomain --> |Yes| gateway
proxy --> proxyReceive
subgraph proxySubgraph [proxy]
proxyReceive[Proxy receives request]
proxySpecialPaths[Request path contains special proxy path?]
proxyBtlinkDomain[Request host ends in .btlink?]
proxyDnslinkHost[Host domain has DNSLink entry?]
serveProxySpecialPath[Serve special proxy path]
end
proxyReceive --> proxySpecialPaths
proxySpecialPaths --> |Yes| serveProxySpecialPath
proxySpecialPaths --> |No| proxyBtlinkDomain
proxyBtlinkDomain --> |No| proxyDnslinkHost
proxyBtlinkDomain --> |Yes| gateway
proxyDnslinkHost --> |No| gatewayDomain
proxyDnslinkHost --> |Yes| gateway
subgraph gatewaySubgraph [gateway]
gateway[Request sent to gateway]
serveBep44Value[Serve BEP44 value]
btlinkSubdomain[Resolve btlink domain schema]
gatewayResolveDnslink[Resolve DNSLink]
gatewayCheckBtlinkSubdomain[Is btlink subdomain?]
gatewayRootDomain[Is gateway or btlink root domain?]
serveGatewayRootUploader[Serve gateway root domain page]
checkSpecialTorrentPath[Does path require special handling?]
serveSpecialTorrentPath[Serve special torrent path]
gatewayServeTorrentFile[Serve torrent file over HTTP]
subgraph torrentClient ["BitTorrent client"]
fetchBep44Value[Get DHT item using BEP44]
dhtBep46Lookup
getTorrentInfo
openTorrentFileReader[Open torrent file reader]
end
end
gateway --> gatewayRootDomain --> |Yes| serveGatewayRootUploader
gatewayRootDomain --> |No| gatewayCheckBtlinkSubdomain
gatewayCheckBtlinkSubdomain --> |No| gatewayResolveDnslink --> btlinkSubdomain
gatewayCheckBtlinkSubdomain --> |Yes| btlinkSubdomain
btlinkSubdomain --> |pk| dhtBep46Lookup(Resolve salt and public key to infohash using BEP46) --> getTorrentInfo(Get info for infohash)
btlinkSubdomain --> |ih| getTorrentInfo --> checkSpecialTorrentPath --> serveSpecialTorrentPath
checkSpecialTorrentPath --> openTorrentFileReader --> gatewayServeTorrentFile
btlinkSubdomain -.-> |44| fetchBep44Value -.-> serveBep44Value
The top-level domain to trigger proxy intervention, and for general identification of btlink domain addressing (referred to as tld) was .bt. However that may be incompatible with the ccTLD of Bhutan (See issue #2). The current tld in use is btlink.
Where possible, separate domains are used to reference different torrents to provide origin isolation.
{infohash}-ih.{tld}/{torrent path schema}}
Files within a torrent are exposed via the URL path being the path components of the files join with /. Suitable headers may be included as determined. How is the info name field handled? Perhaps it is ignored, except for single-file torrents?
({salt..}[.-])?{base36(public key)}-pk.{tld}/{torrent path schema}}
Serves torrent corresponding to lookup of mutable DHT item. Salt is optional per BEP 46. This means that owners of a public key can also manage cookies for their salted subdomains (and potentially other resources that support a subdomain relationship like this). The salt may or may not be part of the same label as the public key for wildcard certificate reasons.
Fetches an immutable item from the DHT. 44 is a reference to BEP 44. The returned item is an encoded bencode value. Various path and query values might support conversion into other formats. Currently unimplemented.
Files within a torrent are exposed with a path equal to the components of the path list in the info files field joined with /. There may be additional special paths exposed within at /.btlink/ and /.well-known/ as found appropriate. Currently the info name is ignored, however for compatibility with webseeding, it may be exposed in a special directory for that purpose (possibly in /.btlink/).
Proxies can serve a dynamic PAC file from /.btlink/proxy.pac, and their CA certificate from /.btlink/rootca.pem.
Domains may link/alias into the .{tld} address scheme by use of a _btlink DNS record on the linked domain. For example chromecast.link might be hosted on btlink, by way of a _btlink.chromecast.link TXT record. The _btlink record contains a [magnet link] (or just the btlink domain) where the content will be found.
If a link record exists, it is possible to CNAME or ALIAS the parent domain to a btlink gateway to allow use by non-proxy-using clients.
Per BEP 46, magnet:?xs=urn:btpk:[ Public Key (Hex) ]&s=[ Salt (Hex) ], corresponding to the .pk.{tld} domain space.
Regular BitTorrent magnet links correspond to the .ih.{tld} domain space.
Here proxies and gateways are described separately, but it's likely that in initial implementations they will be combined. There could be good reasons to separate them for more advanced use.
flowchart TD
user --> proxy
user --> gateway
subgraph btlink proxy
proxy
gateway
end
proxy --> gateway
subgraph confluence
gateway --> client
client --> bittorrent
end
Proxies are used to transparently provide a mapping from URLs to BitTorrent without modifying HTTP client software. Support for configuring HTTP proxies is well-supported and common due to ubiquitous use on corporate and government systems, as well as by anti-censorship and privacy advocates.
Proxies route .{tld} and domains with _btlink records to a gateway. They may also expose special paths for configuration.
Proxies can set a header to tell origin servers that their clients support btlink. This means that dynamic sites can provide generic btlink URLs without explicitly selecting a public gateway as a fallback.
Gateways are HTTP servers that serve according to the Addressing schema. They will also intercept requests to domains with _btlink records and serve those via BitTorrent if possible. Gateways can run behind reverse proxies and CDNs as they serve immutable, long-lived content.
Chrome must be restarted on Windows after installing root CA certificate. You can manually re-apply proxy settings via chrome://net-internals/#proxy.
Firefox will reject certificates with wildcard domains with less than 2 fixed labels (https://bugzilla.mozilla.org/show_bug.cgi?id=1728009). It seems to require ownership information (subject O and OU fields?) on issuer and leaf certificate. It also appears to need restarting to load certificates from the system keychain. It will establish http2 connections to proxies if possible, which doesn't work.
Safari will hang on proxy CONNECT attempts if they respond with Transfer-Encoding: chunked (https://feedbackassistant.apple.com/feedback/9578066, possibly not publicly viewable). Safari does not seem to support HTTPS proxies.
Does not appear to use the system keychain on MacOS. Passing --proxy-cacert and --cacert will let you specify a btlink CA file.
- Implement a secure channel to proxies for Safari.
- See if Firefox supports name constraints on intermediate CAs.
- Separate gateways and proxies.
- Can we have a common root certificate shared by all gateways/proxies?
- Does Safari support SOCKS? Via PAC?
- Should the domain schema be collapsed so that a single wildcard certificate is sufficient?