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

[OSS] Light Validation #113

Open
1 of 5 tasks
h4x3rotab opened this issue Dec 22, 2020 · 0 comments
Open
1 of 5 tasks

[OSS] Light Validation #113

h4x3rotab opened this issue Dec 22, 2020 · 0 comments
Labels

Comments

@h4x3rotab
Copy link
Contributor

h4x3rotab commented Dec 22, 2020

light_validation module implements a Substrate light client. Currently it's coupled with our TEE and blockchain implementation. However to make it easier to share with other projects, we should make it a separate crate.

Caveats

  1. The code is coupled with Phala's blockchain because it uses the types defined in our blockchain runtime. We should remove it and only rely on Substrate itself.
  2. We have a hack to walk around the Substrate's no_std environment. The problem is that Substrate treats no_std environment as wasm, where Substrate exposes the external hash function as a host function, but it's not the case in TEE. So now we require the runtime to use the above repo as a mitigation. We need to document it somewhere, or find a better way to fix it.

Progress

  • Fully functional light client
  • Extract as a standalone package
  • Parachain client demo
  • Tests & lint
  • Documentation
@h4x3rotab h4x3rotab added enhancement New feature or request library pRuntime labels Dec 22, 2020
@h4x3rotab h4x3rotab changed the title Refactor: make light_validation a separate crate [OSS] Light Validation Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant