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

refactor(crypto): add check in multisig verification #23395

Merged
merged 7 commits into from
Jan 17, 2025

Conversation

tac0turtle
Copy link
Member

@tac0turtle tac0turtle commented Jan 15, 2025

Description

this pr adds an extra check to multisig verification. this puts a requirement that all multisigs follow the below ruleset N > M and M > 0


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Enhanced multisignature validation with stricter threshold and key count checks.
    • Improved functionality for creating and managing multisignature accounts.
  • Tests

    • Added comprehensive test cases for multisignature verification rules, covering various key and threshold scenarios.
  • Bug Fixes

    • Improved error handling in the multisignature verification process to prevent invalid signature configurations.

Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

📝 Walkthrough

Walkthrough

The pull request introduces enhanced validation checks in the VerifyMultisignature method of the LegacyAminoPubKey struct. Two validation conditions are added: ensuring the threshold is greater than zero and verifying that the number of public keys exceeds the threshold. Additionally, a new test function is introduced to validate these conditions, and existing tests are updated to reflect changes in multisignature configurations. These modifications enhance the error handling and testing framework related to multisignature accounts.

Changes

File Change Summary
crypto/keys/multisig/multisig.go Added validation checks in VerifyMultisignature method to ensure threshold is greater than zero and public key count exceeds threshold.
crypto/keys/multisig/multisig_test.go Added new test function TestVerifyMultisignatureNMRule to validate multisignature verification logic; updated existing test functions to reflect changes in public key and multisignature configurations.
tests/integration/auth/client/cli/suite_test.go Modified multisig key creation logic to include three public keys and updated key management functionality.

Possibly related PRs

Suggested reviewers

  • sontrinh16
  • testinginprod
  • aaronc
  • julienrbrt

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9ff21ac and 8c9c3a2.

📒 Files selected for processing (1)
  • tests/integration/auth/client/cli/suite_test.go (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
tests/integration/auth/client/cli/suite_test.go (3)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern tests/**/*: "Assess the integration and e2e test code assessing sufficient code coverage for the changes associated in the pull request"


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: tests (00)
  • GitHub Check: test-system-v2
  • GitHub Check: Analyze
  • GitHub Check: Summary
🔇 Additional comments (2)
tests/integration/auth/client/cli/suite_test.go (2)

88-89: LGTM! Proper error handling for public key retrieval.

The public key retrieval is implemented with appropriate error handling.


107-108: LGTM! Well-structured multisig configuration.

The 2-of-3 multisig setup follows best practices:

  • Clear descriptive comment
  • Valid threshold (2 > 0 and 2 < 3)
  • Proper use of the NewLegacyAminoPubKey constructor

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

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.

@tac0turtle tac0turtle marked this pull request as ready for review January 15, 2025 14:58
@tac0turtle tac0turtle added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Jan 15, 2025
@tac0turtle tac0turtle changed the title chore(crypto): add check in verification chore(crypto): add check in multisig verification Jan 15, 2025
@julienrbrt julienrbrt changed the title chore(crypto): add check in multisig verification refactor(crypto): add check in multisig verification Jan 17, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9ed34d0 and 9ff21ac.

📒 Files selected for processing (2)
  • crypto/keys/multisig/multisig_test.go (4 hunks)
  • tests/integration/auth/client/cli/suite_test.go (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • crypto/keys/multisig/multisig_test.go
🧰 Additional context used
📓 Path-based instructions (1)
tests/integration/auth/client/cli/suite_test.go (3)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern tests/**/*: "Assess the integration and e2e test code assessing sufficient code coverage for the changes associated in the pull request"


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

🪛 golangci-lint (1.62.2)
tests/integration/auth/client/cli/suite_test.go

90-90: Error return value of kb.SaveOfflineKey is not checked

(errcheck)

🪛 GitHub Actions: Tests / Code Coverage
tests/integration/auth/client/cli/suite_test.go

[error] 521-954: Multiple test failures due to 'cannot sign with offline keys' error in TestCLITestSuite


[warning] Low test coverage: 4.1% of statements

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: test-system-v2
  • GitHub Check: Analyze
  • GitHub Check: Summary
🔇 Additional comments (2)
tests/integration/auth/client/cli/suite_test.go (2)

108-109: LGTM! Good test coverage for N > M validation.

The 2-of-3 multisig configuration provides a good test case for validating the N > M rule, where N (number of keys = 3) is greater than M (threshold = 2).

🧰 Tools
🪛 GitHub Actions: Tests / Code Coverage

[warning] Low test coverage: 4.1% of statements


Line range hint 1-954: Address test failures and improve test coverage.

  1. Multiple test failures are occurring with the error 'cannot sign with offline keys'. This needs investigation and fixing.
  2. The test coverage is very low at 4.1%. Consider adding more test cases to improve coverage.

Run this script to help identify the failing test cases:

🧰 Tools
🪛 golangci-lint (1.62.2)

90-90: Error return value of kb.SaveOfflineKey is not checked

(errcheck)

🪛 GitHub Actions: Tests / Code Coverage

[warning] Low test coverage: 4.1% of statements

Comment on lines 88 to 90
pub, err := valAcc.GetPubKey()
s.Require().NoError(err)
kb.SaveOfflineKey("newAccount", pub)
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add error handling for SaveOfflineKey.

The error returned by kb.SaveOfflineKey should be checked for consistency with the error handling pattern used throughout the test suite.

 pub, err := valAcc.GetPubKey()
 s.Require().NoError(err)
-kb.SaveOfflineKey("newAccount", pub)
+err = kb.SaveOfflineKey("newAccount", pub)
+s.Require().NoError(err)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
pub, err := valAcc.GetPubKey()
s.Require().NoError(err)
kb.SaveOfflineKey("newAccount", pub)
pub, err := valAcc.GetPubKey()
s.Require().NoError(err)
err = kb.SaveOfflineKey("newAccount", pub)
s.Require().NoError(err)
🧰 Tools
🪛 golangci-lint (1.62.2)

90-90: Error return value of kb.SaveOfflineKey is not checked

(errcheck)

🪛 GitHub Actions: Tests / Code Coverage

[warning] Low test coverage: 4.1% of statements

@tac0turtle tac0turtle added this pull request to the merge queue Jan 17, 2025
Merged via the queue into main with commit 642e881 Jan 17, 2025
70 of 71 checks passed
@tac0turtle tac0turtle deleted the marko/multisig_fix branch January 17, 2025 12:38
mergify bot pushed a commit that referenced this pull request Jan 17, 2025
Co-authored-by: Alex | Interchain Labs <[email protected]>
(cherry picked from commit 642e881)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants