Migration to Coincurve for Non-Windows Systems

Description

This issue will track the continued migration to Coincurve for non-Windows systems, ensuring a smooth transition and addressing any challenges that arise during the process. Coincurve offers a more robust and efficient cryptographic backend, making it a valuable update for improving performance and compatibility across platforms.

Motivation

The current cryptographic library for non-Windows systems has limitations in terms of performance and compatibility for Py-libp2p. Migrating to Coincurve provides a more robust and efficient solution, aligning with our goal to enhance cross-platform support and maintain a modern codebase.

Current Implementation

Complete the migration to Coincurve for non-Windows systems, replacing any dependencies that are incompatible or suboptimal for these environments.

Key Tasks:

• Audit Current Dependencies:

Identify existing cryptographic dependencies that Coincurve will replace.

Document where these dependencies are used in the codebase.

• Implement Coincurve Integration:

Replace outdated dependencies with Coincurve in all relevant modules.

Ensure compatibility with the current codebase.

• Testing:

Create unit tests to verify Coincurve integration.

Perform platform-specific testing on Linux and macOS to ensure there are no compatibility issues.

• Documentation:

Update developer documentation to reflect the migration to Coincurve.

Include instructions for setting up and using Coincurve on non-Windows systems.

• Community Feedback and Support:

Gather feedback from contributors and users during the migration process.

Address any questions or concerns related to Coincurve usage.

Resources:

Coincurve Documentation

How You Can Help:

If you’re familiar with Coincurve or cryptographic migrations, your expertise would be incredibly valuable! Please feel free to share insights, answer questions, or contribute code. You can also help by testing the changes on non-Windows systems and reporting any issues.

Let’s work together to make this migration as seamless as possible. Thank you to everyone involved in this effort!

Are you planning to do it yourself in a pull request ?

Maybe

Start by auditing the repository's existing cryptographic dependencies and documenting where they are used; the issue does not name specific files or tests. Done means Coincurve replaces the relevant non-Windows dependencies, unit and Linux/macOS compatibility tests pass, and developer setup documentation is updated.