lncm / lncm/ideas

IPFS on The Box

Open
#33 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

BUIDL ideas
Dominant language
No language data
Stars
22
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Put some of the website and frontend / JS / Image assets on IPFS, and pin them on each box.

So that it's completely decentralized. Each box supporting each other. Of course there should be a local version too.

Thoughts on this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. First clarify the website and frontend assets to move, how each box should pin and serve them, and how the local version relates to the decentralized one. Done should mean an agreed design and an implementation plan with explicit asset, pinning, and fallback behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
distributed-systems, frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.