Open RnkSngh opened 1 month ago
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.
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. |
Dispatcher
contract's ownership model and initialization methods._channelIdToConnection
mapping in related functions, aligning with acknowledgment handling simplifications.skipAck
option in the Dispatcher
contract, related to acknowledgment management changes.🐰 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! ✨
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
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 unimpactedSummary by CodeRabbit
New Features
Bug Fixes
Documentation