Hey jim, was wondering if you had any updates on the issue here
https://bitcointalksearch.org/topic/m.11313861
I still do get it occasionally.
Topic: MultiBit - page 8. (Read 336309 times)
Any plan to introduce a promt for sliding competitive fees?
September could be an awkward month otherwise http://www.ibtimes.co.uk/coinwallet-plans-bitcoin-dust-attack-september-create-30-day-transaction-backlog-1515981
Hi OmegaStarScream,
We quite like Bitcoin XT as we think the block size needs to increase.
As to what will happen if/ when there is a hardfork:
Currently MultiBit Classic and HD both will follow the chain with the most work done in it.
Thus in a hardfork all the existing MultiBit code will follow the 'winner'. This is how the normal one or two block forks (that occur reasonably frequently) get resolved so it should just be the same but on a larger scale.
Both MultiBit Classic and HD connects to Bitcoin Core and XT happily and they should work correctly with larger blocks. The bloom filtered blocks Core/ XT send back to MultiBit are the same - MultiBit is agnostic about connecting to Core or XT.
Thus at the moment we don't think we will have to make any code changes because of a block size increase/ hardfork
There is also a checkpoint file in MultiBit that is used to speed up wallet replays. That specifies which is the 'correct' block header every 2000ish blocks. After a fork that file will specify the block header in the 'winning' fork. That'll be a couple of weeks after a fork occurs so it should be cut and dried then.
Jim
We quite like Bitcoin XT as we think the block size needs to increase.
As to what will happen if/ when there is a hardfork:
Currently MultiBit Classic and HD both will follow the chain with the most work done in it.
Thus in a hardfork all the existing MultiBit code will follow the 'winner'. This is how the normal one or two block forks (that occur reasonably frequently) get resolved so it should just be the same but on a larger scale.
Both MultiBit Classic and HD connects to Bitcoin Core and XT happily and they should work correctly with larger blocks. The bloom filtered blocks Core/ XT send back to MultiBit are the same - MultiBit is agnostic about connecting to Core or XT.
Thus at the moment we don't think we will have to make any code changes because of a block size increase/ hardfork
There is also a checkpoint file in MultiBit that is used to speed up wallet replays. That specifies which is the 'correct' block header every 2000ish blocks. After a fork that file will specify the block header in the 'winning' fork. That'll be a couple of weeks after a fork occurs so it should be cut and dried then.
Jim
Hi there Jim , Are you planning to do this or you are totally against the BitcoinXT ? : https://bitcointalksearch.org/topic/request-for-all-wallet-developers-1153684
How to import old wallet from classic version to Hd version ?
I'm pretty sure that Multibit HD doesn't support this (unfortunately, in my opinion). If you look in the "help" menu under "upgrading from multibit classic" you'll see:
Quote
One of the problems with random private keys is that they cannot be easily regenerated. It is for this reason that we, the MultiBit developers, have decided against direct import of a Multibit Classic wallet.
I'd like to add that this decision is the main reason why I haven't upgraded to Multibit HD. I'm really not sure why they don't allow a collection of old style private keys to be imported. Andreas' Bitcoin Wallet for Android nowadays provides a HD wallet but you can import old-style private keys. Bitcoin Wallet for android just shows these in a special menu and warns you that you have some old-style addresses in your wallet that aren't going to be regenerated if you are restoring from your wallet words. In my own case, I like HD for 95% of the cases, but I still have some classic addresses that I want to keep track of, therefore I'm not a user of Multibit HD. However, if you're willing to discard your old addresses, Multibit HD is probably a great option.
See the rest of that help section on upgrading from multibit classic if you need further instructions. Basically they suggest backing up all your old keys then spending to your new HD wallet.
How to import old wallet from classic version to Hd version ?
I had a little problem while using the client, which I am sure must have occured with others and would have been discussed somewhere in the previous 82 pages, but its hard to scroll back and look through. So I am just going to ask it again.
Has anyone had issues with the balance not being correct on the wallet ? I have had the problem, that the balance shown is more, I even tried "Reset Blockchain" , but that didn't fix the problem either. The only thing so far that fixes it, is importing the private key to a new wallet, which in turn creates a new address(as a new wallet is created) , so I have to go about exporting the address again.
Anyone has a better fix for this ?
Has anyone had issues with the balance not being correct on the wallet ? I have had the problem, that the balance shown is more, I even tried "Reset Blockchain" , but that didn't fix the problem either. The only thing so far that fixes it, is importing the private key to a new wallet, which in turn creates a new address(as a new wallet is created) , so I have to go about exporting the address again.
Anyone has a better fix for this ?
Bumping this,
and I had another problem today. I was sending bitcoins to a bitpay address, and while doing so, the status of the transaction switched to a triangle, which usually happens if there is not enough balance(due to wrong display) and it usually fixes itself on restarting the client.
However, it didn't change to being confirmed today, and I was scared, that after the 10 minutes were over, it might change to confirmed and would be broadcasted to the blockchain. So I had to start up another PC, to import the key there and get the BTC out of that address just incase it confirmed sometime later from the original pc. Anyone had any issues like these before ?
When you encrypt a previously unencrypted wallet MultiBit goes through all the unencrypted backups and:
+ creates an encrypted copy with the suffix ".cipher"
+ secure deletes the unencrypted copies.
Thus they are safe to leave as they are.
+ creates an encrypted copy with the suffix ".cipher"
+ secure deletes the unencrypted copies.
Thus they are safe to leave as they are.
One small suggestion, extend this text
Quote
The password was added successfully. Private keys have been backed up, using the wallet password, to: "..."
with the above sentences.
More feature request:
* A button pair "move up / move down" for the "Wallets" tab would be nice. Then I could keep my 2013-2014 wallets open, in case something comes in, but push them down; and have my most current and important wallets at the top.
* the QR codes would be much more useful to me without label inserted into the QR
Tiny unimportant details, really. And other than that - what a beautiful program. So happy to have decided for multibit, already in my first contact with bitcoin - and never regretted it.
0.2 BTC never appeared in my wallet.
I was sure that they had to be there. blockchain.info showed them, with dozens of confirmations.
And in multibit the blockchain had moved past the block into which the tx had been mined.
Finally I decided to go through the lengthy (several hours) process "Reset blockchain and Transactions"
- which turned out to fortunately be per wallet, and not multibit-wide (mention that somewhere?).
The 0.2 BTC are back, no problem at all. But only after my intervention.
I remember, I had this problem before, long ago; and a friend, too - he exported the keys, and imported them somewhere else.
Do we have to rescan each wallet once in a while?
Shall I perhaps close my 2013-2014 wallet, and create a completely new one - that would at least make the rescan faster, right?
I was sure that they had to be there. blockchain.info showed them, with dozens of confirmations.
And in multibit the blockchain had moved past the block into which the tx had been mined.
Finally I decided to go through the lengthy (several hours) process "Reset blockchain and Transactions"
- which turned out to fortunately be per wallet, and not multibit-wide (mention that somewhere?).
The 0.2 BTC are back, no problem at all. But only after my intervention.
I remember, I had this problem before, long ago; and a friend, too - he exported the keys, and imported them somewhere else.
Do we have to rescan each wallet once in a while?
Shall I perhaps close my 2013-2014 wallet, and create a completely new one - that would at least make the rescan faster, right?
superb, well done!
Then it is only about possibly existing manual backups from before the encryption.
Then it is only about possibly existing manual backups from before the encryption.
When you encrypt a previously unencrypted wallet MultiBit goes through all the unencrypted backups and:
+ creates an encrypted copy with the suffix ".cipher"
+ secure deletes the unencrypted copies.
Thus they are safe to leave as they are.
If you view the ".cipher" files in a hexeditor you'll just see the usual gobble-de-gook you see with an encrypted file - no structure at all.
+ creates an encrypted copy with the suffix ".cipher"
+ secure deletes the unencrypted copies.
Thus they are safe to leave as they are.
If you view the ".cipher" files in a hexeditor you'll just see the usual gobble-de-gook you see with an encrypted file - no structure at all.
I am cleaning up a bit.
Now I have found a couple of files in a folder called "wallet-unenc-backup"
path-to-my-wallet/wallet-unenc-backup/name-timestamp.wallet.cipher
path-to-my-wallet/wallet-unenc-backup/name-timestamp.info
They are old. Probably from before I encrypted the wallet.
I should better delete them, right?
Now I have found a couple of files in a folder called "wallet-unenc-backup"
path-to-my-wallet/wallet-unenc-backup/name-timestamp.wallet.cipher
path-to-my-wallet/wallet-unenc-backup/name-timestamp.info
They are old. Probably from before I encrypted the wallet.
I should better delete them, right?
Since the thread has 82 Pages, I am thinking it might have been discussed somewhere along these pages.
Actually it was this thread: https://bitcointalksearch.org/topic/m.8175658Maybe related, maybe not...
Since the thread has 82 Pages, I am thinking it might have been discussed somewhere along these pages.
Actually it was this thread: https://bitcointalksearch.org/topic/m.8175658Maybe related, maybe not...
So, in one sense, it sounds like you've found a working solution. But on the other hand, you've experienced the problem more than once. I think the next step is to see if you can figure out steps to reproduce the problem, if you can come up with those, then you've got a bona-fida bug report that will almost certainly get fixed.
I won't call it a working solution, as now everytime, I go about creating a new wallet, and adding the private key, I have to go about backing up all the keys again, as sometimes, the btc is sent to the other address in the wallet when not backed up.
So, if you import the priv-key to a new wallet then the problem is sovled? But does it happen again or something? If it happens repeatedly, it'd be great if you could give steps to reproduce.
Yes, but its like another wallet opened in the Multibit client. If I leave the old wallet opened as well, then that still displays the wrong balance. The new one shows the correct balance. As for repeatedly, I think I have seen this happen 2-3 times till now, with different addresses. So far only on Mac, but might have happened on Windows as well, will have to check, as I hardly close any wallets. So, in one sense, it sounds like you've found a working solution. But on the other hand, you've experienced the problem more than once. I think the next step is to see if you can figure out steps to reproduce the problem, if you can come up with those, then you've got a bona-fida bug report that will almost certainly get fixed.
I think I remember somebody else having this issue where resetting the blockchain didn't help... There was no answer though...
Since the thread has 82 Pages, I am thinking it might have been discussed somewhere along these pages. So, if you import the priv-key to a new wallet then the problem is sovled? But does it happen again or something? If it happens repeatedly, it'd be great if you could give steps to reproduce.
Yes, but its like another wallet opened in the Multibit client. If I leave the old wallet opened as well, then that still displays the wrong balance. The new one shows the correct balance. As for repeatedly, I think I have seen this happen 2-3 times till now, with different addresses. So far only on Mac, but might have happened on Windows as well, will have to check, as I hardly close any wallets. I had a little problem while using the client, which I am sure must have occured with others and would have been discussed somewhere in the previous 82 pages, but its hard to scroll back and look through. So I am just going to ask it again.
Has anyone had issues with the balance not being correct on the wallet ? I have had the problem, that the balance shown is more, I even tried "Reset Blockchain" , but that didn't fix the problem either. The only thing so far that fixes it, is importing the private key to a new wallet, which in turn creates a new address(as a new wallet is created) , so I have to go about exporting the address again.
Anyone has a better fix for this ?
Has anyone had issues with the balance not being correct on the wallet ? I have had the problem, that the balance shown is more, I even tried "Reset Blockchain" , but that didn't fix the problem either. The only thing so far that fixes it, is importing the private key to a new wallet, which in turn creates a new address(as a new wallet is created) , so I have to go about exporting the address again.
Anyone has a better fix for this ?
So, if you import the priv-key to a new wallet then the problem is sovled? But does it happen again or something? If it happens repeatedly, it'd be great if you could give steps to reproduce.
I think I remember somebody else having this issue where resetting the blockchain didn't help... There was no answer though...
I had a little problem while using the client, which I am sure must have occured with others and would have been discussed somewhere in the previous 82 pages, but its hard to scroll back and look through. So I am just going to ask it again.
Has anyone had issues with the balance not being correct on the wallet ? I have had the problem, that the balance shown is more, I even tried "Reset Blockchain" , but that didn't fix the problem either. The only thing so far that fixes it, is importing the private key to a new wallet, which in turn creates a new address(as a new wallet is created) , so I have to go about exporting the address again.
Anyone has a better fix for this ?
Has anyone had issues with the balance not being correct on the wallet ? I have had the problem, that the balance shown is more, I even tried "Reset Blockchain" , but that didn't fix the problem either. The only thing so far that fixes it, is importing the private key to a new wallet, which in turn creates a new address(as a new wallet is created) , so I have to go about exporting the address again.
Anyone has a better fix for this ?
Jump to: