lightninglabs / lightninglabs/taproot-assets
[feature]: Include the default universe federation server in the RPC ListFederationServers return value
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
It is important to include the default (defined in code) universe federation server in the `ListFederationServers` RPC endpoint return values. Otherwise, a user will be mislead into believing that their node do not know of any federation servers out of the box. They also won't be aware that they are syncing against `universe.lightning.finance`.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Go implementation of the ListFederationServers RPC and trace how the default universe federation server is defined and how federation servers are assembled. Done when the RPC includes universe.lightning.finance alongside the known federation servers by default, making the default sync target visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100