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
Cacao-zcap SDK support. #116
Conversation
- Move the core SDK functionality into rust. - Extract some common Kepler lib code into a different crate. - Support for CacaoZcap2022 in the SDK. - Support for #host delegations in the SDK.
- Expand capabilityChain at each level to include the full chain, rather than just the parent. - Express the invocationTarget and root zcap as separate resources in the delegation resource list.
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.
overall LGTM, in future we can think about what else we can move into Kepler-lib, but this works well, is pretty clean and does all we need. is the typescript type declaration in sdk-wasm::host
something we can extend to all fns/does it generate typed TS fns on the other side? I wouldn't think so but I live in hope
- Don't use ring for anything. - Add documented ts types for the wasm boundary types.
Sister kepler-sdk PR: spruceid/kepler-sdk#40