paritytech / paritytech/web3-storage
Supporting mutable data
Open
@antkve is already working on this.
Since Jun 8, 2026.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
Context
Mutable Data is needed in 2 scenarios -
- Meta Data : Say S3 Bucket Key to underlying L0 Bucket details, FS - directories, files, and folder structures, etc
- Mutable Application/User Data : In case of live editing docs or sheets
Some Questions to Answer, while designing
- Can we retain the underlying chunks as immutable and provide mutable support for applications?
- If so, what should be the ideal size of the chunk?
- If not, what are the alternatives?
- What kind of performance complications can this yield?
Footnote
- Part of this is called out in #134
- Need to design the method of mutating blobs, updating MMR, etc
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.