Model "address scopes" in signed peer records
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
There is such thing as “address scopes” for discovery mechanisms, which we have not modelled yet, e.g. a public discovery mechanism should only advertise public addresses, a multi-layer DHT with a private layer or mDNS should advertise private addresses.
When it comes to signed peer records, these two address sets should be contained in records with different _asserted scope_, and these records are _additive_ to one another, rather than exclusive.
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
No files or tests are named. Start by locating the signed peer record and discovery address-handling code, then determine how asserted scopes should be represented and combined; done means public and private address sets can be advertised in separate additive records with distinct scopes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100