should cover rudimentary seedBlob localstorage transfer in docs, however, if corruption occurs, a prompt should be given with instructions on backing up the old seedBlob and renaming it, or this should be done internally for the user, and then re-running them through setup, with an alert before all this.
So far, this has not been an issue, but could be with those that screw with their browers, in which case their warranty may be void, or others could have this occur due to browser/storage corruption.
should cover rudimentary seedBlob localstorage transfer in docs, however, if corruption occurs, a prompt should be given with instructions on backing up the old seedBlob and renaming it, or this should be done internally for the user, and then re-running them through setup, with an alert before all this.
So far, this has not been an issue, but could be with those that screw with their browers, in which case their warranty may be void, or others could have this occur due to browser/storage corruption.