trying to send a fraction of a btc, 'preview tx' button indicates otherwise

[boosblock]

when i go to send a fraction of a coin using my WO wallet on my online machine, i check the "preview transaction" directly above the continue button, and see that its emptying the contents of an entire address housed in that wallet. 

https://en.bitcoin.it/wiki/Transaction#Output

i'm guessing that the tx has to account for the whole wallet in one address in that WO wallet but in actuality only what i want to send is sent and the rest is sent back to me automatically in that wallet. 

is that correct?

thanks.

[1715217703]

1715217703

[1715217703]

1715217703

[1715217703]

1715217703

[1715217703]

1715217703

[1715217703]

1715217703

[PhoenixFire]

This sounds normal to me. Bitcoin doesn't work like a database usually would.
Simplifying but: if you have 2BTC in one lump (UTXO) and want to send 0.5 BTC somewhere, it effectively splits that into 1.5BTC (your change) and 0.5BTC. The .5 gets sent out to the address you specified and the 1.5 gets sent to a change address that is part of your wallet.
This isn't unique to Armory, so there is plenty more reading available

[boosblock]

This sounds normal to me. Bitcoin doesn't work like a database usually would.
Simplifying but: if you have 2BTC in one lump (UTXO) and want to send 0.5 BTC somewhere, it effectively splits that into 1.5BTC (your change) and 0.5BTC. The .5 gets sent out to the address you specified and the 1.5 gets sent to a change address that is part of your wallet.
This isn't unique to Armory, so there is plenty more reading available

ok thanks.  so i successfully sent a fraction of the balance and the rest was returned to me.  i got impatient and just did it.

now i've encountered another very odd problem. i tried sending more from the same wallet (again) and it wont allow me to. 
1) created new offline tx on online machine (0.96.3.99-beta)
2) signed it successfully using offline machine (0.96 beta)
3) i loaded it back onto online machine and tried broadcasting it but but i'm getting an error in red that says 'unrecognized.'  i clicked 'here for more info about this tx' but i'm being told its invalid and cannot be shown.


so i literally just tried to repeat the exact same process which just worked but am gettting this unrecognized error. 

any ideas? thanks.

[PhoenixFire]

ok thanks.  so i successfully sent a fraction of the balance and the rest was returned to me.  i got impatient and just did it.

now i've encountered another very odd problem. i tried sending more from the same wallet (again) and it wont allow me to. 
1) created new offline tx on online machine (0.96.3.99-beta)
2) signed it successfully using offline machine (0.96 beta)
3) i loaded it back onto online machine and tried broadcasting it but but i'm getting an error in red that says 'unrecognized.'  i clicked 'here for more info about this tx' but i'm being told its invalid and cannot be shown.


so i literally just tried to repeat the exact same process which just worked but am gettting this unrecognized error. 

any ideas? thanks.

I'd wager the offline machine needs updating. Goatpig recommends that online and offline Armory setups are kept in lock-step. I'm not sure why it worked the last time and not this time, but still the first thing to update.

[goatpig]

1) created new offline tx on online machine (0.96.3.99-beta)
2) signed it successfully using offline machine (0.96 beta)

These 2 versions are basically incompatible if you are signing for anything but P2PKH.

[boosblock]

1) created new offline tx on online machine (0.96.3.99-beta)
2) signed it successfully using offline machine (0.96 beta)

These 2 versions are basically incompatible if you are signing for anything but P2PKH.

i updated the online machine to 0.96 and it worked.  i have no idea how the hell the first one went through, but it did.  anyway, thanks to everyone for their responses.

[goatpig]

i updated the online machine to 0.96 and it worked. 

You should upgrade, not downgrade.

i have no idea how the hell the first one went through, but it did.  anyway, thanks to everyone for their responses.

Most likely didn't involve any P2SH constructs.