Suggestions - Feature Requests for MultiBit HD 0.0.6beta

[jackbox]

First off I would like the ability for Mulibit to remember the XPUB (master public key) so transactions can be viewed without unlocking the Trezor device.

Then bases on having the XPUB saved, I would like to be able to view all public addresses used and their current balance. I would like to see the change addresses and their balances also. I believe this would be a useful and popular feature.

My last concern is how MultiBit HD 0.0.6beta is unlocking the Trezor and leaving it unlocked until you exit the browser or unplug the Trezor. This means if I leave my Trezor plugged in after unlocking it, and I step away from my computer, someone could send a transaction by pushing confirmation keys on the Trezor twice, without the need to enter my PIN. I would like the option of having Multibit relock the Trezor each and every time it uses the PIN to unlock the device. After starting Trezor PIN is entered to unencrypt the wallet file using the Trezor device but is stays unlocked as long as it remains connected to the computer and Multibit is running. I would like the option of having the Trezor relocked and having to enter the PIN for every send transaction I perform. In this way nobody can send fund using Multibit and My Trezor if I left it on my computer unlocked out of stupidity.

Also, the ability to change tx fees. I sent $2.00 to your Mulitbit donation address and the tx fee the program used was only. 0.00001 BTC and it took nine blocks for the tx to get mined and confirmed. If I had the ability I would have changed the tx fee to 0.0001 for more normal processing the expected timeframe.

I really like having an alternative to the Trezor and BWALLET online wallet sites. This implementation is something that I have wanted for a while now.

Thank you.

[jim618]

Hi Jackbox,

Thanks for your feedback.
Interesting that the BWALLET works directly - it must be a very accurate Trezor clone.
What version is the BWALLET you have ?

RE: your usability points.

We have in our issues db exposing the xpub for the wallet:
https://github.com/bitcoin-solutions/multibit-hd/issues/309

For MBHD our target audience is people who don't really understand Bitcoin so we don't want to baffle them with science.
For instance, a couple of your points relate to "Can we have watch only wallets ?".

We aren't providing watch only wallets in MBHD not because they aren't useful but it's a bit of an advanced concept. You have a wallet that isn't really a wallet because you cannot spend the money in there. What ? That's complicated ! :-)

Once we expose the xpub people will be able to have a watch only wallet in another BIP32 compliant wallet (for instance blockchain.info provide xpub lookup). The privacy implications are quite profound though (this is the reason we haven't exposed it yet).

The same point applies to seeing all receiving and change addresses. That's the equivalent of asking: "Your site that provides <insert functionality here>. Can I see all the rows in the SQL table I know you are using ?". Well, that's possible but not what the users of the site use in their use case realisation. There isn't any coincontrol so there is nothing they can do with a list of change addresses.

The Satoshi Labs team have thought _a_lot_ about the Trezor functionality. With a couple of exceptions of things that we haven't implemented because we think they are too advanced for our target market we have followed their lead on functionality.
The PIN they actually refer to as a "OTP" (one time password). It's purpose is to validate your ownership of the credentials token (the Trezor itself). It's the Trezor itself that asks for a PIN response and it only does it once on power up. We follow that lead (as I imagine all Trezor compliant software will). The easiest way to prevent abuse of your Trezor is the same as with a credit card - pay for something and then unplug it and take it away.

Fees we agree that as they are floating now (in Bitcoin core) there will need to be a bit of tweaking. It is on our list of things to do here:
https://github.com/bitcoin-solutions/multibit-hd/issues/154

Also on that issue is that we are going to count donations to our donation address as (client) fee payments. Thus the $2.00 you sent to us as a donation will be counted against the client fees for the first (about) 1000 sends.


Edit: You ask: can I see all the tx without unlocking the device ? Nope !
In MBHD we have decided to encrypt practically everything. The wallet, contacts, extra tx info, history. If you (or anyone else) don't have the password/ Trezor + PIN you don't get to see anything. This is a deliberate design decision for our post-Snowden world.

[jackbox]

Hi Jackbox,

Thanks for your feedback.
Interesting that the BWALLET works directly - it must be a very accurate Trezor clone.
What version is the BWALLET you have ?

The BWALLET is running version 1.30 of the firmware. It is my understanding that they used it almost unchanged from the bithub open source Trezor code except changing the internal operation of the buttons and signing the firmware with their own signature. I am not sure but I think their version of the firmware might support Chinese language also. When I first got it the MyTrezor.com site treated it as a Trezor and a BWALLET could even be initially set up on that site. But since about one week ago the MyTrezor site was changed to detect a BWALLET device (or undetect I should say) and you can no longer use a BWALLET on the MyTrezor site. That is one reason I like that I can use it with Multibit HD beta. The MyBWALLET.com site is a virtual clone of the MyTrezor site but goes offline very soon as loading all the wallet's activity.

Thanks for answering my questions. I look forward to more developments of Multibit HD.