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

Verification failure: txn-already-in-mempool / bad-txns-inputs-missingorspent #133

Open
pinheadmz opened this issue May 4, 2021 · 3 comments

Comments

@pinheadmz
Copy link
Member

If you see this error in the hsd log after broadcasting your airdrop proof, it means YOUR AIRDROP HAS ALREADY BEEN CLAIMED. This is essentially a double-spend error.

Every GitHub airdrop recipient can claim ONCE on Handshake. This means even if you had 10 PGP keys in your account, you can only claim once, and then the other 9 keys won't work. If you didn't claim with --bare before and are trying that now, it won't work -- you can only claim once.

If you used a Namebase address the first time you claimed and you are seeing this error now, that means your first claim succeeded and your funds belong to Namebase. There is nothing else you can do with handshake-org software, you must contact Namebase support.

Airdrop claims can not be spent until they accumulate 100 blocks. Namebase or any other exchange may require additional confirmations on top of that before crediting your account.

If you are absolutely certain without a doubt that this is the very first time you have ever run hs-airdrop and you are getting this error in your hsd log it means either:

  • Your GitHub keys have been compromised and someone else has managed to claim your airdrop
  • There is something extremely wrong with the airdrop implementation at the consensus level

If you are certain that your GitHub keys have always been safe, and you saw this error the first time you attempted to claim an airdrop, please comment below or if you think there may be a critical consensus bug involved, please contact handshake-org securely.

@icyphox
Copy link

icyphox commented May 9, 2021

Hi, I ran across this error after having realized that I didn’t run it with --bare the first time. However, my account balance won’t update:

  "balance": {
    "account": -1,
    "tx": 0,
    "coin": 0,
    "unconfirmed": 0,
    "confirmed": 0,
    "lockedUnconfirmed": 0,
    "lockedConfirmed": 0
  }

Any ideas? I’ve given it about 8 hours.

@michaelknoch
Copy link

did you find a solution @icyphox ?

@pinheadmz
Copy link
Member Author

@icyphox @michaelknoch airdrops require 100 confirmations to mature before spending (like the miners reward in the coinbase transaction)

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

No branches or pull requests

3 participants