Adds a ShareAccountKeyFlow. #86
Open
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
This flow can be used to share a [PublicKey]-[AccountInfo] mapping with another host.
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.
In response to todays discussion on Slack, this is our attempt to provide the missing functionality of sharing the locally generated key (for an account) with the counterparty's (remote) host in order to allow the latter to also have the
PublicKey-AccountInfomapping for subsequent lookups.The intended usage is to invoke a subflow after the
FinalityFlowones in order to ensure that the generated key is not shared if aFlowExceptionis thrown.e.g.
subFlow(ShareAccountKeyFlow(localAccountGeneratedAnonymousParty.owningKey, remoteAccountHostSession))on the initiating flow, andsubFlow(ShareAccountKeyHandlerFlow(issuingHostSession))on the initiated one.