[FEATURE]: Resolve contract names using nameservice
- Dominant language
- Go
- Stars
- 7
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### New feature
For registering contracts, we should try to resolve contracts using the nameservice system calls.
Ex.
```
🔓 > register_token koin
Contract 'pob' at address 15DJN4a8SgrbGhhGksSBASiSYjGnMU8dGL registered
```
This would allow for system contracts to be upgraded in band without needing a new rc file.
### Anything else?
_No response_
Contributor guide
Research direction
Start at the CLI path for the register_token command and trace how contract names are currently handled. Identify how nameservice system calls can be used during registration, then verify that a registered name resolves to the expected contract address and supports in-band system-contract upgrades.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100