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 the default signing algorithm to ed25519 #2658

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

ckeshava
Copy link
Collaborator

@ckeshava ckeshava commented Mar 7, 2024

High Level Overview of Change

If no signing algorithm is specified, use ed25519. At the moment, the code uses secp256k1. This causes incoherence between the fromSeed and generateSeed functions because they use different defaults.

Note: This change causes breakage in downstream classes like Account

Context of Change

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)
  • Tests (You added tests for code that already exists, or your new feature included in this PR)
  • Documentation Updates
  • Release

Did you update HISTORY.md?

  • Yes
  • No, this change does not impact library users

Test Plan

The current unit tests have been updated to use new values.

@ckniffen
Copy link
Collaborator

ckniffen commented Mar 7, 2024

You should add a way to supply algorithm in secret numbers. Also this should be a major release for some of the packages.

@ckeshava
Copy link
Collaborator Author

ckeshava commented Mar 7, 2024

@ckniffen Are you suggesting that I add an algorithm data member to the Account class? I don't see any other relevant classes in the secret-numbers package.

I agree that this change needs to wait for a major revision of the packages.

@mvadari
Copy link
Collaborator

mvadari commented Mar 8, 2024

Does this count as a breaking change?

@ckniffen
Copy link
Collaborator

ckniffen commented Mar 8, 2024

@ckniffen Are you suggesting that I add an algorithm data member to the Account class? I don't see any other relevant classes in the secret-numbers package.

I agree that this change needs to wait for a major revision of the packages.

Yes the reason being is if you have your secret numbers recorded from a previous account generation it will now not be possbile to generate the same wallet again.

@ckeshava
Copy link
Collaborator Author

ckeshava commented Mar 9, 2024

The default signing algorithm of rippled's wallet_propose method is secp256k1 (Docs: https://xrpl.org/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose)

Why do we have this discrepancy (the defaults for JS client library is ed25519) ?

I saw a note about the inability of rippled command line to generate ed25519 keys, but I don't believe that would have influenced the choice of defaults

@@ -7,6 +7,9 @@ import {
secretToEntropy,
} from '../utils'

// TODO: preferably import this type from ripple-keypairs
// import type { Algorithm } from 'ripple-keypairs'
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Module '"ripple-keypairs"' declares 'Algorithm' locally, but it is not exported. ts(2459)
index.d.ts(2, 15): 'Algorithm' is declared here.

I tried to import the Algorithm type from ripple-keypairs, but I get the above error.
I'm confused, Algorithm is exported here:

export type Algorithm = 'ecdsa-secp256k1' | 'ed25519'

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, updated in
c25d871

@ckeshava
Copy link
Collaborator Author

@ckniffen I have added the algorithm data member in this commit: a234fa9

Please review at your convenience

@justinr1234
Copy link
Collaborator

@ckeshava please fix lint errors and rebase

@mvadari
Copy link
Collaborator

mvadari commented Apr 7, 2024

If this is a breaking change, it needs to wait for a major version bump.

@ckeshava ckeshava requested review from ckniffen and khancode May 8, 2024 20:32
@khancode
Copy link
Collaborator

khancode commented May 8, 2024

If this is a breaking change, it needs to wait for a major version bump.

We could release this with rippled v2 client library support as that will also require a major version bump.

@@ -38,7 +38,7 @@ function generateSeed(
const entropy = options.entropy
? options.entropy.slice(0, 16)
: randomBytes(16)
const type = options.algorithm === 'ed25519' ? 'ed25519' : 'secp256k1'
const type = options.algorithm === 'ecdsa-secp256k1' ? 'secp256k1' : 'ed25519'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be tested against the enum?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 24 should use the enum too for the key

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've lost some of the context here. Which enum are you referring to?
In line 24, I'm using secp256k1 imported from './signing-schemes/secp256k1'

Are you referring to that import?

@justinr1234
Copy link
Collaborator

@CodeRabbit full review

@justinr1234
Copy link
Collaborator

@coderabbitai full review

Copy link

coderabbitai bot commented Sep 19, 2024

Actions performed

Full review triggered.

Copy link

coderabbitai bot commented Sep 19, 2024

Warning

Rate limit exceeded

@justinr1234 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 29 minutes and 56 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 3858a09 and 787ff55.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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.

5 participants