-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protocol 19 - CAP-40 Signed Payload Signer #414
Conversation
…ignedPayload Signer from CAP40 into StrKey encoding/decoding.
…ns, incorporate some pr feedback
…de)ser, use AccountID for signed payload pojo to check discriminant on public key types
…ts into SignedPayloadSigner, pr feedback
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ Did we, or are we, adding a function for signing a payload and generating a decorated signature to attach to a transaction? I couldn't see that functionality in this PR.
Ok, have not done that aspect, just have the StrKey encode/decode updated for payload signer. Is that signature generation in the go client sdk for reference? I can get that in here. The encoded payload signer should go right into the Precondtions.ExtraSigners correct? And then I think need to add a AbstractTransaction.sign(SignedPayloadSigner signedPayloadSigner) to encapsulate both generation and adding the signedpayload decorated sig to the tx in one. |
The signing operation should be independent of a transaction, then let people add the signature manually. That's how the Go SDK works anyway. https://github.com/stellar/go/blob/horizon-protocol-19/keypair/full.go#L115-L123 |
@leighmcculloch , thanks for the references, I added similar convention into Java SDK, up for review on PR #415 |
have reviewed these changes for CAP-40 Signed Payload Signer on PR #413. renamed source repo branch to 'protocol-19', triggered 413 to close, opened this PR on new branch name.
Closes #412
Closes #410