Severity: Medium — ENS (.eth) name resolution is a stub but the README advertises it
The README repeatedly claims name resolution works across chains:
Names, not hex. .sui, .eth, and friends resolve before the request fires.
(README.md:71)
But the Ethereum adapter never resolves ENS:
// cli/src/chains/ethereum.rs:66-72
async fn resolve_name(&self, name: &str) -> Result<Option<String>> {
if !name.ends_with(".eth") { return Ok(None); }
// ENS resolution would go here
Ok(None)
}
(ethereum.rs:66-72). As a result, handlers.rs:387-394 falls back to "could not be resolved! Proceeding with raw input", so txio eth balance vitalik.eth queries the literal string vitalik.eth and fails. Only Sui (suix_resolveNameServiceAddress) actually resolves.
Fix
- Implement ENS resolution (resolver lookup via
eth_call to the ENS registry/resolver), or update the README/CLI to state that only SuiNS is currently supported.
Migrated from Kingvic300/txio#45
Severity: Medium — ENS (
.eth) name resolution is a stub but the README advertises itThe README repeatedly claims name resolution works across chains:
But the Ethereum adapter never resolves ENS:
(ethereum.rs:66-72). As a result, handlers.rs:387-394 falls back to "could not be resolved! Proceeding with raw input", so
txio eth balance vitalik.ethqueries the literal stringvitalik.ethand fails. Only Sui (suix_resolveNameServiceAddress) actually resolves.Fix
eth_callto the ENS registry/resolver), or update the README/CLI to state that only SuiNS is currently supported.Migrated from Kingvic300/txio#45