Description
Currently, names that consist of all numbers (e.g. 123.voi) may cause unexpected behavior or errors when resolving, displaying, or interacting with enVoi-integrated apps. This issue affects components that assume names will include at least one non-numeric character.
Tasks
- Investigate how names like
123.voi are being parsed and resolved
- Identify any validation logic or UI components that break when handling numeric-only names
- Update resolution logic, name validation, or UI rendering to support names with only numbers
- Add tests to confirm that names like
123.voi, 0001.voi, etc., function as expected
Expected Outcome
- Numeric-only names (e.g.
123.voi) are fully supported across resolution, display, and linking
- No crashes, broken links, or false validation errors occur
- Improved name compatibility and flexibility within the enVoi ecosystem
Bounty
Rewarded in BUIDL tokens
Learn more about BUIDL: https://x.com/NicholasShella2/status/1904243228314071368
Description
Currently, names that consist of all numbers (e.g.
123.voi) may cause unexpected behavior or errors when resolving, displaying, or interacting with enVoi-integrated apps. This issue affects components that assume names will include at least one non-numeric character.Tasks
123.voiare being parsed and resolved123.voi,0001.voi, etc., function as expectedExpected Outcome
123.voi) are fully supported across resolution, display, and linkingBounty
Rewarded in BUIDL tokens
Learn more about BUIDL: https://x.com/NicholasShella2/status/1904243228314071368