Hi Grouver,
There are a combination of techniques used to get the initial startup time as quick as possible:
1) With bitcoinj based code only the block headers are stored in the blockchain. These are 100 bytes per block. So the 200,000+ blocks take about 20 MB. I include an up to date copy in the installer. This means you only have to catch up the blockchain since the date of the last installer.
2) When you first start MultiBit you do not have a wallet yet. Thus it can save time because it does not have to check old blocks to see if there any relevant transactions. It thus tells the bitcoind it is connected to: 'just give me the block headers, do not bother giving me the transactions'. This can download at 1000+ blocks a second on a good connection.
Once you have a wallet it currently downloads the full blocks to check the transactions. In the next few months I hope to get server side Bloom filters in (see conference presentation) which should speed up the downloads when you have wallets. It won't ever be as fast as the initial setup but should be a good bit quicker than now.
Topic: MultiBit - page 55. (Read 336309 times)
Regarding your question Jim.
I was curious how many connections i had since the blockchain downloading went really quick.
But since i only download the blockchain from one node it doesnt really matter i guess.
I noticed when I download the client and start it up it downloads the blockchain and light-speed.
Do you download the blockchain within the client? If yes, how does this exactly work.
I was curious how many connections i had since the blockchain downloading went really quick.
But since i only download the blockchain from one node it doesnt really matter i guess.
I noticed when I download the client and start it up it downloads the blockchain and light-speed.
Do you download the blockchain within the client? If yes, how does this exactly work.
Hi Jim,
sorry to find another small strange behaviour:
3) When changing the user language, and afterwards changing from the preferences screen to any other screen, e.g. transactions screen, the language of the elements *inside* of this screen is still in the old language.
The change of the language only takes full effect after exiting and restarting MultiBit.
BTW: I agree that right click menus are not the best way on tablets or cell phones
.
Edit: The reordering of columns by dragging the column header is cool
! I didn't notice it. Glad you mentioned it.
sorry to find another small strange behaviour:
3) When changing the user language, and afterwards changing from the preferences screen to any other screen, e.g. transactions screen, the language of the elements *inside* of this screen is still in the old language.
The change of the language only takes full effect after exiting and restarting MultiBit.
BTW: I agree that right click menus are not the best way on tablets or cell phones
.Edit: The reordering of columns by dragging the column header is cool
! I didn't notice it. Glad you mentioned it.Yes, the language change (and the change of Look and Feel) can be a bit quirky but if you restart MultiBit it always get it right.
It is things being cached and then not being completely reinitialised I think but i have not pinned them all down.
Hi Jim,
sorry to find another small strange behaviour:
3) When changing the user language, and afterwards changing from the preferences screen to any other screen, e.g. transactions screen, the language of the elements *inside* of this screen is still in the old language.
The change of the language only takes full effect after exiting and restarting MultiBit.
BTW: I agree that right click menus are not the best way on tablets or cell phones.
Edit: The reordering of columns by dragging the column header is cool! I didn't notice it. Glad you mentioned it.
sorry to find another small strange behaviour:
3) When changing the user language, and afterwards changing from the preferences screen to any other screen, e.g. transactions screen, the language of the elements *inside* of this screen is still in the old language.
The change of the language only takes full effect after exiting and restarting MultiBit.
BTW: I agree that right click menus are not the best way on tablets or cell phones
.Edit: The reordering of columns by dragging the column header is cool
! I didn't notice it. Glad you mentioned it.
Your number 1) I will have a look at sooner, as that is not what a user would expect for a numeric field.
Yes - there are various things not saved (e.g. screen size and placement and the position of the divider between the wallets) but there is other stuff to work on first.
Did you notice that you can reorder the columns in the Transactions tab by clicking on the column header and dragging it ? :-)
Yes - there are various things not saved (e.g. screen size and placement and the position of the divider between the wallets) but there is other stuff to work on first.
Did you notice that you can reorder the columns in the Transactions tab by clicking on the column header and dragging it ? :-)
Hi Jim,
I just noted the following:
1) When sorting entries in the transaction screen by the amount, the sorting algorithm uses alphabetical ordering instead of numerical ordering.
2) The user is able to make columns in the transaction screen wider and can choose a column to sort the entries, but currently these settings are not stored.
I guess fixing this will be a low priority.
I just noted the following:
1) When sorting entries in the transaction screen by the amount, the sorting algorithm uses alphabetical ordering instead of numerical ordering.
2) The user is able to make columns in the transaction screen wider and can choose a column to sort the entries, but currently these settings are not stored.
I guess fixing this will be a low priority.
Cheers Freemoney
Funny you should mention the Transactions right click context menu as it is on my list to remove it ! :-)
For use on tablet machines the right click has disappeared, replaced with either a button (or two) or a menu button if there are more options than that.
For the transaction screen I was going to put in a button bar down at the bottom with:
"Show details button" and "Export all button"
I am assuming that with Windows Metro/"Whatever It Is Called Today" tablets will become more common. I want MultiBit to be tablet friendly.
Maybe the way to go is what Armory does is have a Basic, Pro, Developer mode the user can switch between.
Funny you should mention the Transactions right click context menu as it is on my list to remove it ! :-)
For use on tablet machines the right click has disappeared, replaced with either a button (or two) or a menu button if there are more options than that.
For the transaction screen I was going to put in a button bar down at the bottom with:
"Show details button" and "Export all button"
I am assuming that with Windows Metro/"Whatever It Is Called Today" tablets will become more common. I want MultiBit to be tablet friendly.
Maybe the way to go is what Armory does is have a Basic, Pro, Developer mode the user can switch between.
Hi Jim,
fair enough that you consider it.
I fully understand that keeping MultiBit simple to use is becoming a challenge since the userbase grows and with it the demands.
Maybe you can make some of the advanced features accessible through 'right click context sensitive menus' like in the transaction screen.
Keep up the great work.
fair enough that you consider it.
I fully understand that keeping MultiBit simple to use is becoming a challenge since the userbase grows and with it the demands.
Maybe you can make some of the advanced features accessible through 'right click context sensitive menus' like in the transaction screen.
Keep up the great work.
Hi Freemoney,
I will have a think about.
Trouble is, the user interface is starting to be a bit complicated for the average user.
For instance, to be able to "delete" i.e archive/ hide a receiving address I need to show the balance controlled for that address.
Adding in the amount as well goes from:
Receiving addresses is a list of:
label + address
to
Receiving addresses is a list of:
label + address + amount + balance.
That's quite a lot more information being shown (and with decreasing marginal utility).
I will have a think about.
Trouble is, the user interface is starting to be a bit complicated for the average user.
For instance, to be able to "delete" i.e archive/ hide a receiving address I need to show the balance controlled for that address.
Adding in the amount as well goes from:
Receiving addresses is a list of:
label + address
to
Receiving addresses is a list of:
label + address + amount + balance.
That's quite a lot more information being shown (and with decreasing marginal utility).
Hi Jim,
Yes, at the moment the amount is not stored on either the receiving addresses (nor on the send addresses).
It is difficult to generalise how the addresses are used - one person might have an address for an item, another might use it for dealings with a particular person or another might use each address only once and not want ANY extra information stored with it.
To store a given amount with the label + address is equivalent to saying "the address describes a thing with a certain price" i.e it makes the list of receiving addresses into a "catalog of items for sale".
I get the feeling half the users would want it, half the users would not want it, and the other half would be undecided ! :-)
It is difficult to generalise how the addresses are used - one person might have an address for an item, another might use it for dealings with a particular person or another might use each address only once and not want ANY extra information stored with it.
To store a given amount with the label + address is equivalent to saying "the address describes a thing with a certain price" i.e it makes the list of receiving addresses into a "catalog of items for sale".
I get the feeling half the users would want it, half the users would not want it, and the other half would be undecided ! :-)
I can understand the differences in usage and that users will have varying preferences even when talking about a single user.
However: If MultiBit would save the amount then users will still be able to choose how to use the amount field.
If somebody does not like to see past amounts for a specific address then he can leave the field empty from the beginning (at least for receiving addresses) or delete the amount later.
As it is very much the convention in Bitcoin land I have changed MultiBit to show all the BTC digits. Screenshot below:
The 'Satoshi digits' are starting to be used to convey extra information (e.g. the dice throws in SicBo) so I have added them in due to popular demand.
This change will appear in future releases.
The 'Satoshi digits' are starting to be used to convey extra information (e.g. the dice throws in SicBo) so I have added them in due to popular demand.
This change will appear in future releases.
Thanks !
Well the keyspace someone has to search is around 58^30 which is still a pretty big number !
Private keys are so important though that it is worth getting in the habit of never exposing anything about them. I remember once I did a demo to a roomful of people and accidentally typed my password in the username field. Everyone saw it. Ooops.
Well the keyspace someone has to search is around 58^30 which is still a pretty big number !
Private keys are so important though that it is worth getting in the habit of never exposing anything about them. I remember once I did a demo to a roomful of people and accidentally typed my password in the username field. Everyone saw it. Ooops.
Also, as I am sure you realise, make sure you do not ever use that private key in the future as it is in the public domain.
Captures are photoshped, priv key is 52 chars long and you can see less than 20, I supose with this is imposible to recreate the key, am I wrong?
Regards
You are probably ok.
I'm scared, you said only "probably"?
Congratulations for the good job in Multibit.
Regards
Jim is there already maybe a option available to see how many nodes your already connected to?
Thanks.
Thanks.
Hi Grouver,
There is no 'network' tab in MultiBit (though I am thinking of putting one in).
Normally MultiBit connects to 4 nodes pretty quickly and then, if it loses one, connects to another.
You can see this indirectly by going to the Transactions tab, right clicking on a pending transaction and doing 'Show transaction details'.
It normally says 'Seen by 4 peers' and then some extra info. Typically a transaction comes in from each of the peers in turn as it propagates through the network.
To save on bandwidth it downloads the full blocks from one peer only.
Just wondering if there any particular reason you need to know the number of peers MultiBit is connected to ?
Also, as I am sure you realise, make sure you do not ever use that private key in the future as it is in the public domain.
Captures are photoshped, priv key is 52 chars long and you can see less than 20, I supose with this is imposible to recreate the key, am I wrong?
Regards
You are probably ok.
Jim is there already maybe a option available to see how many nodes your already connected to?
Thanks.
Thanks.
Also, as I am sure you realise, make sure you do not ever use that private key in the future as it is in the public domain.
Captures are photoshped, priv key is 52 chars long and you can see less than 20, I supose with this is imposible to recreate the key, am I wrong?
Regards
Gary Rowe is taking all of October off his regular job to work solidly on MultiBit Merchant, a new sister offering to MultiBit.
This will be an open source Bitcoin web retail offering - he describes what he is doing here:
http://www.reddit.com/r/Bitcoin/comments/10fzgn/my_october_of_bitcoin_project_multibit_merchant/
This is exciting stuff as it will be great to have an open merchant solution in the Bitcoin space.
This will be an open source Bitcoin web retail offering - he describes what he is doing here:
http://www.reddit.com/r/Bitcoin/comments/10fzgn/my_october_of_bitcoin_project_multibit_merchant/
This is exciting stuff as it will be great to have an open merchant solution in the Bitcoin space.
Hi Vitruvio,
Thanks for the screen shots - I will have to look into that in more detail.
MultiBit should at the minimum give the user more feedback if the format is not what it expects.
Also, as I am sure you realise, make sure you do not ever use that private key in the future as it is in the public domain.
Thanks for the screen shots - I will have to look into that in more detail.
MultiBit should at the minimum give the user more feedback if the format is not what it expects.
Also, as I am sure you realise, make sure you do not ever use that private key in the future as it is in the public domain.
Hi vitruvio,
That is the general way to do it yes.
Things to look out for:
1) MultiBit only imports the sipa format keys - they begin with 5.
2) you could try exporting the private keys from MultiBit unencrypted into a different file and looking at the contents. If the private key in the exported file is different it suggests there is some mismatch in formats.
Slightly difficult to pin down as of course you do not want to reveal the private key value.
Let me know what you find out as it will be useful for other people.
That is the general way to do it yes.
Things to look out for:
1) MultiBit only imports the sipa format keys - they begin with 5.
2) you could try exporting the private keys from MultiBit unencrypted into a different file and looking at the contents. If the private key in the exported file is different it suggests there is some mismatch in formats.
Slightly difficult to pin down as of course you do not want to reveal the private key value.
Let me know what you find out as it will be useful for other people.
Hi jim618, thank you for the response, I supose it must be this, my private key start with L, is the one dumped by satoshi client, so must be diferent format, but when I import it all procedure seem to be Ok.
As you may see it says completed sucessfully, and indeed I have a new address in my wallet.
Regards
Jump to: