Topic: Release information - page 3. (Read 10987 times)

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).

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-----

-----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-----

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

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.





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.

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

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.

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.

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.

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.

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?

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.

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

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

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