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

Add DTLS protocol

Open
#75 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

The issue names no files, tests, or entry points. Start by reviewing the multiaddr protocol and multicodec repositories, then resolve whether DTLS needs an optional value such as a certificate fingerprint and where the protocol should be added; done means the design questions are settled and the appropriate repository changes are scoped.

Written by the indexing model from the issue text.

Description

We're considering building DTLS transports in libp2p/libp2p#49. Therefore, I suggest to add a 'dtls' multiaddr protocol. I'd like to have some input on the following:

  1. We don't really need a 'value' part of the multiaddr to establish a connection. However, we could add a certificate fingerprint as a form of authentication. Is this a good use of the 'value'? Can this be made optional?
  2. Should I open a PR on this, the multicodec or both repo's?
Dominant language
Go
Stars
482
Forks
87
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 multiformats/multiaddr

All issues in multiformats/multiaddr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.