-
Notifications
You must be signed in to change notification settings - Fork 359
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
The IBC ibc
crate should be no-std
#29
Comments
no-std
no-std
The cdot team raised this same issue as Substrate uses no-std. |
We'd like to understand the priority for this issue. Suppose we adapt the |
@en @livelybug @toliuyi maybe you can comment on whether this is blocking, or a feature that's nice-to-have? |
Sorry, I submitted a duplicate issue( #508 ) today because I missed the notification. |
no-std
ibc
crate should be no-std
the no_std support on |
#1158 thoroughly tracks efforts towards no_std. Closing as duplicate of that. |
Summary
The
relayer-modules
crate should beno-std
.Problem Definition
The
relayer-modules
crate should supportno-std
this would make it more useful for solo nodes running in embedded environments and integrating deployment in wasm environments like Substrate Pallets and Eth2 Execution Environments.Proposal
Ideally the full relayer can be in
std
environment and use crates like tokio.There is progress in support unclear how this interacts with using core::future in the API. Needs more inverstigation.
For Admin Use
The text was updated successfully, but these errors were encountered: