Tool to claim coins for all Bitcoin forks without using wallets or running nodes

[Ayms]

Litecoin Cash added

[1714650565]

1714650565

[1714650565]

1714650565

[mys5droid]

So I get this tool is used to either a) send transactions with private key without loading wallet or b) to send or "claim" your coins - by sending them to an address such as an exchange?

How exactly you use it? I assume the data comes from the block explorer...

But which block explorer? If I am claiming my BCH for example, do I look at my transaction in BTC explorer or BCH explorer? Is the block explorer how I know how much of BCH I have?

I am interested in this tool but not sure how exactly it works. I think you just fill in the information from the block explorer, put in the to address for BCH then put the BCH tx fees and dev fee is in BCH?

Thanks

[tarken002]

thanks , i will try

[Ayms]

So I get this tool is used to either a) send transactions with private key without loading wallet or b) to send or "claim" your coins - by sending them to an address such as an exchange?

Yes, exactly

How exactly you use it? I assume the data comes from the block explorer...

Yes, did your read the Quick Start Guide: https://github.com/Ayms/bitcoin-transactions#quick-start-guide ?

The tuto is not as good as it could be, if someone one day wants to make a tuto video...

It's not difficult if you follow the instructions but some little work is required, doing more simple without reverting to a dubious wallet is not possible

But which block explorer? If I am claiming my BCH for example, do I look at my transaction in BTC explorer or BCH explorer? Is the block explorer how I know how much of BCH I have?

You can use either BTC explorer or BCH explorer (or other forks explorer when they exist), please see the link above and https://github.com/Ayms/bitcoin-transactions#claiming-your-coins-bchbtgbcdsbtccdyetc---addresses-and-getting-free-coins

I am interested in this tool but not sure how exactly it works. I think you just fill in the information from the block explorer, put in the to address for BCH then put the BCH tx fees and dev fee is in BCH?

Thanks

Yes, the adresses are the same between networks in fact, so you don't even need to convert them, for example you can use BTC addresses to claim BCH or BTG or whatever (but even if they are the same too don't use the new BCH addresses format for now, it will be supported soon)

It's not a bad idea to take the time to read everything once in https://github.com/Ayms/bitcoin-transactions before proceeding

The best is not to specify any amount, prevamount is enough and the module will calculate amount+dev fees according to the network fees that you decide (decide them in a way that they are coherent with the network you are dealing with, for the new forks it can be very low, for BCH not)

If pb or doubt you can PM/email me, you must get the information "Transaction verified" at the end

If you make a mistake with the inputs the tx will just be rejected, so there is no impact, but just make sure not to make a mistake with the destination address because nobody can check this for you (and check closely the output of the create command before sending the tx), it's of course much better not to use multisig or segwit addresses for the destination

[Ayms]

Support to cashaddresses added, using the very excellent https://github.com/Ayms/cashaddress module

The tool can be used with normal BCH addresses like 1BpEi6DfDAUFd7GtittLSdBeYJvcoaVggu or bitcoincash:qpm2qsznhks23z7629mms6s4cwef74vcwvy22gdx6a or just qpm2qsznhks23z7629mms6s4cwef74vcwvy22gdx6a

[Ayms]

BTCP fork updated and support to automatic Bitcoin Private (BTCP) address conversion added, you can move your coins using legacy BTC addresses and a BTC explorer, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz prevamount=0.00998277 previndex=31 privkey=privkey addr=139AJaowXYerd9hrAyieWyzRxLVzaEP9PN fees=0.00000300

BTC 19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz --> BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
BTC 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN --> BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

You will see in the output of the command that the addresses were converted

Or using legacy ZCL addresses and a ZCL explorer, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=t1SmcsNFjkiqhag8ms6BFZwVRcLSdjqiK8v prevamount=0.00998277 previndex=31 privkey=privkey addr=t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M fees=0.00000300

ZCL t1SmcsNFjkiqhag8ms6BFZwVRcLSdjqiK8v --> BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
ZCL t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M --> BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

Of course this works too if you use BTCP addresses for the origin and/or the destination

Again, please remember that the addresses are the very same between networks, only the way they are represented is different (so if you have the private key corresponding to 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN above, which is the same than t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M on ZCL, you have the private key corresponding to b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s and you can use both addresses on BTCP)

Then to send your transaction:

node tx.js BTCP send full_transaction dnsseed.btcprivate.org

dnsseed.btcprivate.org is not accepting connections for now but probably will after the fork

[bitcoincashplus]

Bitcoin Cash Plus added

But please see: "Bitcoin Cash Plus (Warning: this fork does not implement any replay protection with BCH, it's not recommended to use it unless you really know what you are doing and you owe the destination addresses where you send your coins)"

In one word: don't use it since there is a suspicion that we are dealing with amateurism stuff (or intended one since the devs don't answer, cf https://github.com/bitcoincashplus/bitcoincashplus/issues/32)

[Update]

Warning sent: https://bitcointalk.org/index.php?topic=2392061.msg29329533#msg29329533

