HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
handshake-org
hs-airdrop
JavaScript2019–2021
handshake-org / hs-airdrop

hs-airdrop

Decentralized airdrop to open source developers

11Distinct people
16Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Decentralized airdrop to open source developers

GitHub

Where it is used

No documented product use was verified in the last source check.

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, 5:04:57 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 month16 dated mentions

Observed mentions: 2019-03-30 09:22:25 UTC to 2021-01-13 02:05:51 UTC.

02462019-03-01 00:00:00 UTC to 2019-04-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 20192019-04-01 00:00:00 UTC to 2019-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-01 00:00:00 UTC to 2019-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-06-01 00:00:00 UTC to 2019-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-01 00:00:00 UTC to 2019-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-01 00:00:00 UTC to 2019-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-09-01 00:00:00 UTC to 2019-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-01 00:00:00 UTC to 2019-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-01 00:00:00 UTC to 2019-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2020-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-01 00:00:00 UTC to 2020-03-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 commentsFeb 20202020-03-01 00:00:00 UTC to 2020-04-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020-04-01 00:00:00 UTC to 2020-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-05-01 00:00:00 UTC to 2020-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-01 00:00:00 UTC to 2020-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-01 00:00:00 UTC to 2020-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-01 00:00:00 UTC to 2020-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-01 00:00:00 UTC to 2020-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-01 00:00:00 UTC to 2020-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-01 00:00:00 UTC to 2020-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2021

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
Mar 20192019-03-01 00:00:00 UTC2019-04-01 00:00:00 UTC110
Apr 20192019-04-01 00:00:00 UTC2019-05-01 00:00:00 UTC000
May 20192019-05-01 00:00:00 UTC2019-06-01 00:00:00 UTC000
Jun 20192019-06-01 00:00:00 UTC2019-07-01 00:00:00 UTC000
Jul 20192019-07-01 00:00:00 UTC2019-08-01 00:00:00 UTC000
Aug 20192019-08-01 00:00:00 UTC2019-09-01 00:00:00 UTC202
Sep 20192019-09-01 00:00:00 UTC2019-10-01 00:00:00 UTC000
Oct 20192019-10-01 00:00:00 UTC2019-11-01 00:00:00 UTC000
Nov 20192019-11-01 00:00:00 UTC2019-12-01 00:00:00 UTC000
Dec 20192019-12-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
Jan 20202020-01-01 00:00:00 UTC2020-02-01 00:00:00 UTC000
Feb 20202020-02-01 00:00:00 UTC2020-03-01 00:00:00 UTC707
Mar 20202020-03-01 00:00:00 UTC2020-04-01 00:00:00 UTC514
Apr 20202020-04-01 00:00:00 UTC2020-05-01 00:00:00 UTC000
May 20202020-05-01 00:00:00 UTC2020-06-01 00:00:00 UTC000
Jun 20202020-06-01 00:00:00 UTC2020-07-01 00:00:00 UTC000
Jul 20202020-07-01 00:00:00 UTC2020-08-01 00:00:00 UTC000
Aug 20202020-08-01 00:00:00 UTC2020-09-01 00:00:00 UTC000
Sep 20202020-09-01 00:00:00 UTC2020-10-01 00:00:00 UTC000
Oct 20202020-10-01 00:00:00 UTC2020-11-01 00:00:00 UTC000
Nov 20202020-11-01 00:00:00 UTC2020-12-01 00:00:00 UTC000
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
Jan 20212021-01-01 00:00:00 UTC2021-02-01 00:00:00 UTC101

What Hacker News says

16 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
TL;DR for collecting the airdrop seems to be something like this (I AM NOT suggesting you should, but in case you decide to): * install `https://github.com/handshake-org/hsd` - run `./bin/hsd` and wait for wallet to sync * install `https://github.com/handshake-org/hs-client` - run `./bin/hsw-cli account create` and `./bin/hsw-cli --account=default address` - copy address * install `https://github.com/handshake-org/hs-airdrop` - follow instructions depending on how you whether you want to give the cli your key or sign manually - simplest way is something like `hs-airdrop <key-file> <address>` * back in `hs-client` - run ./bin/hsd-rpc sendrawairdrop <base64-from-hs-airdrop>` * leave the wallet running and wait for 20 or something blocks * back in `hs-client` - `./bin/hsw-cli balance --account=default` should now have a balance.
In Handshake Airdrop for Active GitHub Users (~$1500 in Current Value)
Several apparent reports of someone trying to buy old de-activated github pgp keys. This is probably a social engineering attack - presumably the attacker is gonna want the key pair in the hope the private key will unlock... something else. What is the default linux ssh key used for that would make a good target? Personal sever instances would be hard to locate, so it is probably something central like cloud provider authentication? EDIT: Disappointingly, it's this https://github.com/handshake-org/hs-airdrop
In (Scams Subreddit): [Money for your] GitHub PGP keys – is this a scam?
we do not allow standard PGP signatures on the consensus layer. This is done for simplicity and safety. This means that a regular call to $ gpg --sign will not work for handshake airdrop proofs. As far as SSH keys go, people typically do not sign arbitrary messages with them. Because of this, we require a special tool to do both the signing and merkle proof creation. I like how they say, simplicity and safety. The right solution: Give me a random block of text, I'll sign it using my private RSA/DSA key and you can verify that I am the owner of the public key, send me the money, and everybody is happy. Alleged simplicity: Two hours I'm trying to redeem the airdrop without giving away the private key and the passphrase (hint, it's not implemented, despite the documentation somewhat references it here: h
Read the rest
ttps://github.com/handshake-org/hs-airdrop#fallback-for-hsm... ). Alleged safety: after installing dozens of NPM packages and code from whoever who, and running an algorithm that we don't know (even the developers) if it's reversible or not. I see horrible consequences: https://github.com/handshake-org/hs-airdrop/issues/31 User has key safely inside HSM, gets the key out to get free money that A16Z is supposedly giving. Reminds me the "Elon Musk gives Bitcoin on Twitter, just send YOUR PASSWORD" On the practices overall: It's unclear what the private key derivation process does and if the developers themselves truly understand it. If the developers would understand the full security implications, they would not say it's safe to do it on an air-gapped machine. The process could just multiply by two or base64 encode the private key, it would be near invisible since the whole code and theory is a big soup. All that, supposedly for privacy benefits, when at the end, you have to give your real identity and ID documents to actually withdraw/exchange the coins.
In An airdrop that preserves recipient privacy [pdf]
As an FYI for HN, many of y'all are probably eligible for $400-800 of Handshake coins (HNS). Handshake is airdropping coins to open-source developers to incentivize them to check out the project. If you have over 15 followers on GitHub you can use this tool to claim coins. This is a no-strings-attached giveaway so if you want to you can also sell your coins but it'd be worth it to bid on your name before you do. You can also reach out to me at tieshun at namebase.io if you have questions about the airdrop or Handshake itself. https://github.com/handshake-org/hs-airdrop
In Decentralized DNS with the Handshake Naming System

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

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.