Quote from: paulwall on February 21, 2018, 06:32:53 PM

I don't think you got me right. I did not use anything from different address for another address, I did everything by the guide. However, please, take a look at what I initially had:
The address I can't handle is this: 3JuPB27nMEHvXuu9dmHQVrwHh5Wym8CJso
And if you run it through https://btgexplorer.com you will see that it has the same transaction ID (dc7995b5b2756c85657803519569c2203e7d18ff3bae7679f1a4b579cf9fca6c) as my other address from Electrum Change section: 3JuwWAhRRqa8EQsp5DnoRP8rkBxCjuyZcv

Thus we have two different addresses that share the same transaction ID. And that is where it gets tricky - when you run the first one (3JuPB27nMEHvXuu9dmHQVrwHh5Wym8CJso) with "deserialize" it has 2 outputs but NONE of them have the "address" field that matches the address in question.

It seems you might be a little confused as to which address(es) your coins are/were in. The transaction you are looking at (dc799...), was sending FROM the 3JuPB address TO the 3JuwW address... so the only address of yours that had a UTXO from that transaction was 3JuwW (ps. this UTXO has already been spent on BTG chain)

So 3JuwW address is now EMPTY on BTG chain: Final Balance = 0.00 BTG

Your address: 3JuPB27nMEHvXuu9dmHQVrwHh5Wym8CJso
currently has TWO unspent BTG outputs... from two other transactions:
UTXO1 - 0.35977155 BTG
TXID1: https://btgexplorer.com/tx/28341395c82cfeb645eaa0ad2741b4b22b3df1ba2475153da8d43e7fe78049dd

UTXO2 - 0.33523 BTG
TXID2: https://btgexplorer.com/tx/9925465a2eeb0adbc2d5e21ada0900f32951ad72394afb73710f5cda8ee345ea

So, if you want to claim those BTG, you need to get the all the relevant information for those two transactions:

Code:

{
   "address": "3JuPB27nMEHvXuu9dmHQVrwHh5Wym8CJso",
   "prevout_n": 9,
   "scriptPubKey": "a914bcd0de3ddeeaba6c3f9dd4fab6882d19cded030187",
   "type": 0,
   "value": 35977155
   }

and

Code:

{
   "address": "3JuPB27nMEHvXuu9dmHQVrwHh5Wym8CJso",
   "prevout_n": 8,
   "scriptPubKey": "a914bcd0de3ddeeaba6c3f9dd4fab6882d19cded030187",
   "type": 0,
   "value": 33523000
   }

And then use that info to create your raw transaction: (NOTE: 5000 sat fee)

Code:

createrawtransaction '[{"txid": "28341395c82cfeb645eaa0ad2741b4b22b3df1ba2475153da8d43e7fe78049dd", "vout": 9 },{"txid": "9925465a2eeb0adbc2d5e21ada0900f32951ad72394afb73710f5cda8ee345ea", "vout": 8 }]' '{"YOUR_BTG_ADDRESS": 0.69495155}'

That will spit out the big long hex string (RAW_TRANSACTION_HASH)... you then sign it with the two private keys that you should have got from your "X1" and "X2" wallets that matches the "1" addresses that should have been found from the redeemscript for the 3JuPB address (ie. 2 of these 3 addresses: 1BQtSp5FGMMUKxSGMHWE7YRARDBA5vLYu5, 15F8E7e2faxDeB6F19ZX2UTS65BmassJT4 or 1XsXYJJxEaVN3m4P9ZRmPRgXseWwjP267).

Code:

signrawtransaction "RAW_TRANSACTION_HASH" '[{"txid": "28341395c82cfeb645eaa0ad2741b4b22b3df1ba2475153da8d43e7fe78049dd", "vout": 9, "scriptPubKey": "a914bcd0de3ddeeaba6c3f9dd4fab6882d19cded030187", "redeemScript": "522102b12e4dbbfc4690630efd2d5b7e4843945ada831dc15dc1dbb5b9d577dd8e76b421032ef6597db919e099d42c248f616477a5cae78fcfce64a2b12760d4dd68ce3bfb21037cb10abf43adc77e9da2879320357daaf002a68c06b2ade4e2e6ca4685bfdf8753ae", "amount": "0.35977155"},{"txid": "9925465a2eeb0adbc2d5e21ada0900f32951ad72394afb73710f5cda8ee345ea", "vout": 8, "scriptPubKey": "a914bcd0de3ddeeaba6c3f9dd4fab6882d19cded030187", "redeemScript": "522102b12e4dbbfc4690630efd2d5b7e4843945ada831dc15dc1dbb5b9d577dd8e76b421032ef6597db919e099d42c248f616477a5cae78fcfce64a2b12760d4dd68ce3bfb21037cb10abf43adc77e9da2879320357daaf002a68c06b2ade4e2e6ca4685bfdf8753ae", "amount": "0.33523000"}]' '["X1_PRIVKEY-3JuPB","X2_PRIVKEY-3JuPB"]'

