Just started using MultiBit, works great! Is there a way to add more than 2 rows in the exchange tickers up the top though? I want to keep an eye on about 4-5 markets at a glance.
Cheers
Topic: MultiBit - page 22. (Read 336309 times)
@lunarboy, profbit
Thanks for your feedback. Yes I agree that the Send tab needs more work.
In addition to the usability issues that you've raised, now that there is a feesolver it is practicable to have multi-send.
(It was not doable before because it can generate large transactions).
Also further down the pipe is the work on the payment protocol which would no doubt change things again.
At the moment my priority is HD wallets and preparation for Trezor work.
UI fixes I think might have to wait a while - I find you can only really work on one area at a time.
Cheers
Thanks for your feedback. Yes I agree that the Send tab needs more work.
In addition to the usability issues that you've raised, now that there is a feesolver it is practicable to have multi-send.
(It was not doable before because it can generate large transactions).
Also further down the pipe is the work on the payment protocol which would no doubt change things again.
At the moment my priority is HD wallets and preparation for Trezor work.
UI fixes I think might have to wait a while - I find you can only really work on one area at a time.
Cheers
The problem is it's also very easy to accidentally write over an old send to address
+1
This is the only remaining usability problem I am seeing too. Once that s improved it will be perfect. Default send address should be empty (don't force the user to click the new button because "new" is what he needs anyways in 99.999% of all use cases, so just remove the need for that additional click at all and make this the default state in which this tab opens) and after BTC have been sent it should again imply a click to new to switch to a new empty address immediately again.
Having been playing with multibit for a few months now, i'd have to say I really like the simplicity and user friendly GUI, will definitely be recommending it to new bitcoin users. Seems ideally suited for the novice to intermediate set.
One comment though. I'm finding the send request tab a little bit frustrating. Its very easy to set up a new send to address. The problem is it's also very easy to accidentally write over an old send to address 'C/P', with say Bobs address and before you know it you've lost track of who is who, or unsure if it accidentally changed last time before closing.
I'd like to see the option being a little more robust. If I set up an send to Alice address, i'd like the option to save this and have to click edit to change it, or at least get a prompt that i'm changing Alices address before it disappears forever.
O as a quick fix, have it set with the default send address being blank, rather than the editable address text that was the last 'send' used.
Keep up the great work Jim.
Lunar
One comment though. I'm finding the send request tab a little bit frustrating. Its very easy to set up a new send to address. The problem is it's also very easy to accidentally write over an old send to address 'C/P', with say Bobs address and before you know it you've lost track of who is who, or unsure if it accidentally changed last time before closing.
I'd like to see the option being a little more robust. If I set up an send to Alice address, i'd like the option to save this and have to click edit to change it, or at least get a prompt that i'm changing Alices address before it disappears forever.
O as a quick fix, have it set with the default send address being blank, rather than the editable address text that was the last 'send' used.
Keep up the great work Jim.
Lunar
Hi Lunarboy,
At the moment no - there is some discussion about it in https://bitcointalksearch.org/topic/m.2585913 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
At the moment no - there is some discussion about it in https://bitcointalksearch.org/topic/m.2585913 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.
Hi Lunarboy,
At the moment no - there is some discussion about it in https://bitcointalksearch.org/topic/m.2585913 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
At the moment no - there is some discussion about it in https://bitcointalksearch.org/topic/m.2585913 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
Now fees are calculated automatically in 5.12 is there a way around the auto settings to force a different fee value?
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.
(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.
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.
(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.
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 :/It is also available here:
http://www.multibit.org/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html
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. 
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.
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.
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
It is also available here:
http://www.multibit.org/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html
Transaction seen by 1 peer. Not seen in chain...
What to do?
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.
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 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
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
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.
https://blockchain.info/en/tx/5ec236b3ca1d123180082a5b9318e0d24271a8dff124c10dae015e1dc5095bed
EDIT: Transaction confirmed. time elapsed 2.5 hours
ty jim618 for your answer.
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
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.
To update you just install the new version and it picks up your wallets.
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?
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?
Jump to: