search

ymgve / bitcoin_fork_claimer

Script for transferring/claiming your coins on various Bitcoin forks
202 stars 85 forks source link

BTH, BTP and LBTC does not work at all #77

Open newuser1a opened 5 years ago

newuser1a commented 5 years ago

I am not sure if this is still being maintained but I spend several hours on this with high hopes and it turned out I couldn't get a single transaction send.

Tried BTH first It couldn't connect to any of the servers. Tried over 100 times. Tries BTP next finally was able to connect to some servers but the transaction got rejected some how and it was never in the mempool. After 4 times it just stopped. Had my last hope on LBTC Its been over an hour and its still saying not seeing the transaction in the mempool.

I really appreciate you creating the script here to help others but this has been very aggrevating as nothing with this works. Does this still work or should I try something else?

Thank you

ymgve commented 5 years ago

You're a bit late - a lot of forks are gone, broken, or reorganized so they're not true forks anymore. At least BTH and LBTC have reorganized according to https://forkdrop.io/ and is probably not claimable at all anymore.

newuser1a commented 5 years ago

I tried BCX today. It doesn't work either. Keep saying "Transaction not included in observed block." Does this mean its my key is incorrect or the blockchain it self is not working? Also I noticed that it always says 'mempool' (0 bytes). Shouldn't there be something in the mempool?

When you say reorganized, what do you mean? Like you can no longer claim by using bitcoin keys? I check BCX on forkdrop.io and it says the chain is still good. Any reason I wouldn't be able to claim BCX?

Do you know which of the fork still works? I am thinking about trying GOD next.

Thanks

newuser1a commented 5 years ago

Does this mean my transaction is rejected? like my key is invalid or something? I can see that I have coins on http://www.findmycoins.ninja/.

ymgve commented 5 years ago

What address are you trying to claim from? You can use the convert_address.py script in this repo to convert your address to BCX format, then use their block explorer at https://bcx.info to check if your coins are indeed present on the chain. findmycoins.ninja doesn't do any deeper checks, it only checks that your address had coins on the BTC chain at the point of the fork.

newuser1a commented 5 years ago

Thanks for helping me. This is the address I am trying to get BCX from: https://bcx.info/address/XEKTXg2fGNWvbEM3v4C2qrCzNirz2KyydN.

As you can see it does contain BCX. I am not sure what I am doing wrong. The command I am using is: python2.7 claimer.py BCX 6ea068cfe9be749c5e4183eb50d096e74b7eaf62de269681276cff866e8dc40f "privatekey" 13yDgXg41qmDFitZ5bD8USnzAtYEiFAJYu XJqg79sTb2tY9wAyrJrrrJxrqYNpLhD2N3 --txindex 11 --satoshis 10990000 --force

Am I doing something wrong. I did this according to a guide I found online.

ymgve commented 5 years ago

You've forgotten that BCX is a 10000x coin. Try with -satoshis 109900000000

newuser1a commented 5 years ago

Thanks I tried it but I don't think -satoshis 109900000000 worked. I don't have 1099 BTC in this address.
It still not seeing the transaction. Do you think its the private key that is incorrect? I exported the key out of electrum. Maybe its incompatible with the script?

below is the log.

YOU ARE ABOUT TO SEND 10990000.00000000 BCX (equivalent to 1099.00000000 BTC) FROM 13yDgXg41qmDFitZ5bD8USnzAtYEiFAJYu 10989999.90000000 BCX (equivalent to 1098.99999000 BTC) TO XJqg79sTb2tY9wAyrJrrrJxrqYNpLhD2N3 !!! 0.10000000 BCX (equivalent to 0.00001000 BTC) WILL BE SENT AS FEES! CONTINUE AT YOUR OWN RISK !!! generated transaction 527a50057685bda7f3dfca5d7aeeb592a69bea9a2f37098780fddb80ace563ba

Connecting to servers and pushing transaction Please wait for a minute before stopping the script to see if it entered the server mempool.

Connecting to ('120.92.117.145', 9003) ... SUCCESS, connected to ('120.92.117.145', 9003) ---> 'version' (93 bytes) <--- 'version' (116 bytes) Version information: protocol version 70015 services 13 timestamp Sun Jun 2 02:24:36 2019 user agent '/BitcoinXCore:0.16.1(bitcore)/' block height 867166 ---> 'verack' (0 bytes) <--- 'verack' (0 bytes) <--- 'sendheaders' (0 bytes) ---> 'headers' (1 bytes) <--- 'sendcmpct' (9 bytes) <--- 'sendcmpct' (9 bytes) <--- 'ping' (8 bytes) ---> 'pong' (8 bytes) ---> 'inv' (37 bytes) ---> 'mempool' (0 bytes) <--- 'feefilter' (8 bytes) server requires minimum fee of 1000 satoshis our fee is >= minimum fee, so should be OK <--- 'getdata' (37 bytes) Peer requesting transaction details for 527a50057685bda7f3dfca5d7aeeb592a69bea9a2f37098780fddb80ace563ba ---> 'tx' (192 bytes) SENT TRANSACTION: 527a50057685bda7f3dfca5d7aeeb592a69bea9a2f37098780fddb80ace563ba <--- 'getdata' (37 bytes) Received getdata without our txhash. The transaction may have been rejected. This script will retransmit the transaction and monitor the mempool for a few minutes before giving up. <--- 'inv' (73 bytes) transaction: 6a16fa76fb167c7b19a88055a1764275f7ae399b9a9b1985631b2ba2d1cd89d5 transaction: 1524e8df4daa63622fc582a995ed76ef963368137959c75026c17a2f188131bd

Our transaction was not found in the mempool.
Will retransmit and check again 4 more times.

<--- 'ping' (8 bytes) ---> 'pong' (8 bytes) ---> 'tx' (192 bytes) Re-sent transaction: 527a50057685bda7f3dfca5d7aeeb592a69bea9a2f37098780fddb80ace563ba ---> 'mempool' (0 bytes) <--- 'inv' (109 bytes) transaction: 26a166fa5b851797e96b2610a0a35deeaac449da2006522a1f5f2189ee416fca transaction: 6a16fa76fb167c7b19a88055a1764275f7ae399b9a9b1985631b2ba2d1cd89d5 transaction: 1524e8df4daa63622fc582a995ed76ef963368137959c75026c17a2f188131bd

Our transaction was not found in the mempool.
Will retransmit and check again 3 more times.

<--- 'inv' (37 bytes) block: 00000000000013e8570bc3d022a6779e924150f840a95993c2a6a8d63e24bd4c ---> 'getdata' (37 bytes) requesting 1 blocks <--- 'block' (2006 bytes) Transaction not included in observed block.

ymgve commented 5 years ago

Oh, also your txindex is wrong. It should be 25 if I counted correctly, not 11.

So:

python2.7 claimer.py BCX 6ea068cfe9be749c5e4183eb50d096e74b7eaf62de269681276cff866e8dc40f "privatekey" 13yDgXg41qmDFitZ5bD8USnzAtYEiFAJYu XJqg79sTb2tY9wAyrJrrrJxrqYNpLhD2N3 --txindex 25 --satoshis 109900000000 --force

The private key should be correct as the script checks it against the public address and gives an error if they don't match.

newuser1a commented 5 years ago

Thank you. It finally work.
Really appreciate your fast response and help. I followed a guide online when first setting up the script. Must have set that incorrect.

Thanks again for catching that.