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

Runtime abstraction #106

Open
obycode opened this issue Sep 28, 2023 · 1 comment
Open

Runtime abstraction #106

obycode opened this issue Sep 28, 2023 · 1 comment
Assignees

Comments

@obycode
Copy link
Collaborator

obycode commented Sep 28, 2023

To support Clarinet, potential future upgrades or other use cases, it seems like a good idea to abstract out the Wasm runtime instead of directly integrating wasmtime. The immediate use of this would be for clarinet to call the compiled Wasm contracts from Node.js. Doing this would require defining some trait for the execution of contracts. Each potential runtime environment needs to provide the imports for all of the host-interface functions used by Clarity contracts.

@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Sep 28, 2023
@obycode obycode moved this from Status: 🆕 New to Status: 📋 Backlog in Stacks Core Eng Sep 28, 2023
@cylewitruk
Copy link
Member

There are some synergies here with the a/b testing tool which may be of use. We can see when it gets closer to completion what might be able to pulled out to help support Clarinet.

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

No branches or pull requests

5 participants