You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there has been an oversight in the algorithms run when a label is being changed. It seems that MultiBit is scanning all the addresses each time.
Changing the label on a single address (with the sort marker on the address column) should be a O(1) operation. But in this case it seems to be an O(n) operation.
The text was updated successfully, but these errors were encountered:
Given that MultiBit Classic is being deprecated in favour of MultiBit HD it is doubtful that a fix for this would be put in. Most users would have far fewer than 3000 addresses and would hardly ever see this so it doesn't rate as critical.
I think there has been an oversight in the algorithms run when a label is being changed. It seems that MultiBit is scanning all the addresses each time.
Changing the label on a single address (with the sort marker on the address column) should be a O(1) operation. But in this case it seems to be an O(n) operation.
The text was updated successfully, but these errors were encountered: