|
Title: Huge issue with MultiBit! Inputs from Change addr, Outputs back to same addr! Post by: BitHits on May 18, 2013, 01:02:15 AM Huge issue with MultiBit! Inputs from Change addr, Outputs back to same addr!
http://blockchain.info/tx/9375925ed95d85cd9b5ecda6332c814c35ebf04124ac625da4c0bf10ab597767 This was done on 0.5.9 - I imagine all versions are vulnerable to this glaring oversight. (If Inputs is your whole Bitcoin balance. Which would include your change address from the life of your wallet..Why would you then attempt to output the change back to the original change address...that has been used for an input. Which then results in a 'Sent to Self' and thus an invalid transaction! Why not generate a new address or use one of the dozen other addresses available in the wallet ?) I dont see any options at all in the client regarding change addresses unfortunately. This is a show stopping issue for me. Title: Re: Huge issue with MultiBit! Inputs from Change addr, Outputs back to same addr! Post by: jim618 on May 18, 2013, 02:23:43 PM Hi BitHits,
The change address chosen in MultiBit is fairly simple. It uses the second address in the wallet, if it is available. If there is only one address it uses that. You can send a transaction to yourself no problem - it is one of the release tests I always do - so it will not generate invalid transactions. The wallets in MultiBit are random key addresses so creating a new one for change addresses requires people to reback up their wallets. There has been at least one case where a paper wallet user deleted a wallet with change addresses in and lost bitcoin. With the current wallet creating new keys is a user driven operation. If you want more complex change control then of course you have the choice of other wallets - MultiBit endeavours to keep things simple for new users. Title: Re: Huge issue with MultiBit! Inputs from Change addr, Outputs back to same addr! Post by: BitHits on May 18, 2013, 11:38:51 PM I tried to 'send to myself' in the official client. And that tx will never confirm (That was in 02/2013 ... still not confirmed) So I just assumed that transactions from the same wallet into the same wallet wont confirm.
The tx did eventually confirm. So it turns out it was valid ... which kind of makes me wonder why my previous attempt to send to myself was invalid. My whole purpose for using MultiBit in the first place is to have a completely separate wallet to consolidate my coins lacking the ability to do so in Official client. The MultiBit tx http://blockchain.info/tx-index/9375925ed95d85cd9b5ecda6332c814c35ebf04124ac625da4c0bf10ab597767 And the Official Client tx, which seems to have never hit the blockchain, yet is stuck unconfirmed in my client Status: 0/unconfirmed Date: 27/02/2013 22:07 From: unknown To: 1DNNERMT5MMusfYnCBfcKCBjBKZWBC5Lg2 (own address, label: BitHits.info) Credit: 0.0002388 BTC Net amount: +0.0002388 BTC Transaction ID: ee082cd20d6bd35380d1311f84ca4ff967d72821aa12ca3f354718c3a5208e66 |