MultiBit HD v0.1 almost ready - any localisation would be appreciated

[jim618]

Hello Everybody,

Gary and I have pretty much got MultiBit HD v0.1 ready for release now.
We are just doing final testing to see if it is OK for general use.

One thing we cannot do is the localisation as we aren't clever enough so any effort in this area would be appreciated.
There is a website for it here:

https://crowdin.com/project/multibit-hd

Anything you could localise (in your mother tongue) would be appreciated.
Any localisation done by 9:00 GMT Monday 8 June will definitely get into the v0.1 build.

[jackbox]

Are you adding ability to view balance in every used address and preview future address list?

[jim618]

Hi Jackbox,

The workflow for address generation/ use is pretty much the same as in Beta 8 so no to both questions.

For MBHD we have put showing individual addresses 'low down in the mix' for a few reasons.

You create a new address when you generate a payment request e.g.:'Pay me 0.05 BTC for the beer last night'.
Then this request has the workflow:
+ You requested it (shown in Payment screen, can drill down).
+ Paid (or part paid) when the amount is paid off (or partly paid off).

The transaction that paid off the payment request is linked so that you can see e.g. you requested 0.05 and the person sent you 0.051 say. (And the fiat equivalents of the payment request and tx that paid it).

We don't show more addresses than the payment requests you've generated for simplicity reasons and also we don't want the user to produce gaps in address usage. In BIP 44 there is a gap limit of 20. If the user generates a long run of unpaid payment requests we give them a (rather unintuitive) note and recycle the ultimate address generated.

You see the same behaviour with new addresses, more or less, in all of Lighthouse, Mycelium and Copay where there is a distinct reluctance to show future addresses. This, no doubt, is for exactly the same reason.

We actually pre-generate a lookahead of addresses that aren't shown to the user. This is so that we can see transactions generated from the same wallet on another device and it makes the bloom filtering more efficient