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.

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 support #157

Closed
2 tasks done
juanhurtado10 opened this issue May 10, 2022 · 0 comments
Closed
2 tasks done

Protocol 19 support #157

juanhurtado10 opened this issue May 10, 2022 · 0 comments
Labels
🎯 Epic Big picture of a feature

Comments

@juanhurtado10
Copy link
Contributor

juanhurtado10 commented May 10, 2022

ℹ️ This issue is an Epic

Context

Protocol 19 implements two Core Advancement Proposals.

CAP-21 introduces a new suite of transaction preconditions, which are optional requirements you can add to control transaction validity. Time bounds, which have long been a Stellar transaction precondition, allow you to craft transactions that are only valid in a specific time-based window. The new Protocol 19 preconditions allow you to craft transactions that skip sequence numbers, set ledger bounds, enforce relative time and ledger delays (aka "relative timelocks"), and require extra signers (e.g. hash locks).

CAP-40 adds a new signer type that allows multiple parties to build a set of transactions for signing that guarantees if one transaction is signed, authorized, and submitted, information is revealed that allows all other transactions in the set to be authorized as well.

Objective

  • To add support for the new Stellar protocol 19

Checklist

@juanhurtado10 juanhurtado10 added the 🎯 Epic Big picture of a feature label May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎯 Epic Big picture of a feature
Projects
None yet
Development

No branches or pull requests

2 participants