Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ENS resolution

Open
#4,822 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
backend

Research direction

The report identifies the /bzz/{address} request path and includes logs showing nugaon.eth rejected while handling ACT decryption. Start by tracing how that endpoint parses and resolves names, and compare the ACT-related path with ENS name resolution. Done means a registered .eth name resolves instead of returning HTTP 400; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Description

⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.

Context

Bee 2.2.0

Summary

When I try to open my registered personal page on http://vps:1633/bzz/nugaon.eth I get 400 error.

Expected behavior

I can resolve the nugaon.eth address as so far.

Actual behavior
"time"="2024-09-13 15:37:30.887535" "level"="debug" "logger"="node/api" "msg"="resolve name: attempting to resolve string to address" "string"="nugaon.eth"
"time"="2024-09-13 15:37:30.887822" "level"="debug" "logger"="node/api/act_decryption_handler" "msg"="invalid path params" "error"="1 error(s) occurred: `address=nugaon.eth`: invalid name or bzz address: 1 error occurred:\n\t* failed parsing CID nugaon.eth err invalid cid: selected encoding not supported: could not parse\n\n"
"time"="2024-09-13 15:37:30.887974" "level"="error" "logger"="node/api/act_decryption_handler" "msg"="invalid path params" "error"="1 error(s) occurred: `address=nugaon.eth`: invalid name or bzz address: 1 error occurred:\n\t* failed parsing CID nugaon.eth err invalid cid: selected encoding not supported: could not parse\n\n"
"time"="2024-09-13 15:37:30.888239" "level"="debug" "logger"="node/api" "msg"="content length header not found"
"time"="2024-09-13 15:37:30.888468" "level"="info" "logger"="node/api" "msg"="api access" "ip"="X.X.X.X" "method"="GET" "host"="vps:1633" "uri"="/bzz/nugaon.eth/" "proto"="HTTP/1.1" "status"=400 "size"=240 "duration"="1.412272ms" "user-agent"="browser"
Steps to reproduce

open http://{hostName}:1633/bzz/nugaon.eth in the browser.

Possible solution

seemingly the problem caused by the newly introduced ACT feature

Dominant language
Go
Stars
1.5k
Forks
390
Avg merge
2d 8h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ethersphere/bee

All issues in ethersphere/bee

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.