hirosystems / hirosystems/btc-us-website

"+" symbol in search shows available, but not registerable (miss match)

Open
#17 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Svelte
Stars
49
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Hi,

1) + Symbol not registerable:

During the process of buying BNSs, I have encountered many fail txs from:
- passing the search availability,
- passing the Pre-ordering,
- but failing at Registering.

- After asking around in Stacks Discord support, found the "+" symbol cannot be registered.
- Jasper.#0260 on Discord kindly pointed out + symbol doesn't work, and taught me how to check via https://explorer.stacks.co/sandbox/contract-call
and yeah the "+" returns "error 2022" while on the main webpage shows as available.

> Can someone confirms this, and let me know what other symbols are acceptable and unacceptable?
> Perhaps this warning can be added to the website?

2) Can't register more than 1 BNS per address warning sign:

Another issue is that people who just go on the website do not know u can only hold 1 per address, I was one of the person and pre-ordered 5 names... If this warning can be put somewhere clear near the search bar or during the process, will be great.

Thank you Hiro team!!!!!

![ISSUE001-01](https://user-images.githubusercontent.com/92864860/138976065-084ea9a5-e501-4e10-9ba1-30dd0a93be25.PNG)
![ISSUE001-02](https://user-images.githubusercontent.com/92864860/138976074-7571e13d-cc17-4e2e-a410-a464a5963f87.PNG)

![ISSUE001-03](https://user-images.githubusercontent.com/92864860/139549472-6e5c0de1-f400-4d96-87f4-e8ea398fd000.PNG)
![ISSUE001-04](https://user-images.githubusercontent.com/92864860/139549534-4932d96d-cd0a-4517-ad80-6efea7601155.PNG)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the mismatch through the website search, pre-order, and registration flow, then compare it with the contract-call result linked in the issue. Check how unsupported symbols and the one-name-per-address restriction are presented; done means the availability result no longer misleads users and both constraints are clearly warned about.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.