Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

LIP0045: Fix isChainIDAvailable enpoint and add one for registered names #282

Closed
ricott1 opened this issue Feb 24, 2023 · 0 comments · Fixed by #313
Closed

LIP0045: Fix isChainIDAvailable enpoint and add one for registered names #282

ricott1 opened this issue Feb 24, 2023 · 0 comments · Fixed by #313
Assignees

Comments

@ricott1
Copy link
Contributor

ricott1 commented Feb 24, 2023

  • The endpoint isChainIDAvailable should be moved to a new endpoint section (currently missing).
  • The logic should return False if the input is not on the same network of the mainchain, or if the input equals the mainchain chainID.
  • We should add a similar endpoint for registered names isChainNameAvailable. This should check if the name has the required length, uses the correct character set, and if it is available.

Related SDK issues:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants