daemon: Output announced multiaddresses found after start-up
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
### Checklist
- [X] My issue is specific & actionable.
- [X] I am not suggesting a protocol enhancement.
- [X] I have searched on the [issue tracker](https://github.com/ipfs/go-ipfs/issues?q=is%3Aissue) for my issue.
### Description
(This is a smaller issue that continues from https://github.com/ipfs/go-ipfs/issues/9043, and a `ipfs daemon` equivalent to https://github.com/ipfs/ipfs-webui/issues/1964)
Currently, `ipfs daemon` prints `Swarm announcing` for the initial, local multiaddresses. However, when using `RelayClient`, public multiaddresses aren't found until after `Daemon is Ready` and so are never reported.
Ideally, `ipfs daemon`'s output should report additional `Swarm announcing` messages for multiaddresses found after it reports `Daemon is ready`.
Contributor guide
Research direction
Start at the `ipfs daemon` startup path and examine how initial `Swarm announcing` messages and `Daemon is ready` are emitted. Trace how `RelayClient` discovers public multiaddresses after readiness. Done means later-discovered multiaddresses produce additional `Swarm announcing` output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100