Release information

[jim618]

-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org

Version 0.5.13

Changes:
#190. The backing up of wallets has been improved.
      There is now a data directory for each wallet.

#111. Failing test fixed. Also fixed functional tests.
#174. Send address is properly trimmed.
#182. Swiss Francs now has correct currency prefix.
#189. Receiving addresses that are manually added to the info file do not appear in the UI.
#191. Swahili added as a target language.
#195. Fixed Verify Message tooltip on a Mac.
#201. Fixed blank validation message if fee takes total over amount in wallet.

Release checklist:
https://multibit.org/test/releaseCheckList-0.5.13.jpg


Bitcoin signing:
This message text (starting with "There is a new release" and ending with "Jim")
is Bitcoin signed with the https://multibit.org donation address.


SHA256 hashes for files:
aaaad8848e69aca528567dfc8ef879a76cb007fd8649ca1baa1c9ff7829c32b9  multibit-0.5.13-linux.jar
64b62ed86bcab0b56cb15670e9504e2bb7a5420c9e3879caeaadbc9f3762248a  multibit-0.5.13-linux.jar.asc
da47611fa8ae82627db93de1d69ba439dce520d05abe62b35ef1be7116eda905  multibit-0.5.13-windows.exe
ce4ba37887a094717982b80351ae0dc3468ff8b134aecfea9708a3f01bcd78c1  multibit-0.5.13-windows.exe.asc
1b3c975ea4b4abf616b8ae6ecd115c6ece95fcdd448d16e5cefbf3c5f1c207e6  multibit-0.5.13.dmg
a92e2c98d0f90f63faed53e21356bb890db82ccd55390fec92a795d64d4ffa4b  multibit-0.5.13.dmg.asc
978369211040430b64364b4a289abf37a6a8d0d667375140f91252d2273f9fc2  multibit-exe.jar
7293ffbbff8c5673d719ad5042d1d3b5c1d9904102ce73397b726c5c53b0d124  multibit-exe.jar.asc
0294dad7f93721c2550c4c483940c40499cdcd6d249636728d975081ca638b01  multibit.exe
676db0e0ec814e3cc048c4cc406947a961b16d1b2dd46c91e94ad86c70efb309  multibit.exe.asc


PGP signing:
You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572
from http://pgp.mit.edu. The files are signed with the subkey with id 0x23F7FB7B.

Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
-----END BITCOIN SIGNATURE-----

[mjb]

FYI: When I copy the release information from Firefox into MultiBit the signature cannot be verified (on MacOS). Could be due to line breaking?!

[melon]

create auto-installation script? what is it?...advanced use only I suppose for future releases im guessing

[jim618]

FYI: When I copy the release information from Firefox into MultiBit the signature cannot be verified (on MacOS). Could be due to line breaking?!

I checked it using Safari on a Mac - check that the last character is the 'm' of Jim. It is easy to add an extra line break at the end.

[jim618]

create auto-installation script? what is it?...advanced use only I suppose for future releases im guessing

It is one of the standard features in the installer creator I use. I must admit I never really use it.

[mjb]

FYI: When I copy the release information from Firefox into MultiBit the signature cannot be verified (on MacOS). Could be due to line breaking?!

I checked it using Safari on a Mac - check that the last character is the 'm' of Jim. It is easy to add an extra line break at the end.

Curiously, on Safari it works. Firefox trims the whitespace before the line breaks:

Line breaks indicated by "$"

Code:

diff safari.txt firefox.txt
7c7
< #190. The backing up of wallets has been improved. $
---
> #190. The backing up of wallets has been improved.$
41c41
< You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572 $
---
> You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572$

Does anyone else see this behaviour? The solution would be not to have trailing white space in the announcement, which could be quite annoying to check.

[jim618]

Well investigated !

I'll make sure I do not put any trailing spaces in the release.txt in future.

[jimbobway]

FYI: When I copy the release information from Firefox into MultiBit the signature cannot be verified (on MacOS). Could be due to line breaking?!

I checked it using Safari on a Mac - check that the last character is the 'm' of Jim. It is easy to add an extra line break at the end.

Curiously, on Safari it works. Firefox trims the whitespace before the line breaks:

Line breaks indicated by "$"

Code:

diff safari.txt firefox.txt
7c7
< #190. The backing up of wallets has been improved. $
---
> #190. The backing up of wallets has been improved.$
41c41
< You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572 $
---
> You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572$

Does anyone else see this behaviour? The solution would be not to have trailing white space in the announcement, which could be quite annoying to check.

I was also not able to verify using Chrome.

Edit: I even downloaded the release text but it doesn't work when I download it either.

[jim618]

Thanks for your feedback.
Signing certainly is fiddly to verify at the moment.

I just tried Chrome Version 28.0.1500.71 on a Mac by going to the release page and simply copy-pasting and it verified ok in MultiBit 0.5.13

It really needs a proper agreed "Bitcoin Signed Message' format so that you can just verify the whole thing without the CopyPasta.

[jimbobway]

Thanks for your feedback.
Signing certainly is fiddly to verify at the moment.

I just tried Chrome Version 28.0.1500.71 on a Mac by going to the release page and simply copy-pasting and it verified ok in MultiBit 0.5.13

It really needs a proper agreed "Bitcoin Signed Message' format so that you can just verify the whole thing without the CopyPasta.

Sorry to bug you again but I can't seem to get it to verify it via bitcoin verification on 0.5.12.  I downloaded the release.txt file and opened it in Notepad, copied the donation address from bitcoin.org, the bitcoin signed message, and the bitcoin signature.  Then I hit "Verify Message".

I get the following error:

The verification of the message failed.
The error was "java.security.SignatureException Header byte out of range: 85".

Not sure what I am doing wrong.  I was able to verify the message in the prev release so I have successfully verified before and at the moment I don't think it is user error...hmmm.  Any ideas?

[jim618]

From your post it looks like you used the bitcoin.org donation address rather than the https://multibit.org donation address.
I have the private key for the multibit.org one and that is the address I used to sign it.

[jimbobway]

Ok, it was user error.  For the signature I pasted this:

Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=

which didn't work.  But, this works for the signature and it verifies:

HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=

In the relase notes it says this:

-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
-----END BITCOIN SIGNATURE-----

Thx.

[jim618]

Glad you got it sorted.

Gary has written a blog item on the steps required to verify the downloads. It should go on multibit.org in a day or two.
That will make it easier for others to repeat your steps.

[jim618]

-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org

Version 0.5.14

Changes:
#133. The Windows installer is signed with authenticode.
#161. Fixed bug: Still prompted for password after a send.
#179. Moved 'Show transaction details' to button bar on Transactions tab.
#180. Added 'Export transactions' to Transactions tab.
#181. Improved build to check dependencies using Gary's dependency checker.
#202. Improved closedown of MultiBit. There are now messages in the titlebar.
#209. Fixed bug: Request labels being wiped after private key import.
#223. Tidied up UI.
#224. Updated to bitcoinj 0.10.1.
#225. Updated to XChange 1.8.0.
#229. Renamed windows installer to get automatic administrator elevation.


Release checklist:
https://multibit.org/test/releaseCheckList-0.5.14.jpg


Bitcoin signing:
This message text (starting with "There is a new release" and ending with "Jim")
is Bitcoin signed with the https://multibit.org donation address.


SHA256 hashes for files:
faa5963fbed111c552b1bb12c45157d3e0d7bb7b6a2531f5aac507c808cb3a3c  multibit-0.5.14-linux.jar
9fff5bd10d2f04756d9a249a32e991efd4238840dd0b8f042dc1f933f9947cf2  multibit-0.5.14-linux.jar.asc
6e568a16a8a1570c34df7006ec0a4270edd205ab5182b254f0d11d88ad8687c4  multibit-0.5.14-windows-setup.exe
9443e26f496631e1df0f790f7f17607efeead7fd8a0531b28aa7aab589071d9b  multibit-0.5.14-windows-setup.exe.asc
1d70f445e5304235989c186c7517886333c844b6b1f30bc794f0590121daa3c4  multibit-0.5.14.dmg
46b186f5398498524693cc60dc7169ef3f4ecec59c6af39a4bb1452a43e3d309  multibit-0.5.14.dmg.asc
1cd0375bac9d15140268996411be82cfcf3baea9dbbbfb2fcdd835e968734742  multibit-exe.jar
34a466a8865b90715c872ac51dc013a88804862f784901e22a473307c65313c0  multibit-exe.jar.asc
156f7b21477460276a3f23df2f9cf706e3af09a8c38d19b189b6e733e77cee08  multibit.exe
07627c99c018c27f32aacdf79f6d1935a53b64798cde22e85fb45ff8da75b874  multibit.exe.asc