"This just means that if you still have BCH before the BCH fork (therefore BCPs), transactions that you will do with them can be replayed on both chains (BCH and BCP)"

Unfortunately there is nothing we can do about this, so, finally, unlike what I keep saying (don't rush to "claim" your coins, you have them already), given the number of forks, it's probably not a bad idea to "claim" coins (ie to move them after a fork so the coins can't be subject later to a replay attack of a later misdesigned fork, which of course can be intentional)

[Update2]


To explain a little bit more, those that are in such a situation, should they decide to send their coins, should send them ONLY to an address that they master (and not to an exchange for example), then the attacker could replay the transaction and will just send the coins to you on the other chain, which can be disturbing since you are not supposed to know it (and you might not even know that someone sent your coins to some unknown chains) and you might be confused by the different addresses between both chains (which in fact are the same, see the tool repo again where this is explained) to find your coins back

Bitcoin cash plus forked from Bitcoin chain NOT Bitcoin Cash. We have 2-way Replay protection (SIGHASH_FORK_ID).

[Ayms]

Bitcoin Cash Plus added

But please see: "Bitcoin Cash Plus (Warning: this fork does not implement any replay protection with BCH, it's not recommended to use it unless you really know what you are doing and you owe the destination addresses where you send your coins)"

In one word: don't use it since there is a suspicion that we are dealing with amateurism stuff (or intended one since the devs don't answer, cf https://github.com/bitcoincashplus/bitcoincashplus/issues/32)

[Update]

Warning sent: https://bitcointalk.org/index.php?topic=2392061.msg29329533#msg29329533

"This just means that if you still have BCH before the BCH fork (therefore BCPs), transactions that you will do with them can be replayed on both chains (BCH and BCP)"

Unfortunately there is nothing we can do about this, so, finally, unlike what I keep saying (don't rush to "claim" your coins, you have them already), given the number of forks, it's probably not a bad idea to "claim" coins (ie to move them after a fork so the coins can't be subject later to a replay attack of a later misdesigned fork, which of course can be intentional)

[Update2]


To explain a little bit more, those that are in such a situation, should they decide to send their coins, should send them ONLY to an address that they master (and not to an exchange for example), then the attacker could replay the transaction and will just send the coins to you on the other chain, which can be disturbing since you are not supposed to know it (and you might not even know that someone sent your coins to some unknown chains) and you might be confused by the different addresses between both chains (which in fact are the same, see the tool repo again where this is explained) to find your coins back

Bitcoin cash plus forked from Bitcoin chain NOT Bitcoin Cash. We have 2-way Replay protection (SIGHASH_FORK_ID).

Yes, this is what is explained, you have the same replay protection than BCH, which makes possible to replay transactions on BCH (ie for coins not moved after the BCH fork)

Between all the forks that's the only known case for now of replay protection collision, you should correct is asap (adding for example a FORKID_IN_USE not used by another fork, see https://github.com/Ayms/bitcoin-transactions/blob/master/tx.js#L80-L473)

[Ayms]

Update for BTCP transactions can be sent to dnsseed.btcprivate.org and btcp.suprnova.cc

[Ayms]

BitClassic Coin "BICC" added

[Ayms]

You can use also the BTCP explorer to send transactions https://explorer.btcprivate.org/tx/send

In that case 'transaction body' must be used, not the 'complete transaction', see https://github.com/Ayms/bitcoin-transactions#sending-your-transaction

[Ayms]

BTCP fork updated and support to automatic Bitcoin Private (BTCP) address conversion added, you can move your coins using legacy BTC addresses and a BTC explorer, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz prevamount=0.00998277 previndex=31 privkey=privkey addr=139AJaowXYerd9hrAyieWyzRxLVzaEP9PN fees=0.00000300

BTC 19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz --> BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
BTC 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN --> BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

You will see in the output of the command that the addresses were converted

Or using legacy ZCL addresses and a ZCL explorer, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=t1SmcsNFjkiqhag8ms6BFZwVRcLSdjqiK8v prevamount=0.00998277 previndex=31 privkey=privkey addr=t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M fees=0.00000300

ZCL t1SmcsNFjkiqhag8ms6BFZwVRcLSdjqiK8v --> BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
ZCL t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M --> BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

Of course this works too if you use BTCP addresses for the origin and/or the destination

Again, please remember that the addresses are the very same between networks, only the way they are represented is different (so if you have the private key corresponding to 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN above, which is the same than t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M on ZCL, you have the private key corresponding to b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s and you can use both addresses on BTCP)

Then to send your transaction:

node tx.js BTCP send full_transaction dnsseed.btcprivate.org

dnsseed.btcprivate.org is not accepting connections for now but probably will after the fork

The above method works to move/claim ZCL but not BTC, for BTC you need to:

- convert your addresses to BTCP ones, for this you can use a fake create command with your BTC addresses and look at the ouput, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz prevamount=0.00998277 previndex=0 privkey=privkey addr=139AJaowXYerd9hrAyieWyzRxLVzaEP9PN fees=0.00000300

BTC 19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz converted in BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
BTC 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN converted in BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

- use the BTCP explorer: https://explorer.btcprivate.org/address/b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr to find your BTCP

- and for each transaction that you see:

node tx.js BTCP create prevtx=transaction prevaddr=b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr prevamount=(prevamount associated to transaction) previndex=0 privkey=(privkey of  b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr) addr=(destination address) fees=0.00000300

or for multisig

node tx.js BTCP create prevtx=transaction prevaddr=bxDNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr prevamount=(prevamount associated to transaction) previndex=0 privkey=priv1-priv2-redeem addr=(destination address) fees=0.00000500

- send the "transaction body" of the output of the command using https://explorer.btcprivate.org/tx/send

Note that segwit is not supported in BTCP but a fix has been implemented to move coins from segwit addresses, which does not seem to be working for now, under investigation, please contact us for segwit addresses

[Ayms]

Lightning Bitcoin (LBTC) added

[Ayms]

Specific support to claim Bitcoin Private (BTCP) from segwit addresses added

[Ayms]

Bitcoin Interest (BCI) added

Warning this fork does not implement any replay protection with BTG

[Ayms]

Cleanblockchain BCBC added

[Ayms]

Lighthing Bitcoin (LBTC) updated following the new fork

[Ayms]

BTCP fork updated and support to automatic Bitcoin Private (BTCP) address conversion added, you can move your coins using legacy BTC addresses and a BTC explorer, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz prevamount=0.00998277 previndex=31 privkey=privkey addr=139AJaowXYerd9hrAyieWyzRxLVzaEP9PN fees=0.00000300

BTC 19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz --> BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
BTC 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN --> BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

You will see in the output of the command that the addresses were converted

Or using legacy ZCL addresses and a ZCL explorer, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=t1SmcsNFjkiqhag8ms6BFZwVRcLSdjqiK8v prevamount=0.00998277 previndex=31 privkey=privkey addr=t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M fees=0.00000300

ZCL t1SmcsNFjkiqhag8ms6BFZwVRcLSdjqiK8v --> BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
ZCL t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M --> BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

Of course this works too if you use BTCP addresses for the origin and/or the destination

Again, please remember that the addresses are the very same between networks, only the way they are represented is different (so if you have the private key corresponding to 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN above, which is the same than t1L1mJvE5VsSTDnkk7QXmeo6MCzh5MHMp8M on ZCL, you have the private key corresponding to b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s and you can use both addresses on BTCP)

Then to send your transaction:

node tx.js BTCP send full_transaction dnsseed.btcprivate.org

dnsseed.btcprivate.org is not accepting connections for now but probably will after the fork

The above method works to move/claim ZCL but not BTC, for BTC you need to:

- convert your addresses to BTCP ones, for this you can use a fake create command with your BTC addresses and look at the ouput, example:

node tx.js BTCP create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz prevamount=0.00998277 previndex=0 privkey=privkey addr=139AJaowXYerd9hrAyieWyzRxLVzaEP9PN fees=0.00000300

BTC 19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz converted in BTCP b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr
BTC 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN converted in BTCP b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s

- use the BTCP explorer: https://explorer.btcprivate.org/address/b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr to find your BTCP

- and for each transaction that you see:

node tx.js BTCP create prevtx=transaction prevaddr=b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr prevamount=(prevamount associated to transaction) previndex=0 privkey=(privkey of  b1DNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr) addr=(destination address) fees=0.00000300

or for multisig

node tx.js BTCP create prevtx=transaction prevaddr=bxDNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr prevamount=(prevamount associated to transaction) previndex=0 privkey=priv1-priv2-redeem addr=(destination address) fees=0.00000500

- send the "transaction body" of the output of the command using https://explorer.btcprivate.org/tx/send

Note that segwit is not supported in BTCP but a fix has been implemented to move coins from segwit addresses, which does not seem to be working for now, under investigation, please contact us for segwit addresses

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

Please see https://www.reddit.com/r/BitcoinPrivate/comments/828chv/claim_btcp_from_btc_segwit_address/dw7hg0x

The fix for segwit has been implemented by the BTCP team and is being propagated in the network

To claim/move your coins from a segwit address, you must run (add -segwit for the address to be spent):

node tx.js BTCP create prevtx=transaction prevaddr=bxDNDYDgbXZ6D7KQSsoo72dNBywxdKmhkpr-segwit prevamount=(prevamount associated to transaction) previndex=0 privkey=(privkey) addr=(destination address) fees=0.00000300

As explained in the reddit link we must finalize manually the transaction before sending it to the network, so please email the output of the above command (without your private key) to contact peersm com, we might automate this final step too should a significant number of people ask for it

[Update] FIRST SEGWIT OUTPUT SPENT AND MINED Please see https://bitcointalk.org/index.php?topic=2675257.msg34531713#msg34531713

[Ayms]

Bitcoin Hush (BTCH) added

[Ayms]

Bitcoin God (GOD) added