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

feat(contracts): parse validator indexes as arrays from solidity #120

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

merklefruit
Copy link
Collaborator

@merklefruit merklefruit commented Jul 5, 2024

Replicates the rust functionality added in #119, but in Solidity for registering on-chain.
Testing this soon with registration of our validators on Helder.

UPDATE: the script worked and allowed me to register 100 validators using the provided range.

Summary by CodeRabbit

  • New Features

    • Enhanced the RegisterValidators contract to process validator indexes more efficiently using a new library for string-to-uint256 conversion.
    • Introduced the StringToUintArrayLib library with the fromStr function to convert strings of validator indexes into uint256 arrays.
  • Tests

    • Added tests for the StringToUintArrayLib to validate its functionality in converting strings to arrays of uint256.

Copy link
Contributor

coderabbitai bot commented Jul 5, 2024

Walkthrough

The RegisterValidators contract has been improved by using the StringToUintArrayLib library to convert a string of validator indexes into a uint256 array. This makes the registration process with the Bolt registry more efficient. Additionally, tests were introduced to validate the new string parsing functionality.

Changes

Files Change Summary
bolt-contracts/script/RegisterValidators.s.sol Introduced StringToUintArrayLib for converting string indexes to uint256, improving registration process.
bolt-contracts/test/StringToUintArrayLib.t.sol Created new test file containing functions to validate StringToUintArrayLib.fromStr() method.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RegisterValidators
    participant StringToUintArrayLib
    participant BoltRegistry

    User ->> RegisterValidators: call run()
    RegisterValidators ->> RegisterValidators: Fetch validatorIndexes
    RegisterValidators ->> StringToUintArrayLib: Convert string to uint256 array
    StringToUintArrayLib ->> RegisterValidators: Return uint256 array
    RegisterValidators ->> BoltRegistry: Register validators using uint256 array
    BoltRegistry ->> RegisterValidators: Acknowledge registration
    RegisterValidators ->> User: Registration complete
Loading

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@merklefruit merklefruit changed the title feat: parse validator indexes as arrays from solidity feat(contracts): parse validator indexes as arrays from solidity Jul 5, 2024
@merklefruit merklefruit marked this pull request as ready for review July 5, 2024 12:49
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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 1cb16f3 and d9c722a.

Files selected for processing (2)
  • bolt-contracts/script/RegisterValidators.s.sol (3 hunks)
  • bolt-contracts/test/StringToUintArrayLib.t.sol (1 hunks)
Additional comments not posted (9)
bolt-contracts/test/StringToUintArrayLib.t.sol (6)

9-9: LGTM!

The setUp function is currently empty but can be used for future setup code.


11-23: LGTM!

The test correctly verifies the parsing of a simple comma-separated string of indexes.


25-37: LGTM!

The test correctly verifies the parsing of a range string of indexes.


39-54: LGTM!

The test correctly verifies the parsing of a combination of ranges and individual values.


56-71: LGTM!

The test correctly verifies the parsing of a more complex combination of ranges and individual values.


73-81: LGTM!

The test correctly verifies the parsing of a large range of indexes.

bolt-contracts/script/RegisterValidators.s.sol (3)

13-13: LGTM!

The using directive correctly imports the StringToUintArrayLib library.


54-112: LGTM!

The fromStr method correctly parses a string into an array of uint256 values, including handling ranges.


20-24: LGTM! But verify the function usage in the codebase.

The code changes are approved.

However, ensure that all function calls to run match the new logic.

Verification successful

Verified the function usage in the codebase.

The run function in RegisterValidators.s.sol includes the new logic and is consistent with the changes. The run function in DeployRegistry.s.sol is unrelated and does not require any changes.

  • bolt-contracts/script/RegisterValidators.s.sol: run function includes the new logic.
  • bolt-contracts/script/DeployRegistry.s.sol: run function is unrelated to the changes.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `run` match the new logic.

# Test: Search for the function usage. Expect: Only occurances of the new logic.
rg --type solidity $'run'

Length of output: 57


Script:

#!/bin/bash
# Description: Verify all function calls to `run` match the new logic.

# Test: Search for the function usage. Expect: Only occurrences of the new logic.
rg 'run' --glob '*.sol'

Length of output: 169


Script:

#!/bin/bash
# Extract the `run` function implementation from RegisterValidators.s.sol
ast-grep --lang solidity --pattern $'function run() public {
  $$$
}' bolt-contracts/script/RegisterValidators.s.sol

# Extract the `run` function implementation from DeployRegistry.s.sol
ast-grep --lang solidity --pattern $'function run() public {
  $$$
}' bolt-contracts/script/DeployRegistry.s.sol

Length of output: 465


Script:

#!/bin/bash
# Extract the `run` function implementation from RegisterValidators.s.sol
sed -n '/function run() public {/,/^}/p' bolt-contracts/script/RegisterValidators.s.sol

# Extract the `run` function implementation from DeployRegistry.s.sol
sed -n '/function run() public {/,/^}/p' bolt-contracts/script/DeployRegistry.s.sol

Length of output: 1647

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: 2

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between d9c722a and ea73098.

Files selected for processing (1)
  • bolt-contracts/script/RegisterValidators.s.sol (3 hunks)

@merklefruit merklefruit merged commit 721ffd7 into unstable Jul 11, 2024
@merklefruit merklefruit deleted the feat/val-index-solidity branch July 11, 2024 10:24
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.

1 participant