liftedinit / liftedinit/roadmap
Web hosting updates recorded on Manifest blockchain network
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description: Web3 KvStore feature for dweb hosting on the Manifest network. Users can write site updates such as a deployment to a kvstore. We present the user with the hash when an update is made. This would be recorded on the network and the user can check Talib to see proof that their deployment is live on the network. This adds a more Web3 feel to basic dweb hosting.
As a user, I want site updates recorded on a blockchain network so that I can view proof that the update occurred and give my site a more Web3 feel.
- Should create a hash when a site update is made.
- Should include the update types of:
- X, Y, Z.
- Should be able to lookup the site update on Talib.
- Should be able to be demoed as an E2E implementation in dev environment.
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.
Research direction
Start with the linked Notes and locate the dweb hosting KvStore flow described in the issue. Clarify the update types represented by X, Y, and Z, then trace how a deployment can be checked on Talib. Done means updates produce a hash, can be looked up on Talib, and the full flow is demonstrated end to end in the development environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100