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

PoC: Extension as a program #9

Open
xlc opened this issue Apr 29, 2024 · 2 comments
Open

PoC: Extension as a program #9

xlc opened this issue Apr 29, 2024 · 2 comments

Comments

@xlc
Copy link
Member

xlc commented Apr 29, 2024

Depends on #8

Research if it is possible to implement an extension with a PolkaVM program.

The use case is that a chain can enable new extension by simply uploading a PolkaVM program and it will be used as extension implementation.

The PolkaVM program will be executed on a similar environment of the XCQ executor. i.e. it can call into other extensions. In that way, it could use an extension to read raw storages and basically do anything.

@indirection42
Copy link
Contributor

Is this requirement an additional feature or expected results? I was thinking the implementation of the different extension are done in host side, and the caller provides polkavm blob (like smart contract) and other input data to do query.

@xlc
Copy link
Member Author

xlc commented Jun 3, 2024

This is an additional feature. Most of the extensions should still be implemented natively in runtime for performance reason. This will be useful to dynamically add new extensions without runtime upgrade and that can be useful in many use cases. However, this is a nice to have and not needed for the first release version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants