search

ymgve / bitcoin_fork_claimer

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

BCL claiming problem #51

Closed talesfromthecrypt closed 6 years ago

talesfromthecrypt commented 6 years ago

Hi i am trying to claim BCL and here is what the response i get in the terminal%

Connecting to ('seed.bitcoinclean.org', 8338) ... SUCCESS, connected to ('195.201.119.226', 8338) ---> 'version' (93 bytes) <--- 'version' (107 bytes) Version information: protocol version 70015 services 1037 timestamp Mon May 28 06:56:06 2018 user agent '/LittleGlobe:0.15.99/' block height 565108 ---> '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) <--- 'addr' (31 bytes) Got peer address: 195.201.119.226:8338 <--- '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 735c1af55cf450bb6aaf512c8c68444adaa29d71fe99308b52693d39938663dc ---> 'tx' (190 bytes) SENT TRANSACTION: 735c1af55cf450bb6aaf512c8c68444adaa29d71fe99308b52693d39938663dc <--- '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. <--- 'ping' (8 bytes) ---> 'pong' (8 bytes) ---> 'tx' (190 bytes) Re-sent transaction: 735c1af55cf450bb6aaf512c8c68444adaa29d71fe99308b52693d39938663dc ---> 'mempool' (0 bytes)

ymgve commented 6 years ago

What's the TXID and address you're trying to claim from?

talesfromthecrypt commented 6 years ago

TXID 8b47f12b7efbdf8cd57d47390e88f5efb065e002412c307a39c27bf0dc724556

from: 18hSZ4i42ag7xWpRy7stUmzz5qY6CaKC2s to 3GToFyPdH62KpzRnZL56xwNbtAreVJ16yi

ymgve commented 6 years ago

That output was spend in this transaction https://blockchain.info/tx/1468cc44b40dbc41452575c96767b7cc771c980facc7dd228522a9be5fd67579 at block height 510512, which was before the fork height for BCL at height 518800. At the time of the fork, the address was empty.

talesfromthecrypt commented 6 years ago

Yes, i guess it was incoming transaction and the funds were on this address until the fork

talesfromthecrypt commented 6 years ago

Ok, i resolved it, thank you for support!