MultiBit

[GuiltySpark343]

BUMP. +1 for adding ability to sign messages, this way I can truly dump the QT wallet app!

[1713496737]

1713496737

[1713496737]

1713496737

[1713496737]

1713496737

[1713496737]

1713496737

[GuiltySpark343]

Ok dumb question: I know you can create multiple addresses for receiving coins, but when you send other people coins, what address does Multibit use as the "sending address"?

[giszmo]

Ok dumb question: I know you can create multiple addresses for receiving coins, but when you send other people coins, what address does Multibit use as the "sending address"?

I am not familiar with the internals of MB but as coin age plays an important role in the transaction priority, the satoshi client will pick an old address. Also the client most likely tries to optimize the transaction size by taking fewer inputs, so when you have addresses with 0.1, 0.2 and 0.3Ƀ respecitvely, it would take the 0.3Ƀ address when you try to send 0.27Ƀ rather than the 0.1+0.2.

If the 0.3Ƀ is less than 3 days old though, it would have less than 1BTC-day of age and would need a transaction fee to get processed, so the client might pick the older coins.

If you want to control that, you need a feature called "coin control". Again I'm not sure if MB has that.

[jim618]

I just wanted to thanks to the people who have made donations to the multibit.org address in the last month, whoever you are !
:-)

[ZoladkowaGorzka]

I'm just wondering. How to send bitcoins in one transaction to multiple addresses?
f.e http://blockchain.info/tx-index/f7546fc26292094ed1920a13e47630c902ab2c389c037a9f4823d17d86909012
There's only 1 fee but there are multiple recipient addresses.


EDIT:
how to update Multibit? By just downloading and installing the new version?

[jim618]

At the moment MultiBit does not support sending to multiple addresses. It is on the list of planned developments.

To update you just install the new version and it picks up your wallets.

[ZoladkowaGorzka]

At the moment MultiBit does not support sending to multiple addresses. It is on the list of planned developments.

I would be obliged if you implemented this

To update you just install the new version and it picks up your wallets.

just as I thought. Thanks

[fsb4000]

hello. I have a problem. I made a transaction with multibit 0.5.11. It has turned out more than 1 kilobyte. Why was it used 7inputs instead of 5 intputs?(5 inputs tx less 1 kb) Whether the added ability in the future to manually select inputs? Does it confirm sometimes? It has not been confirmed within 8 blocks...
https://blockchain.info/en/tx/5ec236b3ca1d123180082a5b9318e0d24271a8dff124c10dae015e1dc5095bed
EDIT: Transaction confirmed. time elapsed 2.5 hours  
ty jim618 for your answer.

[jim618]

Hi fsb400,

Your tx has a fee of 0.0001 BTC for a tx over 1KB.
That makes it a bit unattractive to miners which is probably what is causing the delay.

I have had to wait a couple of days before  a tx of mine with a low fee got in a block. That was with a tx with a smaller fee per kilobyte than yours mind.

The default fee in 0.5.11 is a flat fee of 0.0005 BTC which should be ok for tx up to size 5KB. With the 0.5.12 code the fee would have been calculated as 0.0002 BTC

Re selecting inputs - I am not sure this is very useful for the average user as most people do not know (or want to know) transaction  structure

[mjb]

Re selecting inputs - I am not sure this is very useful for the average user as most people do not know (or want to know) transaction  structure

For all the group buys that are going on in the Hardware section it would actually be quite useful to control the sender address, as they are also used to prove ownership by signing shipment delivery addresses later etc.
What about offering this as an option when you right click an address? Something like "pay only using this address"? This way it would be hidden enough for the casual user but still available for power users.

Which reminds me that it would also be nice to offer "sign message using this address" in said context menu. Right now much more clicks and cut and pasting are needed to sign a message.

[jim618]

Re selecting inputs - I am not sure this is very useful for the average user as most people do not know (or want to know) transaction  structure

For all the group buys that are going on in the Hardware section it would actually be quite useful to control the sender address, as they are also used to prove ownership by signing shipment delivery addresses later etc.
What about offering this as an option when you right click an address? Something like "pay only using this address"? This way it would be hidden enough for the casual user but still available for power users.

Which reminds me that it would also be nice to offer "sign message using this address" in said context menu. Right now much more clicks and cut and pasting are needed to sign a message.

