<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DHT on Skycoin Blog</title><link>https://blog.theskywirenetwork.net/tags/dht/</link><description>Recent content in DHT on Skycoin Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.theskywirenetwork.net/tags/dht/index.xml" rel="self" type="application/rss+xml"/><item><title>Skywire DHT: Decentralizing the Discovery Layer</title><link>https://blog.theskywirenetwork.net/posts/skywire-dht-decentralizing-discovery/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.theskywirenetwork.net/posts/skywire-dht-decentralizing-discovery/</guid><description>&lt;p&gt;Skywire has always depended on centralized HTTP discovery services. When a visor wants to find another visor&amp;rsquo;s DMSG servers, it queries &lt;code&gt;dmsg-discovery&lt;/code&gt;. When it wants to know what transports are available, it queries &lt;code&gt;transport-discovery&lt;/code&gt;. When it wants to find a VPN or proxy, &lt;code&gt;service-discovery&lt;/code&gt;. These services are reliable and fast, but they&amp;rsquo;re single points of failure and they concentrate load on the deployment operator.&lt;/p&gt;
&lt;p&gt;Over the past week, we&amp;rsquo;ve been building and deploying a Kademlia DHT that will gradually replace these centralized services with peer-to-peer discovery. The production deployment is transitioning from the source of truth to a bootstrapping point and network observer.&lt;/p&gt;</description></item></channel></rss>