It is not perfect but I think it is now usable.
Screenshot in Farsi:
This will appear in the next live version 0.4.12 which should be this week.
Topic: MultiBit - page 51. (Read 336309 times)
I have updated the MultiBit layout for when it is displaying right-to-left languages like Arabic, Farsi, Hebrew.
It is not perfect but I think it is now usable.
Screenshot in Farsi:
This will appear in the next live version 0.4.12 which should be this week.
It is not perfect but I think it is now usable.
Screenshot in Farsi:
This will appear in the next live version 0.4.12 which should be this week.
While I use this client from time to time, the biggest issue I have with it is that it sometimes doesn't let me send my money, and I have to reset the blockchain and it just dies on me.
This is all good feedback Mushroomized. Is the 'it sometimes doesn't let me send my money" the thing about unconfirmed change ? If so, then yeah we have a plan for that. If it is something else please give some more detail.
The 'it just dies on me' I would like to know more about. What platform are you running on ? I have seen that very occasionally on the Linux VM I use for testing. It is a difficult one to get to the bottom of so any information you have would be useful.
Apparently I am just going to become a bother....
So after getting it to it will not connect
I left if for over an hour and a half
log: http://pastie.org/5025538
So after getting it to it will not connect
I left if for over an hour and a halflog: http://pastie.org/5025538
In your paste I can see that it had a list of 14 peers (i.e. Satoshi clients) that it would subsequently try to connect to. What it should do is try all of these and, if all of them are stale it waits a while and then trys again. This code is relatively new so it could be that it is not recreating a whole new list again. I will have a look into this.
Try just closing down MultiBit and restarting it again and it will reinitialise the list of all the peers etc.
While I use this client from time to time, the biggest issue I have with it is that it sometimes doesn't let me send my money, and I have to reset the blockchain and it just dies on me.
Apparently I am just going to become a bother....
So after getting it to it will not connect I left if for over an hour and a half
log: http://pastie.org/5025538
So after getting it to it will not connect
I left if for over an hour and a halflog: http://pastie.org/5025538
Please read the sections posted above on unconfirmed transactions and what 'Available to spend' means.
You have a wallet where there are only a small number of transactions outputs available to create transactions.
I expect the unconfirmed transaction of 08 Oct has a large change output. If you select that transaction and do a right click and 'View transaction details' you can see the transaction in detail.
The post above by SRoulette explains how you can create more transaction outputs.
If you are not comfortable with the structure of transactions - as outlined in the previous posts - then I suggest you do not use MultiBit. Just export your private keys and import them into blockchain.info or similar.
You have a wallet where there are only a small number of transactions outputs available to create transactions.
I expect the unconfirmed transaction of 08 Oct has a large change output. If you select that transaction and do a right click and 'View transaction details' you can see the transaction in detail.
The post above by SRoulette explains how you can create more transaction outputs.
If you are not comfortable with the structure of transactions - as outlined in the previous posts - then I suggest you do not use MultiBit. Just export your private keys and import them into blockchain.info or similar.
wow ...
5 available to send ... why?
transaction from 08.10. is confirmed with over 100 confirmations?!
damn client, sorry but it is really not good!
5 available to send ... why?
transaction from 08.10. is confirmed with over 100 confirmations?!
damn client, sorry but it is really not good!
Have you tried the setting as described in the mountain lion link a couple of posts up ? That would decide it one way or the other.
Setting GateKeeper to ANYWHERE does indeed solve the problem. This means that despite Apple's own words:
Control+Clicking to allow the package is not the equivalent to saying 'let it run, no matter what'
Doing some further research (as I don't really want to turn off gatekeeper) it turns out that it has to do with the quarantine flag as described here: http://apple.stackexchange.com/a/58089/30611
I first tried lowering the setting and running MultiBit, then moving it back (damaged error).
Removing the quarantine flag (xattr -d com.apple.quarantine /Applications/MultiBit.app) fixed the broken error.
You might want to document this on the gatekeeper page Jim as I was under the belief that Ctrl+Clicking would do the same thing.
It definitely is Gatekeeper. There appears to be some kind of bug (in something, somewhere) where Gatekeeper doesn't like Java apps, perhaps there is a mismatched signature somewhere. The error means a signature failed to match, but it's unclear where such a signature would come from.
Have you tried the setting as described in the mountain lion link a couple of posts up ? That would decide it one way or the other.
The "damaged and can't be opened" error is from Gatekeeper. MacOS is crying because Jim isn't signing the app. He needs to get a Mac developer ID and sign MultiBit with that to make the error go away. Alternatively, disable Gatekeeper and the issue should also resolve itself.
I dont think it is gatekeeper, as you get a different error for that.
hm, but I dont understand this.
I receive 720 Bitcoin.
The Transaction has more than 6 Confirmations.
I send 10 Bitcoins to an address and must wait, that I can send more Bitcoin to another address.
In the normal Client I dont have this problem?!
Did the windows client has the same problem?
I must send often about 4-7 transactions at the same moment.
But when I must wait every transaction to confirm, I don't
will use the client anymore
I receive 720 Bitcoin.
The Transaction has more than 6 Confirmations.
I send 10 Bitcoins to an address and must wait, that I can send more Bitcoin to another address.
In the normal Client I dont have this problem?!
Did the windows client has the same problem?
I must send often about 4-7 transactions at the same moment.
But when I must wait every transaction to confirm, I don't
will use the client anymore
You are correct that it is the recent transactions that need to be confirmed (for the change part of your transaction to appear on the blockchain). It is a known limitation and will be looked at in the future.
If you have only one or two unspent transactions in a wallet it can be a pain. If you have lots of unspent transactions (ie several small payments into the wallet rather than one big one) it is less noticeable. That is what I do - I 'load up' a wallet with payments in that are roughly the size of the payments I am making. That way you can make simultaneous payments, each of which are consuming different available transaction outputs.
Re: is it the same on Windows.
The MultiBit code is almost the same on all of Linux, Mac and Windows.
@ErebusBat
Re: GateKeeper - it is as Mike says - I need to start signing MultiBit with an Apple dev id. There is a note on the multibit.org help page that links to this how-to to fix it:
http://multibit.org/help_mountain_lion.html
It is not a fault of the wallet but more a feature of the bitcoin protocol.
bitcoin will try to build a transaction from your unspent inputs, but often you cannot match the exact size.
eg: your trying to bet 0.25 on mini dice but only have a single unspent input of 0.3.
bitcoin will send 0.25 to the betting address and 0.5 (minus tx fees) back to one of your existing addresses.
This is how you bitcoin automatically breaks unspent inputs into smaller usable amounts.
So to stop all/ most of you bitcoins becoming unavailable for ~10 minutes after 1 transaction you do the following:
N = Number of new addresses (I used 10 )
T = Total balance
X = T / ( N + 1) we add 1 to N to allow for tx fees .
create N new addresses
Create a transaction that sends X to each of the new addresses (done from another wallet as multibit does not seem to support multi send atm).
Now when you send an amount under X only a portion of your wallet becomes unconfirmed ( X / T * 100 = ~ %10 ).
We found this out very quickly when testing multi bit on our site, but also found a easy solution
hm, but I dont understand this.
I receive 720 Bitcoin.
The Transaction has more than 6 Confirmations.
I send 10 Bitcoins to an address and must wait, that I can send more Bitcoin to another address.
In the normal Client I dont have this problem?!
Did the windows client has the same problem?
I must send often about 4-7 transactions at the same moment.
But when I must wait every transaction to confirm, I don't
will use the client anymore
I receive 720 Bitcoin.
The Transaction has more than 6 Confirmations.
I send 10 Bitcoins to an address and must wait, that I can send more Bitcoin to another address.
In the normal Client I dont have this problem?!
Did the windows client has the same problem?
I must send often about 4-7 transactions at the same moment.
But when I must wait every transaction to confirm, I don't
will use the client anymore
You are correct that it is the recent transactions that need to be confirmed (for the change part of your transaction to appear on the blockchain). It is a known limitation and will be looked at in the future.
If you have only one or two unspent transactions in a wallet it can be a pain. If you have lots of unspent transactions (ie several small payments into the wallet rather than one big one) it is less noticeable. That is what I do - I 'load up' a wallet with payments in that are roughly the size of the payments I am making. That way you can make simultaneous payments, each of which are consuming different available transaction outputs.
Re: is it the same on Windows.
The MultiBit code is almost the same on all of Linux, Mac and Windows.
@ErebusBat
Re: GateKeeper - it is as Mike says - I need to start signing MultiBit with an Apple dev id. There is a note on the multibit.org help page that links to this how-to to fix it:
http://multibit.org/help_mountain_lion.html
The "damaged and can't be opened" error is from Gatekeeper. MacOS is crying because Jim isn't signing the app. He needs to get a Mac developer ID and sign MultiBit with that to make the error go away. Alternatively, disable Gatekeeper and the issue should also resolve itself.
Is anyone else getting a damaged Warning under OSX?
I just downloaded 0.4.11; however it happened with 0.4.10 also and never got back around to troubleshooting it (until today, so I just downloaded the newest ver).
I just downloaded 0.4.11; however it happened with 0.4.10 also and never got back around to troubleshooting it (until today, so I just downloaded the newest ver).
hm, but I dont understand this.
I receive 720 Bitcoin.
The Transaction has more than 6 Confirmations.
I send 10 Bitcoins to an address and must wait, that I can send more Bitcoin to another address.
In the normal Client I dont have this problem?!
Did the windows client has the same problem?
I must send often about 4-7 transactions at the same moment.
But when I must wait every transaction to confirm, I don't
will use the client anymore
I receive 720 Bitcoin.
The Transaction has more than 6 Confirmations.
I send 10 Bitcoins to an address and must wait, that I can send more Bitcoin to another address.
In the normal Client I dont have this problem?!
Did the windows client has the same problem?
I must send often about 4-7 transactions at the same moment.
But when I must wait every transaction to confirm, I don't
will use the client anymore
All the beta are here:
https://github.com/jim618/multibit/downloads
As I am sure you know if you storing three figure sums of BTC it is imperative that you backup your private keys somewhere safe.
Available to spend is explained here:
http://multibit.org/help_availableToSpend.html
Basically it is waiting for change to be confirmed as flatfly stated.
https://github.com/jim618/multibit/downloads
As I am sure you know if you storing three figure sums of BTC it is imperative that you backup your private keys somewhere safe.
Available to spend is explained here:
http://multibit.org/help_availableToSpend.html
Basically it is waiting for change to be confirmed as flatfly stated.
Where to find the BETA for mac?
And there is another problem.
If I send BTC to another address, there are only some BTC left to send, why?
Look at this screen:
Deposit 720 BTC ...
send out 15.8****
Available only 0.0045, why?
And there is another problem.
If I send BTC to another address, there are only some BTC left to send, why?
Look at this screen:
Deposit 720 BTC ...
send out 15.8****
Available only 0.0045, why?
I'm not sure, but I think you need to wait for a couple of confirmations for the rest to become available.
Where to find the BETA for mac?
And there is another problem.
If I send BTC to another address, there are only some BTC left to send, why?
Look at this screen:
Deposit 720 BTC ...
send out 15.8****
Available only 0.0045, why?
And there is another problem.
If I send BTC to another address, there are only some BTC left to send, why?
Look at this screen:
Deposit 720 BTC ...
send out 15.8****
Available only 0.0045, why?
Also, can you email me the log files I mentioned (to jim at multibit.org) as I would like to see if there is anything unusual going on. I try to keep the "reset blockchain and transactions" as solid as possible (as it is only used when things go wrong) but clearly there is something not quite right in it.
Thanks,
Jim
Thanks,
Jim
Ok, just gave you a PM.
Jump to: