There is also a blog article about this release here:
https://multibit.org/blog/2014/04/28/private-key-safety-improvements.html
Topic: Release information (Read 10910 times)
-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.18
Changes:
Upgrade to bitcoinj 0.11.2. This is mainly bug fixes.
Update of localisation and checkpoints files.
#540: Removal of import of blockchain.info wallet export files
#540: New utility "Tool | Check Private Keys"
#533, #534: Fix for cannot send 1000BTC or more (fix by Telepatheic)
#530: Fix for test timezone error (fix by allada)
#529: Fix for padding bytes in private key export files (fix by Andreas Schildbach)
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.18.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:
a067c9638edfdf39f3e9fa154b0c6d8cfb7c58c0edd95a02c0ca903160ca3aad multibit-0.5.18-linux.jar
76ce043b26fc7d18fcbc3d17583b2fdec0dcd3023f5e7e7c03f1a8dde6b3f663 multibit-0.5.18-linux.jar.asc
dc0c2ef689507c57347c0cbed58ea90fe12617a6fb026b308e81ec2127531b7e multibit-0.5.18-windows-setup.exe
b8812322e670a1a46fc06d01109f7ca7479c0e8655bc167a18c59878023dbeb5 multibit-0.5.18-windows-setup.exe.asc
0d2fe6fa68385c1ca964d9588272787dabffbc2061f29ebaab422317d0972257 multibit-0.5.18.dmg
0f1d5c880fa7f10930e34773374fb6f97f01ea2ae38cb32302b7efc4887baa2b multibit-0.5.18.dmg.asc
55dd9b0bf5ed45b2ad064f444fe99373b2601e1404bb1da44b59ff4bd343f968 multibit-exe.jar
e9fdd68d266745334e4ce184f227ca1e316e21293e359b16196708f56ad137d3 multibit-exe.jar.asc
ae1950d2a74e9b91059467de1f0255cfbf3c3002cb02902971b27900b7a941f6 multibit.exe
644390e4a3cebef3da30081e3032bdb08d18e26950ebc14714bc98e3c71c612f 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 Core (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
G2+386Q8y/Mn8fhu6h/4gsKkX63zE9oSImkAkOn2W+c1aZh/y0Lhi/uSP5yjv3atdzvbFSbrTXY36YKR+r8czAM=
-----END BITCOIN SIGNATURE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.18
Changes:
Upgrade to bitcoinj 0.11.2. This is mainly bug fixes.
Update of localisation and checkpoints files.
#540: Removal of import of blockchain.info wallet export files
#540: New utility "Tool | Check Private Keys"
#533, #534: Fix for cannot send 1000BTC or more (fix by Telepatheic)
#530: Fix for test timezone error (fix by allada)
#529: Fix for padding bytes in private key export files (fix by Andreas Schildbach)
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.18.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:
a067c9638edfdf39f3e9fa154b0c6d8cfb7c58c0edd95a02c0ca903160ca3aad multibit-0.5.18-linux.jar
76ce043b26fc7d18fcbc3d17583b2fdec0dcd3023f5e7e7c03f1a8dde6b3f663 multibit-0.5.18-linux.jar.asc
dc0c2ef689507c57347c0cbed58ea90fe12617a6fb026b308e81ec2127531b7e multibit-0.5.18-windows-setup.exe
b8812322e670a1a46fc06d01109f7ca7479c0e8655bc167a18c59878023dbeb5 multibit-0.5.18-windows-setup.exe.asc
0d2fe6fa68385c1ca964d9588272787dabffbc2061f29ebaab422317d0972257 multibit-0.5.18.dmg
0f1d5c880fa7f10930e34773374fb6f97f01ea2ae38cb32302b7efc4887baa2b multibit-0.5.18.dmg.asc
55dd9b0bf5ed45b2ad064f444fe99373b2601e1404bb1da44b59ff4bd343f968 multibit-exe.jar
e9fdd68d266745334e4ce184f227ca1e316e21293e359b16196708f56ad137d3 multibit-exe.jar.asc
ae1950d2a74e9b91059467de1f0255cfbf3c3002cb02902971b27900b7a941f6 multibit.exe
644390e4a3cebef3da30081e3032bdb08d18e26950ebc14714bc98e3c71c612f 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 Core (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
G2+386Q8y/Mn8fhu6h/4gsKkX63zE9oSImkAkOn2W+c1aZh/y0Lhi/uSP5yjv3atdzvbFSbrTXY36YKR+r8czAM=
-----END BITCOIN SIGNATURE-----
You can upgrade by simply installing the new version using the installers from https://multibit.org
It will automatically pick up your old wallets and settings.
thanks for reply It will automatically pick up your old wallets and settings.
You can upgrade by simply installing the new version using the installers from https://multibit.org
It will automatically pick up your old wallets and settings.
It will automatically pick up your old wallets and settings.
please how to upgrade from Version 0.5.16 to Version 0.5.17
Great! Wish this version will be without any bugs and it actually seems to be a breakthrough in altcoin's wallets
-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.17
Changes:
+ upgrade to bitcoinj 0.11.1
+ removal of "one satoshi" spam transactions
+ removal of MtGox exchange, default is now Bitstamp/ USD
+ update of localisation and checkpoints files
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.17.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:
e6ec9b243aa57c822ebe016b7ca82d5206a1151ddb1b7c8e8119f73deb15ea42 multibit-0.5.17-linux.jar
3d20da936a5baf7e7ff32ff38f554bca1475e508390037653d4f8885363e351c multibit-0.5.17-linux.jar.asc
90506bf43a64986ce8219ca0fb18a5e1f0776cfeb31043ca848cea7f71eda45d multibit-0.5.17-windows-setup.exe
bcd489a3cf9130dd7f346f4caaa2d8a8f08558f7b0dc8408b31e491b74c3cfdb multibit-0.5.17-windows-setup.exe.asc
1facdaacaec20c24777c26e05f2655a727c7ea92f0cfe84bb1fbdfcb65ae893c multibit-0.5.17.dmg
fc59d716bc777ea2c12ab27c2081673ae13f0d197756f04635a48433601d88a2 multibit-0.5.17.dmg.asc
3bdb779bf053000ab1f537739f4b823b9d345f2e898fc3373d39a964b6e61ef3 multibit-exe.jar
e6d76247ea5c9f0317a21c6fd26fd38e9d9b95473f169aaaf5990cedbdaa4da6 multibit-exe.jar.asc
74738b9a40e5de3e3ce54992b9f41b8ae533a37585498d172d61db51911172ce multibit.exe
1163618127ec4a94690d8ab696520fd7b622d01aed8d39b8b75217946ef856cd 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
G5cOxE7yu1tOfbUkMjQcXduJp3OqXw2gI2ugquGjIf8KJkfyY5ApG+FB4l7Bf/zCaKcH6KXsbPmcy1s/DTYz35g=
-----END BITCOIN SIGNATURE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.17
Changes:
+ upgrade to bitcoinj 0.11.1
+ removal of "one satoshi" spam transactions
+ removal of MtGox exchange, default is now Bitstamp/ USD
+ update of localisation and checkpoints files
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.17.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:
e6ec9b243aa57c822ebe016b7ca82d5206a1151ddb1b7c8e8119f73deb15ea42 multibit-0.5.17-linux.jar
3d20da936a5baf7e7ff32ff38f554bca1475e508390037653d4f8885363e351c multibit-0.5.17-linux.jar.asc
90506bf43a64986ce8219ca0fb18a5e1f0776cfeb31043ca848cea7f71eda45d multibit-0.5.17-windows-setup.exe
bcd489a3cf9130dd7f346f4caaa2d8a8f08558f7b0dc8408b31e491b74c3cfdb multibit-0.5.17-windows-setup.exe.asc
1facdaacaec20c24777c26e05f2655a727c7ea92f0cfe84bb1fbdfcb65ae893c multibit-0.5.17.dmg
fc59d716bc777ea2c12ab27c2081673ae13f0d197756f04635a48433601d88a2 multibit-0.5.17.dmg.asc
3bdb779bf053000ab1f537739f4b823b9d345f2e898fc3373d39a964b6e61ef3 multibit-exe.jar
e6d76247ea5c9f0317a21c6fd26fd38e9d9b95473f169aaaf5990cedbdaa4da6 multibit-exe.jar.asc
74738b9a40e5de3e3ce54992b9f41b8ae533a37585498d172d61db51911172ce multibit.exe
1163618127ec4a94690d8ab696520fd7b622d01aed8d39b8b75217946ef856cd 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
G5cOxE7yu1tOfbUkMjQcXduJp3OqXw2gI2ugquGjIf8KJkfyY5ApG+FB4l7Bf/zCaKcH6KXsbPmcy1s/DTYz35g=
-----END BITCOIN SIGNATURE-----
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.
So this is true but you can try just one time if this check is not passable you can do noting - key is already imported so I don't know how program work and if I import again the same private key with different date if program will start to reset blokchain again from this date - and you know some time you have to 3-4 time reset blockchain for satisfactory result .It only has to be before the date of the first transaction, which you could look up from a block explorer.
So for another think you right but you can keep minimum thinks for advanced users like import and export private keys.
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.
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.
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. 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.
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.
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.
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.
-----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-----
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.
-----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-----
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-----
-----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-----
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-----
-----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-----
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-----
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.
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.
Ok, it was user error. For the signature I pasted this:
which didn't work. But, this works for the signature and it verifies:
In the relase notes it says this:
Thx.
Quote
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
which didn't work. But, this works for the signature and it verifies:
Quote
HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
In the relase notes it says this:
Quote
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
-----END BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
HFtPFVkjPBWmDj1Btw/xQ+wlML+NBTunvXURBBOaNvxrSjHFMQGNxB6frFTmW8qQhBOBxuQqEOkazt18KfmyRpE=
-----END BITCOIN SIGNATURE-----
Thx.
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.
I have the private key for the multibit.org one and that is the address I used to sign it.
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.
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?
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.
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.
Jump to: