libp2p / libp2p/go-libp2p

Round-trip additional fields in public keys.

Open
#757 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
6.9k
Forks
1.3k
Avg merge
13d 21h
Merged PRs (30d)
1

Description

We need to make sure we can decode and then re-encode public keys back into the same datastructure. That means preserving unknown fields (which I believe we don't currently do).

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Locate the public-key decode and encode entry points in the Go repository and inspect how fields are represented between those operations. Check existing tests around public-key serialization, if present, and verify that decoding and re-encoding a key preserves unknown fields and produces the same data structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cryptography, networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.