libp2p / libp2p/go-libp2p

How to Add the Ed448-Goldilocks elliptic curve to the project

Open
#2,622 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

### Description

I would like to explore the possibility of adding the Ed448-Goldilocks elliptic curve support to the go-libp2p project. This would be a significant change and has the potential to enhance the security and performance of the project. I would appreciate guidance and assistance on how to make this enhancement.

### Requested Changes

I would like to understand the necessary steps to add the Ed448-Goldilocks elliptic curve to the go-libp2p project. This may include modifications to cryptographic libraries, code changes, and any other related adjustments.

### Questions

1. Could you provide guidance on the codebase files that would need modification for this transition?
2. Are there any compatibility concerns or potential breaking changes this might introduce?

### Additional Information

Please provide any additional context, recommendations, or relevant information related to this elliptic curve change that would help me better understand the process.

Thank you for your assistance and support in considering this change. I'm looking forward to your guidance and expertise on this matter.

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

The issue names no files, tests, or entry points and asks for guidance on a broad cryptographic addition. Start by locating the project's existing cryptographic key and curve integration, then identify affected libraries and compatibility constraints. Done would require an agreed design, an inventory of impacted files and tests, and a clear assessment of breaking changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.