Javascript implementation of the Bitcoin protocol for any Bitcoin based coins, on server and inside browsers, discover and move/manage your coins by yourself: Bitcoin transactions made simple for standard or multisig wallets, segwit and bech32 are supported, create and send by your own your Bitcoin, Bitcoin Cash, Zcash, Litecoin, DOGE, Dash, etc transactions, manage your keys and do not disclose them to dubious wallets software
This is the original README giving more details and examples for non expert people, please note that the dev fees have now been removed and that the whole code is open source in clear under a MIT license
If you experience some issues with this module or don't feel comfortable to use it by yourself, or just don't know how to use it, please email at our github address or email contact peersm com, or post an issue
While the wording in this presentation is marketed to "claim" coins this is not the global intent, which is to allow people to discover and manage their coins by themselves without needing to sync nodes or use wallets
It will be merged with Ayms/bitcoin-wallets and provide all necessary tools to manage any Bitcoin based coins from the browser or from the command line on server side
Should this project be funded we will remove the dev fees and put it fully open source
It is envisioned also to add smart contracts for lightning for example and to support stablecoins or other techno based on bitcoin-like blockchains
If you don't want/know how to use the command line stuff you can use the tool from your browser here
This is a browserfication of this module, then a secure standalone application inside browsers, nothing is sent/queried outside, you can use it offline
Dev fees still apply in the web app, they will be removed from this module/web app should the equivalent of 5 BTCs be reached in terms of founding/donation (and then the code will be released in clear and open source)
If you don't know very well where to start here and don't want to read what follows, then please use the easy way:
1- start installing and see how to use the command line mode if you are not used to it, this is easy
2- run the createauto command that will find your coins automatically and output the transaction to be sent:
Standard: node tx.js BTCP createauto addr1_addr2_..._addrn privkey1_privkey2_..._privkeyn destination_address
Multisig: node tx.js BTCP createauto addr1_addr2_..._addrn <priv1 addr1-priv2 addr1-redeem-2of2 or 2of3 or 2of4>_..._<priv1 addrn-priv2 addrn-redeem-2of2 or 2of3 or 2of4> destination_address
Segwit standard: node tx.js BTCP createauto addr1-segwit_addr2-segwit_..._addrn-segwit privkey1_privkey2_..._privkeyn destination_address
Segwit multisig: node tx.js BTCP createauto addr1-segwit_addr2-segwit_..._addrn-segwit <priv1 addr1-priv2 addr1-redeem-2of2 or 2of3 or 2of4>_..._<priv1 addrn-priv2 addrn-redeem-2of2 or 2of3 or 2of4> destination_address
3- you will get an impressive bunch of logs but understandable, check carefully that the transaction is correct
4- send the transaction to the network:
paste the body (and not the complete transaction) in an explorer (example: https://explorer.btcprivate.org/tx/send as shown in supported coins section), this is the easiest method
or
node tx.js BTCP send complete transaction advised full node (as shown in supported coins section)
You can use the legacy or bech32 addresses, the tool will convert them automatically, however you might need sometimes to convert addresses to find your coins with the explorers, example for BTCP:
node tx.js convert BTCP 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN
Address 139AJaowXYerd9hrAyieWyzRxLVzaEP9PN converted to b16cMymewGhgxkS2R889d7Uy7acD4sk1j3s
To convert a bech32 address you can do:
node tx.js BTC convert bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
which will output Address 3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLN converted to 3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLN, which just means that bech32 address bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 is 3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLN
or
node tx.js BTG convert bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
which will output Address 3JvL6Ymt8MVWiCNHC7oWU6nLeHNJKLZGLN converted to AZ1BpW94ubqHRzsqdfoFCMgVyN1H4CnSEp, which just means that bech32 BTC address bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 is BTG address AZ1BpW94ubqHRzsqdfoFCMgVyN1H4CnSEp
To quickly move/claim coins to an exchange for example, you can look Claiming your coins (BCH,BTG,BCD,SBTC,CDY,etc) - Addresses and getting 'free' coins or Tool to claim coins for all Bitcoin forks without using wallets or running nodes
You can use Find My Coins .ninja, enter one of your addresses and copy the full report:
You will get this:
Which even give you the commands to use with the tool, if you have several addresses and are an advanced user you can run this for each address and group the inputs as explained in Multiple inputs
Still you can doublecheck that the parameters are correct at the end of the full report :
If something does not look correct when using the tool, please email us or post an issue (always without your private keys)
node tx.js acronym create prevtx= prevaddr=addr prevamount= previndex= privkey= addr= fees=0.00000300
If you don't know how to retrieve the redeem script corresponding to your address, please see Retrieving the redeem script or email us (if you spent this address on another network we can retrieve the redeem script from the corresponding transactions)
node tx.js acronym create prevtx= prevaddr=addr prevamount= previndex= privkey=priv1-priv2-redeem-2of2 or 2of3 or 2of4 addr= fee=0.00000500
If you coins are on a segwit address you must add the -segwit string in prevaddr:
node tx.js acronym create prevtx= prevaddr=addr-segwit prevamount= previndex= privkey= addr= fees=0.00000300
node tx.js acronym create prevtx= prevaddr=addr-segwit prevamount= previndex= privkey=priv1-priv2-redeem-2of2 or 2of3 or 2of4 addr= fee=0.00000500
Same as above depending on the type of address with a _ separator, please see Multiple inputs section below
The difference between complete transaction and body in the output of the create command is just that complete transaction includes the body with the network headers:
node tx.js acronym send complete transaction advised full node (as shown in supported coins section)
or
paste the body (and not the complete transaction) in an explorer (example: https://btgexplorer.com/tx/send or https://explorer.btcprivate.org/tx/send)
node tx.js BTG create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=GSjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo prevamount=0.00998277 previndex=31 privkey=privkey addr=GKz5ii8tWQG9hd196vNkwkLKsWHqaeKSoB fees=0.00000300
node tx.js BTG create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=AMjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo prevamount=0.00998277 previndex=31 privkey=privkey1-privkey2-redeem-2of3 addr=GKz5ii8tWQG9hd196vNkwkLKsWHqaeKSoB fees=0.00000500
node tx.js BTG create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=ASjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo-segwit prevamount=0.00998277 previndex=31 privkey=privkey addr=GKz5ii8tWQG9hd196vNkwkLKsWHqaeKSoB fees=0.00000300
node tx.js BTG create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=ATjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo-segwit prevamount=0.00998277 previndex=31 privkey=privkey1-privkey2-redeem-2of3 addr=GKz5ii8tWQG9hd196vNkwkLKsWHqaeKSoB fees=0.00000500
node tx.js BTG send complete transaction btg.suprnova.cc
or
paste the body in https://btgexplorer.com/tx/send or https://explorer.btcprivate.org/tx/send
The module will calculate the amount to be spent according to the fees and advise if the numbers are not coherent:
amount+dev fees+network fees=prevamount
You can adjust the fees if you like according to the size of the transaction instead of using 0.00000300 or 0.00000500
Please see below the supported coins and acronym to be used, as well as explorer link to send your transactions or full nodes, use/tests cases, fork height and explorer
Bitcoin SV (Warning this fork does not implement any replay protection with BCH and BCP) "BSV" - bitcoinsv.io or seed.bitcoinsv.io - please note that this is a Bitcoin cash fork, same use than the others - Height: 15th November 2018
Bitcoin Clean (Warning this fork does not implement any replay protection with BTC) "BCL" - seed.bitcoinclean.org - same use than the others - Height: 518800
New Bitcoin "NBTC" - 1.newbitcoin.org or 2/3/4 1.manghao.com or 2/3/4 - same use than the others but you are supposed to multiply the amounts by 2, don't do it with this tool, keep the original numbers and this will work the same (ie you will get the double on NBTC) - Height: 501225
Big Bitcoin "BBC" - seed.bigbitcoins.org - same use than the others but you must multiply the amounts by 10 - Height: 508888
Bitcoin God "GOD" - s.bitcoingod.org - same use than the others - Height: 501226 - Explorer: http://explorer.bitcoingod.org
Bitcoin Hush "BTCH" - https://explorer.btchush.org/tx/send or seeds.komodoplatform.com - same use than the others - Height: 507089 - Explorer: https://explorer.btchush.org/
Bitcoin@CBC "BCBC" - btcseed.cleanblockchain.io or btcseed.cleanblockchain.org - same use than the others - Height: 498754 - Explorer: http://be.cleanblockchain.org/
Bitcoin Interest (Warning this fork does not implement any replay protection with BTG) "BCI" - https://explorer.bitcoininterest.io/tx/send or seeder1.bci-server.com or seeder2/3.bci-server.com or 216.250.117.221- 74.208.166.57 - 50.27.27.80 - 66.85.74.54 - 69.195.159.106 - 69.195.157.106 - 74.208.235.89 - same use than the others - Height: 505083 - Explorer: https://explorer.bitcoininterest.io/
Lightning Bitcoin "LBTC" - seed10.lbtc.io - same use than the others - Height: 499888 - Explorer: http://explorer.lbtc.io
BitClassic Coin "BICC" - 47.104.59.46 or 47.104.59.9 - same use than the others - Height: 499888 - Explorer: http://info.bicc.io
Litecoin Cash "LCC" - seeds.litecoinca.sh - Litecoin fork, you must multiply the numbers by 10 - Height: 1371111 - Explorer: https://explorer.litecoinca.sh
Bitcoin Community "BTSQ" - seed1.aliyinke.com (or seed2/seed3) - Same as BCD except that you must multiply the numbers by 1000 - Height: 506066
Bitcoin King "BCK" - 47.52.28.49 - same use than the others - Height 499999
Bitcoin Pay "BTP" - http://exp.btceasypay.com/insight/tx/send - Same as BCD except that you must multiply the numbers by 10 - Height: 499345 - Explorer: http://exp.btceasypay.com/insight/
Bitcoin Top "BTT" - dnsseed.bitcointop.org - same use than the others - Height: 501118
Bitcoin Vote "BTV" - https://block.bitvote.one/address/tx/send or seed1.bitvote.one - same use than the others - Height: 505050 - Explorer: https://block.bitvote.one/address
Bitcoin Hot "BTH" - seed-us.bitcoinhot.co - Same as BCD except that you must multiply the numbers by 100 - Height: 498848 - Explorer: block.bithot.org
Bitcoin New "BTN" - dnsseed.bitcoin-new.org - same use than the others - Height: 501000 - Explorer: http://bitcoin-new.org/
Bitcoin X "BCX" - https://bcx.info/tx/send or 192.169.227.48 - Same as BCD except that you must multiply the numbers by 10000 - Height: 498888 - Explorer: https://bcx.info
Bitcoin Faith "BTF" - a.btf.hjy.cc - same use than the others - Height: 500000
Bitcoin World "BTW" - dnsseed.btw.one - Same as BCD except that you must multiply the numbers by 10000 - Height: 499777
World Bitcoin "WBTC" - dnsseed.wbtcteam.org - same use than the others - Height: 503888 - Explorer: http://142.44.242.32:3001/
Bitcoin Atom "BCA" - https://explorer.bitcoinatom.io/rpc-terminal (sendrawtransaction body) or seed.bitcoinatom.io or seed.bitcoin-atom.org or seed.bitcoinatom.net - same use than the others - Height: 505888 - Explorer: https://explorer.bitcoinatom.io
Bitcoin Candy "CDY" - http://block.cdy.one/tx/send or seed.bitcoincandy.one or seed.cdy.one - please note that this a Bitcoin Cash fork and read Specific case of CDY and see cdy.js - Height: 512666 - Explorer: http://block.cdy.one/
Bitcoin Cash Plus (Warning: this fork does not implement any replay protection with BCH) "BCP" - http://bcpexp.org/tx/send or seed.bitcoincashplus.org - same use than the others - Height: 501407 - Explorer: http://bcpexp.org/
Bitcoin Private "BTCP" - https://explorer.btcprivate.org/tx/send or btcp.suprnova.cc - please note that this a BTC and Zcash Classic (ZCL) fork, please look here to move/claim ZCL and BTC on BTCP - Height: 511346 BTC - 272991 ZCL - Explorer: https://explorer.btcprivate.org
Bitcoin Pizza "BPA" - 89.38.97.62 or 46.28.204.17 - same use than the others - Height: 501888 - Explorer: http://47.100.55.227/info/
SegwitB2X "B2X" - https://explorer.b2x-segwit.io/tx/send or node1.b2x-segwit.io (or node2/3) - see b2x.js - Height: 501451 - Explorer: https://explorer.b2x-segwit.io/tx/send
United Bitcoin "UBTC" - ip.ub.com - see ubtc.js - Height: 498777 - Explorer: https://www.ub.com/explorer/
Bitcoin Gold "BTG" - https://btgexplorer.com/tx/send or btg.suprnova.cc - see below and Ayms/bitcoin-transactions#5 - Height: 491407 - Explorer: https://explorer.bitcoingold.org/
Bitcoin Cash "BCH" - https://blockdozer.com/tx/send or bch.suprnova.cc - see Ayms/bitcoin-transactions#4 and example-4.js and Specific case of BCH for the new address format - Height: 478559 - Explorer: https://blockdozer.com/tx/send
Bitcoin Diamond "BCD" - seed1.dns.btcd.io or 139.198.190.221 or 121.201.13.117 - please read Specific case of BCD and see bcd.js - Height: 495866 - Explorer: http://explorer.btcd.io
Super Bitcoin "SBTC" - http://block.superbtc.org/tx/send or seed.superbtca.com - Height: 498888 - Explorer: http://block.superbtc.org/
Bitcore "BTX" - btx.suprnova.cc - Height: 492820 - Explorer: https://chainz.cryptoid.info/btx
Keep in mind that most of those forks are probably scams, so in any case never use their wallets
Bitcoin Core "BTC" - https://blockexplorer.com/tx/send or bitcoin.sipa.be - see https://github.com/Ayms/bitcoin-transactions/blob/master/verify.txt - Explorer: https://blockchain.info/
Zcash "ZEC" - https://explorer.zcashfr.io/insight/tx/send or mainnet.z.cash - see https://github.com/Ayms/bitcoin-transactions/blob/master/verify.txt - Explorer: https://explorer.zcashfr.io/insight/
Litecoin "LTC" - ltc.suprnova.cc - see https://github.com/Ayms/bitcoin-transactions/blob/master/verify.txt - Explorer: https://live.blockcypher.com/ltc
Dogecoin "DOGE" - 5.135.158.86 - Explorer: https://dogechain.info/
Dash "DASH" - dash.suprnova.cc - Explorer: https://chainz.cryptoid.info/dash/
ZClassic "ZCL" - eu1.zclassic.org - Explorer:
This module is equivalent to bitcoin-cli for some features but much more simple to use. To use bitcoin-cli you need to run the full bitcoin software, sync with the network and then sync your wallet.
This is a nightmare for quite a lot of people since syncing a full node can take 10 days and most likely will fail at the end
And this does not help the network since even if you succeed to sync from home most likely you will run a non efficient full node
In addition many people lost everything by using malware wallets trying to get their 'free' coins, and apparently there are some common misunderstanding with the addresses format, please see the Claiming your coins (BCH, BTG, BCD,CDY,etc) - Adresses and getting "free" coins
And finally, if you succeeded to sync you can prune after but you still need to run constantly the bitcoin software
The whole purpose of this module is to allow you to make transactions without having to run and sync a full node
Given the size of the blockchain and number of different networks, at a certain point of time it will become impossible for people to run the full sw for each one just to have their wallet synced and be able to send transactions
And it is crazy to let wallet sw manage your keys
Then even if the restart of this module was inspired by the epic bitcoin gold launch it is intended for the long term
This is not coming from nowhere, neither a scam, you can read BTCGPU/BTCGPU#238
This module is using elliptic and bs58
Please read the specific conditions of the license, the code is now unfortunately minified, the rationale for this is that people are constantly trying to cheat with the dev fees and this gives us additional work for each modification when using the code in clear, if you don't like the fees, don't use this module, and modifying anything can be quite dangerous
It's not rare that the explorer of the forks are not working well, so you can use the legacy explorers to find your coins as explained here or here
You can also use Find My Coins .ninja to get an overview of spendable coins
Unlike bitcoin-cli this modules allows you to manage your fees too, do not go below ~1 satoshi per byte for the network fees or your transaction will not be accepted by the network
There are development fees of ~6.25% (with a minimum of 0.00017000 and 12.5% for BTCP segwit) that are added to each transaction that you broadcast, of course the fees apply only when your broadcasted transaction to the network is included in a block, no fees apply to create/test your transactions
If you don't like the dev fees then please do not use this module but please realize that you can adjust the network fees to compensate
This module is not trivial at all, the bitcoin protocol and formats do not make things easy, it is not recommended (neither authorized by the license) to try to modify anything, if you send wrong transactions to the network at best you will be immediately banned by the nodes for one day and at worse you could send transactions that could spend your funds at a wrong place
Please note that due to rounding issues there is always a satoshi floating around that will go to the network, this is normal
Should this project be funded we will remove the dev fees and put it fully open source
Install nodejs for Windows,Mac,Linux, usually this is easy
Create a bitcoin-transactions directory, install elliptic and bs58 with npm in node-modules and copy tx.js
Or just unzip bitcoin-transactions.zip (137 kB)
For Windows users that are not used to the command line tools:
Install nodejs using the above link
Unzip [bitcoin-transactions.zip](http://www.peersm.com/bitcoin-transactions.zip) somewhere (let's say C:/Users/Me)
[key Windows]+[X], then "execute" and enter cmd, this will open the console
cd /Users/Me/bitcoin-transactions
Now you can enter the commands (please see below): node tx.js BTG create prevtx= prevaddr= prevamount= previndex= privkey= addr= fees= amount=
See example-1.js, Bitcoin Gold transaction 118d6160c8ae2465835ad41908a154cd9be6c78ca4012f79edbf65ca96407f97 was created with this module and mined in block 501249, see https://btgexp.com/tx/118d6160c8ae2465835ad41908a154cd9be6c78ca4012f79edbf65ca96407f97
Please note that the examples do not reflect the current dev fees
example-1.js is now deprecated, please see example-2.js for the new format and transaction https://btgexp.com/tx/cc9684a4243999d1a1fc21c7ad7dbd1b3462bb1fb29614ed16b4d2763ab12bd4
We will follow this transaction for our examples, the previous transaction was d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206
See example-3.js for "Two of two" and "Two of three" transactions examples
And see example-4.js for a "Two of four" example
Multisig transactions/wallets (and why it's a very bad idea to use them) is explained here(TODO)
Please see above
While using this module if you make a mistake with the parameters the transaction might look valid but will just be rejected by the network, so there is no impact, except if you make a mistake with the destination address, nobody can check this, then make sure that the destination address is one that you master
If you have just as little as a slight shadow of a doubt while creating a transaction and looking at the outcome, please don't send it, email us or post an issue (WITHOUT YOUR PRIVATE KEYS)
Before this, please do some work and check precisely what you did, common mistakes are related to wrong private keys and/or wrong redeem script or prevamount for multisig, or fees too low, or amount to be spent on a destination address too low (referenced as "dust" if below 546 Satoshis)
In our example we are going to spend output 31 of transaction d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 with a prevamount of 0.00998277 that belongs to us since GSjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo is one of our addresses, with 0.00001001 network fees
prevamount is like a bank note, you cannot cut it in half, give half to a merchant and keep the rest, you have to give the totality to the merchant (here the network) and get back the rest from him
Here we can decide to spend the whole 0.00998277 amount or just a part
In case we decide to spend a part, the delta will be refunded to our address GSjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo
This is what we do in our example, where we have decided to spend 0.005 to a given address and will get back 0.00488776 on address GSjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo which corresponds to the total amount minus the dev and network fees 0.00998277=0.005 + 0.00488776 + fees
The calculation is simply:
amount+dev fees+network fees=prevamount
But this is easy to make mistakes, then we have added the testamount feature which is recommended to use before using the create command where you explicity say how much network fees you want to pay
Same applies for multisig transactions, the delta, if any, will be refunded to your multisig address as you can see in example-3.js
You have decided to spend the whole amount with 0.0001001 fees and want to know what will be the amount (including dev fees) to put in the create command, do:
node tx.js BTG testamount prevamount=0.00998277 fees=0.00001001
--- Prevamount is small, min dev fees of 8500 apply - amount should be 0.00988776
Then you should use 0.00988776 in the amount parameter of the create command or use the create command without the amount parameter as explained in the "easy way" section above
node tx.js BTG testamount prevamount=0.00998277 fees=0.00001001 amount=0.005
--- Previous amount is: 0.00998277
--- Amount to spend is: 0.00500000
--- Network fees are: 0.00001001
--- Dev fees are: 0.00008500
--- Refunded amount to spending address is: 0.00488776
You will spend 0.005, pay 0.00001001+0.00008500 as fees and get back 0.00488776 on your initial address
As you can see in example-2.js since the numbers are rounded and checked again by the create command there can be a the end a difference of 0.00000001 with that numbers as network fees
For multisig wallets, that's the same and both examples can be seen in example-3.js
Once the numbers are correct you can create your transaction:
node tx.js BTG create prevtx=d5a80b216e5966790617dd3828bc13152bad82f121b16208496e9d718664e206 prevaddr=GSjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo prevamount=0.00998277 previndex=31 privkey=privkey addr=GKz5ii8tWQG9hd196vNkwkLKsWHqaeKSoB fees=0.00001001 amount=0.005
first argument (BTG here) is the network you want to use, please see the "supported coins" section above
prevtx is the previous transaction containing the output that you want to spend
prevaddr is the address where was sent the output that you want to spend (then one of yours)
prevamount is the amount of the output that you want to spend
previndex is the index of the output in the transaction
privkey is the private key of prevaddr as you can see it in your wallet.dat dump
addr is the address where to spend the output
amount is the amount the address will receive
fees are the network fees that you have decided to pay
You can get all those information simply from a blockchain explorer, in case of a transaction with many outputs, to get the index of your output just copy/paste from the site and look at the line number for your output (don't forget that it starts from 0, the first output index is 0 not 1)
If you don't know very well how to retrieve those parameters from an explorer, please see:
One BTC will become 10 BCDs, it just means that amount, prevamount and fees are multiplied by 10, then they have now 7 decimals instead of 8 (so amount, prevamount or fees of 0.00001234 become 0.0001234 in the create command)
This is just a marketing representation and does not change anything else, please see example-6.js that you can compare with example-2.js
You can claim your coins using a BTC explorer and standard BTC addresses (starting with a 1 or 3)
Read also Claiming your coins (BCH, BTG, BCD,CDY,etc) - Adresses and getting "free" coins
The BCH address format did change recently, this does not really make any difference for this module but we have updated the address format with the very excellent cashaddress module
Then legacy and new format can be used
See also BCH addresses converter
One BCH will become 1000 CDYs, it just means that amount, prevamount and fees are multiplied by 1000, then they have now 5 decimals instead of 8 (so amount, prevamount or fees of 0.00001234 become 0.01234 in the create command)
This is just a marketing representation and does not change anything else, please see cdy.js
You can claim your coins using a BCH explorer and standard BCH addresses (starting with a 1 or 3), you will see in the output of the create command that they are converted to the CDY format (addresses are the same in fact, only the representation changes between both networks)
Read also Claiming your coins (BCH, BTG, BCD,CDY,etc) - Adresses and getting "free" coins
node tx.js BTG create prevtx= prevaddr= prevamount= previndex= privkey=priv1-priv2-redeem-<2of2 or 2of3 or 2of4> addr= fee= amount=(optional)
The arguments are the same than before except privkey where priv1 and priv2 are the two private keys required to spend your coins on your multisig address, redeem is the redeem script, 2of2 or 2of3 or 2of4 is the multisig scheme corresponding to your address
To find what are the public keys included in the redeem script, please run:
node tx.js BTG decoderedeem <redeem>
Public Key: GLU1deMwMToTt7s87Nv98v9qrK2sbZML5k equivalent to bitcoin address 13d6DX2zNcCAoeZqBSG2i9oww9F2bvd82o
Public Key: GLbb8AJPnpbwaFxHJAH6UggaB6e4u1CtFQ equivalent to bitcoin address 13kfi2ySoxzeVnezNDcz3vLgFvrDrpL1qW
Public Key: GSjwHAAYmFfQ4WPArc2ErtjQGr3Q2nkjvo equivalent to bitcoin address 19u1s2qbnQ46z35svfN8S8PWMgFZ1vqpxz
Then you need to find at least two private keys corresponding to two of those public keys, to retrieve them (and the redeem script first) from your wallet, you can look at the first part of this tutorial How to extract Bitcoin Gold from a 2fa Electrum Wallet [STEP BY STEP] but of course you don't need to run a full node
This can look complicate but is not so much
You will get a summary of everything at the end of the command and warnings if the numbers are not correct, the create command does check the transaction again after it has been created, you must get at the end the message 'Transaction verified', if not something went wrong
Most likely if you get 'Bad transaction' this is because you made a mistake with the private key(s) and/or the redeem script or prevamount in case of multisig, or you are trying to spend something that does not belong to you, if this happens and everything looks correct, please report (but never send to us/advertise your private keys, remove them and post the logs)
It's a good idea to check again your transaction once it has been created, use the transaction body
node tx.js BTG decode 020000000106e26486719d6e490862b121f182ad2b1513bc2838dd17067966596e210ba8d51f0000006a473044022039e2eee9a14fd18665eceeaac8af87888704ef2bfa14afe850b850e6fc7fdea702201d3c4340cc6998738295176320dc2597b3b6fcb93abc01add17b57b9ea70f0754121039f1e160a02079a6d6b7be0334cc4d76a125cd13a6f8d7131b11c263bc20bf918ffffffff0320a10700000000001976a914177b585b5401ad21b60b78b1b3c91996f250296d88ac47750700000000001976a91461975b3a4b9d5059e3db3e301e394d6d13275b3688ac34210000000000001976a9145b79a9d29a34f2f284ecdd33009ffa5e0252b68988ac00000000
If you want you can double check again using something else like bitcoin-cli
Once you are sure that everything is correct, you can send your transaction to the network using the complete transaction:
node tx.js BTG send e1476d4474780000000000000000000003010000d42bb13a020000000106e26486719d6e490862b121f182ad2b1513bc2838dd17067966596e210ba8d51f0000006a473044022039e2eee9a14fd18665eceeaac8af87888704ef2bfa14afe850b850e6fc7fdea702201d3c4340cc6998738295176320dc2597b3b6fcb93abc01add17b57b9ea70f0754121039f1e160a02079a6d6b7be0334cc4d76a125cd13a6f8d7131b11c263bc20bf918ffffffff0320a10700000000001976a914177b585b5401ad21b60b78b1b3c91996f250296d88ac47750700000000001976a91461975b3a4b9d5059e3db3e301e394d6d13275b3688ac34210000000000001976a9145b79a9d29a34f2f284ecdd33009ffa5e0252b68988ac00000000
Some addresses of nodes are hard coded, they don't belong to us and we can't say how long they will work, so if you want to use a specific node, do node tx.js BTG send <tx> A.B.C.D where A.B.C.D is the IP address of the node (please see the recommended full nodes above)
Before sending your transaction it's a good idea too to check the network by doing node tx.js BTG testconnect or node tx.js BTG testconnect A.B.C.D
A more easy way if available for your network is to copy and paste the body of the transaction (and not the complete transaction) to a blockchain explorer that will broadcast it, there are no risks of doing this except that you don't know if the explorer will do its job, the explorer can't modify the transaction
The addresses between the different networks are the same, it always ends up with the hash of your public key and is encoded in a specficic way for each network, but they still are the same
There are some tools existing to convert addresses, you might consider using the very excellent Ayms/bitcoin-wallets module to create your wallet and/or convert addresses
This module is not intended to push you to get your 'free' coins from bitcoin core (or other legacy network)
Because, unlike many people think, you have them already so there is no need to rush to 'convert' them (unless you want to send them quickly to an exchange to sell them), many people did not get their 'free' coins and just lost all what they had by using malware wallets
That's why, even if there are zero technical reason for doing this, it is highly advised to transfer first your bitcoins (or legacy coins) to another wallet before moving/claiming forked coins
Another advantage of doing so is that it becomes easier to get your parameters to claim your coins (like the redeem script in case of multisig address, or the address corresponding to your segwit address), indeed we can see them on the transactions made on the legacy network to move your coins
If you want to move your bitcoins "from bitcoin core to BCH, BTG, BCD or SBTC, etc" or from "bitcoin core to a bitcoin X exchange", you can just use the create command:
node tx.js BTG create prevtx= prevaddr= prevamount= previndex= privkey=privkey addr= fees= amount=(optional)
or
node tx.js BTG create prevtx= prevaddr= prevamount= previndex= privkey=priv1-priv2-redeem-<2of2 or 2of3 or 2of4> addr= fee= amount=(optional)
where prev[tx,addr,amount,index] refers very exactly to the same that you can see in a bitcoin core explorer (or the legacy explorer of the network being forked) like https://blockchain.info before the block forking height (same transaction id, same address, same amount, same index) and privkey is the private key corresponding to your bitcoin core address or priv1-priv2-redeem corresponds to your multisig bitcoin address
and addr can be a bitcoin address too that will be converted into a BCH, BTG, BCD, etc address as you will see in the output of the command (even if most likely you will use a destination address corresponding to the fork, which of course works also), as well as prevaddr, so you don't need to convert the addresses, the tool will do it for you
You can convert before if you like the prevaddr and addr from a bitcoin core one to a bitcoin gold one but this is of no use, the create command will work with the original bitcoin addresses
If this explanation is unclear, please see the examples given here or here
If for any reason you don't trust this project then it's easy to use bitcoin-cli to check that the transactions are correct, especially decoderawtransaction and signrawtransaction using the body of the transaction to compare the output and the signatures
node tx.js BTG create prevtx=tx1_tx2_..._txn prevaddr=addr1_addr2_..._addrn prevamount=amount1_amount2_..._amountn previndex=index1_index2_..._indexn privkey=privkey1_privkey2_..._privkeyn addr=<destination address> fees=0.00000600
You can put the amount= parameter (but we believe that it's quite stupid even if included in our examples), then the delta will be refunded to addr1
To simplify, if prevaddr and/or index are always the same (and why not amount), you can do:
node tx.js BTG create prevtx=tx1_tx2_..._txn prevaddr=addr1 prevamount=amount1_amount2_..._amountn previndex=index1 privkey=privkey1 addr=<destination address> fees=0.00000600
or
node tx.js BTG create prevtx=tx1_tx2_..._txn prevaddr=addr1 prevamount=amount1 previndex=index1 privkey=privkey1 addr=<destination address> fees=0.00000600
This works the same privkey=privkey1_privkey2_..._privkeyn where each privkeyi is priv1-priv2-redeem-<2of2 or 2of3 or 2of4>
You can mix standard inputs and multisig ones, see all the examples in multiinputs.js
Don't forget to adjust the fees according to the size of your transaction
This has not been extensively tested for now even if we are confident that this is working well, so please check very closely the outcome before sending the transaction, most likely it will only be rejected if there is an issue but again check the destination addresses
This module is subject to the following modified MIT license which removes the rights to modify, merge, sublicense, and sell:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, publish, and/or distribute copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.