For the tx ID described in this topic, how can those two addresses have the BTC i owned in my 1H5h wallet to equal out the transaction i sent? When i sent the BTC during tx 20da23d639 I only authorized the 0.0048, and somehow that additional transaction I didn't authorize ( the 0.01 that when to 1FiN ) was tacked onto it.
Similar story for when I authorized a similar in size transaction (f944) i only intended to send the 0.0038, but then that 0.01 was sent to the 1Ha2fx "wallet" by being tacked onto this tx just like the first one.
that's how bitcoin works, unlike the way your conventional banking works.
when you "authorized" (make payment) of 0.0048, the wallet would use available utxo for sending out
though I'm not sure why it used more than enough inputs and why your destination address was the 2nd output
usually by default it would only use enough utxo for the amount transacted,
and the 1st address as the payment address then 2nd address for the change address
How did these two wallets ( 1FiN & 1Ha2 ) become into existence, and "secretly" have BTC sent to them without being shown in my tx log in my BTC Core wallet app? How can i prevent this from happening again?
these addresses are what I called as change address as I mentioned above
it was auto generated by default by the wallet and you can't prevent it from happening again,
unlesss you enable coin select and setting/using custom (the same) change address every time you create new transactions
Finally... when i run -zapwallettxes it does clear the unconfirmed txs and restores my wallet balance, but once i remove the command from the conf file and the wallet re-syncs the txs are immediately replaced and my balance goes to zero again. Suggestions?
you did run -zapwallettxes=1 -rescan as arguments in the command line?
have you tried running it while offline, see if it helps... you can re-create the tx and then go online to send it
but make sure you get the hex rawtx by typing on console:
getrawtransaction yournewtxidso if it goes wrong again you can push/broadcast the hex rawtx manually to other nodes
Even if these two wallets are "working together" to get my topics tx come true... Would I just have to wait until it confirms, or would i have to somehow get a CPFP'd/double spend to make sure they go through?
You could just wait or like I said above, re-create the transaction with high enough tx fee
but this time you can make 2 payments (if it was your intention) at once in a single transaction (to save fee)