livepeer / livepeer/explorer

Feature Request: host explorer on IPFS / ENS

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
11
Forks
26
Avg merge
11h 58m
Merged PRs (30d)
16

Description

As a user, I would like to be able to load Livepeer Explorer from IPFS, with addressing done via ENS.

For example, using livepeer.eth ENS name, to create a URL https://explorer.livepeer.eth.limo, which loads content from an associated IPFS content hash.

Examples of other web properties using this approach:

https://swervefi.eth.limo/
https://uniswap.eth.link/
https://tornadocash.eth.limo/
https://vitalik.eth.limo/

Contributor guide

Open the contributing guide

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

The issue names no files, tests, or entry points; begin by mapping how Livepeer Explorer is currently built and deployed, then investigate serving its content through IPFS and resolving it with ENS. Done means the Explorer loads at the proposed livepeer.eth.limo URL from an associated IPFS content hash.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
infrastructure, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.