search

ymgve / bitcoin_fork_claimer

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

Problem with CDY, BCP, BTN claim #41

Open talesfromthecrypt opened 6 years ago

talesfromthecrypt commented 6 years ago

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.
ymgve commented 6 years ago

CDY works fine in the latest version here, not sure why your system has issues. Maybe flush your DNS cache so the seeds provide other nodes.

BCP seed nodes seem down and your only option is to find some active seed IPs and use those instead.

I need more info about the BTN transaction to see why it fails, what TXID are you trying to claim?

talesfromthecrypt commented 6 years ago

CDY works fine in the latest version here, not sure why your system has issues. Maybe flush your >DNS cache so the seeds provide other nodes. I need more info about the BTN transaction to see why it fails, what TXID are you trying to claim?

But the error says that its reset by peer Connecting to ('seed.bitcoincandy.one', 8367) ... SUCCESS, connected to ('47.52.0.131', 8367) ---> 'version' (93 bytes) Connection failed with: error(54, 'Connection reset by peer') Will retry 100 more times.

ymgve commented 6 years ago

I don't know why you got connection reset by peer. I just did a successful CDY transaction with the latest version of the script. If you want to manually edit the seeds, the node it worked with for me was "47.74.144.158"

talesfromthecrypt commented 6 years ago

I tried from several different country locations, from what country did you try with success last time?

ymgve commented 6 years ago

Did you verify that the script you're using is the latest version? Country shouldn't matter.

talesfromthecrypt commented 6 years ago

I just have downloaded again a zip archive with the script from repository, and here is what i do:

claimer.py CDY 24cc785f5b7c6827a72b80608496ec35e315dbf9cb50fcec575cedda557f2a0c BCH Private key 1312JQCvamfXs7qHD326VFrXSAd9a1w8CE CVP6M7hoiH9v5MxzXzVe9oJSiDyqyFFrqP --txindex 0 --satoshis 706694385 (i have converted the amount i had in BCH on this address the conversion was 706694385.8801, thus i put only the part before the point )

ymgve commented 6 years ago

The details doesn't matter for CDY as the disconnect happens before the transaction is sent at all. Also I have no idea where you got that satoshis amount from, the correct amount should be 3996258438.

talesfromthecrypt commented 6 years ago

I have used this online converter and for the BCH it should less then for BTC dont you think so? https://www.cryps.info/en/BCH_to_Satoshi/39.96258438/

ymgve commented 6 years ago

That is a currency converter. You need to give the number of raw BCH satoshis, not BTC satoshis.

talesfromthecrypt commented 6 years ago

Oh, now it worked out for me, thank you!

talesfromthecrypt commented 6 years ago

The BTN error: 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) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known') Will retry 100 more times. Connecting to ('dnsseed.bitcoin-new.org', 8838) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known') Will retry 99 more times. Connecting to ('dnsseed.bitcoin-new.org', 8838) ... Connection failed with: gaierror(8, 'nodename nor servname provided, or not known') Will retry 98 more times.

talesfromthecrypt commented 6 years ago

Trying with TXid: 721650cc9fedbfce20fa77f402782a1730b2208ceba703ae8f4ba810db6d8f7a

ymgve commented 6 years ago

That's a different situation than the first BTN issue you described. Seems like you have DNS problems?

talesfromthecrypt commented 6 years ago

Well, as i said, i am trying from different locations, i already flashed the dns, but still have this problem. Should i try a different location?

talesfromthecrypt commented 6 years ago

Now, from my original location i get this:

I am sending coins on the Bitcoin New network and I accept the risks 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.41', 8838) ---> 'version' (93 bytes) <--- 'version' (108 bytes) Version information: protocol version 70016 services 13 timestamp Thu May 10 14:01:28 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.
ymgve commented 6 years ago

Actually, seems like BTN has done an "upgrade" of their network where they started a completely new blockchain. And it seems like not all addresses that held coins at the time of the fork have been funded, look up your address here: http://explorer.btn.org/

talesfromthecrypt commented 6 years ago

Should I convert it firstly?

ymgve commented 6 years ago

There is nothing to convert. You don't own any coins on the new BTN chain, and I don't know if there is any off-chain claiming process.

talesfromthecrypt commented 6 years ago

Thus I guess i lost my BTN claim option for ever... And with BCP i should find a pingable seed IP