# \[RFC\] Hashflow Usernames **URL:** \ **Category:** Governance\ **Created:** [December 12, 2022, 8:38pm UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434 "2022-12-12T20:38:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![neo3t](https://avatars.discourse-cdn.com/v4/letter/n/ec9cab/32.png) [@neo3t](https://gov.hashflow.com/u/neo3t)\ **Post date:** [December 12, 2022, 8:38pm UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/1 "2022-12-12T20:38:29Z")
## Proposal Structure - Title: [DRAFT] Hashflow Usernames - Author(s): @neo3t - Submission Date: 12/12/2022 **Proposal:** - Simple Summary: TL,DR : Create .HFT handles to navigate through Hashflow, registered on the blockchain. - Abstract: We are a team of developers who would like to build native decentralized domains on Hashflow. It would be an innovative system working in a similar way to ENS for the back-end. The feature aims to register user with usernames such as username.hft on Hashflow instead of simple adresses. - Motivation: More than technical use-cases, we believe a sense of community is primordial when building a product especially on the blockchain. Therefore, it would be great to have a feature for the community to have a traceable Hashflow identity while using Hashflow. - Specification & Rationale: The feature has a large potential for growth which would increase transactions by facilitating exchanges and profiles. It would also create great use-cases for competitions and leaderboards. - Benefits (Pros): As discussed with the team, the DAO would benefit financially from this by receiving the incentives (domain fees). It would be a way to bring the community together but also an opportunity for them to support Hashflow and get more visibility. - Downside (Cons): Options such as Unstoppable Domains exist, although the domains wouldn’t be integrated into Hashflow (the solution doesn’t provide use-cases whereas we would built it for Hashflow). - Voting: Voting: Yes would mean you want this proposal to be implemented. No would mean you do not want this proposal implemented. ---
**Author:** ![tD1](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@tD1](https://gov.hashflow.com/u/tD1)\ **Post date:** [December 13, 2022, 8:46pm UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/2 "2022-12-13T20:46:08Z")
I don’t think we need something like this, since there’s no any utility. ---
**Author:** ![moon998](https://yyz1.discourse-cdn.com/flex035/user_avatar/gov.hashflow.com/moon998/32/17_2.png) [@moon998](https://gov.hashflow.com/u/moon998)\ **Post date:** [December 13, 2022, 10:12pm UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/3 "2022-12-13T22:12:09Z")
too early to talk about these stuffs ---
**Author:** ![NIKA](https://yyz1.discourse-cdn.com/flex035/user_avatar/gov.hashflow.com/nika/32/141_2.png) [@NIKA](https://gov.hashflow.com/u/NIKA)\ **Post date:** [December 13, 2022, 11:25pm UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/4 "2022-12-13T23:25:42Z")
It seems like an interesting idea. But currently it is not a priority for Hashflow. ---
**Author:** ![neo3t](https://avatars.discourse-cdn.com/v4/letter/n/ec9cab/32.png) [@neo3t](https://gov.hashflow.com/u/neo3t)\ **Post date:** [December 16, 2022, 3:04am UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/6 "2022-12-16T03:04:40Z")
Understood! Thank you for the feedback. ---
**Author:** ![neo3t](https://avatars.discourse-cdn.com/v4/letter/n/ec9cab/32.png) [@neo3t](https://gov.hashflow.com/u/neo3t)\ **Post date:** [December 16, 2022, 3:05am UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/7 "2022-12-16T03:05:59Z")
Around $40,000 and it would be integrated within a month, including a session within two weeks in which the dao is testing the feature / providing feedbacks and then we can deliver a final product. ---
**Author:** ![brian](https://yyz1.discourse-cdn.com/flex035/user_avatar/gov.hashflow.com/brian/32/162_2.png) [@brian](https://gov.hashflow.com/u/brian)\ **Post date:** [December 17, 2022, 8:15pm UTC](https://gov.hashflow.com/t/rfc-hashflow-usernames/434/8 "2022-12-17T20:15:38Z")