Storage markets
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- distributed-systems
Research direction
No files, tests, or entry points are identified in the issue. First clarify the market-node design, pricing model, allocation verification, speed testing, relay behavior, and replication responsibilities; done would require an agreed implementation scope and corresponding tests.
Written by the indexing model from the issue text.
Description
Market node, used for routing, LN channels are made to the market node route by both storage clients and storage providers. Storage prices rise on a per-node basis; this encourages a more even distribution of load, and incentivizes adding storage to a network in a competitive market as prices rise with demand. For instance, price should be a function of supply, and increase exponentially as a storage allocation approaches 100%.
Storage allocation can be verified by the storage provider node. Speed tests can be used between the storage provider and the storage market. Storage markets can relay data between multiple storage providers, improving replication, with replication factor managed by the storage market node itself, or replication can be performed peer to peer between storage clients and individual storage clients. The primary function of a market node is to set a market price. Otherwise, fully P2P operation can occur at a fixed price.
- Dominant language
- Rust
- Stars
- 119
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 bitmask-stack/carbonado
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitmask-stack/carbonado#31 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitmask-stack/carbonado#28 · 1 comment ·
-
Catalog Format v0May be free again @cryptoquick claimed this 1310 days ago, and no pull request is open. Open
bitmask-stack/carbonado#21 · 1 assignee ·
-
Web Storage ProviderOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitmask-stack/carbonado#18 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitmask-stack/carbonado#17 ·
All issues in bitmask-stack/carbonado
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stellar/stellar-cli#2773 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
voidzero-dev/oxc-angular-compiler#511 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yantrikos/yantrik-os#539 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation station:mac ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rolter-ai/rolter#2490 · 1 comment ·
Maintainers usually reply within 1 day