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/sendNote 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