Specified SSH key is not eligible for claiming. Only RSA and Ed25519 keys added before our Github snapshot are supported for proof generation.

[wufengtao1]

Specified SSH key is not eligible for claiming. Only RSA and Ed25519 keys added before our Github snapshot are supported for proof generation.

WTF? Because I replaced the key after the snapshot, I can't claim the airdrop anymore? Why is there such a stupid setup? Is there a problem with frequently changing keys for security? Who is your user growth director, and why such a foolish decision?

[phryneas]

Hi there :)

Is there a chance that the metadata.bin might get regenerated at some point with newly added keys? I am using a hardware token, and age cannot access that, so I had to add a new ssh-key in the hopes you'll pick that up after a while.

[L-Qun]

Specified SSH key is not eligible for claiming. Only RSA and Ed25519 keys added before our Github snapshot are supported for proof generation.

Is there any way to solve?

[xlc]

It is interesting to see that the more secure setup is not supported so a good chunk of top tier devs are excluded. 💁‍♂️

[akim-bow]

Dublicate of #63