MultiBit

[Atruk]

Yeah I was going to put 0 as an option for the number of keys in the create wallet wizard.

I don't want to put the import key in the create wallet as it would just repeat the existing tab. 99% of the people going to a 'create wallet' wizard just want to create a wallet, if you see what I mean.

I've found your instructions on manually importing keys on the Multibit.org site to be rather ammenable to bastardization for this purpose.

I didn't do this for noble purposes though. I just wanted a vanity profanity wallet...

[1713538849]

1713538849

[1713538849]

1713538849

[Binford 6100]

congrats to the brilliant description of use case with imported key, spending and deleted wallet.
could you allow sending change back to originating address (if it was an imported address) in the long run?
that might save troubles to folks who import keys from paper wallets and expect the unspent balance to magically reappear there after use. or highlight this risk in the import key tab? I don't know if multibit internally distinguishes between imported and locally created addresses. electrum does distinguish between them but they use seed & deterministic wallet approach.
or keep hoping/wishing for educated user base?

[jim618]

It's probably simpler to allow wallets with no keys in so that the only key in there is the one you want.
In general there is not a single 'originating' address in Bitcoin.

There is little point in putting a warning in the import private key because:
+ the user may be doing something different: false positive warning
+ the user is focused on importing, not spending. The warning is 'far away' from where the mistake occurs.

[spiccioli]

Hi Jim,

regarding wallets and keys, I'd like to have the possibility to drag and drop an address from one wallet to another one (inside multibit) as a form of coin control.

For example: let's say that I got a sizeable sum from a trade on an address and I want to move that address to my encripted/safe wallet removing it from my day-to-day one which is not encrypted.

Would this be feasible?

There is a second question now, in the transaction grid I can resize columns but when I restart multibit, columns get resized back to their default. Can column sizes be made permanent?

Thanks!

spiccioli

[jim618]

RE moving keys.

I have thought about something similar but it gets quite confusing because to move a key you need to:

1) add it to the new wallet
2) delete it from the old wallet.

Unfortunately because a transaction spends multiple transaction inputs you might have a transaction:

Spends:
   5 BTC from an output from transaction on address A
   5 BTC from an output from transaction on address B

   sends it to
   7 BTC to address C
   3 BTC to address B (change)

If you move address A out of the wallet then the transaction now looks like it has spent an output that is no longer in the wallet.
This is pretty confusing as it "kind of" looks like you spent 5 BTC from address B, sent 7 BTC to address C and sent 3 BTC back to address B "oh plus there was an address A that I spent from but I don't have that address so god knows what happened there".

I don't think it is practical.


Remembering size and position of screen, dividers, column widths etc then yes it is already on my TODO list. I will probably do the screen size, position and divider position first as that is more intrusive that it forgets it.

[yacare]

Yeah I was going to put 0 as an option for the number of keys in the create wallet wizard.

I don't want to put the import key in the create wallet as it would just repeat the existing tab. 99% of the people going to a 'create wallet' wizard just want to create a wallet, if you see what I mean.

Perfectly clear.
For that 1% you can make a "How to use a paper wallet" step by step instructions on the website.

[jim618]

I am starting writing a few blog pages for various things - there is a new section on the website for it.

Paper wallets would be a good one to explain to people.

[spiccioli]

RE moving keys.

I have thought about something similar but it gets quite confusing because to move a key you need to:

...

I don't think it is practical.


Remembering size and position of screen, dividers, column widths etc then yes it is already on my TODO list. I will probably do the screen size, position and divider position first as that is more intrusive that it forgets it.

Jim,

thanks for clarifying.

spiccioli

[freethink2013]

are there upgrade instructions? I only see install instructions.

[jim618]

If you have a normal setup you just need to install the new version. When you start up the new version you'll see your existing wallets.

[freethink2013]

If you have a normal setup you just need to install the new version. When you start up the new version you'll see your existing wallets.

brilliant. I presumed it was that but there was a shadow of a doubt. You might consider putting that on the site. Easy upgrade is a plus point. thanks again

[jim618]

Yes - good idea put a note in the site.

[Atruk]

I've had a couple of friends running Multibit on Windows 7 run into corrupted blockchains. The fix was fairly easy in that it involved updating to the latest version, deleting the blockchain file, redownloading the blockchain, and then rescanning their addresses. The first time was a few weeks ago, but the most recent incident of "Oops, corrupted blockchain!" was this past Saturday (Multibit 0.4.21, Windows 7). The fix is easy and reliable enough, but the cause is a mystery to me.

[jim618]

I will put it into the issues as something to watch out for and have a look at the code.
Also I will put in a support note on the website so people can find out what to do to fix it.

Have you seen it on the 0.5.9 version ? The blockstore is different - it is a lot smaller.

[Atruk]

I will put it into the issues as something to watch out for and have a look at the code.
Also I will put in a support note on the website so people can find out what to do to fix it.

Have you seen it on the 0.5.9 version ? The blockstore is different - it is a lot smaller.

Haven't seen it in 0.5.9, but switching to 0.5.9 on its own isn't a fix. I haven't seen it begin in 0.5.9 yet.

[prof7bit]

I have a question regarding the new 54µBTC minimum output rules of the bitcoin-qt client. How is this handled by Multibit? The problem I see here is if I have a wallet with 1.000550 BTC and send an 1 BTC transaction then  it would send 1 BTC to the receiver, 50 µBTC as change to myself and 500µBTC as fees. Such a transaction would qualify as "spam" by most peers acording to the new rules and might be difficult to broadcast. I know that its extremely unlikely that this happens to a normal user very often but it is a possible scenario happening to users that are totally unaware of the problem. How does Multibit deal with this? Possible solutions are: If this happens then either look for other available outputs that are better suited for this transaction or if no other outputs are available then just add the < 54µBTC dust to the fees and return no change at all. Is something like this already implemented in Multibit or is it planned?

[jim618]

Mike Hearn has put in an interface CoinSelector into bitcoinj so we can tweak the rules for which outputs get used pretty easily.

I haven't decided what to do about the '54 uBTC' change to be honest. Excluding them from
transactions effectively makes them unspendable and that messes up usability.

For instance, you might have 10BTC in your wallet.
1) Oh but you cannot spend all of that, because the fee is 0.0005 BTC
2) Oh but you cannot spend 9.9995 BTC because you have some unspendable dust.

Rule 1) already catches people out so another similar rule, but different, would compound things.

It need some more thought basically.

[jim618]

Thanks for the MultiBit donations received in the last month - a grand total of 604 millis, including one of 500 millis.

Cheers !

[San1ty]

I'm having an issue with MultiBit importing a blockchain encrypted wallet.
I know the password, and fill it in, then click unlock but nothing happens...

I don't get any error message, just "Number of keys Replay Date" is empty.

I'm running this on ubuntu, am I missing a package?

(I did download this file in windows and dragged it in an ubuntu VM)

[jim618]

Hi NodePool,

You are not missing a package. There is a bug raised for this here:
https://github.com/jim618/multibit/issues/116

I have not investigated it yet.
If it is only a few keys you can show the keys decrypted in blockchain.info and then copy them into a key file one by one and then import it.