That *should* spit out the hex string and say that it is complete (I'm fairly sure that you don't actually have to do two signrawtransactions, you can just do it once and provide all the required keys).

You should then be able to sendrawtransaction.

Things get a little more complicated when you are attempting to send multiple UTXOs from multiple addresses and multiple transactions. You need to make sure that you get all the transactionIDs, redeemscripts, scriptpubkeys etc sorted out... and just step through it logically.

The number of private keys required will change based on how many 2FA addresses you are claiming from. Each 2FA address involved requires TWO private keys. So, for the transaction I've outlined above where you have 2 UTXOs, but only 1 address... you need TWO private keys.

If you had 2 UTXOs and they were from 2 addresses, you would need FOUR private keys.

For instance... lets assume that the output from transaction (dc799...) had not yet been spent... and you wanted to include that as well... Now we have THREE UTXOs... and TWO addresses...

3rd UTXO:

Code:

{
   "address": "3JuwWAhRRqa8EQsp5DnoRP8rkBxCjuyZcv",
   "prevout_n": 0,
   "scriptPubKey": "a914bcebdb20e40d359009993dae5ea9b273c49ab34287",
   "type": 0,
   "value": 262924200
   },

So, the createrawtransaction would have been something like:

Code:

createrawtransaction '[{"txid": "28341395c82cfeb645eaa0ad2741b4b22b3df1ba2475153da8d43e7fe78049dd", "vout": 9 },{"txid": "9925465a2eeb0adbc2d5e21ada0900f32951ad72394afb73710f5cda8ee345ea", "vout": 8 },{"txid": "dc7995b5b2756c85657803519569c2203e7d18ff3bae7679f1a4b579cf9fca6c", "vout": 0 }]' '{"YOUR_BTG_ADDRESS": 3.32419355}'

and the signrawtransaction would have been something like:

Code:

signrawtransaction "RAW_TRANSACTION_HASH" '[{"txid": "28341395c82cfeb645eaa0ad2741b4b22b3df1ba2475153da8d43e7fe78049dd", "vout": 9, "scriptPubKey": "a914bcd0de3ddeeaba6c3f9dd4fab6882d19cded030187", "redeemScript": "522102b12e4dbbfc4690630efd2d5b7e4843945ada831dc15dc1dbb5b9d577dd8e76b421032ef6597db919e099d42c248f616477a5cae78fcfce64a2b12760d4dd68ce3bfb21037cb10abf43adc77e9da2879320357daaf002a68c06b2ade4e2e6ca4685bfdf8753ae", "amount": "0.35977155"},{"txid": "9925465a2eeb0adbc2d5e21ada0900f32951ad72394afb73710f5cda8ee345ea", "vout": 8, "scriptPubKey": "a914bcd0de3ddeeaba6c3f9dd4fab6882d19cded030187", "redeemScript": "522102b12e4dbbfc4690630efd2d5b7e4843945ada831dc15dc1dbb5b9d577dd8e76b421032ef6597db919e099d42c248f616477a5cae78fcfce64a2b12760d4dd68ce3bfb21037cb10abf43adc77e9da2879320357daaf002a68c06b2ade4e2e6ca4685bfdf8753ae", "amount": "0.33523000"},{"txid": "dc7995b5b2756c85657803519569c2203e7d18ff3bae7679f1a4b579cf9fca6c", "vout": 0, "scriptPubKey": "a914bcebdb20e40d359009993dae5ea9b273c49ab34287", "redeemScript": "5221038256ab0ff75ec35e8d8796da1f3c4740daffd3b20a3a0ddf4e9ad2d232e7eaff2103b2972991bf628c8dc80f9921241371fed1181f5f6dab0cdacbc72e531cc539892103f7637f9b89436d14455f1771d10e6f539606b5e650b1ac828aada72ad0f1503d53ae", "amount": "2.629242"}]' '["X1_PRIVKEY-3JuPB","X2_PRIVKEY-3JuPB","X1-PRIVKEY-3JuwW","X2-PRIVKEY-3JuwW"]'

See how the 3rd "TX" block has a different scriptpubkey and redeemscript? Also, note the four private keys required... 2 privkeys for 3JuPB address... and 2 privkeys for 3JuwW

Again, the privkeys for 3JuwW should have come from two of the addresses from the 3JuwW redeemscript (15rhdRoyuM9XA3wEpJpwx3w6EDCPhjjz25, 1PZQJMxvVWzjd8agCCgDVDD87SEFej85h3 and 14r64vr5MxHE7wfrBZcrZMjnNr3edpx3Wr) and would have been in your X1 and x2 wallets.