ymgve / bitcoin_fork_claimer

Script for transferring/claiming your coins on various Bitcoin forks
204 stars 86 forks source link

Received getdata without our txhash. The transaction may have been rejected. #42

Closed host2gate closed 6 years ago

host2gate commented 6 years ago

Seeing below error, when running the script, could you please take a look and help

python.exe claimer.py BCH 551a6ca27feab07d53bba655094291891ec3310f40cd455157ae14633be8b0f5 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreD437Nay 19vxtDbLMNasSpbAEZd7va5Qge6d2zYWbp 1NBVZrG2uyAkmUmJuHLJPkoBG8KZq5H3yc Querying blockchain.info API about data for transaction 551a6ca27feab07d53bba655094291891ec3310f40cd455157ae14633be8b0f5 Candidate transaction, index 21 with 10000000 Satoshis (0.10000000 BTC) Raw transaction 0100000001f5b0e83b6314ae575145cd400f31c31e8991420955a6bb537db0ea7fa26c1a55150000008a473044022026aec92ba070ae30267032b512a02df0fc62714c1ce258277c3c7c67f478b42f0220214e277f94f06107779fc5a6a202f9642f6346ca2c0c36ca040266c9a31e7fe8414104352bbf4a4cdd12564f93fa332ce333301d9ad40271f8107181340aef25be59d5321eb4075348f534d59c18259dda3e1f4a1b3b2e71b1039c67bd3d8bcf81998cffffffff0198929800000000001976a914e856a5a70358e18ee1b0352ba6632fc6bdf918f788ac00000000

YOU ARE ABOUT TO SEND 0.10000000 BCH (equivalent to 0.10000000 BTC) FROM 19vxtDbLMNasSpbAEZd7va5Qge6d2zYWbp 0.09999000 BCH (equivalent to 0.09999000 BTC) TO 1NBVZrG2uyAkmUmJuHLJPkoBG8KZq5H3yc !!! 0.00001000 BCH (equivalent to 0.00001000 BTC) WILL BE SENT AS FEES! CONTINUE AT YOUR OWN RISK !!!

Write 'I am sending coins on the Bitcoin Cash network and I accept the risks' to continue I am sending coins on the Bitcoin Cash network and I accept the risks generated transaction 8ae80b030155ab8d943f70cd29afb37141e17e24d3db5b1f94c6fad02d395682

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 ('seeder.criptolayer.net', 8333) ... SUCCESS, connected to ('52.212.77.122', 8333) ---> 'version' (93 bytes) Connection failed with: error('Connection reset!',) Will retry 100 more times. Connecting to ('seed.bitcoinabc.org', 8333) ... SUCCESS, connected to ('47.88.77.13', 8333) ---> 'version' (93 bytes) <--- 'version' (114 bytes) Version information: protocol version 70015 services 37 timestamp Sat May 12 10:37:13 2018 user agent '/Bitcoin ABC:0.17.1(EB32.0)/' block height 529885 ---> 'verack' (0 bytes) <--- 'verack' (0 bytes) <--- 'sendheaders' (0 bytes) ---> 'headers' (1 bytes) <--- 'sendcmpct' (9 bytes) <--- 'ping' (8 bytes) ---> 'pong' (8 bytes) ---> 'inv' (37 bytes) ---> 'mempool' (0 bytes) <--- 'addr' (31 bytes) Got peer address: 47.88.77.13:8333 <--- 'getdata' (37 bytes) Peer requesting transaction details for 8ae80b030155ab8d943f70cd29afb37141e17e24d3db5b1f94c6fad02d395682 ---> 'tx' (223 bytes) SENT TRANSACTION: 8ae80b030155ab8d943f70cd29afb37141e17e24d3db5b1f94c6fad02d395682 <--- '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' (1513 bytes) transaction: 647e67f9e315ea1e59fb3097789a45dd0654eb668cd3f9ecffd2cc83ae294ead transaction: da6c2ab1a23c1138911f873bd20207e1fe0a47a0b8a5171c3976f62aa9e70289 transaction: 6c9cd99b738d76998a2daf756dc263922bd2bb62c1b5d3d6cf18ffbf4a3fbb87 transaction: 68b78681f4dd3577bd5a4c48609093a67f6c90a1bed3ea8ecf50689098e3e281 transaction: e93970a28a14aad67124fa003995ad2f9e15dd075fb9d795d3b4955519624f60 transaction: ddc6ac740093d36a248513435100b05011c849463aabdffca26a1dcd5247a701 transaction: 5ffa48cd3aafff084b6a495ab47bc6c9c26dc431f864f12c60afb4dc440e2fa9 transaction: 58c0e2ed1e6ada2cf9da851d12ccf8794faa83863606a54d834c8398c8397565 transaction: 4c70f4bd3e8a1ee29d01c165b22b0b5a959b224eb13ca78c0f61b630bf30f01c transaction: e73724be4de61fb574690be6cc27d28a5bbe9b3f89e363d9244d9d5530a63e3f ... Not printing additional 32 transactions

    Our transaction was not found in the mempool.
    Will retransmit and check again 4 more times.
ymgve commented 6 years ago

Why are you trying to claim a transaction that was spent in 2013? Of course it will be rejected, as there is no BCH to claim.