PGP signing:
You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572
from http://pgp.mit.edu. The files are signed with the subkey with id 0x23F7FB7B.

Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

G/4pb5HDIC2e+vpeRkrMUHIcCJVFOYcIiSCwF78rSEPf4YQt14q4iFaAo6qU+XBmjaz/8GAIjZ1B+/knOAQHFNI=
-----END BITCOIN SIGNATURE-----

[jim618]

-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org

Version 0.5.15

Changes:
#196. Fixed: Bitcoin URI protocol handler does not work properly under Windows.
#203, #276. Inverted colour scheme now working ok.
#230. Fixed: Exception when sending coins.
#234. Fixed: The addresses in Sign Message / Verify Message need white space trimming.
#235. Fixed: USB drive installation instructions are out of date.
#262. Added support for new blockchain.info wallet format to Import Private Keys.
#280, #284. Fixed: MultiBit does not build.
#283. Fixed: Misleading error message when trying to send very small amount.
#293. Updated build to bitcoinj 0.10.2
#297. Added a message when wallet closes (with location of wallet).
#299. Added Serbian as a target language.
#304. Updated XChange library to 1.10.0

Release checklist:
https://multibit.org/test/releaseCheckList-0.5.15.jpg


Bitcoin signing:
This message text (starting with "There is a new release" and ending with "Jim")
is Bitcoin signed with the https://multibit.org donation address.


SHA256 hashes for files:
f0744e153d1d14b4c469ff7264939c094578968ad32c9e3a03a42ec963729881  multibit-0.5.15-linux.jar
e78ca6c41ec14f566f5e3adf3f6dfe875c7ed5ac05f0c0ad14793cabf5faf369  multibit-0.5.15-linux.jar.asc
fe9e0ef9e8dbfe7bd91005bdc8fdfcf6cc4818910b623e090beaf5eaf4197308  multibit-0.5.15-windows-setup.exe
82a3af4d07c85d41e19f696daf0971ddd4357b32f9a75cc68de6ab3323699850  multibit-0.5.15-windows-setup.exe.asc
52e69866da553590fb2af09006454c5fac094c4970f63cd3bb7c78aefdc8c462  multibit-0.5.15.dmg
88da0e208ef20e082645ce6b04a2ddc1275c5dd51de0cae9d6fc4977b28729c9  multibit-0.5.15.dmg.asc
e551d48b474e46a898afcbf0f1c35dec42de0e1fdf9be8381bac3c845f7ce1a2  multibit-exe.jar
eed20851ecba5bbfdb3874ffbdd26f4f0d95a4eaef63ab5fc5c3a846332abd15  multibit-exe.jar.asc
d826522772307cca4d94a0b7eda48178d1bff6e19dd6ae81f942c1708eec2c52  multibit.exe
ed61898b7e3c1377789b16488a0cba7fda103367867eb960e80a8dcffb4a55dc  multibit.exe.asc


PGP signing:
You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572
from http://pgp.mit.edu. The files are signed with the subkey with id 0x23F7FB7B.

Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

HFJJFTWRzCFU2U4b5k2gTmKha1aPKVtlQYzNflJ5UpNTNQyWooytTXcvUEuQxeBp2p4wzHPKFNph1Et 6kl3RqaM=
-----END BITCOIN SIGNATURE-----

[jim618]

-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org

Version 0.5.16

Changes:
#340. Fixed: if you close a wallet then open it immediately it does not appear.
#347, #410. Updated code to bitcoinj 0.10.3 (transaction is now resent ok if not initially sent).
#407. Changed reset block chain and transactions to always run before wallet creation date.
#408. Send is now prevented until sync completes.
#409. Examined code to see if 'tx is missing' can be improved.
#415. Removed 'File | Delete Wallet' entirely for safety reasons.
#418. Now performs a ping of peers before send as a network check.

