Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dilithium submodule to latest changes #5131

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Xtinc-T
Copy link

@Xtinc-T Xtinc-T commented Sep 13, 2024

High Level Overview of Change

This change integrates the Dilithium library as a submodule within the external folder. It enhances the modularity of the API to support different types of Dilithium. The CMake configuration has been updated to utilize Dilithium alongside existing cryptographic libraries, and Dilithium2 has been added as a library in the conanfile.

Context of Change

The integration of Dilithium aims to improve the cryptographic capabilities of the project by providing modular support for various types of Dilithium. This change ensures that the project can leverage Dilithium in conjunction with other cryptographic libraries like secp256k1 and ed25519-donna.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Performance (increase or change in throughput and/or latency)
  • Tests (you added tests for code that already exists, or your new feature included in this PR)
  • Documentation update
  • Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
  • Release

API Impact

  • Public API: New feature (new methods and/or new fields)
  • Public API: Breaking change (in general, breaking changes should only impact the next api_version)
  • libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
  • Peer protocol change (must be backward compatible or bump the peer protocol version)

@dangell7
Copy link
Collaborator

Looks good so far I would make the PR into your own develop branch though or make this a draft as its not ready yet.

@Xtinc-T
Copy link
Author

Xtinc-T commented Sep 14, 2024

@dangell7 Yes youre right. It was by accident yesterday. I have created a fork of develop and created an upstream branch to push my changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants