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 10988 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.
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.
Well investigated !
I'll make sure I do not put any trailing spaces in the release.txt in future.
I'll make sure I do not put any trailing spaces in the release.txt in future.
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.
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.
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.
create auto-installation script? what is it?...advanced use only I suppose for future releases im guessing
FYI: When I copy the release information from Firefox into MultiBit the signature cannot be verified (on MacOS). Could be due to line breaking?!
-----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-----
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-----
I just checked on blockchain.info.
As I type there are about 2500 transactions 'hanging around' unconfirmed.
The miners seem to cap their blocks at just under 250KB, clearing about 500 transactions each block.
Network is busy, transactions stack up, miners are not clearing them by putting them in blocks
As I type there are about 2500 transactions 'hanging around' unconfirmed.
The miners seem to cap their blocks at just under 250KB, clearing about 500 transactions each block.
Network is busy, transactions stack up, miners are not clearing them by putting them in blocks
Hi gotpetum,
The blockchain.info estimates can be a bit larger than things actually take.
Would be interested to see how much time/ how many blocks your tx actually takes for its first confirmation.
The blockchain.info estimates can be a bit larger than things actually take.
Would be interested to see how much time/ how many blocks your tx actually takes for its first confirmation.
@Chooseusername
I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
To make my transactions being processed fast in cause of %whatever_happened%, for example. And because it's my money and I want to control it by myself, not by algorythm. And at last because I can. So, I'll stick with 0.5.11, I guess. It's your program of course, and you choose how to develop it, but why make slider, why not just field pre-filled with automatically calculated fee which I can change? Why you disable me to change fees? I'm not a new user, I can worry about fees by myself.I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
I appreciate what you are saying but it is just more complicated than that.
Say you increase the calculated fee. That needs paying for so you may need to bring in another tx input to spend. So now the tx is bigger. Maybe it needs MORE fee because it has slipped over a 1000 byte limit. So you try adding MORE tx inputs. But if you only have dust remaining in your wallet you can be worse off in that the tx inputs you just added are worth less than the extra fee you need to pay for adding them. You had a good tx with the smaller fee but cannot find a tx providing the increased fee.
Or maybe the new change amount you've created is under the new limit for small tx outputs - 5430 is it or is it 5340 satoshi ? Best write it down as you'll need to manually check that after you made the change to your fee - that small amount should get added to your fee to eliminate the small output. So you've eliminated a tx output so now the tx is smaller. So now you can possibly have a smaller fee to get the same effect as you had before you changed the fee. Do you want the option to rechange the fee a second time ?
Honestly have a look at the code I pointed to about calculating a fee.
Of course it is your bitcoin but it is now impractical to work out the right fee manually.
A 'bad' fee means your tx either cannot be constructed (immediate fail), does not propagate (obviously bad but worse because then any change won't be spendable - very unpopular) or your tx takes ages to confirm (equally unpopular).
Sticking on 0.5.11 means you may create tx that don't propagate or take ages to confirm. It is your choice of course but my aim is to get people's transactions out in the network, propagated and confirmed as painlessly as possible for everyone.
Thanks for working on principled solutions that will elegantly handle the edge cases, jim618 :-)
In the meanwhile...
Fees 0.0001 BTC
Estimated BTC Transacted 0.781 BTC
Estimated Confirmation Time 12 hours (queue position 3002)
:-P
Hi Chooseusername, HostFat,
No problem at all - I thought I would reply in detail as the technical details aren't at all obvious. Fees have become a little complicated and I expect they will change again in the future.
Bitcoin is an experiment after all !
I think you are right that there is still something missing though in that the user DOES want to change the fee sometimes according to the priority of the transaction. Simply having a computed value and not being able to change it does not feel right.
For instance if I am moving money around my own wallets/ amoungst friends it does not matter if it takes a little longer. But if I am in a coffee shop sending money to someone (eg localbitcoins) then I would probably increase the fees paid so that it will (almost certainly) get in the next block as we both save time. Or the payment might be important/ urgent for some other reason.
One of the parameters in the feesolver is "fee per kilobyte of transaction" so that seems like a good candidate for tweaking. It is hardwired at 0.001 BTC / KB at the moment but it might be worth making this something the user can set in the Preferences. Of course it is a little more work but that might be the way to go.
That way users still have control over what they want to set (tx urgency/ priority) but don't have to worry about all the fee rules.
No problem at all - I thought I would reply in detail as the technical details aren't at all obvious. Fees have become a little complicated and I expect they will change again in the future.
Bitcoin is an experiment after all !
I think you are right that there is still something missing though in that the user DOES want to change the fee sometimes according to the priority of the transaction. Simply having a computed value and not being able to change it does not feel right.
For instance if I am moving money around my own wallets/ amoungst friends it does not matter if it takes a little longer. But if I am in a coffee shop sending money to someone (eg localbitcoins) then I would probably increase the fees paid so that it will (almost certainly) get in the next block as we both save time. Or the payment might be important/ urgent for some other reason.
One of the parameters in the feesolver is "fee per kilobyte of transaction" so that seems like a good candidate for tweaking. It is hardwired at 0.001 BTC / KB at the moment but it might be worth making this something the user can set in the Preferences. Of course it is a little more work but that might be the way to go.
That way users still have control over what they want to set (tx urgency/ priority) but don't have to worry about all the fee rules.
Of course it is your bitcoin but it is now impractical to work out the right fee manually.
Sticking on 0.5.11 means you may create tx that don't propagate or take ages to confirm. It is your choice of course but my aim is to get people's transactions out in the network, propagated and confirmed as painlessly as possible for everyone.
Sticking on 0.5.11 means you may create tx that don't propagate or take ages to confirm. It is your choice of course but my aim is to get people's transactions out in the network, propagated and confirmed as painlessly as possible for everyone.
Well, you're right. I'm sorry for my ignorance and thank you for detailed explanation.
@Chooseusername
I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
To make my transactions being processed fast in cause of %whatever_happened%, for example. And because it's my money and I want to control it by myself, not by algorythm. And at last because I can. So, I'll stick with 0.5.11, I guess. It's your program of course, and you choose how to develop it, but why make slider, why not just field pre-filled with automatically calculated fee which I can change? Why you disable me to change fees? I'm not a new user, I can worry about fees by myself.I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
I appreciate what you are saying but it is just more complicated than that.
Say you increase the calculated fee. That needs paying for so you may need to bring in another tx input to spend. So now the tx is bigger. Maybe it needs MORE fee because it has slipped over a 1000 byte limit. So you try adding MORE tx inputs. But if you only have dust remaining in your wallet you can be worse off in that the tx inputs you just added are worth less than the extra fee you need to pay for adding them. You had a good tx with the smaller fee but cannot find a tx providing the increased fee.
Or maybe the new change amount you've created is under the new limit for small tx outputs - 5430 is it or is it 5340 satoshi ? Best write it down as you'll need to manually check that after you made the change to your fee - that small amount should get added to your fee to eliminate the small output. So you've eliminated a tx output so now the tx is smaller. So now you can possibly have a smaller fee to get the same effect as you had before you changed the fee. Do you want the option to rechange the fee a second time ?
Honestly have a look at the code I pointed to about calculating a fee.
Of course it is your bitcoin but it is now impractical to work out the right fee manually.
A 'bad' fee means your tx either cannot be constructed (immediate fail), does not propagate (obviously bad but worse because then any change won't be spendable - very unpopular) or your tx takes ages to confirm (equally unpopular).
Sticking on 0.5.11 means you may create tx that don't propagate or take ages to confirm. It is your choice of course but my aim is to get people's transactions out in the network, propagated and confirmed as painlessly as possible for everyone.
why not just field pre-filled with automatically calculated fee which I can change?
I agree with this.You can even add an advanced option to enable this possibility if you want, but I think that it's really needed.
I also want to be able to chose/change the fee.
@Chooseusername
I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
To make my transactions being processed fast in cause of %whatever_happened%, for example. And because it's my money and I want to control it by myself, not by algorythm. And at last because I can. So, I'll stick with 0.5.11, I guess. It's your program of course, and you choose how to develop it, but why make slider, why not just field pre-filled with automatically calculated fee which I can change? Why you disable me to change fees? I'm not a new user, I can worry about fees by myself. I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
Yes it's time to find the miners who are still doing that and ask them to reconsider.
Hi Mike,
I think what's happening is:
1) Currently the 'general' fee for a < 1KB tx in BitcoinLand is 0.0005 BTC. This is my estimate from having a look at the tx in the live stream on the blockchain.info home page.
2) MultiBit 0.5.12, Andreas's Wallet v3.0.9 and Bitcoin-QT 0.8.2/3 have moved to lower fees of 0.0001 BTC for the first KB.
3) Generally tx seem to get 'serviced' in order of creation but when there is a big gap between blocks the unconfirmed tx start piling up.
4) Miners seem to be using a soft limit of 250 KB so they naturally put in the juiciest tx into their block. They clear about 600 of the tx from the unconfirmed pool for each block.
If the next block also takes an above average time to solve then the low-fee-tx can continue to get bumped by juicier tx that appear.
I have suggested to the other alt client devs that they have a *great* opportunity to save their users cash and drop their calculated fees to match the Bitcoin-QT fees. It is a bit of a Prisoner's Dilemma - I think Electrum tried to drop their fees to 0.0001 BTC / KB about a month ago but had to increase them again as no-one else did.
I think if/once most clients match the Bitcoin-QT fee structures the current soft limit on blocks will be sufficient - I think the miners are processing same-fee tx by age first (which effectively makes it first-transmitted-first-served).
It's a pretty interesting dynamic system the whole area of fees I must admit.
I think what's happening is:
1) Currently the 'general' fee for a < 1KB tx in BitcoinLand is 0.0005 BTC. This is my estimate from having a look at the tx in the live stream on the blockchain.info home page.
2) MultiBit 0.5.12, Andreas's Wallet v3.0.9 and Bitcoin-QT 0.8.2/3 have moved to lower fees of 0.0001 BTC for the first KB.
3) Generally tx seem to get 'serviced' in order of creation but when there is a big gap between blocks the unconfirmed tx start piling up.
4) Miners seem to be using a soft limit of 250 KB so they naturally put in the juiciest tx into their block. They clear about 600 of the tx from the unconfirmed pool for each block.
If the next block also takes an above average time to solve then the low-fee-tx can continue to get bumped by juicier tx that appear.
I have suggested to the other alt client devs that they have a *great* opportunity to save their users cash and drop their calculated fees to match the Bitcoin-QT fees. It is a bit of a Prisoner's Dilemma - I think Electrum tried to drop their fees to 0.0001 BTC / KB about a month ago but had to increase them again as no-one else did.
I think if/once most clients match the Bitcoin-QT fee structures the current soft limit on blocks will be sufficient - I think the miners are processing same-fee tx by age first (which effectively makes it first-transmitted-first-served).
It's a pretty interesting dynamic system the whole area of fees I must admit.
If people's transactions are getting bumped we should ask miners to increase their soft block size limits again.
@Chooseusername
I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
I am interested in why exactly you want to set a specific fee. Is the calculated one causing you problems ?
At the moment you cannot tweak the calculated fees.
They are calculated as pretty much the minimum bitcoin-QT will accept.
Currently, as other software has not adjusted their fees downwards, when the network is busy you can get bumped to later blocks as the fee is a bit on the low side. I'm going to see how this develops - the fees people set create a feedback loop as to which transactions get in which block. (If you have a look at some of the posts I have put in the other alt clients threads this is explained more).
It might be necessary to add in something like a slider so that you can increase the fees above the minimum but I am hoping not to have to do that. Fees aren't something that a new user should have to worry about as it just adds to the learning curve for Bitcoin.
Edit: Also, to get the 'correct' fee is quite involved - have a look at the class FeeCalculation in this class:
http://code.google.com/r/jimburton618-bitcoinj-coinbase-tx/source/browse/core/src/main/java/com/google/bitcoin/core/Wallet.java?name=bcj-master-mb-alice
(starts line 2982).
They are calculated as pretty much the minimum bitcoin-QT will accept.
Currently, as other software has not adjusted their fees downwards, when the network is busy you can get bumped to later blocks as the fee is a bit on the low side. I'm going to see how this develops - the fees people set create a feedback loop as to which transactions get in which block. (If you have a look at some of the posts I have put in the other alt clients threads this is explained more).
It might be necessary to add in something like a slider so that you can increase the fees above the minimum but I am hoping not to have to do that. Fees aren't something that a new user should have to worry about as it just adds to the learning curve for Bitcoin.
Edit: Also, to get the 'correct' fee is quite involved - have a look at the class FeeCalculation in this class:
http://code.google.com/r/jimburton618-bitcoinj-coinbase-tx/source/browse/core/src/main/java/com/google/bitcoin/core/Wallet.java?name=bcj-master-mb-alice
(starts line 2982).
+ Fees are now calculated automatically. Code by Matt Corallo
So, where do I turn off this "feature"? If I want to set it manually?
-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.12
Changes
+ Updated to bitcoinj v0.9
+ Fees are now calculated automatically. Code by Matt Corallo
+ The size of the transaction appears on the transactions detail dialog
+ Fixed issues 150, 165 - Automatically recreates BlockStore if there are problems loading it
+ Fixed issue 155 - Version.txt retrieval error on Java 7
+ Fixed issue 156 - Verify message available when wallet is syncing
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.12.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:
8ceefa0edafbf297c9276b6cb893e808a36646e915b5c671ab884ac5c431f83e multibit-0.5.12-linux.jar
38347714a510a07f47b81d218da63ea83aebb6de4eb36952ae90e970b25c7480 multibit-0.5.12-linux.jar.asc
248e13824a422266ebf6f13252863aaac3db4658cda120d091468fd493817a62 multibit-0.5.12-windows.exe
290504e880984a93cf91d5b944fe0527f039b744e9a0ae9ffff23a12531d81da multibit-0.5.12-windows.exe.asc
947f73aa519a14f5bebda1f94a9c51c57bf5713a61f706def8cd4f8c189eddd8 multibit-0.5.12.dmg
4e5d0be0ad4e91a0f7ee716cdd312de861ad5de153a09671f4c1eefb60175766 multibit-0.5.12.dmg.asc
f8e1523023a54a7af390138373991de305844bb339c036439f9055d0ef23db26 multibit-exe.jar
ee6f5125d1faf7fa939b91d991eb0001de515b6b3fa6bcd2370411122d633fbe multibit-exe.jar.asc
b2a953ba49dcae2f6f9a731663e3e81b6276956a701176ea5c8f8a862d7f9291 multibit.exe
10cced6434441462ac8388d9071a92fec2c95653ac821b22a7658b4528b1cab9 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
GyNn9yWgY0s5BKZLu3PxRtt9BaGL0ATVHVAQKlEo0fd9c/7jKzqTwCu3k/y/JagsLOT5T+XuAhtn6W+acrM5yq4=
-----END BITCOIN SIGNATURE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.12
Changes
+ Updated to bitcoinj v0.9
+ Fees are now calculated automatically. Code by Matt Corallo
+ The size of the transaction appears on the transactions detail dialog
+ Fixed issues 150, 165 - Automatically recreates BlockStore if there are problems loading it
+ Fixed issue 155 - Version.txt retrieval error on Java 7
+ Fixed issue 156 - Verify message available when wallet is syncing
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.12.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:
8ceefa0edafbf297c9276b6cb893e808a36646e915b5c671ab884ac5c431f83e multibit-0.5.12-linux.jar
38347714a510a07f47b81d218da63ea83aebb6de4eb36952ae90e970b25c7480 multibit-0.5.12-linux.jar.asc
248e13824a422266ebf6f13252863aaac3db4658cda120d091468fd493817a62 multibit-0.5.12-windows.exe
290504e880984a93cf91d5b944fe0527f039b744e9a0ae9ffff23a12531d81da multibit-0.5.12-windows.exe.asc
947f73aa519a14f5bebda1f94a9c51c57bf5713a61f706def8cd4f8c189eddd8 multibit-0.5.12.dmg
4e5d0be0ad4e91a0f7ee716cdd312de861ad5de153a09671f4c1eefb60175766 multibit-0.5.12.dmg.asc
f8e1523023a54a7af390138373991de305844bb339c036439f9055d0ef23db26 multibit-exe.jar
ee6f5125d1faf7fa939b91d991eb0001de515b6b3fa6bcd2370411122d633fbe multibit-exe.jar.asc
b2a953ba49dcae2f6f9a731663e3e81b6276956a701176ea5c8f8a862d7f9291 multibit.exe
10cced6434441462ac8388d9071a92fec2c95653ac821b22a7658b4528b1cab9 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
GyNn9yWgY0s5BKZLu3PxRtt9BaGL0ATVHVAQKlEo0fd9c/7jKzqTwCu3k/y/JagsLOT5T+XuAhtn6W+acrM5yq4=
-----END BITCOIN SIGNATURE-----
-----BEGIN BITCOIN SIGNED MESSAGE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.11
Changes
+ Implemented issue 96 - Sign and Verify message.
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.11.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:
a6bcffea1fc04d5ccbd8d240854d62d7ae425802010bdbd3ed9335907246a922 multibit-0.5.11-linux.jar
111096d1db1952d623512a970057aa28f3951769c627fb49c2d29b6b263e60bb multibit-0.5.11-linux.jar.asc
90a11dfe000311b6e3051c00b31befdc48dc75415254df4ab45f0fc464b3cd23 multibit-0.5.11-windows.exe
20088187c694feb9ed12aab20fa3019852e6a32bdcbf8d393c291bdb2697d9aa multibit-0.5.11-windows.exe.asc
8446d10a78642f1fe2dc3db97f931eb2f2adc0235798a323ecd6f0e007c63746 multibit-0.5.11.dmg
b4f0d30c2e7f9a16d099f528c8c5a643ba793e2054def09908a38531a0f3af69 multibit-0.5.11.dmg.asc
b335678911efc743bf8e1149fd54a5c8bfc2a9105d6c06f1e51df70f5112df7a multibit-exe.jar
f193ca928e9df520b55d1765ffb9743c5bdb9cc1501079895f321d5931ea8dea multibit-exe.jar.asc
bee1a14a97268455d41303bc09e51a097ad028a7cdd213e6a4072f4c6bd815ed multibit.exe
29d14ddb98337a52a63046ec0d3cb0574d43a8f0e9020ee00306910aafe5432a 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. To verify, say, multibit.exe type:
gpg --verify multibit.exe.asc
The files are signed with the subkey with id 0x23F7FB7B
Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
HCHgnCEBrhm9DoywH6qyRkiLcdkwlI388/uHZ2e2tDBwu5HkrMFrCAoXN+FU4FvOueAxM/XYGoaDvYVeI/0tXkw=
-----END BITCOIN SIGNATURE-----
There is a new release of MultiBit at:
https://multibit.org
Version 0.5.11
Changes
+ Implemented issue 96 - Sign and Verify message.
Release checklist:
https://multibit.org/test/releaseCheckList-0.5.11.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:
a6bcffea1fc04d5ccbd8d240854d62d7ae425802010bdbd3ed9335907246a922 multibit-0.5.11-linux.jar
111096d1db1952d623512a970057aa28f3951769c627fb49c2d29b6b263e60bb multibit-0.5.11-linux.jar.asc
90a11dfe000311b6e3051c00b31befdc48dc75415254df4ab45f0fc464b3cd23 multibit-0.5.11-windows.exe
20088187c694feb9ed12aab20fa3019852e6a32bdcbf8d393c291bdb2697d9aa multibit-0.5.11-windows.exe.asc
8446d10a78642f1fe2dc3db97f931eb2f2adc0235798a323ecd6f0e007c63746 multibit-0.5.11.dmg
b4f0d30c2e7f9a16d099f528c8c5a643ba793e2054def09908a38531a0f3af69 multibit-0.5.11.dmg.asc
b335678911efc743bf8e1149fd54a5c8bfc2a9105d6c06f1e51df70f5112df7a multibit-exe.jar
f193ca928e9df520b55d1765ffb9743c5bdb9cc1501079895f321d5931ea8dea multibit-exe.jar.asc
bee1a14a97268455d41303bc09e51a097ad028a7cdd213e6a4072f4c6bd815ed multibit.exe
29d14ddb98337a52a63046ec0d3cb0574d43a8f0e9020ee00306910aafe5432a 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. To verify, say, multibit.exe type:
gpg --verify multibit.exe.asc
The files are signed with the subkey with id 0x23F7FB7B
Jim
-----BEGIN BITCOIN SIGNATURE-----
Version: Bitcoin-qt (1.0)
Address: 1AhN6rPdrMuKBGFDKR1k9A8SCLYaNgXhty
HCHgnCEBrhm9DoywH6qyRkiLcdkwlI388/uHZ2e2tDBwu5HkrMFrCAoXN+FU4FvOueAxM/XYGoaDvYVeI/0tXkw=
-----END BITCOIN SIGNATURE-----
Hi Cameron,
I have pushed the MultiBit master branch but noticed I made a slight mistake in build procedure.
I built the 0.5.10 artifacts whilst on the release-0.5.10 branch, not master.
You probably want to checkout that branch and see if you can reproduce the artifacts.
Jim
I have pushed the MultiBit master branch but noticed I made a slight mistake in build procedure.
I built the 0.5.10 artifacts whilst on the release-0.5.10 branch, not master.
You probably want to checkout that branch and see if you can reproduce the artifacts.
Jim
Since this release contains code that I have written.
I have done only casual checking, other than verifying Jim's pgp signatures for the files.
Code:
SHA256(multibit-0.5.10-linux.jar)= 4b9593444abe96c8e777bddc85227b26685c2fb6dd3ce7a6db856d61a78e059a
SHA256(multibit-0.5.10-windows.exe)= 15817c0b10cd60e39dcc8aee31db0b03b5a2aafd8337578e3f381bad5c0e4937
SHA256(multibit-0.5.10.dmg)= 133b504295be167ce41476cb2d6c21b219fbe786fa97d08ce2c6e5dee30bafbe
SHA256(multibit-exe.jar)= ce4c8248fda31a466c5c7af23537f324ee162fef63328cc79a0a08bfefc9f91e
SHA256(multibit.exe)= 5123099005ebb9bfbd5329a9867cf3da1e498eea50fb341e60e6f4d5ac8cc2fd
Code:
-----BEGIN PGP MESSAGE-----
Version: GnuPG v2.0.19 (MingW32)
owF1kT1olEEQhr+YKPFEML1F7ExxH7s7+4sIKgi2Yi/M7MyG83IRTUIOFa4RVLAQ
bBXxBwRRtLlaLBRRwUIIaGflKdhbCHEDsQppZ+B5Zt73zsHpZnZu5sFhBeMfG1Mf
38xTc/bJs1Pnzpw0zh8drC2t9qi32lWta7XqLvWW14btBby8cHzeUnIJrLVIknyO
EkIg5hydMYGM99FlU8gzQ5aAnik6z15jiKJcws4ujvXeMl9cX2llKNWiXdQhK9Iq
s1cCiXOOKAKaSZECcmgQC0eA4CoZCkRNyC4rsQnCLpaWB4tbdKgAZU1yJNqHLFbb
4DMZ9tloMjoVkhB9wRRYxSwme3Fc9YqwrnbQ69Hb8VRWjsbGwggarffZ5YDFgINQ
wFipQlOkeAATcw4JFapIdZJTSXoHejsPpw2olJRyQpSoEDswCVOs1xdg1PXrKIJO
FQKrpWbmi2WHuUpM4c7N8zPN3Gyzb++erZ6bzv5D/9t/1Z9qnh84vXL7yKfR5F7/
xte/7eTX+OXjp+9fbCyO375W10/cbzb7I79wN936M3x0dfPb75/Hrj280v3wzo+m
B4PJl0vfP/8D
=dIYL
-----END PGP MESSAGE-----
Edit: Jim, can you please push your master branch, I would like to see if it is possible for me to create identical builds.
There is a new live MultiBit release at:
https://multibit.org
Version 0.5.10
Changes:
+ Fixed issue 116 - could not import blockchain.info backups.
+ Fixed issue 117 - fee was too high.
+ Fixed issue 121 - MtGox ticker information not showing.
+ Fixed issue 125 - improved overzealous syncing of wallet(s).
+ Fixed issue 137 - Import / Export filechooser nomenclature.
+ Fixed issue 140 - use installed checkpoints file if newer.
+ Fixed issue 141 - bump to XChange 1.7.0, XChart 2.2.0.
Release checklist
This is primarily a bug fix release, together with updates of the XChange and XChart libraries.
https://multibit.org
Version 0.5.10
Changes:
+ Fixed issue 116 - could not import blockchain.info backups.
+ Fixed issue 117 - fee was too high.
+ Fixed issue 121 - MtGox ticker information not showing.
+ Fixed issue 125 - improved overzealous syncing of wallet(s).
+ Fixed issue 137 - Import / Export filechooser nomenclature.
+ Fixed issue 140 - use installed checkpoints file if newer.
+ Fixed issue 141 - bump to XChange 1.7.0, XChart 2.2.0.
Release checklist
This is primarily a bug fix release, together with updates of the XChange and XChart libraries.
There is a new live MultiBit release at:
https://multibit.org
Version 0.5.9 (Encrypted wallets release)
+ You can now password protect your wallets.
+ Version number removed from Mac app name.
+ Updated help files.
+ Fixed bug on opening wallet that is already open.
+ Fixed ticker restart bug.
Release checklist
https://multibit.org
Version 0.5.9 (Encrypted wallets release)
+ You can now password protect your wallets.
+ Version number removed from Mac app name.
+ Updated help files.
+ Fixed bug on opening wallet that is already open.
+ Fixed ticker restart bug.
Release checklist
The encrypted wallets release candidate is now available at:
https://multibit.org/releases/multibit-0.5.9rc1/
Version 0.5.9rc1
Features:
+ Upgrade to bitcoinj v0.8
+ Delete Wallet not shown by default, challenge question added (see configuration.txt).
+ Romanian added as target language.
+ Mac app is now signed with a "James Burton" developer id.
+ Fix for Mac retina display showing fuzzy text.
+ Twisty and callout panel in the wallet panels have been removed.
Release checklist
This is the MultiBit release candidate for the encrypted wallets.
Please try it out.
I plan to keep it on the website for a week and see what feedback/ bug reports I get.
If people generally give it the thumbs up then I will release it as live code for the general user.
Whilst people are testing it I will be tidying up the help and unit tests. Gary and I are also working on a multibit.org website re-vamp.
I have also bought an 'identity verified' certificate to sign the Windows exe. There will be a delay in getting this as it involves bits of paper with authorisation codes being transported across Europe. The version 0.5.9 will probably get released without this.
https://multibit.org/releases/multibit-0.5.9rc1/
Version 0.5.9rc1
Features:
+ Upgrade to bitcoinj v0.8
+ Delete Wallet not shown by default, challenge question added (see configuration.txt).
+ Romanian added as target language.
+ Mac app is now signed with a "James Burton" developer id.
+ Fix for Mac retina display showing fuzzy text.
+ Twisty and callout panel in the wallet panels have been removed.
Release checklist
This is the MultiBit release candidate for the encrypted wallets.
Please try it out.
I plan to keep it on the website for a week and see what feedback/ bug reports I get.
If people generally give it the thumbs up then I will release it as live code for the general user.
Whilst people are testing it I will be tidying up the help and unit tests. Gary and I are also working on a multibit.org website re-vamp.
I have also bought an 'identity verified' certificate to sign the Windows exe. There will be a delay in getting this as it involves bits of paper with authorisation codes being transported across Europe. The version 0.5.9 will probably get released without this.
There is a new test MultiBit release at:
https://multibit.org/releases
Version 0.5.9-SNAPSHOT
Features:
+ I18n update.
+ Update to bitcoinj 0.8-SNAPSHOT
+ added 'Close Wallet'
+ wallets now resync automatically when opened
+ added better sync control on import and reset blockchain
+ changed blockstore to SPVBlockStore - smaller download
+ uses checkpoints file (12K) rather than block headers file (about 20MB).
+ changed 'Reset blockchain and transactions' suggested replay date to 2 days ago.
+ reduced default fee to 0.0005 BTC
Bug fixes:
+ fix for unparseable fee amount
+ apostrophes now appear in French and Italian translations properly
Release checklist
This (after an official bitcoinj v0.8 release, more testing, a release candidate, more testing and then another release) will become the first live release with encrypted wallets in it.
https://multibit.org/releases
Version 0.5.9-SNAPSHOT
Features:
+ I18n update.
+ Update to bitcoinj 0.8-SNAPSHOT
+ added 'Close Wallet'
+ wallets now resync automatically when opened
+ added better sync control on import and reset blockchain
+ changed blockstore to SPVBlockStore - smaller download
+ uses checkpoints file (12K) rather than block headers file (about 20MB).
+ changed 'Reset blockchain and transactions' suggested replay date to 2 days ago.
+ reduced default fee to 0.0005 BTC
Bug fixes:
+ fix for unparseable fee amount
+ apostrophes now appear in French and Italian translations properly
Release checklist
This (after an official bitcoinj v0.8 release, more testing, a release candidate, more testing and then another release) will become the first live release with encrypted wallets in it.
It's not really the "wrong" address, is it? I guess you mean you were expecting to see both addresses there instead of just the first. All the money did actually turn up.
I could argue that it is the wrong address because it's not the right address. 
But you are correct that I mean I was expecting to see both addresses listed, perhaps in two separate "transactions" in the UI. And the address that it showed as receiving the full amount was actually the second of my two addresses in the transaction. The 1EDvr address was output 309, while the 17Z63 address was output 195.It's good to see that it's only a UI issue, though.
It's not really the "wrong" address, is it? I guess you mean you were expecting to see both addresses there instead of just the first. All the money did actually turn up.
This is basically a MultiBit UI issue, it should probably try to show all matching addresses/labels, though that case is going to be rare for most transactions.
This is basically a MultiBit UI issue, it should probably try to show all matching addresses/labels, though that case is going to be rare for most transactions.
I'll test 0.4.23 sometime in the next few days (sorry, I'm kind of busy this week).
Here's a transaction that Multibit recorded:
12 Mar 2013 05:29
0.00098 BTC
Received with 1EDvr5PCtn5CikTBxqkEYg3A72K5vUAjHz
Transaction: 1f1e3ffe3a091bde54181f43aa24bf182444691f190edf4bde316b51361217ea
However, if you look at the details of that transaction on blockexplorer.com or blockchain.info, you'll see that only 0.0002 BTC was sent to that address. I have another address (17Z63hLi2ox4fCMhDqVJrLTJiXVcBMJpMo) that just happened to receive 0.00078 BTC in the same transaction. Both of these outputs add up to 0.00098 BTC. I suspect that Multibit is getting tripped up by the fact that both addresses are receiving money in the same Bitcoin transaction.
I don't really know what you mean by "a transaction got accounted to the wrong address". Could you be more specific?
Here's a transaction that Multibit recorded:
12 Mar 2013 05:29
0.00098 BTC
Received with 1EDvr5PCtn5CikTBxqkEYg3A72K5vUAjHz
Transaction: 1f1e3ffe3a091bde54181f43aa24bf182444691f190edf4bde316b51361217ea
However, if you look at the details of that transaction on blockexplorer.com or blockchain.info, you'll see that only 0.0002 BTC was sent to that address. I have another address (17Z63hLi2ox4fCMhDqVJrLTJiXVcBMJpMo) that just happened to receive 0.00078 BTC in the same transaction. Both of these outputs add up to 0.00098 BTC. I suspect that Multibit is getting tripped up by the fact that both addresses are receiving money in the same Bitcoin transaction.
Yes, exactly, it's not safe to do this yet because there are cases in which you might accidentally create double spends. As far as I know there are currently no clients that are guaranteed to do this right (except for the ones where the whole wallet is hosted by some remote server).
I don't really know what you mean by "a transaction got accounted to the wrong address". Could you be more specific?
I don't really know what you mean by "a transaction got accounted to the wrong address". Could you be more specific?
Can you see if you have problems with receiving transactions with the 0.4.23 code as there is a bug fix in for that ?
There are a few subtleties with sharing private keys.
For instance, currently the user is not prevented from sending transactions whilst the block chain is being synced. This only works in general if keys are not shared (as there could be transactions in later blocks from somewhere else that have spends in).
If sharing private keys is relatively common (which it probably is) then I will have to add in that you cannot do a spend until the blockchain is synced. With bloom filters that is not too much of a hindrance but is still a restriction.
On some of your other points:
+ yes there is a minimum fee by design to reduce the poor user experience of transactions with zero fees taking ages and ages to confirm.
+ if you have a transaction where bitcoin is sent to more than one of your addresses MultiBit might report that it is sent to one that you did not expect - the transaction is the same and the amount is the same. If you do a right click on the transaction and see the details you can see the raw transaction which explains it.
There are a few subtleties with sharing private keys.
For instance, currently the user is not prevented from sending transactions whilst the block chain is being synced. This only works in general if keys are not shared (as there could be transactions in later blocks from somewhere else that have spends in).
If sharing private keys is relatively common (which it probably is) then I will have to add in that you cannot do a spend until the blockchain is synced. With bloom filters that is not too much of a hindrance but is still a restriction.
On some of your other points:
+ yes there is a minimum fee by design to reduce the poor user experience of transactions with zero fees taking ages and ages to confirm.
+ if you have a transaction where bitcoin is sent to more than one of your addresses MultiBit might report that it is sent to one that you did not expect - the transaction is the same and the amount is the same. If you do a right click on the transaction and see the details you can see the raw transaction which explains it.
Is there a reason you're importing keys instead of just sending money between wallets using regular transactions? I mean, it should work, but sharing keys between different wallets opens up a variety of ways things can go wrong. It's really not meant to work that way.
So far I've only received money into all of the keys that I've imported, so there shouldn't be a problem. Multibit should record money coming in regardless of where the key was originally created, such as in Bitcoin-qt, with vanitygen, or with any other private key generator. Even sending money with one of those keys from another client shouldn't cause any issues, as any client worth its salt would record those transactions and deduct the amount from the respective wallet(s) correctly.I can understand that (apparent) issues might be caused by Bitcoin-qt's handling of hidden private keys (for returning change, for example), but that is not the case here as I have not made any transactions with any Bitcoin client with those keys. I've also verified transaction amounts on Blockexplorer and Blockchain to see how much has been sent to my addresses, and it simply mismatches what Multibit reported.
Besides, if sharing keys exposes bugs in the software, then it's a good way to shake out those bugs so they can be fixed.
Lastly, I want to share keys between clients because I want to have access to my Bitcoins on multiple computers--one at home and one at work. I'm also in the early stages of learning about Bitcoin and figuring out which clients are worth using by seeing how they handle transactions. Only Multibit has incorrectly accounted for received coins so far.
Is there a reason you're importing keys instead of just sending money between wallets using regular transactions? I mean, it should work, but sharing keys between different wallets opens up a variety of ways things can go wrong. It's really not meant to work that way.
Nice. I'll give Multibit another try. I played with it a week or so ago but a couple major bugs turned me off. I'll see if those bugs are still present in the latest version, and if they are I'll report them officially this time.
Here are the bugs I found in the older release and will be testing in a newer release:
- Importing a second private key into a wallet causes Multibit to hang
- Sometimes syncing hangs (probably due to first problem)
- One of my transactions got accounted to the wrong address
- Cannot set tx fee to less than (I believe) 0.0005
Here are the bugs I found in the older release and will be testing in a newer release:
- Importing a second private key into a wallet causes Multibit to hang
- Sometimes syncing hangs (probably due to first problem)
- One of my transactions got accounted to the wrong address
- Cannot set tx fee to less than (I believe) 0.0005
There is a new live MultiBit release at:
https://multibit.org
Version 0.4.23
+ Fix for incoming transactions not seen sometimes.
+ Updated to bitcoinj 0.7.3.
+ Notifies user when a new version of MultiBit is available.
+ Tidied up UI when switching "look and feels".
+ Change is now sent to the second key in a wallet if present (this helps people who have imported a blockchain.info backup).
+ More logging.
Release checklist
https://multibit.org
Version 0.4.23
+ Fix for incoming transactions not seen sometimes.
+ Updated to bitcoinj 0.7.3.
+ Notifies user when a new version of MultiBit is available.
+ Tidied up UI when switching "look and feels".
+ Change is now sent to the second key in a wallet if present (this helps people who have imported a blockchain.info backup).
+ More logging.
Release checklist
There is a new live MultiBit release at:
https://multibit.org
Version 0.4.22
Features:
+ Addition of OpenExchangeRates.org as an exchange. Provides over 150 currencies for currency conversion. (Needs free sign up).
+ Charts can be saved (right click on the chart: "Save as").
+ Updated to Bitcoinj 0.7.1, XChart 2.0.0, XChange 1.5.0.
+ Reset blockchain and transactions default "replay from" date now goes back 2 days.
+ Simplified buttons in wallet list.
Bug fixes:
+ Fixed appearance of blank request screen.
+ Menu tooltips on Macs shown properly.
Release checklist
The help for the OpenExchangeRates sign up is now available from your MultiBit "Help | Help Contents" menu option. It is the help page "Currency ticker" which shows:
https://multibit.org/help_ticker.html
https://multibit.org
Version 0.4.22
Features:
+ Addition of OpenExchangeRates.org as an exchange. Provides over 150 currencies for currency conversion. (Needs free sign up).
+ Charts can be saved (right click on the chart: "Save as").
+ Updated to Bitcoinj 0.7.1, XChart 2.0.0, XChange 1.5.0.
+ Reset blockchain and transactions default "replay from" date now goes back 2 days.
+ Simplified buttons in wallet list.
Bug fixes:
+ Fixed appearance of blank request screen.
+ Menu tooltips on Macs shown properly.
Release checklist
The help for the OpenExchangeRates sign up is now available from your MultiBit "Help | Help Contents" menu option. It is the help page "Currency ticker" which shows:
https://multibit.org/help_ticker.html
Yeah - it's a big improvement especially if you are on a slow network (the sheer size of the blocks was starting to slow my syncs down)
wow ,synchronising with network take only few second thx
There is a new live MultiBit release at:
https://multibit.org
Version 0.4.21
Features
+ Bloom filters now active to speed up blockchain sync (when talking to bitcoind v0.8 nodes)
+ You can now specify particular peers to connect to with the 'peers' property in multibit.properties. (Use a comma separated list).
+ Upgrade to bitcoinj v0.7 - numerous changes under the hood e.g. quicker network connect, sends between wallets you can spend immediately.
UI Changes
+ Currencies in the Preferences tab now have a full description in addition to the currency code
Release info
https://multibit.org/test/releaseCheckList-0.4.21.jpg
Bloom filter support
This is the release with the bloom filter support in. When you connect to a bitcoind v0.8 node you sync speeds should be a lot quicker.
At the moment there are just over 10% of the nodes upgraded. MultiBit connects to 4 peers so the chances of getting at least one v0.8 node is:
1 - (1 - 0.1)^4 = 34%
When it goes up to 15% of nodes your chance are 48% and at 20% of nodes it is 60%. That will probably take a week or two for that many nodes to update.
Thanks
Thanks to Mike Hearn and Matt Corralo who coded up the bloom filter work, and Andreas Schildbach for his detailed testing of the early versions.
https://multibit.org
Version 0.4.21
Features
+ Bloom filters now active to speed up blockchain sync (when talking to bitcoind v0.8 nodes)
+ You can now specify particular peers to connect to with the 'peers' property in multibit.properties. (Use a comma separated list).
+ Upgrade to bitcoinj v0.7 - numerous changes under the hood e.g. quicker network connect, sends between wallets you can spend immediately.
UI Changes
+ Currencies in the Preferences tab now have a full description in addition to the currency code
Release info
https://multibit.org/test/releaseCheckList-0.4.21.jpg
Bloom filter support
This is the release with the bloom filter support in. When you connect to a bitcoind v0.8 node you sync speeds should be a lot quicker.
At the moment there are just over 10% of the nodes upgraded. MultiBit connects to 4 peers so the chances of getting at least one v0.8 node is:
1 - (1 - 0.1)^4 = 34%
When it goes up to 15% of nodes your chance are 48% and at 20% of nodes it is 60%. That will probably take a week or two for that many nodes to update.
Thanks
Thanks to Mike Hearn and Matt Corralo who coded up the bloom filter work, and Andreas Schildbach for his detailed testing of the early versions.
Cheers Slush.
This means that if you put into your multibit.properties:
peers=riker.plan99.net,84.42.190.168
You will connect to BOTH bloom filter nodes - this has the advantage that your change is spendable straight away (the only problem with connecting to a single node).
This means that if you put into your multibit.properties:
peers=riker.plan99.net,84.42.190.168
You will connect to BOTH bloom filter nodes - this has the advantage that your change is spendable straight away (the only problem with connecting to a single node).
If you are running a bitcoind v0.8rc1 node on an external IP address and don't mind people connecting, please post your IP address here so that people can try out the bloom filters.
My node is 84.42.190.168
There is a new test release of MultiBit available at:
https://multibit.org/releases/multibit-0.5.8beta.spendpolicy/
Version 0.5.8beta.spendpolicy
This version is very similar to v0.5.8beta but has Mike Hearn's branch called 'spendpolicy' merged in.
This gives the same functionality as the 'boomerang rule' code where your change is spendable once it is seen by 2 or more peers. It is implemented in bitcoinj rather than the MultiBit code base and is implemented in a more general way.
From the MultiBit user's point of view the only difference is that when you spend from one wallet to another (of your own wallets) it is immediately spendable now. This code was a 'stretch goal' for inclusion into bitcoin-v0.7 so if it tests ok it should go in.
Release checklist
https://multibit.org/releases/multibit-0.5.8beta.spendpolicy/
Version 0.5.8beta.spendpolicy
This version is very similar to v0.5.8beta but has Mike Hearn's branch called 'spendpolicy' merged in.
This gives the same functionality as the 'boomerang rule' code where your change is spendable once it is seen by 2 or more peers. It is implemented in bitcoinj rather than the MultiBit code base and is implemented in a more general way.
From the MultiBit user's point of view the only difference is that when you spend from one wallet to another (of your own wallets) it is immediately spendable now. This code was a 'stretch goal' for inclusion into bitcoin-v0.7 so if it tests ok it should go in.
Release checklist
There is a new test MultiBit release at:
https://multibit.org/releases/multibit-0.5.8beta
Version 0.5.8beta
Bitcoinj v0.7 features:
+ Bloom filters now active to speed up blockchain sync (when talking to bitcoind v0.8rc1 nodes or later).
+ You can now specify particular peers to connect to with the 'peers' property in multibit.properties. (Use a comma separated list).
+ Fix for zero confirmation transaction vulnerability identified by Retep.
XChange 1.4.0 features:
+ More exchanges supported for currency lookup: MtGox, Bitstamp, BTC-E, CampBX, VirtEx.
UI enhancements:
+ You can use Shift-ArrowUp and Shift-ArrowDown to move between wallets when the Wallets panel is selected.
+ Wallet icon now highlighted when wallet is selected, more contrast between selected and unselected.
+ Display less flicky when changing languages, fonts and look-and-feel.
+ User chosen font now set properly in dialogs and Help screens.
General:
+ No longer opens in 'local mode' - it picks up your other MultiBit wallets.
+ Removed cacheManager code - no longer supported
+ Backward compatible wallet changes (description added, minor version dropped).
+ Serialised wallets now no longer always load - you may have to use an older version of MultiBit and migrate them to protobuf format.
+ Refactoring of encryption code in response to review comments.
+ Fix for 'Transaction cannot be cast to Comparable' bug on wallet reorgs.
Release checklist
To get the benefit of bloom filters you currently need to connect to a bitcoind v0.8rc1 node.
There is one at riker.plan99.net (courtesy of Mike Hearn).
If you are running a bitcoind v0.8rc1 node on an external IP address and don't mind people connecting, please post your IP address here so that people can try out the bloom filters. Thanks.
https://multibit.org/releases/multibit-0.5.8beta
Version 0.5.8beta
Bitcoinj v0.7 features:
+ Bloom filters now active to speed up blockchain sync (when talking to bitcoind v0.8rc1 nodes or later).
+ You can now specify particular peers to connect to with the 'peers' property in multibit.properties. (Use a comma separated list).
+ Fix for zero confirmation transaction vulnerability identified by Retep.
XChange 1.4.0 features:
+ More exchanges supported for currency lookup: MtGox, Bitstamp, BTC-E, CampBX, VirtEx.
UI enhancements:
+ You can use Shift-ArrowUp and Shift-ArrowDown to move between wallets when the Wallets panel is selected.
+ Wallet icon now highlighted when wallet is selected, more contrast between selected and unselected.
+ Display less flicky when changing languages, fonts and look-and-feel.
+ User chosen font now set properly in dialogs and Help screens.
General:
+ No longer opens in 'local mode' - it picks up your other MultiBit wallets.
+ Removed cacheManager code - no longer supported
+ Backward compatible wallet changes (description added, minor version dropped).
+ Serialised wallets now no longer always load - you may have to use an older version of MultiBit and migrate them to protobuf format.
+ Refactoring of encryption code in response to review comments.
+ Fix for 'Transaction cannot be cast to Comparable' bug on wallet reorgs.
Release checklist
To get the benefit of bloom filters you currently need to connect to a bitcoind v0.8rc1 node.
There is one at riker.plan99.net (courtesy of Mike Hearn).
If you are running a bitcoind v0.8rc1 node on an external IP address and don't mind people connecting, please post your IP address here so that people can try out the bloom filters. Thanks.
There is a new live MultiBit release at:
https://multibit.org
Version 0.4.20
Features:
+ Support for more currency exchanges. (XChange 0.4.0).
+ You can move up and down wallets with the Shift-ArrowUp and Shift-ArrowDown keys.
UI changes:
+ More contrast between the active wallet and the others.
+ Less flicky when changing language, font and look-and-feel.
+ Improved font display in dialogs, help, tooltips.
Bug fixes:
+ Fixed bug on display of fiat amount in Send/ Request when changing languages.
+ Fix for 'Transaction cannot be cast to Comparable' bug on wallet reorgs.
Release checklist
https://multibit.org
Version 0.4.20
Features:
+ Support for more currency exchanges. (XChange 0.4.0).
+ You can move up and down wallets with the Shift-ArrowUp and Shift-ArrowDown keys.
UI changes:
+ More contrast between the active wallet and the others.
+ Less flicky when changing language, font and look-and-feel.
+ Improved font display in dialogs, help, tooltips.
Bug fixes:
+ Fixed bug on display of fiat amount in Send/ Request when changing languages.
+ Fix for 'Transaction cannot be cast to Comparable' bug on wallet reorgs.
Release checklist
Jump to: