-
Notifications
You must be signed in to change notification settings - Fork 313
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
js-stellar-sdk: Smart Contracts: Support new txn types, events, and contract calls #787
Comments
A prototype operation can be found here https://github.com/stellar/rs-stellar-xdr/blob/main/xdr/next/Stellar-transaction.x#L69 with the additional restriction that if you use this it must be the only operation in the transaction (not the only kind of operation, the only operation as in there must be exactly 1). This is almost sure to change in the future, but it should be an acceptable starting point. |
Goal for this stage is something we could use for the end-to-end example dapp https://github.com/stellar/jump-cannon-deliverables/issues/18 for now. |
XDR Updates are in stellar/js-stellar-base#538 |
These are done in the |
@paulbellamy should the priority and iteration for this issue be updated? I see we have decided as noted above this will go with @jonjove 's option and we will fix it later when the CAPs are finalized. |
@paulbellamy just saw this - you could set a tag before publishing (off the top of my head, the syntax is something like |
Once either https://github.com/stellar/stellar-protocol/blob/master/core/cap-0050.md or https://github.com/stellar/stellar-protocol/blob/master/core/cap-0052.md lands.Let's go with @jonjove's option below for now and change it again when the caps finalize.TODO
The text was updated successfully, but these errors were encountered: