Content hash

Open
#151 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
solidity
Domain
blockchain

Research direction

No file, test, or entry point is identified in the issue. Start by locating the Basenames contract and its current name-resolution flow, then compare the requested content-hash behavior with ENS; done means users can set a content hash and host a website through a Basename.

Written by the indexing model from the issue text.

Description

Base names does not allow users to set content hash. So users can't host a website. ENS allows full functionality which makes base names less attractive for users to buy a base name. For base names to attract users, base should allow users to set the content hash. This is a feature request and not a issue.

Dominant language
Solidity
Stars
164
Forks
115
PR merge metrics
No merged PRs in 30d

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.

More from base/basenames

All issues in base/basenames

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.