MultiBit HD 0.0.8beta released

[jim618]

There is a new release of MultiBit HD - Beta 8.
This has support for the Bitcoin payment protocol (BIP 70) and an update for Trezor 1.3.3. firmware.

It is available on https://beta.multibit.org as usual.

There is a blog article describing it in more detail, with the usual SHA256 hashes, here:
https://beta.multibit.org/blog/2015/04/14/multibit-hd-beta-8.html

[Mickeyb]

Hello, is there a manual or explanation on how to install multibit hd and trezor.

Thanks

[jim618]

It's pretty straightforward (or at least it should be !):

1) Go to https://beta.multibit.org and download the installer for your operating system (Win / Mac / Linux).
2) After you download the installer the webpage forwards to a "How to install' page for your OS. Follow the instructions.
3) Plug in your Trezor.
4) Start up MultiBit HD. It starts up showing a Trezor setup wizard so just work your way through it.

After that to use your Trezor with MultiBit HD you simply plug it in.

[Mickeyb]

It's pretty straightforward (or at least it should be !):

1) Go to https://beta.multibit.org and download the installer for your operating system (Win / Mac / Linux).
2) After you download the installer the webpage forwards to a "How to install' page for your OS. Follow the instructions.
3) Plug in your Trezor.
4) Start up MultiBit HD. It starts up showing a Trezor setup wizard so just work your way through it.

After that to use your Trezor with MultiBit HD you simply plug it in.

Thanks, I got it!

Why am I seeing only partial balance? I have much more BTC in my trezor? Is multibit showing only a first address balance?

[jim618]

We only show bitcoin that you have on your 'Account 1' in myTrezor.com.
If you have created other accounts they are not seen by MultiBit HD

If you go into 'Manage wallet | Dashboard' at the bottom in Wallet capabilities it states what exactly the kind of wallet is.

The reason for this is a bit technical - it's to do with how we connect to the Bitcoin network. It's a limitation of our SPV wallet architecture.

[spin]

I was having trouble sending btc from my trezor yesterday.  Using this.

I'm on Win 7 64bit.  Was using HD 0.0.7 before.  I downloaded and upgraded to 0.0.8.  I have the latest firmware from mytrezor.com.

It connects to the Trezor and shows tx history fine.  It just doesn't seem to want to send.  When I send it stops at the screen on the app which says please confirm.  The app is still fine and is responsive.  I.e. I can cancel at this point. 

On the trezor it's stuck at "signing transaction" but the gears aren't turning.  It seems to be frozen also.  Have to pull the usb cable out to get it off the screen.

I was able to complete the transaction using mytrezor.com, but I really prefer multibit as it's true spv and independent of a central server.

Any thoughts?

[garyrowe]

I was having trouble sending btc from my trezor yesterday.  Using this.

I'm on Win 7 64bit.  Was using HD 0.0.7 before.  I downloaded and upgraded to 0.0.8.  I have the latest firmware from mytrezor.com.

It connects to the Trezor and shows tx history fine.  It just doesn't seem to want to send.  When I send it stops at the screen on the app which says please confirm.  The app is still fine and is responsive.  I.e. I can cancel at this point. 

On the trezor it's stuck at "signing transaction" but the gears aren't turning.  It seems to be frozen also.  Have to pull the usb cable out to get it off the screen.

I was able to complete the transaction using mytrezor.com, but I really prefer multibit as it's true spv and independent of a central server.

Any thoughts?

Hi spin,

Thanks for reporting this issue. I wrote the MultiBit Hardware/hid4java libraries which handle the communications between MultiBit HD and Trezor.

It sounds like there might be a comms problem that occurred. Did you visit mytrezor.com while having an unlocked Trezor wallet?

These kind of problems are very difficult to debug without logs, so would you be willing to upload your logs to MultiBit.org for analysis?

In Release 0.1 (coming soon) we will have a built-in encrypted error reporting system, but for now we have to do it manually. Here are the steps:

1. Visit https://multibit.org and follow the links under the "Verify" section to get Jim's public GPG key. You should see http://pgp.mit.edu:11371/pks/lookup?search=0x79F7C572 and click the link on 0x79F7C572)
2. Use Save As and name the file "multibit-key.asc".
3. Locate the log file covering the day when the problem occurred (see C:\Users\user.name\AppData\Roaming\MultiBitHD\logs on Windows)
4. ZIP the log file(s) up and copy it/them to where you put Jim's key as "error-report.zip"
5. Install GPG if you don't already have it (see https://www.gnupg.org/download/)
6. Encrypt the ZIP for MultiBit.org as follows

gpg --import multibit-key.asc
gpg --recipient jim618@fastmail.co.uk --encrypt error-report.zip

7. Send the report to Jim and he'll arrange for it to be forwarded to me
8. I'll post an update here containing a link to our issue database or a better analysis of the problem

Kind regards,

Gary

[spin]

Have been away and just saw your post.  Will post logs when I can. 

[ParkExcite]

Can we have a fix BTC adress for receive payment ?

It always generating a new one....

[jim618]

You can reuse an address is you really want to.

New addresses are generated for each new transaction as it improves privacy and you can label each transaction individually.