Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Future ChildStorage design and capabilities #11913

Closed
mustermeiszer opened this issue Jul 25, 2022 · 0 comments
Closed

Future ChildStorage design and capabilities #11913

mustermeiszer opened this issue Jul 25, 2022 · 0 comments

Comments

@mustermeiszer
Copy link
Contributor

Before submitting a PR, I thought it would be best to agree on a "spec", and more importantly if you guys even want such a core element to be externally submitted. I have thought about it for the past few days and wanted to draft my approach here and get some feedback.

Referencing:

paritytech/polkadot-sdk#278
paritytech/polkadot-sdk#363
paritytech/polkadot-sdk#368

As a disclaimer, in my "design" I am assuming that it is wanted, that the child storage is open for non-substrate data structures. If this is not wanted, closing this issue is the most straightforward.

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

No branches or pull requests

1 participant