Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NonceError despite correct GitHub SSH key and > 15 followers #137

Closed
hubert3 opened this issue May 11, 2021 · 3 comments
Closed

NonceError despite correct GitHub SSH key and > 15 followers #137

hubert3 opened this issue May 11, 2021 · 3 comments

Comments

@hubert3
Copy link

hubert3 commented May 11, 2021

Hi,

like a few other commenters here, hs-airdrop is telling me:

NonceError: Could not find nonce in bucket xxx

I am trying with an SSH key that I am confident was in place on my @hubert3 GitHub account in Feb 2019, and I definitely had > 15 followers at that time.

Are there any logs from when the GitHub data collection was done that can confirm whether my account was or wasn't included?

How were accounts with multiple SSH keys handled? Was the first public key shown on https://github.com/username.keys chosen?

The fingerprint of the old key I've retrieved from a backup matches with the Github SSH key add notification email dated 2016 and it's a 2048 bit RSA key. The next SSH key change notification email wasn't til 2020 and I tried that key too, so it ought to be the 2016 key.

If my account wasn't included in the airdrop for whatever reason that's fine, but it would be nice to know if it was selected before spending any more time on this (took me a while to find the right backup disk containing the 2016 key).

@pinheadmz
Copy link
Member

How were accounts with multiple SSH keys handled? Was the first public key shown on https://github.com/username.keys chosen?

All keys from your github account are in the airdrop tree, and all may qualify. However, each user is only to claim their airdrop once. This is handled with "subtrees" of keys for each user account, then the root of each subtree is the hash included (and proven) in the consensus airdrop merkle tree. If you had other keys on your account at the time of the snapshot, you should try those.

closing as duplicate: #35

@hubert3
Copy link
Author

hubert3 commented May 11, 2021

Thanks.

I'm fairly certain only the one 2016 SSH key I've already tried would have been added as of Feb 2019.

If it's possible in future to create some kind of interface to check if any key was taken from a particular GitHub account (even without identifying the key), that would be useful.

There were 2 older keys from 2012 which I'm almost certain I would have deleted from GitHub by 2019. If there was a way to check if any key was added from my GitHub profile, that would save potentially wasted effort looking for even older backups.

@pinheadmz
Copy link
Member

Unfortunately there is no way to know if keys were properly included in the airdrop tree:

handshake-org/hsd#549

more details: #35 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants