open-ibc / vibc-core-smart-contracts

Apache License 2.0
29 stars 23 forks source link

Low Hanging Gas Optimizations #224

Open RnkSngh opened 1 month ago

RnkSngh commented 1 month ago

Pr to remove the unused ackpacket commitment mapping from dispatcher.

This mapping was originally included for async acks, but adds gas cost of an SLOAD, so we've decided to get rid of it for now

Note: The writeAckPacket event is still emitted, so peptide integration should be unimpacted

Summary by CodeRabbit

coderabbitai[bot] commented 1 month ago

Walkthrough

The pull request introduces significant modifications to the Dispatcher.sol contract, particularly in its internal logic and state management. The _ackPacketCommitment mapping has been removed, simplifying acknowledgment packet tracking. Corresponding checks in the recvPacket function have also been eliminated, streamlining packet handling. Additionally, a placeholder timeout function indicates ongoing development in timeout management. In the Dispatcher.base.t.sol test file, a new state variable enhances code clarity by replacing a hardcoded value, along with minor formatting adjustments.

Changes

File Change Summary
contracts/core/Dispatcher.sol - Removed _ackPacketCommitment mapping.
- Removed related checks in recvPacket.
- timeout function is a placeholder.
test/utils/Dispatcher.base.t.sol - Added uint32 CHANNEL_ID_TO_CONNECTION_STARTING_SLOT = 258;.
- Replaced hardcoded value 259 in _storeChannelidToConnectionMapping with the new variable.
- Minor formatting adjustments.

Possibly related PRs

Poem

🐰 In the code where packets flow,
A change was made, a simpler show.
No more tracking, just let it be,
A clearer path for you and me.
With constants bright, the code does gleam,
A rabbit's hop, a coder's dream! ✨


📜 Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
📥 Commits Files that changed from the base of the PR and between 9748cb41d67625412d0d689a79c7c867b470ef17 and bac76783cb27faf73ab33a41bb1ee5cd5f331e5e.
📒 Files selected for processing (2) * contracts/core/Dispatcher.sol (0 hunks) * test/utils/Dispatcher.base.t.sol (2 hunks)
💤 Files with no reviewable changes (1) * contracts/core/Dispatcher.sol
🧰 Additional context used
🔇 Additional comments (3)
test/utils/Dispatcher.base.t.sol (3)
`58-58`: **LGTM: New constant improves code clarity** The addition of `CHANNEL_ID_TO_CONNECTION_STARTING_SLOT` as a named constant is a good practice. It replaces a magic number with a descriptive variable name, enhancing code readability and maintainability. --- `273-273`: **LGTM: Consistent use of the new constant** The modification in `_storeChannelidToConnectionMapping` correctly utilizes the newly added `CHANNEL_ID_TO_CONNECTION_STARTING_SLOT` constant. This change enhances code consistency and reduces the risk of errors associated with hardcoded values. --- Line range hint `1-314`: **Overall assessment: Changes improve code quality** The modifications in this file, while minimal, contribute to better code quality by introducing a named constant and using it consistently. These changes align with good coding practices and likely support the larger goal of removing the ack packet commitment mapping as mentioned in the PR objectives. However, to ensure completeness: Let's verify if there are any remaining references to the ack packet commitment mapping in this file:
✅ Verification successful Let's rerun the search without specifying the file type to check for any remaining references to `ackPacketCommitment`: --- **Verified:** No remaining references to `ackPacketCommitment` found in `test/utils/Dispatcher.base.t.sol`.
🏁 Scripts executed The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Search for any remaining references to ack packet commitment rg --type sol "ackPacketCommitment" test/utils/Dispatcher.base.t.sol ``` Length of output: 96 --- Script: ```shell #!/bin/bash # Search for any remaining references to ackPacketCommitment without specifying file type rg "ackPacketCommitment" test/utils/Dispatcher.base.t.sol ``` Length of output: 57
--- 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 - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.