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
{{ message }}
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.
We need to make an importer to use the account module from an existing seed.
Method signature: ´iotaAccount.importStateFromSeed(boolean overwriteCurrent)´
Boolean is used when we find conflicting balances in the existing account state, and the one from the node.
Does not run by default on anything, and must have a disclaimer on the javadoc that it is unchecked. Developers should not underestimate responsibility for usage of this method.
The text was updated successfully, but these errors were encountered:
Yes, Accounts are for now intended to use from a clean slate. It is best to generate a new seed, use it on the account to get a new deposit address, and send your balance to this new seed.
We made this decision because from a technical standpoint, nodes cannot with certainty know which addresses are spent from, and what balances are on which account. (although currently with the coordinator we can)
Otherwise, you could find the balance for each address and manually add them in the json storage, but that seems like a lot of effort :D
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to make an importer to use the account module from an existing seed.
Method signature: ´iotaAccount.importStateFromSeed(boolean overwriteCurrent)´
Boolean is used when we find conflicting balances in the existing account state, and the one from the node.
Does not run by default on anything, and must have a disclaimer on the javadoc that it is unchecked. Developers should not underestimate responsibility for usage of this method.
The text was updated successfully, but these errors were encountered: