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

no_std support for subxt #159

Closed
melynx opened this issue Sep 3, 2020 · 2 comments
Closed

no_std support for subxt #159

melynx opened this issue Sep 3, 2020 · 2 comments

Comments

@melynx
Copy link

melynx commented Sep 3, 2020

Currently there isn't any no_std support for substrate-subxt making it really difficult to craft extrinsics from within a restricted environment. Is there any planned support for no_std / alloc environments?

@DemiMarie
Copy link
Contributor

I am not aware of any such plans on Parity’s end, though community contributions would be welcome. That said, much of the client code is likely to be completely rewritten at some point. Currently, each extrinsic requires manual effort in this repo, which just does not scale. In the future, the client code will be generated from the chain metadata.

@jsdw
Copy link
Collaborator

jsdw commented May 10, 2024

Nowadays we have a subxt-core crate which contains the no-std compatible subset of subxt functionality (it does require alloc though; I think for non-alloc cases you're probably going to have to do something more manual as needed since we rely on it quite a lot!)

So I'll close this, and we can open new issues to address things missing from subxt-core or whatever :)

@jsdw jsdw closed this as completed May 10, 2024
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

3 participants