HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
UrkelLabs
rsd
Rust2019–2020
UrkelLabs / rsd

rsd

A Handshake Daemon implementation in Rust.

3Distinct people
4Mentions
0Explicit recommenders
61GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A Handshake Daemon implementation in Rust.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week4 dated mentions

Observed mentions: 2019-09-18 01:47:40 UTC to 2020-03-30 00:16:38 UTC. Weeks start Monday, UTC.

012019-09-16 00:00:00 UTC to 2019-09-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 162019-09-23 00:00:00 UTC to 2019-09-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-09-30 00:00:00 UTC to 2019-10-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-07 00:00:00 UTC to 2019-10-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-14 00:00:00 UTC to 2019-10-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-21 00:00:00 UTC to 2019-10-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-28 00:00:00 UTC to 2019-11-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-04 00:00:00 UTC to 2019-11-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-11 00:00:00 UTC to 2019-11-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-18 00:00:00 UTC to 2019-11-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-25 00:00:00 UTC to 2019-12-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-02 00:00:00 UTC to 2019-12-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-09 00:00:00 UTC to 2019-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-16 00:00:00 UTC to 2019-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-23 00:00:00 UTC to 2019-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 232019-12-30 00:00:00 UTC to 2020-01-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-06 00:00:00 UTC to 2020-01-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-13 00:00:00 UTC to 2020-01-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-20 00:00:00 UTC to 2020-01-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-27 00:00:00 UTC to 2020-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-03 00:00:00 UTC to 2020-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-10 00:00:00 UTC to 2020-02-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-02-17 00:00:00 UTC to 2020-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-24 00:00:00 UTC to 2020-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-02 00:00:00 UTC to 2020-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-09 00:00:00 UTC to 2020-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-16 00:00:00 UTC to 2020-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-23 00:00:00 UTC to 2020-03-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-03-30 00:00:00 UTC to 2020-04-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 30

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 162019-09-16 00:00:00 UTC2019-09-23 00:00:00 UTC101
Sep 232019-09-23 00:00:00 UTC2019-09-30 00:00:00 UTC000
Sep 302019-09-30 00:00:00 UTC2019-10-07 00:00:00 UTC000
Oct 72019-10-07 00:00:00 UTC2019-10-14 00:00:00 UTC000
Oct 142019-10-14 00:00:00 UTC2019-10-21 00:00:00 UTC000
Oct 212019-10-21 00:00:00 UTC2019-10-28 00:00:00 UTC000
Oct 282019-10-28 00:00:00 UTC2019-11-04 00:00:00 UTC000
Nov 42019-11-04 00:00:00 UTC2019-11-11 00:00:00 UTC000
Nov 112019-11-11 00:00:00 UTC2019-11-18 00:00:00 UTC000
Nov 182019-11-18 00:00:00 UTC2019-11-25 00:00:00 UTC000
Nov 252019-11-25 00:00:00 UTC2019-12-02 00:00:00 UTC000
Dec 22019-12-02 00:00:00 UTC2019-12-09 00:00:00 UTC000
Dec 92019-12-09 00:00:00 UTC2019-12-16 00:00:00 UTC000
Dec 162019-12-16 00:00:00 UTC2019-12-23 00:00:00 UTC000
Dec 232019-12-23 00:00:00 UTC2019-12-30 00:00:00 UTC000
Dec 302019-12-30 00:00:00 UTC2020-01-06 00:00:00 UTC000
Jan 62020-01-06 00:00:00 UTC2020-01-13 00:00:00 UTC000
Jan 132020-01-13 00:00:00 UTC2020-01-20 00:00:00 UTC000
Jan 202020-01-20 00:00:00 UTC2020-01-27 00:00:00 UTC000
Jan 272020-01-27 00:00:00 UTC2020-02-03 00:00:00 UTC000
Feb 32020-02-03 00:00:00 UTC2020-02-10 00:00:00 UTC000
Feb 102020-02-10 00:00:00 UTC2020-02-17 00:00:00 UTC101
Feb 172020-02-17 00:00:00 UTC2020-02-24 00:00:00 UTC000
Feb 242020-02-24 00:00:00 UTC2020-03-02 00:00:00 UTC000
Mar 22020-03-02 00:00:00 UTC2020-03-09 00:00:00 UTC000
Mar 92020-03-09 00:00:00 UTC2020-03-16 00:00:00 UTC000
Mar 162020-03-16 00:00:00 UTC2020-03-23 00:00:00 UTC000
Mar 232020-03-23 00:00:00 UTC2020-03-30 00:00:00 UTC101
Mar 302020-03-30 00:00:00 UTC2020-04-06 00:00:00 UTC101

What Hacker News says

4 sources
I wasn't actually sure that the URL would work when posting. I was hoping to show the reverse proxy (https://dns.live/redirect), that DNS is live on handshake, and that DNS Live is available via handshake but also wanted to be clear as to what Handshake is since there could be confusion. (Copied from the link in my previous comment): Handshake is a naming system built in a decentralized way utilizing blockchain. It's been quietly in development for several years, but it only launched in February of 2020. The system builds on top of the legacy DNS system, further extending and improving upon it, so all legacy domains will continue to resolve (e.g. ycombinator.com). However, since ycombinator was in the top 100K Alexa, it can also claim ycombinator. and simply use that name (more on this later). The blockchain distributes names by 'releasi
Read the rest
ng' permission to open an auction on a schedule wherein a SHA3 hash of a name is modulo'd (%) against 52 to determine the week it will be available. When a name is available, anybody can send an OPEN transaction which will subsequently open up a public blind Vickrey auction for everyone to participate. Potential buyers can then send bids and, whoever wins, will pay the second highest bid [1]. They can also add an optional blind to the bid to mask their actual bid (so I can bid 10, but add a blind of 50 to make it look like I bid 60 to try to scare people off for example - like a bluff in poker). After bidding ends, a reveal period starts where the actual bids are revealed. Since launch, there have been a number of domains opened and sold. Some names have sold for quite a bit of value, such as crypto for 200,000 HNS [2]! This is at the time of this writing, the equivalent of $32,000. Past naming projects have struggled for adoption due to the fact that existing stakeholders in the space (e.g., popular websites, etc.) were unable to obtain their own names. In order to make sure this would make sense for everyone in the world, the blockchain prereserved the top 100K domains (and the legacy internet, so all existing tlds) for the people who are leasing/holding these names today [3]. Recently, major websites including torrentfreak, voat and brave have claimed their names [4]. In terms of funding, the project received $10m from early sponsors [5] and donated it all to FOSS projects and non profit organizations [6][7][8][9][10][11][12]! Unlike many of the 'blockchains' that have come into existence, a fundamental difference of Handshake has been that the founding team and earliest developers did not receive a substantial amount of coins. Instead, they received similar amounts to that of the original coin sponsors which includes the who's who of Silicon Valley. Further, the vast majority of the genesis coins have been distributed to FOSS developers (that's worth ~150m today) and FOSS/non profit projects [13]. There are a lot more coin allocations described in the design notes [14]. The blockchain is owned at a minimum by the open source internet community or, at best, the whole of humanity [15]. From an ownership perspective, the internet namespace, and the world namespace really, should belong to the people. Handshake is an experiment to deliver it to its rightful owners. From a technical perspective, Handshake creates an opportunity to finally upgrade our technology to gain real security as we will no longer need to rely on third party CAs [16] nor keep hot keys on servers since DNSSEC keys can be stored offline [17]. To be clear, without Handshake, DANE is a backdoor [18]. With Handshake, DANE is complete and the internet is more secure. How can you get involved? 1. Start using a hosted or local resolver [19][20]! 2. Register a name and use it [21][22]! 3. Develop and integrate the Handshake Naming System with existing software. 4. Submit PRs to hsd[23] or the newer implementations that are being developed like the Rust implementation, rsd[24]. [1] https://www.namebase.io/blog/tutorial-3-basics-of-handshake-.... [2] https://hsd.tools/leaderboard [3] https://dns.live/top.html [4] https://dns.live/topclaim-clean.html [5] https://web.archive.org/web/20191123130625/https://handshake.... [6] https://www.fsf.org/news/free-software-foundation-receives-1.... [7] https://www.debian.org/News/2019/20190329 [8] https://www.gnome.org/news/2018/08/gnome-foundation-receives.... [9] https://www.gimp.org/news/2018/08/30/handshake-gnome-donatio.... [10] https://dot.kde.org/2020/01/21/kde-receives-generous-donatio.... [11] https://calligra.org/news/handshake-donation/ [12] http://guix.gnu.org/.i18n/de/blog/2018/gnu-guix-receives-don.... [13] https://github.com/handshake-org/hs-airdrop [14] https://handshake.org/files/handshake.txt ; Search for: "# Stakeholders" [15] https://handshake.org/files/handshake.txt ; Search for: "# Project Summary" [16] https://www.thesslstore.com/blog/what-is-a-rogue-certificate.... [17] https://github.com/handshake-org/hdns [18] https://sockpuppet.org/blog/2016/10/27/14-dns-nerds-dont-con.... [19] https://nextdns.io/ [20] https://github.com/handshake-org/hsd --rs-port 53 | port forward dest 127.0.0.1:53 -> 5350 [21] https://www.namebase.io [22] https://github.com/kyokan/bob-wallet [23] https://github.com/handshake-org/hsd [24] https://github.com/UrkelLabs/rsd
In Show HN: DNS Live on Handshake
Submission Statement (SS): Handshake is a naming system built in a decentralized way utilizing blockchain. It's been quietly in development for several years, but it only launched in February of 2020. The system builds on top of the legacy DNS system, further extending and improving upon it, so all legacy domains will continue to resolve (e.g. ycombinator.com). However, since ycombinator was in the top 100K Alexa, it can also claim ycombinator. and simply use that name (more on this later). The blockchain distributes names by 'releasing' permission to open an auction on a schedule wherein a SHA3 hash of a name is modulo'd (%) against 52 to determine the week it will be available. When a name is available, anybody can send an OPEN transaction which will subsequently open up a public blind Vickrey auction for everyone to participate. P
Read the rest
otential buyers can then send bids and, whoever wins, will pay the second highest bid [1]. They can also add an optional blind to the bid to mask their actual bid (so I can bid 10, but add a blind of 50 to make it look like I bid 60 to try to scare people off for example - like a bluff in poker). After bidding ends, a reveal period starts where the actual bids are revealed. Since launch, there have been a number of domains opened and sold. Some names have sold for quite a bit of value, such as crypto for 200,000 HNS [2]! This is at the time of this writing, the equivalent of $32,000. Past naming projects have struggled for adoption due to the fact that existing stakeholders in the space (e.g., popular websites, etc.) were unable to obtain their own names. In order to make sure this would make sense for everyone in the world, the blockchain prereserved the top 100K domains (and the legacy internet, so all existing tlds) for the people who are leasing/holding these names today [3]. Recently, major websites including torrentfreak, voat and brave have claimed their names [4]. In terms of funding, the project received $10m from early sponsors [5] and donated it all to FOSS projects and non profit organizations [6][7][8][9][10][11][12]! Unlike many of the 'blockchains' that have come into existence, a fundamental difference of Handshake has been that the founding team and earliest developers did not receive a substantial amount of coins. Instead, they received similar amounts to that of the original coin sponsors which includes the who's who of Silicon Valley. Further, the vast majority of the genesis coins have been distributed to FOSS developers (that's worth ~150m today) and FOSS/non profit projects [13]. There are a lot more coin allocations described in the design notes [14]. The blockchain is owned at a minimum by the open source internet community or, at best, the whole of humanity [15]. From an ownership perspective, the internet namespace, and the world namespace really, should belong to the people. Handshake is an experiment to deliver it to its rightful owners. From a technical perspective, Handshake creates an opportunity to finally upgrade our technology to gain real security as we will no longer need to rely on third party CAs [16] nor keep hot keys on servers since DNSSEC keys can be stored offline [17]. To be clear, without Handshake, DANE is a backdoor [18]. With Handshake, DANE is complete and the internet is more secure. How can you get involved? 1. Start using a hosted or local resolver [19][20]! 2. Register a name and use it [21][22]! 3. Develop and integrate the Handshake Naming System with existing software. 4. Submit PRs to hsd[23] or the newer implementations that are being developed like the Rust implementation, rsd[24]. [1] https://www.namebase.io/blog/tutorial-3-basics-of-handshake-... [2] https://hsd.tools/leaderboard [3] https://dns.live/top.html [4] https://dns.live/topclaim-clean.html [5] https://web.archive.org/web/20191123130625/https://handshake... [6] https://www.fsf.org/news/free-software-foundation-receives-1... [7] https://www.debian.org/News/2019/20190329 [8] https://www.gnome.org/news/2018/08/gnome-foundation-receives... [9] https://www.gimp.org/news/2018/08/30/handshake-gnome-donatio... [10] https://dot.kde.org/2020/01/21/kde-receives-generous-donatio... [11] https://calligra.org/news/handshake-donation/ [12] http://guix.gnu.org/.i18n/de/blog/2018/gnu-guix-receives-don... [13] https://github.com/handshake-org/hs-airdrop [14] https://handshake.org/files/handshake.txt ; Search for: "# Stakeholders" [15] https://handshake.org/files/handshake.txt ; Search for: "# Project Summary" [16] https://www.thesslstore.com/blog/what-is-a-rogue-certificate... [17] https://github.com/handshake-org/hdns [18] https://sockpuppet.org/blog/2016/10/27/14-dns-nerds-dont-con... [19] https://nextdns.io/ [20] https://github.com/handshake-org/hsd --rs-port 53 | port forward dest 127.0.0.1:53 -> 5350 [21] https://www.namebase.io [22] https://github.com/kyokan/bob-wallet [23] https://github.com/handshake-org/hsd [24] https://github.com/UrkelLabs/rsd
In The Internet Can No Longer Be Censored
The JS implemention is a fork of bcoin, the JS Bitcoin full node and production backend. It binds to libunbound but you are right that you would want a lower level language for it to be more scalable. There is a rust implemention work in progress here: https://github.com/UrkelLabs/rsd There is also a C light client here: https://github.com/handshake-org/hnsd For the consensus, there are C bindings for the cryptography and a workerpool that really speeds things up. It could also be possible to dump the Handshake zone into a zone file and serve from behind unbound.
In Handshake: Decentralizing DNS to Improve the Security of the Internet

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.