Release checklist:
https://multibit.org/test/releaseCheckList-0.5.16.jpg


Bitcoin signing:
This message text (starting with "There is a new release" and ending with "Jim")
is Bitcoin signed with the https://multibit.org donation address.


SHA256 hashes for files:
9ddd139167500036520e322ed6a4feecaf962446e2eb520cf9b28ea05548fbf6  multibit-0.5.16-linux.jar
fc02c2d089e9b3b46146252d44d2342de8cf249b39ad1ae7a38d168555a73788  multibit-0.5.16-linux.jar.asc
fb71064c04273f3ddf913a8ebfe21b00cb9d108c4da7681135bb032880055f2f  multibit-0.5.16-windows-setup.exe
387f088b344b41501650c7b0126afe08886ca4f604cbf240f43a12ae3130be61  multibit-0.5.16-windows-setup.exe.asc
94f673b54b90f7aa35cac2fab08a85d26bdab8eebcb751e41256c853b045c25a  multibit-0.5.16.dmg
f0b5142b17ce4c5a18ebfe9a207fb97572c623408e121c10dda23064ac1137fe  multibit-0.5.16.dmg.asc
5ad29833a767ee4678d6979414f2e89021b64132ea7bc955a3f4bfb8d5be56f8  multibit-exe.jar
c333f4e9ccba93ce1c665a49a89dec3c7fdfd88d1fe4a3e4f50868dad849dbbc  multibit-exe.jar.asc
8f19002159b09f7f7b4aa9d2fd5f96b7a5d0c32fb84fda8962148eb070993a33  multibit.exe
c49df798a7299c6a38cad9f1b663d4203a5912d91d5da5c066ea69d5e2d8e57c  multibit.exe.asc


PGP signing:
You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572
from http://pgp.mit.edu. The files are signed with the subkey with id 0x23F7FB7B.

Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

HGCqMGGX8Wn7Gd99WkFcXu3dDCj7Sl9XiPGHLCFPveDXQT8p+nXGtkb++oGLH3SQQwtSEMwXll1BA201wA4f5KM=
-----END BITCOIN SIGNATURE-----

[filchef]

-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org

Version 0.5.16

Changes:
#340. Fixed: if you close a wallet then open it immediately it does not appear.
#347, #410. Updated code to bitcoinj 0.10.3 (transaction is now resent ok if not initially sent).
#407. Changed reset block chain and transactions to always run before wallet creation date.
#408. Send is now prevented until sync completes.
#409. Examined code to see if 'tx is missing' can be improved.
#415. Removed 'File | Delete Wallet' entirely for safety reasons.
#418. Now performs a ping of peers before send as a network check.

Release checklist:
https://multibit.org/test/releaseCheckList-0.5.16.jpg


Bitcoin signing:
This message text (starting with "There is a new release" and ending with "Jim")
is Bitcoin signed with the https://multibit.org donation address.


SHA256 hashes for files:
9ddd139167500036520e322ed6a4feecaf962446e2eb520cf9b28ea05548fbf6  multibit-0.5.16-linux.jar
fc02c2d089e9b3b46146252d44d2342de8cf249b39ad1ae7a38d168555a73788  multibit-0.5.16-linux.jar.asc
fb71064c04273f3ddf913a8ebfe21b00cb9d108c4da7681135bb032880055f2f  multibit-0.5.16-windows-setup.exe
387f088b344b41501650c7b0126afe08886ca4f604cbf240f43a12ae3130be61  multibit-0.5.16-windows-setup.exe.asc
94f673b54b90f7aa35cac2fab08a85d26bdab8eebcb751e41256c853b045c25a  multibit-0.5.16.dmg
f0b5142b17ce4c5a18ebfe9a207fb97572c623408e121c10dda23064ac1137fe  multibit-0.5.16.dmg.asc
5ad29833a767ee4678d6979414f2e89021b64132ea7bc955a3f4bfb8d5be56f8  multibit-exe.jar
c333f4e9ccba93ce1c665a49a89dec3c7fdfd88d1fe4a3e4f50868dad849dbbc  multibit-exe.jar.asc
8f19002159b09f7f7b4aa9d2fd5f96b7a5d0c32fb84fda8962148eb070993a33  multibit.exe
c49df798a7299c6a38cad9f1b663d4203a5912d91d5da5c066ea69d5e2d8e57c  multibit.exe.asc


