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

The IBC ibc crate should be no-std #29

Closed
4 tasks
zmanian opened this issue Mar 11, 2020 · 6 comments
Closed
4 tasks

The IBC ibc crate should be no-std #29

zmanian opened this issue Mar 11, 2020 · 6 comments
Labels
E: no-std External: support for no_std compatibility E: substrate External: substrate integration, requirements & problems O: new-feature Objective: cause to add a new feature or support
Milestone

Comments

@zmanian
Copy link

zmanian commented Mar 11, 2020

Summary

The relayer-modules crate should be no-std.

Problem Definition

The relayer-modules crate should support no-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

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@romac romac added the O: new-feature Objective: cause to add a new feature or support label Mar 12, 2020
@romac romac changed the title the IBC relayer-modules crate should be no-std The IBC relayer-modules crate should be no-std Mar 12, 2020
@ebuchman ebuchman added this to the v.0.0.3 milestone Jul 30, 2020
@ancazamfir ancazamfir modified the milestones: v.0.0.3, v0.0.7 Aug 14, 2020
@hxrts
Copy link

hxrts commented Jan 6, 2021

The cdot team raised this same issue as Substrate uses no-std.

@romac romac modified the milestones: v0.0.7, v0.0.8 Jan 6, 2021
@adizere
Copy link
Member

adizere commented Jan 7, 2021

We'd like to understand the priority for this issue. Suppose we adapt the modules crate to no-std in the second trimester of 2021 (after may, before end of august), would that work?

@hxrts
Copy link

hxrts commented Jan 7, 2021

@en @livelybug @toliuyi maybe you can comment on whether this is blocking, or a feature that's nice-to-have?

@en
Copy link

en commented Jan 8, 2021

Sorry, I submitted a duplicate issue( #508 ) today because I missed the notification.
I think this issue will not block the current integration work. Once ibc-rs supports no_std, substrate-ibc will support no_std without modification.

@adizere adizere added the E: substrate External: substrate integration, requirements & problems label Jan 8, 2021
@adizere adizere mentioned this issue Jan 8, 2021
5 tasks
@ancazamfir ancazamfir modified the milestones: v0.1.1, v0.1.2 Feb 11, 2021
@adizere adizere changed the title The IBC relayer-modules crate should be no-std The IBC ibc crate should be no-std Mar 3, 2021
@andynog
Copy link
Contributor

andynog commented Mar 8, 2021

the no_std support on tendermint-rs repo -> informalsystems/tendermint-rs#824

@adizere adizere added the E: no-std External: support for no_std compatibility label Jun 8, 2021
@adizere
Copy link
Member

adizere commented Jan 6, 2022

#1158 thoroughly tracks efforts towards no_std. Closing as duplicate of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E: no-std External: support for no_std compatibility E: substrate External: substrate integration, requirements & problems O: new-feature Objective: cause to add a new feature or support
Projects
None yet
Development

No branches or pull requests

8 participants