ymgve / bitcoin_fork_claimer Goto Github PK

Can you add support for CLAMcoin? Thank you for considering this.

When trying to send to a WBTC address (e.g. WTfvVSuE6fKGyG7Kf5uxoSjuH9jcw37MDK), I get this error

Exception: The destination address WTfvVSuE6fKGyG7Kf5uxoSjuH9jcw37MDK does not match BTC or WBTC. Are you sure you got the right one?

Please see https://bitcointalk.org/index.php?topic=2827163.msg30284004#msg30284004

And https://github.com/Ayms/bitcoin-transactions

Hi, after some elusive time fiddling around... I got the script working for SBTC (had an earlier version and found it missing "self.versionno = 70017" ; pfffff ;-)
But anyway.. it worked, great piece of work;
BUT....
When I check my address via https://btcdiv.com/ I get: 12.97806829 SuperBitcoin to claim
When I check my address via fork-helper.py I get: 6.48790590 SBTC to claim
When I execute the fork_claimer script: it successfully obtained 6.48742589 SBTC using all TXIDs found with fork-helper.py !?
THEN I check my address via https://btcdiv.com/ again... and see: 0 SuperBitcoin to claim left !?!?!
THUS somewhere something doesnt add up?
Is anyone having the same observation? what could be intervening?
I do not see anything weird in the script, thus I am at a lost here.
Rgds,
Poul

I think the problem appears above 2147483647 satoshi.
Maybe a problem with cast int, struct.pack...

When trying to claim B2X, I am getting rejected and the transaction does not make it into mempool.

'reject' '\x02tx@Jnon-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID_SHIFT)

Dear bitcoin forkers,

Thank you for this great script! I have successfully clamied the following coins.

BCX, BCI, BCD, B2X, BTW, LBTC, FBTC, BTP, SBTC, BIFI, BTV

However, I am struggling with the following and would be grateful for any help:

BTN, BTF, BPA, BCA, BTCP, BICC, BTCH, GOD, BEC, BTH, BTT, BCP, WBTC, BCS, BTSQ, BTX

BTN seems to submit the transaction successfully but the balance never shows up.

BPA, BTT, BICC cannot connect to any peer, trying to reconnect 100 times with no luck.

BTX comes back with "Block explorer didn't find any coins at that address" even though the helper scripts find them.

BTF, BCA, GOD, BTH, BEC, WBTC have some sort of destination address issues, returning the below before submission:
Traceback (most recent call last):
File "claimer.py", line 1394, in
rawaddr = b58decode(destaddr)
File "claimer.py", line 68, in b58decode
n = n * 58 + b58ab.index(c)
ValueError: substring not found

BTCP :
No %s at this address!" % coin.ticker

BTCH:
No BTCH at this address!

My previous bitcoin address:
14q8yEpikK2waeB6NjDAQbPdHbvQYEPfP6

Faithfully,

Alexander

I would like to generate a transaction with many inputs and just one output.
If I have balance in three different addresses of a particular coin, I want to make just one transaction, sending all the balance together.

Is that possible?

Are you planning an upgrade where we can combine several utxo's in a single transaction bundle (multi input, single output)?

This was the only with problem in a set of 20 addresses.

Address: 1E4vfzJBS4jPvHewpGB7Z59cQ6ezvsHkHM

Error:

  File "claimer.py", line 1324, in <module>
    txindex, bciscript, satoshis = get_tx_details_from_blockchaininfo(args.txid, args.srcaddr, coin.hardforkheight)
  File "claimer.py", line 327, in get_tx_details_from_blockchaininfo
    if outinfo["addr"] == addr:
KeyError: 'addr'

Got the same error for any coin.

Command:

python2.7 claimer.py SBTC 1a08c68c543b2c78a63ba78bd3b97484d7cd10f6fb082fd264a8b2380c39926e PRIVKEY 1E4vfzJBS4jPvHewpGB7Z59cQ6ezvsHkHM 18X1pEg48ETzLf44sPPhaQCiqWjGTP7ALq

seed1.dns.btcd.io seed2.dns.btcd.io.... isn't working. just change for 139.198.190.221 in line 820 and the tx will be broadcasted.

Connecting to ('seed4.btcd.io', 7117) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known')
Will retry 98 more times.
then voila

Connecting to ('139.198.190.221', 7117) ... SUCCESS, connected to ('139.198.190.221', 7117)
---> 'version' (93 bytes)
<--- 'version' (110 bytes)
Version information:
protocol version 70015
services 13
timestamp Tue May 22 14:12:42 2018
user agent '/Bitcoin Diamond:0.14.2/'
block height 517968

Connecting to ('f.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 100 more times.
Connecting to ('a.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 99 more times.
Connecting to ('b.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 98 more times.
Connecting to ('c.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 97 more times.
Connecting to ('d.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 96 more times.
Connecting to ('e.btf.hjy.cc', 8346) ... Connection failed with: error(111, 'Connection refused')
Will retry 95 more times.
Connecting to ('f.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 94 more times.
Connecting to ('a.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 93 more times.
Connecting to ('b.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 92 more times.
Connecting to ('c.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 91 more times.
Connecting to ('d.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 90 more times.
Connecting to ('e.btf.hjy.cc', 8346) ... Connection failed with: error(111, 'Connection refused')
Will retry 89 more times.
Connecting to ('f.btf.hjy.cc', 8346) ... Connection failed with: timeout('timed out',)
Will retry 88 more times.

This is what I get.

Having read the README.md, it's clear to me how to use the script itself. But I'm still unsure of exact steps around using this script, specifically the destination address: This may sound stupid but do I have to manually create a wallet for each forked coin, and specify that wallet's public address in the script's command?

I'm just asking because "findmycoins.ninja" tells me I have unclaimed amounts in around 15 different forks and I assume I would have to manually create 15 corresponding wallets. Before I do that tedious task, can you confirm that I'm right? I really do have to manually create a wallet for each forked coin?

I keep receiving a connection failed with timeout when trying to send on the BCI chain. Is the coin dead or something wrong with the script?

New to scripts. Downloaded Python 2.7. Followed the script verbatim, however I keep getting invalid syntax error upon entry. Tried one space between inputs & two spaces. Double checked all data, can't see any errors in my inputs. Any ideas on where I may be messing up? Thanks in advance.

Hi,
You stated in the readme file that the default fee in set to 1000 sat, I was wondering if that is sat/byte or if that is sat/kilobyte. I would assume it's per kilobyte but I wanted to ask and make sure.

And I'm looking to claim CDY which is x1000 the BCH and because I have to do that in standalone mode and specify the number of satoshis do I put that in BCH or CDY? ie. 362,711,623 vs 362,711,623,000

this the transaction ID I'm trying to claim from by the way, on the BCH explorer and the CDY explorer

Thank you.

Can we claim BTCP with this script and send directly to a BTCP address (an exchange for example) when it's coming from a segwit address? Or do we need to send to a Z-address first?

When claiming it using the BTCP core wallet we can't send it to a BTCP address directly. It has to be sent to a Z-address first and from there to a BTCP address.

In the readme you write, we need for the standalone mode the

--txindex "output index in transaction"

Question: Where can I find this? Assumed this https://blockchain.info/de/tx/89112b285a9fff7f70f104bbb449f94cd2f6edb407c61b7bbcae26bc596cf52d was the latest transaction before the fork: Where can I find the output index in transaction?

Thank you.

Hi,

Running the script for BCX gave the following error:

Traceback (most recent call last):
File "claimer.py", line 1339, in
txindex, bciscript, satoshis = get_tx_details_from_blockchaininfo(args.txid, args.srcaddr, coin.hardforkheight)
File "claimer.py", line 316, in get_tx_details_from_blockchaininfo
res = urllib2.urlopen("https://blockchain.info/rawtx/%s" % txid)
File "C:\Python27\lib\urllib2.py", line 154, in urlopen
return opener.open(url, data, timeout)
File "C:\Python27\lib\urllib2.py", line 435, in open
response = meth(req, response)
File "C:\Python27\lib\urllib2.py", line 548, in http_response
'http', request, response, code, msg, hdrs)
File "C:\Python27\lib\urllib2.py", line 473, in error
return self._call_chain(*args)
File "C:\Python27\lib\urllib2.py", line 407, in _call_chain
result = func(*args)
File "C:\Python27\lib\urllib2.py", line 556, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 500: Internal Server Error

Any ideas?

Some exchanges have started accepting Bitcoin File (BIFI) deposits. Please add support for BIFI. BIFI repo has just been released a couple of days ago here https://github.com/bitcoinfile/bitcoinfile

You write in the read.me

Default fee is set to 1000 satoshis, but can be changed with the --fee option.

Question:
For which transaction do we pay fee? Is this a BTC transaction which needs fees, or is this the fork-coin transaction which needs this fees? Does bitcoin_fork_claimer make a transaction on the blockchain of the fork coin?

Thank you for an answer.

is there any way of doing this?

i already claimed bci using the script to a bci private key but if i wanted to dump it i would have to use the full node wallet, which failed to synchronize for me and i dont want to wait another month for it to sync as they have no light wallet yet.

they announced they would get listed on bitfinex on may first (not holding my breath) so if it actually does and gets a decent price i wont be able to dump.

is there any way of doing it with the current script or would it need a thorough rewrite?

thanks.

Any plans for supporting BTCC? thebitcoincore.org Thanks!

Any plans to add LBTC fork to this tool?

The scrypt doesn't recognize the key type when I introduce the p key.

Traceback (most recent call last):
File "C:\bitcoin_fork_claimer\claimer.py", line 1101, in
get_txid(coin, args)
File "C:\bitcoin_fork_claimer\claimer.py", line 346, in get_txid
restofprogram(coin, args)
File "C:\bitcoin_fork_claimer\claimer.py", line 961, in restofprogram
keytype, privkey, pubkey, sourceh160, compressed = identify_keytype(args.wifkey, args.srcaddr)
File "C:\bitcoin_fork_claimer\claimer.py", line 313, in identify_keytype
raise Exception("Unable to identify key type!")
Exception: Unable to identify key type!

it is a segwit adress, starts with 3, and the pkey starts wit L.

Any idea about what is hapenning?

I've tried sending a BTT transaction several times. The script is able to connect to the server. It tries to send the transaction, but it never ends up in the mempool. I'm wondering if this has anything to do with the replay support they recently added.

Is it possible for this script to support BTCP also?

Webite:
https://btcprivate.org/

Full node wallet:
https://github.com/BTCPrivate/bitcoin-private-full-node-wallet

Electrum wallet:
https://github.com/BTCPrivate/electrum-btcp

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.

With CDY i get this

generated transaction 508b5e0e365c0ba85c0df393688abce5e2d3f58cc48bf0278f479eac17a3b9ff

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 ('seed.cdy.one', 8367) ... SUCCESS, connected to ('47.75.50.178', 8367)
---> 'version' (93 bytes)
Connection failed with: error('Connection reset!',)
Will retry 100 more times.
Connecting to ('seed.bitcoincandy.one', 8367) ... SUCCESS, connected to ('47.90.53.137', 8367)
---> 'version' (93 bytes)
Connection failed with: error('Connection reset!',)
Will retry 99 more times.
Connecting to ('seed.cdy.one', 8367) ... SUCCESS, connected to ('47.75.50.178', 8367)
---> 'version' (93 bytes)
Connection failed with: error('Connection reset!',)
Will retry 98 more times.

BCP

generated transaction 3c70ef7541e48498180a960b179062031bab511fa04d1a8430e255e47e3bd1c4

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 ('seed.bcpfork.org', 8337) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known')
Will retry 100 more times.
Connecting to ('seed.bcpseeds.net', 8337) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known')
Will retry 99 more times.
Connecting to ('seed.bitcoincashplus.org', 8337) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known')
Will retry 98 more times.
Connecting to ('seed.bcpfork.org', 8337) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known')
Will retry 97 more times.
Connecting to ('seed.bcpseeds.net', 8337) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known')
Will retry 96 more times.

BTN

generated transaction 2437719802e303d51073a388c816bccffbc2ab51877111c0c0ee93c07725e219

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 ('dnsseed.bitcoin-new.org', 8838) ... SUCCESS, connected to ('39.104.79.58', 8838)
---> 'version' (93 bytes)
<--- 'version' (108 bytes)
Version information:
protocol version 70016
services 13
timestamp Thu May 10 04:49:57 2018
user agent '/Bitcoin New:0.15.0.1/'
block height 514234
---> 'verack' (0 bytes)
<--- 'verack' (0 bytes)
<--- 'sendheaders' (0 bytes)
---> 'headers' (1 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 2437719802e303d51073a388c816bccffbc2ab51877111c0c0ee93c07725e219
---> 'tx' (191 bytes)
SENT TRANSACTION: 2437719802e303d51073a388c816bccffbc2ab51877111c0c0ee93c07725e219
<--- 'reject' (57 bytes)
'reject' '\x02tx\x12\x14txn-mempool-conflict\x19\xe2%w\xc0\x93\xee\xc0\xc0\x11q\x87Q\xab\xc2\xfb\xcf\xbc\x16\xc8\x88\xa3s\x10\xd5\x03\xe3\x02\x98q7$'
<--- 'inv' (973 bytes)
transaction: 22c5d99c4576ab2239c720f1d1defbf72166864627928490615ff1bf93801307
transaction: 95d7a2d910cbd36bc53fa78fe8d36f465da361234705616a657000a82821ffbc
transaction: 42dd924a74aa6e673158f3fa04ae3fad5ace02611acf9498eaefec99c1f84eff
transaction: 12dfca1edd5f080b8fbdf38566583c1618bf40abb296ee51803a8bcabe5c2ece
transaction: c1d925d4347a411f2104e16b6b3602b895c8ae529eca0ce190e1632e56c8048e
transaction: 9054eeaefd07f633e58441a97c45aedf9c2cae85a1078931f4e8a6d92cda1738
transaction: 03945a710db31b4af8401fbccfd012476d8b47f0929e824af744420458830f2e
transaction: 003177518232a71d695a305bfb5cc019e789c9ab3df8ad0fbdf6244702a44b16
transaction: 17231c3d63f6a7a054ca049614d3a7dc12601b1b8f34004d53254fcf9948f10b
transaction: b10e5b7ca20d91ca352bcff4cb3a3293f9e1e302b9cd61b03129856e565ec2fe
...
Not printing additional 17 transactions

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

Attempt at claiming BTV was not successful. The transaction never made it.

<--- '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.

Thank you for your great work!

I tried to claim BTN (Bitcoin New). The transaction was transmitted but did not appear in the mempool and the coins did not arrive at the destination, so probably it was rejected by the network. I see in #13 the user reports some differences in the parameters for BTN, but I am not familiar enough with both codebases to spot the difference.

Connecting to ('dnsseed.bitcoin-new.org', 8838) ... Connection failed with: gaierror(-2, 'Name or service not known')

I want to claim BCH.

So I have this address for claiming BCH:
1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh

When I have a look at the Block Explorer:
https://blockchain.info/address/1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh
there are two transactions:
c7ad778f0197f4750813900d207e6ee4c416d9f699906074a8a3598a23450c4b and
bdb96a71881780b5622b9ab4a382f207e6d6514d6a5cc5dfa0ccafe243662f79

A) Do I have to make two commands to claim all BCH like:

python claimer.py BCH c7ad778f0197f4750813900d207e6ee4c416d9f699906074a8a3598a23450c4b PRIV_KEY_OF_1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh 1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh BCH_ADDR
python claimer.py BCH bdb96a71881780b5622b9ab4a382f207e6d6514d6a5cc5dfa0ccafe243662f79 PRIV_KEY_OF_1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh 1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh BCH_ADDR

B) Or is it enough to only make one command to claim all BCH's like:
python claimer.py BCH c7ad778f0197f4750813900d207e6ee4c416d9f699906074a8a3598a23450c4b PRIV_KEY_OF_1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh 1Pv17qmWEANskhVr4PTNd73sc87CWjMPAh BCH_ADDR

C) If I have to make two commands (like A) ), do I have to pay transaction fees twice?

Would appreciate your answers. Thank you.

With kind regards
Golddouble

line 426 reads:

return self.maketx_segwitsig(sourcetx, sourceidx, sourceh160, sourcesatoshis, sourceprivkey, pubkey, compressed, outscript, fee, keytype)

while it should be

return self.maketx_segwitsig(sourcetx, sourceidx, sourceh160, signscript, sourcesatoshis, sourceprivkey, pubkey, compressed, outscript, fee, keytype)

Thank you for your great work！
I have successfully claimed BCX, BTX using this python script file, but have problems with BTH and BCI .

# BTH
YOU ARE ABOUT TO SEND 1139.91000000 BTH (equivalent to 11.39910000 BTC) FROM (1HRU.......my address)
1139.90900000 BTH (equivalent to 11.39909000 BTC) TO HTiKbtCMSFkVJfjN7Pf62Hxq2racC4r28C
!!! 0.00100000 BTH (equivalent to 0.00001000 BTC) WILL BE SENT AS FEES! CONTINUE AT YOUR OWN RISK !!!

Write 'I am sending coins on the Bitcoin Hot network and I accept the risks' to continue
I am sending coins on the Bitcoin Hot network and I accept the risks
generated transaction aee326449c0691017e658cd16fb2a22283081e3383272083f1a3c10473014584

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 ('seed-jp.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 100 more times.
Connecting to ('seed-hk.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 99 more times.
Connecting to ('seed-uk.bitcoinhot.co', 8222) ... Connection failed with: gaierror(11001, 'getaddrinfo failed')
Will retry 98 more times.
Connecting to ('seed-cn.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 97 more times.
Connecting to ('seed-us.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 96 more times.
Connecting to ('seed-jp.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 95 more times.

    Will retry 3 more times.

Connecting to ('seed-jp.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 2 more times.
Connecting to ('seed-hk.bitcoinhot.co', 8222) ... Connection failed with: timeout('timed out',)
Will retry 1 more times.
Connecting to ('seed-uk.bitcoinhot.co', 8222) ...
Traceback (most recent call last):
File "D:\bitcoin_fork_claimer-master\claimer.py", line 1467, in
client.send_tx(txhash, tx, args.fee)
File "D:\bitcoin_fork_claimer-master\claimer.py", line 466, in send_tx
self.sc = socket.create_connection(address, 10)
File "C:\Python27\lib\socket.py", line 557, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
socket.gaierror: [Errno 11001] getaddrinfo failed

# BCI
generated transaction 4e12751178a2be1afa41abe0abf7c31bd8ccd33e64ce19386e6207d0d8c9b8f0

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 ('seeder1.bci-server.com', 8331) ... Connection failed with: error(10061, '')
Will retry 100 more times.
Connecting to ('seeder2.bci-server.com', 8331) ... Connection failed with: error(10061, '')
Will retry 99 more times.
Connecting to ('seeder3.bci-server.com', 8331) ... Connection failed with: error(10061, '')
Will retry 98 more times.
Connecting to ('74.208.166.57', 8331) ... SUCCESS, connected to ('74.208.166.57', 8331)
---> 'version' (93 bytes)
<--- 'version' (113 bytes)
Version information:
protocol version 70016
services 13
timestamp Mon May 21 07:40:22 2018
user agent '/Bitcoin Interest:0.15.0.1/'
block height 526109
---> 'verack' (0 bytes)
<--- 'verack' (0 bytes)
<--- 'sendheaders' (0 bytes)
---> 'headers' (1 bytes)
<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'inv' (37 bytes)
---> 'mempool' (0 bytes)
<--- 'addr' (31 bytes)
Got peer address: 74.208.166.57:8331
<--- '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 4e12751178a2be1afa41abe0abf7c31bd8ccd33e64ce19386e6207d0d8c9b8f0
---> 'tx' (192 bytes)
SENT TRANSACTION: 4e12751178a2be1afa41abe0abf7c31bd8ccd33e64ce19386e6207d0d8c9b8f0
<--- '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: 48b584d88f4c2ec83fbe55e5e685c3b64e9de588cd41c49bcafd05b734913142
transaction: 7a9f4041cfe5945993168e5e4940d01a96b8719f91c2f2c6456220bdee27eafa

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

   Our transaction was not found in the mempool.
   Traceback (most recent call last):

File "D:\bitcoin_fork_claimer-master\claimer.py", line 1467, in
client.send_tx(txhash, tx, args.fee)
File "D:\bitcoin_fork_claimer-master\claimer.py", line 571, in send_tx
raise Exception("\tGiving up on transaction. Please verify that the inputs have not already been spent.")
Exception: Giving up on transaction. Please verify that the inputs have not already been spent.

Of course, I have not already been spent or claimed BCI.

Thank you!

Transactions NOT shown in Mempool for SegWit addresses to my knowledge. I haven't tried with Legacy addresses.

I've written an easy to follow tutorial on using ymgve/bitcoin_fork_claimer to claim bitcoin forks. It might be helpful for people who are planning on claiming the forks. Maybe it can be linked from the README.md of ymgve/bitcoin_fork_claimer.

The tutorials are available here https://steemit.com/bitcoin/@thegripmaster/bitcoin-fork-claim-guide-or-claim-your-forked-bitcoins-from-trezor-ledger-nano-keepkey and https://github.com/fazlearefin/bitcoin-fork-claim-guide

Connecting to ('seed1.bitvote.one', 8333) ... SUCCESS!
---> 'version' (93 bytes)
Traceback (most recent call last):
File "C:\Python27\claimer.py", line 1038, in
client.send_tx(txhash, tx, args.fee)
File "C:\Python27\claimer.py", line 428, in send_tx
cmd, payload = client.recv_msg()
File "C:\Python27\claimer.py", line 399, in recv_msg
header = recv_all(24)
File "C:\Python27\claimer.py", line 395, in recv_all
raise socket.error("Connection reset!")
socket.error: Connection reset!

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)

Hi guy, BTT update source

Solve the bitcoin forks currency between the issue of replay.

https://github.com/bitcointop/bitcointop

Claiming from a segwit address (private key) doesn't seem to work.
Is this not yet possible with the script?

Hi,
is it possible to claim the forked coins from a copay wallet? Thanks

In the read.me you write:

In blockchain.info mode it uses the blockchain.info API to query and validate information about the transaction you're spending from. This only works for transferring/claiming coins that existed on the BTC main chain pre-fork.

I do not understand what this means.

Surely I want to claim all this coins:

B2X - Segwit 2X
BCD - Bitcoin Diamond
BCH - Bitcoin Cash
BCX - Bitcoin X
BPA - Bitcoin Pizza
BTF - Bitcoin Faith
BTG - Bitcoin Gold
BTH - Bitcoin Hot
BTN - Bitcoin New
BTP - Bitcoin Pay
BTSQ - Bitcoin Community
BTT - Bitcoin Top
BTV - Bitcoin Vote
BTW - Bitcoin World
BTX - Bitcore
SBTC - Super Bitcoin
UBTC - United Bitcoin
WBTC - World Bitcoin

So I must to know, which of them I can claim with the blockchain.info assisted mode, and which I have to claim with the standalone mode.

Can you please help me. Thank you.

There are a couple of exchanges supporting deposits of this fork now, but it's very difficult to claim.

Hi, Im having problems claiming BTG, any help would be appreciated.

Connecting to ('btg1.stage.bitsane.com', 8338) ... SUCCESS, connected to ('164.132.121.47', 8338)
---> 'version' (93 bytes)
<--- 'version' (109 bytes)
Version information:
protocol version 70016
services 13
timestamp Tue May 22 12:15:58 2018
user agent '/Bitcoin Gold:0.15.0.2/'
block height 529591
---> 'verack' (0 bytes)
<--- 'verack' (0 bytes)
<--- 'sendheaders' (0 bytes)
---> 'headers' (1 bytes)
<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'inv' (37 bytes)
---> 'mempool' (0 bytes)
<--- 'addr' (31 bytes)
Got peer address: 164.132.121.47: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 d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
---> 'tx' (218 bytes)
SENT TRANSACTION: d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
<--- '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' (97815 bytes)
transaction: f2f1711a25d5b14e930b3bafdc105ce6d136ed75112c5b56f3f596e4390e2739
transaction: 0c06b486bb94187ed23e38629c5cbde0ee21181fc9bb0980cd312e058febe590
transaction: c5277b2098a18a8bffbff11706db57c6a4e83c9648f0c88cbcf82fcdd4bd7aaf
transaction: a9f7063ddf6ad47d30a56298a7261be5fc78acd58490034d2e648253e4007abc
transaction: d43e736db88145f3aede5546cf93859badc6c5e111198be6369adb569dc34082
transaction: 853d51e706f82ef952c9ec26e706e178dde6b900ec3dd219ceac9285a209737b
transaction: 56b95c63208b290f8d2eac6f49ddf90d5206b39cf5753b9143af7549210c14e7
transaction: f41aa64c7865433fe36f1b9e08b081f86c48322d7163db4b39c54187b3403192
transaction: 3bc07708fcfe30e5211981fc869abb11d4f153e1a116a97d9346bab10c07926e
transaction: fc2eae66a4c50f6ca597c17a7563744c0eef15889e3b798fdcc39fa2285de1d0
...
Not printing additional 2707 transactions

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

<--- 'addr' (61 bytes)
Got peer address: 110.10.189.189:8338
Got peer address: 109.128.16.178:8338
<--- 'inv' (37 bytes)
block: 000000002005dfd5c1656befd777faeadb4502aaf5b0e77879e30ab92c2c796f
---> 'getdata' (37 bytes)
requesting 1 blocks
<--- 'block' (739746 bytes)
Transaction not included in observed block.
<--- 'addr' (31 bytes)
Got peer address: [2001:0678:053c:0002:0010:0000:0001:0103]:8338
<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'tx' (218 bytes)
Re-sent transaction: d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
---> 'mempool' (0 bytes)
<--- 'inv' (97275 bytes)
transaction: 48bfa144878edd8c6b08b8494cab7c0b2cd10599a647f2ffb1ceb06b21ddb049
transaction: 8afd4b5c931dfcfebbfd8b448fbbcc74a345b37e757dc6cceaddebdc04ba3929
transaction: ac40dc3f920004ec5ed0c79ca1437ae25e03b2e98d4e54eda077fbb55bcbe8af
transaction: c576178f84f43ed596a46d3f681cd62183cb6fa945739af3dcc5608b801fde9c
transaction: 82c86c7714dd99202deac6f35e2f70c54ebb41619f2bbb092d8d6bee2b310c81
transaction: 181f2b1229a323919527868884b7e055c6eaef58e1348d85d6e75cf2bbfb2e60
transaction: 60f2e717b0a1dac4ea9e3d1aa88df6867358ed28361722ba4866ca878d15f06f
transaction: a4b310dd5392e25c87477d47ee9586d0b42a5c84421810356d60d83d5022a052
transaction: fc5a17c6d56a0326526ad176202840a9400300db1162896483bb050004142ec2
transaction: e7c0d5a6482ed7fba4d05519ac02b1b54e8bf5d99cd140fd823466d0e634ac9e
...
Not printing additional 2692 transactions

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

<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'tx' (218 bytes)
Re-sent transaction: d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
---> 'mempool' (0 bytes)
<--- 'inv' (97743 bytes)
transaction: 48bfa144878edd8c6b08b8494cab7c0b2cd10599a647f2ffb1ceb06b21ddb049
transaction: 8afd4b5c931dfcfebbfd8b448fbbcc74a345b37e757dc6cceaddebdc04ba3929
transaction: 7a6a27cdaa7372a26383626fa7fb949219ebde7058bb238e3ce731322f706bc9
transaction: ac40dc3f920004ec5ed0c79ca1437ae25e03b2e98d4e54eda077fbb55bcbe8af
transaction: c576178f84f43ed596a46d3f681cd62183cb6fa945739af3dcc5608b801fde9c
transaction: 82c86c7714dd99202deac6f35e2f70c54ebb41619f2bbb092d8d6bee2b310c81
transaction: 181f2b1229a323919527868884b7e055c6eaef58e1348d85d6e75cf2bbfb2e60
transaction: 60f2e717b0a1dac4ea9e3d1aa88df6867358ed28361722ba4866ca878d15f06f
transaction: ca676bfb8ed5bc8657332a0ca032a41ea91b5ed323d42038a10000c3d2c4ea6b
transaction: 70989e8e2adfe09e776b0d1fee5b7b6968d40aed4da5bac342c8a88e79738fb5
...
Not printing additional 2705 transactions

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

<--- 'addr' (31 bytes)
Got peer address: [2001:0000:9d38:78cf:043b:1839:dd09:a52f]:8338
<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'tx' (218 bytes)
Re-sent transaction: d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
---> 'mempool' (0 bytes)
<--- 'inv' (98247 bytes)
transaction: e6cf95330921d67c7bc50c7d7c5fbf3e33221143a23c12ff666b603f0963157e
transaction: 48bfa144878edd8c6b08b8494cab7c0b2cd10599a647f2ffb1ceb06b21ddb049
transaction: 8afd4b5c931dfcfebbfd8b448fbbcc74a345b37e757dc6cceaddebdc04ba3929
transaction: 7a6a27cdaa7372a26383626fa7fb949219ebde7058bb238e3ce731322f706bc9
transaction: ac3e3374fc0fb42996d9f014e0428381a652fdb8b5405b2f8a666e2c5c7394a2
transaction: ad4fb23794a8ae4b004fac6240b10ed346f8c24c12832883c45dd0088f6f60f5
transaction: ac40dc3f920004ec5ed0c79ca1437ae25e03b2e98d4e54eda077fbb55bcbe8af
transaction: c576178f84f43ed596a46d3f681cd62183cb6fa945739af3dcc5608b801fde9c
transaction: 82c86c7714dd99202deac6f35e2f70c54ebb41619f2bbb092d8d6bee2b310c81
transaction: 181f2b1229a323919527868884b7e055c6eaef58e1348d85d6e75cf2bbfb2e60
...
Not printing additional 2719 transactions

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

<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'tx' (218 bytes)
Re-sent transaction: d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
---> 'mempool' (0 bytes)
<--- 'inv' (98751 bytes)
transaction: e6cf95330921d67c7bc50c7d7c5fbf3e33221143a23c12ff666b603f0963157e
transaction: 48bfa144878edd8c6b08b8494cab7c0b2cd10599a647f2ffb1ceb06b21ddb049
transaction: 8afd4b5c931dfcfebbfd8b448fbbcc74a345b37e757dc6cceaddebdc04ba3929
transaction: 7a6a27cdaa7372a26383626fa7fb949219ebde7058bb238e3ce731322f706bc9
transaction: ac3e3374fc0fb42996d9f014e0428381a652fdb8b5405b2f8a666e2c5c7394a2
transaction: ad4fb23794a8ae4b004fac6240b10ed346f8c24c12832883c45dd0088f6f60f5
transaction: ac40dc3f920004ec5ed0c79ca1437ae25e03b2e98d4e54eda077fbb55bcbe8af
transaction: c576178f84f43ed596a46d3f681cd62183cb6fa945739af3dcc5608b801fde9c
transaction: 82c86c7714dd99202deac6f35e2f70c54ebb41619f2bbb092d8d6bee2b310c81
transaction: a476f27e475260200bcea8953cb9dcfebd3443619f42d9581b2c852bf960a84a
...
Not printing additional 2733 transactions

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

<--- 'ping' (8 bytes)
---> 'pong' (8 bytes)
---> 'tx' (218 bytes)
Re-sent transaction: d7f18f6cc671227e1522f78e9c8b5196bc29fe59e132607c9d67a8998b0a5b37
---> 'mempool' (0 bytes)
<--- 'inv' (99183 bytes)
transaction: e6cf95330921d67c7bc50c7d7c5fbf3e33221143a23c12ff666b603f0963157e
transaction: 48bfa144878edd8c6b08b8494cab7c0b2cd10599a647f2ffb1ceb06b21ddb049
transaction: 8afd4b5c931dfcfebbfd8b448fbbcc74a345b37e757dc6cceaddebdc04ba3929
transaction: 7a6a27cdaa7372a26383626fa7fb949219ebde7058bb238e3ce731322f706bc9
transaction: ac3e3374fc0fb42996d9f014e0428381a652fdb8b5405b2f8a666e2c5c7394a2
transaction: ad4fb23794a8ae4b004fac6240b10ed346f8c24c12832883c45dd0088f6f60f5
transaction: ac40dc3f920004ec5ed0c79ca1437ae25e03b2e98d4e54eda077fbb55bcbe8af
transaction: c576178f84f43ed596a46d3f681cd62183cb6fa945739af3dcc5608b801fde9c
transaction: 82c86c7714dd99202deac6f35e2f70c54ebb41619f2bbb092d8d6bee2b310c81
transaction: a476f27e475260200bcea8953cb9dcfebd3443619f42d9581b2c852bf960a84a
...
Not printing additional 2745 transactions

Our transaction was not found in the mempool.

Traceback (most recent call last):
File "claimer.py", line 1467, in
client.send_tx(txhash, tx, args.fee)
File "claimer.py", line 571, in send_tx
raise Exception("\tGiving up on transaction. Please verify that the inputs have not already been spent.")
Exception: Giving up on transaction. Please verify that the inputs have not already been spent.

When I have to claim forks from one address but with different "source transaction ID"'s:
For example this:

claimer.py <cointype> <source transaction ID 1> <source private key 1> <source address 1> <destination address 1>

and afterwards:

claimer.py <cointype> <source transaction ID 2> <source private key 1> <source address 1> <destination address 1>

Do I have to start claimer.py twice?

First start
claimer.py <source transaction ID 1> <source private key 1> <source address 1> <destination address 1>

Then wait until block inclusion; and afterwards start the second command:

claimer.py <source transaction ID 2> <source private key 1> <source address 1> <destination address 1>

Or is there a method to start both with one command? For example something like this:
claimer.py <source transaction ID 1>, <source transaction ID 2> <source private key 1> <source address 1> <destination address 1>

Or for example
claimer.py <source transaction ID 1> <source private key 1> <source address 1> <destination address 1>, <source transaction ID 2> <source private key 1> <source address 1> <destination address 1>

Thank you for your help.

Hi, I am trying to claim Bitcoin Clean (BCL) and I am receiving this warning, please tell me if I should proceed or not (my BTC address starts with 3 and so does the Yobit address where I would like to deposit... so I assume they are both Segwit addresses?):

YOU ARE TRYING TO SEND TO A P2SH ADDRESS! THIS IS NOT NORMAL! Are you sure you know what you're doing?

Write 'I am aware that the destination address is P2SH' to continue

Thanks a lot for your help.

1)can you format the e-mail address so it opens the mail client? (mailto: ...)
2)how to insert pictures efficiently? (can you demo a couple of pics to show how you want them included? Try with a random picture of a book atop the guide
3)Why in the footer I only see "How it works" "Preparation" "The golden rule" and not the following ones (for the guide sublinks)?
4)the particle effect takes a lot of space in desktop mode... can we do something about it?
5)Coinmarketpie doesn't recognise bitpie and as an exchange. Yet the info about Bitpie and Coinomi is prominent for us... Can you think of a fix?
6)The field TRADE FEE is supposed to be a %, can you change it to string?
7)The field COMMISSION should be named "WITHDRAWAL FEE" - it could be both a fixed amount or a percentage so it should be a string as well
8)When you calculate the coin value, multiply it by the fork ratio. See example of BCX: they have 10k ratio, therefore value yielded should be multiplied by 10k too
9)how to make an inner link from the instructions on home to the "page" with the fork guide?
10) In "home" I added the blueprint for a consultancy page (similar to the "Services" page on forkdrop.io) - can you format it and create it?