spike(vault): large artefacts with UnixFS in an IndexedDB blockstore
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- database
Research direction
Start by locating the browser blockstore and its IndexedDB configuration, then check how the project uses @helia/unixfs. Measure write and read time, memory use, and eviction behavior for 10, 100, and 500 MB payloads on Chrome, Firefox, and Safari. Done means a results table and recommendation covering supported size limits, chunking settings, or server-side storage, with a follow-up issue if warranted.
Written by the indexing model from the issue text.
Description
Summary
Find out whether state vectors and datasets in the tens to hundreds of megabytes are practical in the browser blockstore.
Estimated size: S
Proposal
- Store 10, 100 and 500 MB payloads with
@helia/unixfs. - Record write time, read time, memory use and eviction behavior on Chrome, Firefox and Safari.
Acceptance criteria
- A table of measurements and a recommendation (supported size limit, chunking settings, or server-side only).
- Follow-up issue if a feature is justified.
Out of scope
- Production implementation.
Dependencies
- None; can be picked up independently.
Part of #43. Ground rules for the content layer: no secrets in the repo, content-layer failures must never block or discard quantum execution, and tests and docs ship with every PR.
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- Avg merge
- 5h 19m
- Merged PRs (30d)
- 11
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from QMeshPy/distributed-quantum
-
enhancement good first issue helia storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QMeshPy/distributed-quantum#53 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments research-spike tier-2
Difficulty 4/5 3-5 days Newbie friendliness 55/100
QMeshPy/distributed-quantum#78 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments research-spike tier-2
Difficulty 3/5 1-2 days Newbie friendliness 66/100
QMeshPy/distributed-quantum#77 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments tier-2
Difficulty 5/5 Over a week Newbie friendliness 35/100
QMeshPy/distributed-quantum#76 ·
Maintainers usually reply within 1 day
-
documentation good first issue kubo storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
QMeshPy/distributed-quantum#75 ·
Maintainers usually reply within 1 day
All issues in QMeshPy/distributed-quantum
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gramaziokohler/compas_timber#870 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
autowarefoundation/autoware_carla_scenario#500 ·
Maintainers usually reply within 1 day
-
good first issue priority: low size: XS testing
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
cubrid-lab/cubrid-mcp-server#385 ·
Maintainers usually reply within 1 day
-
good first issue priority: low size: S testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
cubrid-lab/cubrid-cookbook-python#447 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100