Doesn't work with GPG key about hs-airdrop HOT 9 OPEN

The key you passed to hs-airdrop is not in the airdorp snapshot, I can not help you understand why. Either it's the wrong key or you didn't qualify on the snapshot date. It works with GPG and SSH keys, if you think you had another key in your Github account at that time, try it. All your keys at the time of the snapshot are included in the airdrop tree but each user can only claim one airdrop (it will then invalidate the remaining keys)

from hs-airdrop.

Well, I did easily have more than 15 followers in 2018/2019. And as per GitHub, you see when the key was added, so it was there. So, the airdrop snapshot must be broken then.

from hs-airdrop.

Is it possible your key was not an acceptable type? There are some restrictions on the readme and more details here: #35 (comment)

from hs-airdrop.

The key in question is an Ed25519 key, whch is unsupported by GNUPG 1. Might that be the reason?

from hs-airdrop.

Hmm no that should be ok:

https://github.com/handshake-org/hs-airdrop#accepted-key-algorithms

from hs-airdrop.

Is there a way to check if a key's in there with just the public key? Then I'll iterate over all my keys.

from hs-airdrop.

The only way to check is to run hs-airdrop. It can be done on an air gapped machine if you prefer but it must search the hs-tree-data for the nonce.

from hs-airdrop.

Hmm, I'm reluctant to try it on my main SSH key that I use ~ everywhere for years now. How can I be sure the private key is not leaked into the base64 output from hs-airdrop?

from hs-airdrop.

You can audit the code, rotate your 3-year-old keys out so they aren't important anymore, or simply do not claim the airdrop. There are lots of other ways to get involved in HNS

from hs-airdrop.