Author

Topic: Tool to claim coins for all Bitcoin forks without using wallets or running nodes (Read 9345 times)

member
Activity: 182
Merit: 33
The browser version (standalone secure and offline webapp) is now released, please see: https://peersm.com/wallet
member
Activity: 182
Merit: 33
Please see https://github.com/Ayms/bitcoin-transactions this is a merge of former bitcoin-transactions and bitcoin-wallets nodejs modules with additional features to be implemented as described in the README

It is financed by NLnet via EU Horizon 2020 Next Generation Internet Search and Discovery call

So the initial dev fees have been removed and the code is now open source and provided in clear under a MIT license

The intent is to provide all the necessary tools for anybody to discover and manage their coins, as well as making transactions by themselves, without having to sync a full node or as an alternative to wallets when people don't understand where their coins are (we saw quite a lot of confusion for people not understanding at all how to find their coins and to what keys their addresses did relate in case of multisig, segwit and now bech32)

It's somewhere bitcoin-cli outside of bitcoin core more easy to use and not restricted to its own wallet, available for any bitcoin based coins

At the end it will be a secure standalone offline js webapp inside browsers (like https://peersm.com/wallet but the app does not reflect the current state of the nodejs repo)

It's not a remake of iancoleman's tool but of course some features overlap, as well as for other existing tools, we will also extend all of this inside one tool with no limitations (for example some tools do not accept "invalid" bip39 seeds, or bip32 seeds, etc)
member
Activity: 182
Merit: 33
Can I know who has deleted my message about BSV?

How comes a message is deleted without reasons and without knowing by whom?

No answer=I will remove BSV
member
Activity: 182
Merit: 33
Still nobody is financing this, so the dev fees are still there and this is still not open source (will be removed and become open source if the equivalent of 5 BTCs is reached), but here is the offline standalone version inside browsers : https://peersm.com/wallet

The code is loaded once with one request (including the data-uri image, so the design is a bit succinct) and is sandboxed so nothing can leak/be easily accessed even from the browser console, it can be checked using the check code button and comparing with a third party (here github, if some people want to host it also, they are welcome), this button can be installed as a bookmarklet for future uses/checks

It is highly recommended to use the advanced mode offline, the tool will advise if this is not the case

Of course this is not sending anything outside, not using tracking stuff, neither browser storage or whatever insecure feature

It can be used with the Tor Browser if you activate javascript

This is a kind of bitcoin-cli outside of bitcoin core for different coins, it could be extended for Lightning and other use
member
Activity: 182
Merit: 33
And now a web interface to ease the use of the tool, please see https://peersm.com/wallet :

- convert from any address to any address, including bech32
- decode redeem scripts
- create your transaction automatically

To come: advanced mode (ie enter your parameters yourself instead of using the automatic retrieval feature)
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
The tool is now automated for each fork, you just need to input your addresses, corresponding private keys and the destination address, see https://github.com/Ayms/bitcoin-transactions#quick-start-guide

The tool is converting automatically the addresses but an address conversion feature has been added also

Next steps:

- claim and send coins for all the forks in one command

- web interface to connect to the tool
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
Great project that helps you manage your own token without need to exchange from one to another I will try join and promote this good work. Keep it up

Thanks!
sr. member
Activity: 604
Merit: 250
Great project that helps you manage your own token without need to exchange from one to another I will try join and promote this good work. Keep it up
member
Activity: 182
Merit: 33
Bitcoin God (GOD) added

Can we claim GOD from Segwit BTC addresses?

Yes, why? (I am not aware of anything specific here, no?)

In case there is still a doubt I confirm that GOD can be claimed with the tool from segwit addresses
member
Activity: 182
Merit: 33
Big Bitcoin "BBC", New Bitcoin "NBTC" and Bitcoin Clean "BCL" (Warning this fork does not implement any replay protection with BTC) added
member
Activity: 182
Merit: 33
Bitcoin God (GOD) added

Can we claim GOD from Segwit BTC addresses?

Yes, why? (I am not aware of anything specific here, no?)
sr. member
Activity: 476
Merit: 250
Bitcoin God (GOD) added

Can we claim GOD from Segwit BTC addresses?
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
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:

Quote
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:

Quote
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:

Quote
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://bitcointalksearch.org/topic/m.34531713

member
Activity: 182
Merit: 33
Lighthing Bitcoin (LBTC) updated following the new fork
member
Activity: 182
Merit: 33
Cleanblockchain BCBC added
member
Activity: 182
Merit: 33
Bitcoin Interest (BCI) added

Warning this fork does not implement any replay protection with BTG

member
Activity: 182
Merit: 33
Specific support to claim Bitcoin Private (BTCP) from segwit addresses added
member
Activity: 182
Merit: 33
Lightning Bitcoin (LBTC) added
member
Activity: 182
Merit: 33
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:

Quote
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:

Quote
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:

Quote
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

member
Activity: 182
Merit: 33
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
member
Activity: 182
Merit: 33
BitClassic Coin "BICC" added
member
Activity: 182
Merit: 33
Update for BTCP transactions can be sent to dnsseed.btcprivate.org and btcp.suprnova.cc
member
Activity: 182
Merit: 33
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://bitcointalksearch.org/topic/m.29329533

"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)


newbie
Activity: 8
Merit: 0
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://bitcointalksearch.org/topic/m.29329533

"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).
member
Activity: 182
Merit: 33
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:

Quote
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:

Quote
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:

Quote
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
member
Activity: 182
Merit: 33
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
member
Activity: 182
Merit: 33
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

Quote

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

Quote

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

Quote

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
newbie
Activity: 406
Merit: 0
jr. member
Activity: 109
Merit: 1
mine pexa @ pool.easyx.cc
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
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
Segwit support added, see https://github.com/Ayms/bitcoin-transactions

P2WPKH and P2WSH

@Lion Bitcoin Shop I email you
hero member
Activity: 588
Merit: 500
BitcoreService.com
hello @ayms
can you make video tutorial to claiming  bitcoin gold from block.io ( i have the privekey) this is the example
* Address: 3NtGVdCnt4TNUgtgrABCxxxxxxx
* Address Type: P2WSH-over-P2SH

* Required Signatures: 2

* Redeem Script: 2 xxcxxxx xxxxxx 2 OP_CHECKMULTISIG

* Redeem Script Hex: xxxxxx

* Public Keys: ["xxxxxx", "xxxxx"]

* Private Keys: ["xxxxx", "xxxxx"]

i will give the privekey detail at PM if you interesting, and the bitcoin gold amount will be yours as fee.

the final balance is 0.14btg


For now I have added those images as a tutorial https://github.com/Ayms/bitcoin-transactions#standard-wallets-2 but probably it's not enough

Could you please email me for your case? Don't send me the private keys of course, not sure to get "P2WSH-over-P2SH" for your multisig address, need to take a look


send you via PM
member
Activity: 182
Merit: 33
hello @ayms
can you make video tutorial to claiming  bitcoin gold from block.io ( i have the privekey) this is the example
* Address: 3NtGVdCnt4TNUgtgrABCxxxxxxx
* Address Type: P2WSH-over-P2SH

* Required Signatures: 2

* Redeem Script: 2 xxcxxxx xxxxxx 2 OP_CHECKMULTISIG

* Redeem Script Hex: xxxxxx

* Public Keys: ["xxxxxx", "xxxxx"]

* Private Keys: ["xxxxx", "xxxxx"]

i will give the privekey detail at PM if you interesting, and the bitcoin gold amount will be yours as fee.

the final balance is 0.14btg


For now I have added those images as a tutorial https://github.com/Ayms/bitcoin-transactions#standard-wallets-2 but probably it's not enough

Could you please email me for your case? Don't send me the private keys of course, not sure to get "P2WSH-over-P2SH" for your multisig address, need to take a look
hero member
Activity: 588
Merit: 500
BitcoreService.com
hello @ayms
can you make video tutorial to claiming  bitcoin gold from block.io ( i have the privekey) this is the example
* Address: 3NtGVdCnt4TNUgtgrABCxxxxxxx
* Address Type: P2WSH-over-P2SH

* Required Signatures: 2

* Redeem Script: 2 xxcxxxx xxxxxx 2 OP_CHECKMULTISIG

* Redeem Script Hex: xxxxxx

* Public Keys: ["xxxxxx", "xxxxx"]

* Private Keys: ["xxxxx", "xxxxx"]

i will give the privekey detail at PM if you interesting, and the bitcoin gold amount will be yours as fee.

the final balance is 0.14btg
sr. member
Activity: 548
Merit: 265
My old account was "Ghoom" (hacked) u=199247
Added: Bitcoin Community "BTSQ", Bitcoin King "BCK", Bitcoin Pay "BTP", Bitcoin Top "BTT", Bitcoin Vote "BTV", Bitcoin Hot "BTH", Bitcoin New "BTN", Bitcoin X "BCX", Bitcoin Faith "BTF", Bitcoin World "BTW", World Bitcoin "WBTC"

@ghoom2 I used the git repos when available, if not the info in your tool, I did not compare everything but for example we have different protocol versions for UBTC, BTN and BTSQ

It's not my tool. it may be https://bitcointalksearch.org/user/ymgve-19707
member
Activity: 182
Merit: 33
Added: Bitcoin Community "BTSQ", Bitcoin King "BCK", Bitcoin Pay "BTP", Bitcoin Top "BTT", Bitcoin Vote "BTV", Bitcoin Hot "BTH", Bitcoin New "BTN", Bitcoin X "BCX", Bitcoin Faith "BTF", Bitcoin World "BTW", World Bitcoin "WBTC"

@ghoom2 I used the git repos when available, if not the info in your tool, I did not compare everything but for example we have different protocol versions for UBTC, BTN and BTSQ
sr. member
Activity: 504
Merit: 251
I claim my fork bitcoin in yobit,not much money but better then nothing.
member
Activity: 182
Merit: 33
Thanks for tool.

You can look https://github.com/ymgve/bitcoin_fork_claimer too

Thanks, looks cool, a bit different on some aspects but very similar in general
sr. member
Activity: 548
Merit: 265
My old account was "Ghoom" (hacked) u=199247
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
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://bitcointalksearch.org/topic/m.29329533

"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


member
Activity: 182
Merit: 33
it is a a great contribution to the crypto world, i will try to promote it
hope you get more attention on your nice project

Thanks!
hero member
Activity: 1132
Merit: 536
it is a a great contribution to the crypto world, i will try to promote it
hope you get more attention on your nice project
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
member
Activity: 182
Merit: 33
Please see https://github.com/Ayms/bitcoin-transactions

Quasi all of the altcoins and forked coins are using the Bitcoin core code, therefore the transactions have quasi the same format with some minor differences

Then a simple tool can be used, this standalone tool allows you to create your transactions and manage your keys by yourself, eliminating the risk of disclosing them and getting robbed, eliminating the risk of getting stuck into your wallet and eliminating the need to run/sync a full node and/or wallet

This works for standard and multisig transactions (but do not use segwit addresses) from any kind of "wallets"

Once you have created your transaction offline, you can send it via the tool to a recommended full node or via a blockchain explorer

Supported coins for now are: BTG, BCH, BCD, SBTC, BTX, BTC, ZEC, LTC, DOGE, DASH but many others could be added (please post an issue if you see a need), upcoming bitcoin forks coins will be added as soon as they release their code on github (thanks to post an issue too or email when this happens since we don't monitor it every day)

It can look a bit complicate but is not so much if you follow carefully the recommended use, you just need a blockchain explorer to retrieve the inputs (and to know your keys of course)

There are dev fees of ~1.5% to support the development effort but on another hand you can decide for the network fees and lower them to compensate

This tool is not only to "claim" coins which as explained does not really mean anything but also to manage your transactions by yourself and eventually stop sending coins (and paying fees) "from wallets to other wallets" which is not relevant in most cases

There are many forks coming, we can suspect that some are quite dubious (if you look at the code of some projects it's quite funny how they just modfied a very little the Bitcoin core code, probably a two years old child could do this better and launch a fork), as well as how they will instruct people to "claim" their coins, using this tool is at no risk (again if you carefully check what you are doing)
Jump to: