feat: allow specification of sync wallet #111
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables the user to specify a seperate wallet for syncing the DID to the chain. This means one walllet can be used to deploy an app and sync multiple DIDs using that app.
It should be noted that this still requires each pubkey to be managed by the local store. It would certainly be useful to also allow creation of DIDs for pubic keys that are NOT managed by the local store, but that is a separate issue. This PR is mainly for simplifying the usage in fully custodial contexts.
algoid wallet create deployeralgoid deploy deployer tesnetFor any new user:
algoid wallet create userNalgoid create testnet userNdeployeraccount:algoid sync userN deployer