-
Notifications
You must be signed in to change notification settings - Fork 172
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
Airdrop claim transactions randomly fail to be mined #126
Comments
Thanks for posting, hopefully we can try to figure what's going on. It's possible some users are trying to set the fee too low: https://github.com/handshake-org/hs-airdrop#usage Version 2.3.0 of hsd has a few improvements to help low fee transactions propagate and get confirmed. It's also possible (though unlikely) that blocks are "full" of airdrops -- only up to 10 maximum are added to each block. |
@johnnywu-namebase actually it may be helpful if you can direct users with this issue to... this issue. Maybe we can get some details and try to find a bug instead of just hitting retry. |
Sorry just seeing this (Github emails were getting spammed). Will redirect future airdrop claimers to this issue instead of just telling them to try it 👍 |
@pinheadmz bisa Beritahu saya? Untuk memberi tahukan step by step nya? |
Dear @pinheadmz, I recently tried the claiming process, but I currently have a red banner on Namebase saying "There was an error submitting your airdrop to Handshake. If you're confident this airdrop has not already been claimed, contact support." I am confident the airdrop has not been claimed before. Here is what I did:
What would you recommend I should try next? Thank you very much for your time |
@paiva normally I would say you need to stick with Namebase support on this, but I have a suspicion, which is explained in #131 Could you email me the base64 output if you still have it? pinheadmz@gmail.com @johnnywu-namebase I need to update the docs for hs-airdrop because goosig is now expired. Basically, all airdrop claims need to be generated with the |
@pinheadmz Thank you for the quick reply! I have sent you an email with the Base64 output. Thanks! |
@paiva confirmed my suspicion:
You will need to re-run the hopefully Namebase allows you to resubmit. If they don't you can send the NEW base64 to me and I'll broadcast it. As long as you use the same HNS address from the Namebase wallet, it'll work. |
@pinheadmz I did the re-run with the |
Got it, thanks so much for identifying this, I suspect a lot of recent failed airdrops have this same problem |
I have the same problem. I use Here is the log:
|
@hacket I tried broadcasting your raw airdrop proof but my full node is telling me it has already been confirmed (or an airdrop to one of your other keys, including possibly the goosig-tweaked key). You will have to continue to address this issue with Namebase support.
|
@pinheadmz I have two SSH keys, one for work and one for home use. The one above is the one used at home. Now the following is a working computer ssh key. Already have a red banner on Namebase.
|
@hacket I am getting a double-spend error for this airdrop proof as well. Let me explain a bit: For the github user airdrop, every user only gets one. Even if you had 10 SSH keys and 10 PGP keys on github at the time of the snapshot, you can only claim one airdrop. Once you claim, the other 19 keys (in this example) are invalidated. What these two proofs' validation errors are telling me is that one of your github keys was successfully submitted to the blockchain to claim an airdrop. If you claimed with a Namebase receive address, your airdrop should be included in your balance on Namebase. |
@pinheadmz If I claimed. How can I find out which NameBase account I have claimed? |
Hi @pinheadmz , I've tried to add Could you please help me check out what the problem is? thanks in advance! Here's the output detail:
|
@albertcht looks like the same as error as the previous one (#126 (comment)). It has already been claimed.
|
Hi @rithvikvibhu , Thanks for your reply. However, I'm pretty sure I haven't claimed the airdrop successfully and didn't see the reward on my nambase's wallet either. Is there any other possibilities that may cause this error? |
@hacket @albertcht don't forget airdrop claims require 100 confirmations before they are spendable. Give it at least a full day to show up in namebase. |
@johnnywu-namebase Seems like that generating base64 proof with |
Hi @pinheadmz , @rithvikvibhu , @johnnywu-namebase , I've waited over than 2 days and it seems still doesn't work. The status in namebase's dashboard is always I'm one hundred percent sure that I haven't claimed the airdrop successfully. How can I find out the reason that causes this error? Thanks for your help. |
@albertcht you must contact namebase support on their website or discord, unfortunately your case is now off-topic for this repository. |
Using $ ./bin/hs-airdrop --bare <path to key> <address> <fee> also ./bin/hs-airdrop <path to key> <address> --fee 0.1 --bare |
Some airdrop claim transactions fail to get mined. Fortunately, the current solution is pretty simple: just submit an airdrop claim once a day and eventually the claim will work.
The text was updated successfully, but these errors were encountered: