Right now, every threshold and master key weight needs to be set anytime there is a change to the masterkey weight or threshold. We force the user to set the entire 4 byte map each time a change is made. If the user doesn't do this properly or forgets to pull the latest values from the server, he can screw himself by potentially overriding the master key.
An alternative proposal is to make each (master key, threshold level) optional so the account holder can set individual levels without worrying about the others.
@MonsieurNicolas @jedmccaleb
Right now, every threshold and master key weight needs to be set anytime there is a change to the masterkey weight or threshold. We force the user to set the entire 4 byte map each time a change is made. If the user doesn't do this properly or forgets to pull the latest values from the server, he can screw himself by potentially overriding the master key.
An alternative proposal is to make each (master key, threshold level) optional so the account holder can set individual levels without worrying about the others.
@MonsieurNicolas @jedmccaleb