Topic: MultiBit - page 20. (Read 336309 times)
Could you make it so that multibit remembers the window size i set it to? Currently it reverts back to the standard window size everytime when started and that is imho too big.
One newbie question here:
https://bitcointalksearch.org/topic/m.3270671
https://bitcointalksearch.org/topic/m.3270671
The Help Contents is here:
https://multibit.org/en/help/v0.5/help_contents.html
The section 'Wallet backups' is a general overview of backups with 'File descriptions' the details of filenames.
It is exactly the same help as in MultiBit itself in the Help | Help contents. Just with a different CSS.
https://multibit.org/en/help/v0.5/help_contents.html
The section 'Wallet backups' is a general overview of backups with 'File descriptions' the details of filenames.
It is exactly the same help as in MultiBit itself in the Help | Help contents. Just with a different CSS.
Do you have a link to the wallet files help section I have no idea where that's at. I downloaded a .key file is that sufficient when restoring a wallet?
There is a section in the help called 'File descriptions' describing all the files on your disk.
You basically:
1) shut down multibit.
2) copy the wallet file (and it is worth copying the info file and the backup directory - explained in the help)
As the wallets are not deterministic if you create more receiving addresses / private keys you will need to redo your backup.
You basically:
1) shut down multibit.
2) copy the wallet file (and it is worth copying the info file and the backup directory - explained in the help)
As the wallets are not deterministic if you create more receiving addresses / private keys you will need to redo your backup.
With MultiBit currently each new receiving address is created from a brand new, random private key.
Thus every time you create new receiving address(es) you have new data in your wallet that needs backing up.
When you create receiving addresses you can create 1, 5, 20, 100 at a time. And you can repeat it to, say, create 400.
So you can create 100 new receiving addresses, back that wallet up and you'll be good for a while.
Addresses you SEND to are not so critical and transactions you can always get from the Bitcoin network.
It is the private keys that are critical.
If you are on the most recent code (0.5.13 onwards) there is also an automatic backup system that stores copies of wallets when you add new keys locally on your disk. These are useful up to a point but are useless if you lose your computer.
When HD wallets are supported you will have a mnemonic phrase to write down from which you will be able to rebuild your keys (like Electrum and Armory) so life should become easier. This will still be a while yet though.
Thus every time you create new receiving address(es) you have new data in your wallet that needs backing up.
When you create receiving addresses you can create 1, 5, 20, 100 at a time. And you can repeat it to, say, create 400.
So you can create 100 new receiving addresses, back that wallet up and you'll be good for a while.
Addresses you SEND to are not so critical and transactions you can always get from the Bitcoin network.
It is the private keys that are critical.
If you are on the most recent code (0.5.13 onwards) there is also an automatic backup system that stores copies of wallets when you add new keys locally on your disk. These are useful up to a point but are useless if you lose your computer.
When HD wallets are supported you will have a mnemonic phrase to write down from which you will be able to rebuild your keys (like Electrum and Armory) so life should become easier. This will still be a while yet though.
Do we have to backup everytime again and again? Or if we backup one time, there is no need to back up again? I mean should we update our backups?
There is a section in the help called 'File descriptions' describing all the files on your disk.
You basically:
1) shut down multibit.
2) copy the wallet file (and it is worth copying the info file and the backup directory - explained in the help)
As the wallets are not deterministic if you create more receiving addresses / private keys you will need to redo your backup.
You basically:
1) shut down multibit.
2) copy the wallet file (and it is worth copying the info file and the backup directory - explained in the help)
As the wallets are not deterministic if you create more receiving addresses / private keys you will need to redo your backup.
How do I backup my Multibit wallet to a thumb drive I don't see anywhere in the program where it allows you to make a backup
It is always calculated automatically - there is some discussion 'up the thread' on it.
Edit: found it : https://bitcointalksearch.org/topic/m.2585913
Edit: found it : https://bitcointalksearch.org/topic/m.2585913
In the latest version of MultiBit, is there any way to set the fee manually, or is it always calculated automatically?
Thanks.
Thanks.
Hi Clipcoins.
I have a 'soundey' friend, Garcia, who has created some sound samples for me. I haven't received them just yet. Also have some original chimes from another source (not sure if they want to be named).
I'll post them all when I get them for people to listen to.
I have a 'soundey' friend, Garcia, who has created some sound samples for me. I haven't received them just yet. Also have some original chimes from another source (not sure if they want to be named).
I'll post them all when I get them for people to listen to.
Feature request:
It would be nice if there was a cool sound that would play when you receive or send BTC. I love the little "beep" that blockchain.info wallet uses. It's very helpful as well as nice to hear...the "sound of success".
But even better for Multibit would be if you could choose the sound to play from your PC...wav file or mp3, etc. It seems like it would be simple to implement (well easy for me to say), but just a suggestion that would be a nice improvement..thanks for the consideration.
It would be nice if there was a cool sound that would play when you receive or send BTC. I love the little "beep" that blockchain.info wallet uses. It's very helpful as well as nice to hear...the "sound of success".
But even better for Multibit would be if you could choose the sound to play from your PC...wav file or mp3, etc. It seems like it would be simple to implement (well easy for me to say), but just a suggestion that would be a nice improvement..thanks for the consideration.
You need to ask them as it depends how often they send them (and what fees they out on the transactions).
How many days it will take to receive payment from sites like coinad and other bitcoin giving sites
For now, don't try to import wallets. Just send your money from one to the other and keep bitcoin-qt around in case you want to refer to old transactions.
It's a bit hacky, but the label for an address is stored in the .info file.
This is a fairly simple text file - have a look at an existing one.
I guess if you could get the labels out of Bitcoin-QT you could put them in there.
A bit of a complication is that they are URI encoded (spaces, special characters, line breaks etc) so you might have to fiddle around in a text editor.
Obviously you'd want to take backups before and check things afterwards etc.
This is a fairly simple text file - have a look at an existing one.
I guess if you could get the labels out of Bitcoin-QT you could put them in there.
A bit of a complication is that they are URI encoded (spaces, special characters, line breaks etc) so you might have to fiddle around in a text editor.
Obviously you'd want to take backups before and check things afterwards etc.
Any chance to import Bitcoins-QT wallet to Multibit INCLUDING labels?
I have cca 1000 addresses in the original client and want to get rid of it, but did not find out how to import the wallet to Multibit. Manually labeling 1000 addresses is not a good way to go.
Thanks for any tips.
I have cca 1000 addresses in the original client and want to get rid of it, but did not find out how to import the wallet to Multibit. Manually labeling 1000 addresses is not a good way to go.
Thanks for any tips.
I think the answer is to put in the ability to set the fee per KB.
The default would be as now: 0.0001 BTC per KB.
But if you want a higher fee you might increase it to, say, 0.0005 BTC per KB
Then if your tx comes in at 1.5 KB instead of paying 0.0002 BTC (it's rounded up) you would pay 0.001.
The fee solver would still take care of things like ensuring very small outouts aren't produced - this is completely impractical to do manually.
The default would be as now: 0.0001 BTC per KB.
But if you want a higher fee you might increase it to, say, 0.0005 BTC per KB
Then if your tx comes in at 1.5 KB instead of paying 0.0002 BTC (it's rounded up) you would pay 0.001.
The fee solver would still take care of things like ensuring very small outouts aren't produced - this is completely impractical to do manually.
Honestly this would be bliss.
I think the answer is to put in the ability to set the fee per KB.
The default would be as now: 0.0001 BTC per KB.
But if you want a higher fee you might increase it to, say, 0.0005 BTC per KB
Then if your tx comes in at 1.5 KB instead of paying 0.0002 BTC (it's rounded up) you would pay 0.001.
The fee solver would still take care of things like ensuring very small outouts aren't produced - this is completely impractical to do manually.
The default would be as now: 0.0001 BTC per KB.
But if you want a higher fee you might increase it to, say, 0.0005 BTC per KB
Then if your tx comes in at 1.5 KB instead of paying 0.0002 BTC (it's rounded up) you would pay 0.001.
The fee solver would still take care of things like ensuring very small outouts aren't produced - this is completely impractical to do manually.
Jump to: