Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update StrKey implementations to support CAP-40 signed payloads #4262

Closed
3 tasks done
Tracked by #409
Shaptic opened this issue Mar 7, 2022 · 0 comments
Closed
3 tasks done
Tracked by #409

Update StrKey implementations to support CAP-40 signed payloads #4262

Shaptic opened this issue Mar 7, 2022 · 0 comments

Comments

@Shaptic
Copy link
Contributor

Shaptic commented Mar 7, 2022 •
edited
Loading

Breakdown and Rollout: Horizon & Protocol 19. See #4261 for the master issue.

CAP-40 introduces a new type of signer: a signed payload, which is a signer that includes both a payload and the signature on that payload alongside it. The StrKey representation of this new signer is defined in stellar/stellar-protocol#1014 as a change to SEP-23. This is blocked on stellar/stellar-protocol#1014 getting finalized, approved, and merged.

SDKs must be updated to support this new signer:
@Shaptic Shaptic self-assigned this Mar 7, 2022
This was referenced Mar 7, 2022
Closed
Closed
Closed
Closed
@Shaptic Shaptic moved this from Todo to In Progress in Protocol 19 Mar 14, 2022
@Shaptic Shaptic removed their assignment Mar 23, 2022
@Shaptic Shaptic mentioned this issue Mar 31, 2022
Closed
@Shaptic Shaptic closed this as completed Apr 6, 2022
Repository owner moved this from In Progress to Done in Protocol 19 Apr 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
No open projects
Protocol 19
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Shaptic