Hi mjb,

That's interesting - I notice signing is being mainly used by group buys. I'll see if I can beef up what is effectively coin control.
Edit: https://github.com/jim618/multibit/issues/176 - actually more complicated as you also need to see the balance per address for it to be useful.

I agree there is too much cut-and-paste with signing (but at least it is available now!). Andreas came up with the similar suggestion that you choose a receiving address and, somewhere, click on 'Sign' then it switches to the 'Sign Message' page with the address filled out. I have added that to my TODO list.
Edit: https://github.com/jim618/multibit/issues/175

What signing/ verifying really needs is an agreed "Bitcoin Signed Message" format similar to PGP signing.

[ZoladkowaGorzka]

Transaction seen by 1 peer. Not seen in chain...

What to do?

[jim618]

There is a section in the "Help | Help Contents'. In the 'Support' section called 'I sent bitcoin from MultiBit but they are stuck'.
It is also available here:
http://www.multibit.org/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html

[Binford 6100]

thought on coin control and selection of inputs:
hi jim, i think no need to worry about developing the perfect feature, just allow selecting an address that should be used for sure in the payment.

if the balance is not enough, let the app chose other inputs as usual. as long as the funds are send in the same transaction, it can be proved that the one of the source addresses was chosen by the user, he can sign the group buy message with the chosen address/key and the rest of the payment comes from his wallet, so no more issues.
(if I can sign for one address used as input, i'm also able to sign with other addresses, just makes no sense to go through all the loops).

tl;dr; just pick an address that must be used for outgoing payment, the rest is already there.

[ZoladkowaGorzka]

There is a section in the "Help | Help Contents'. In the 'Support' section called 'I sent bitcoin from MultiBit but they are stuck'.
It is also available here:
http://www.multibit.org/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html

Unfortunately, the situation become even more curious than it used to be :/
After resetting the blockchain:
the balance was 0.69..BTC 

To my surprise there were no transactions I sent (you can see them in picture in previous post, the not-seen-in-chain ones)
I've exported the private keys (all of them), and installed multibit on my netbook.
The result was:

WTF? Not only 2.0612 Bitcoin missing (from transactions) but another 0,67675428 BTC disappeared as well.

[jim618]

The transactions that got stuck on one peer (unless it was a network failure as per the help) were most likely sent to a peer but then subsequently did not propagate through the network.

(You don't mention which version of MultiBit you sent the tx from. Anything earlier than 0.5.12 used a flat fee which can cause problems if you have big tx).

When you do a reset blockchain and transactions it syncs your wallet to what is on the blockchain and what is in the memory pool of the peer you are talking to. It would not include the transaction you sent no (because they did not propagate the network).

You don't mention if you reset the whole wallet (back to the first transaction) or not.
I would recommend resetting back to the first transaction (it is an option on the reset blockchain page). That way you can be sure that all your transactions match what is on the blockchain.

Because what your goal is is to replicate what is on the blockchain you can also use blockchain.info and blockexplorer.com to cross check you have the transactions you expect.

[jim618]

Looking more closely at your screen shots it looks like you have your fee set at 0.0001 BTC (looking at your earlier send tx).
(If you are not on 0.5.12) This may be the root cause of your problem in your tx not propagating. The relay fee is 0.0001 BTC per KB so if you have a larger tx you'll need to bump up the fee. With version 0.5.12 this is worked out automatically.

[lunarboy]

 Now fees are calculated automatically in 5.12 is there a way around the auto settings to force a different fee value?

[jim618]

Hi Lunarboy,

At the moment no - there is some discussion about it in https://bitcointalk.org/index.php?topic=143274.msg2585913#msg2585913 and for the next few post on that thread.

They are currently set at pretty much the lowest the Bitcoin network will accept - I am hoping this will be sufficient but again have a look at that thread.

Cheers

[lunarboy]

Hi Lunarboy,

At the moment no - there is some discussion about it in https://bitcointalk.org/index.php?topic=143274.msg2585913#msg2585913 and for the next few post on that thread.

They are currently set at pretty much the lowest the Bitcoin network will accept - I am hoping this will be sufficient but again have a look at that thread.

Cheers

Thanks, missed that one.