PGP signing:
You can verify the PGP signatures by installing gpg and importing the key id 0x79F7C572
from http://pgp.mit.edu. The files are signed with the subkey with id 0x23F7FB7B.

Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty

HGCqMGGX8Wn7Gd99WkFcXu3dDCj7Sl9XiPGHLCFPveDXQT8p+nXGtkb++oGLH3SQQwtSEMwXll1BA201wA4f5KM=
-----END BITCOIN SIGNATURE-----

Did you remove calendar from reset blokcain - If you did I think this is not good idea because when I import one private key from date long time ago before wallet creation  and like to reset blockchain for this date this will be impossible. 

[jim618]

When you import a private key it automatically replays the blocks from the key creation date that is in the private key inport file.
See the help article on importing a single private key for the exact format.


Yes - I removed it because it was causing problems.

The reason for its removal was that people would have a problematic transaction that consumed an earlier output in their wallet.
They were doing a reset from the date of the problematic transaction but the earlier transaction also needed to be resynced. It did not fix things.

It is a bit annoying with older wallets but I have had to go for safety over convenience.
You can sync (on coffeeshop wifi) about a year in 5 minutes so it is not too bad.


In a similar vein, you now cannot send before sync is complete. This is to stop people accidentally double spending themselves because they have shared private keys between two wallets and there are spends that need to be added to the wallet. Again, it would be nice not to have to enforce this but it is necessary now with so many users to avoid errors occurring.

The other fixes are similar - v0.5.16 is all about trying to close down error paths. Removing the delete wallet functionality entirely is like destroying a sharp knife because it 'cuts' the user more often than not when they use it.

[filchef]

When you import a private key it automatically replays the blocks from the key creation date that is in the private key inport file.
See the help article on importing a single private key for the exact format.


Yes - I removed it because it was causing problems.

The reason for its removal was that people would have a problematic transaction that consumed an earlier output in their wallet.
They were doing a reset from the date of the problematic transaction but the earlier transaction also needed to be resynced. It did not fix things.

It is a bit annoying with older wallets but I have had to go for safety over convenience.
You can sync (on coffeeshop wifi) about a year in 5 minutes so it is not too bad.


In a similar vein, you now cannot send before sync is complete. This is to stop people accidentally double spending themselves because they have shared private keys between two wallets and there are spends that need to be added to the wallet. Again, it would be nice not to have to enforce this but it is necessary now with so many users to avoid errors occurring.
I don't understand why you make changes  which restrict advanced users.
The other fixes are similar - v0.5.16 is all about trying to close down error paths. Removing the delete wallet functionality entirely is like destroying a sharp knife because it 'cuts' the user more often than not when they use it.

But wen you import private key and you don't know when it is generated like in Bitcoin-Qt wallet you can't try to reset blockcain to earlier date it is not gut solution so I don't like to instal new version - you have to back the calendar and just make impossible to fix date more near then creating the wallet date.
I don't think this is very hard to programme  just check if date is before date of creating the wallet and if it is start reset blokcain from this date if not start reset from date of first generation

I do not understand why you make changes which restrict advanced users.

[jim618]

The date you used to use in the 'reset blockchain' screen, you can just use the same date in the import file.
It only has to be before the date of the first transaction, which you could look up from a block explorer.


It is a balance, to get the features 'right' for any particular wallet.
We aim MultiBit (and MultiBit HD even more so) for entry level and novice users so want to keep things simple.

Moving private keys around is quite advanced use (most users are probably a bit fuzzy about what a private key actually is).
Fortunately, there are several teams now working on wallets e.g. Hive, Armory, Electrum and (next year) Dark Wallet so you might be better served by the wallets targets for advanced users.

We don't mind at all if people start off using MultiBit and then, when they want to do more advanced things, move over to different wallets.


We've found over 2013 that some features, whilst useful if you know what you are doing, can sometimes lead users to make mistakes and cause confusion. 'Delete Wallet' is a good example. For the entry level bitcoin user it is almost always a bad idea to delete your wallet. For advanced users such as yourself - sure - you know what they are doing.