Closed parodime closed 2 months ago
[!WARNING]
Rate limit exceeded
@parodime has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 47 seconds before requesting another review.
:hourglass: 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.:vertical_traffic_light: 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](https://coderabbit.ai/docs/faq) for further information.:inbox_tray: Commits
Files that changed from the base of the PR and between 594a48cf8df1cfd60d353071bd6b9f5a8fffc9bb and bcdb2585955f973de5d59da8d39a7b8ca0643fe6.
The changes in this pull request involve modifications to the prove
function within the FastBridgeV2
contract, specifically altering its parameter handling and processing logic. The external prove
function now accepts a bytes32 transactionId
instead of a bytes memory request
, enhancing clarity in its responsibilities. Additionally, the test suite for FastBridgeV2
has been expanded to include various scenarios related to the new prove
functionality, ensuring comprehensive coverage and validation of the contract's behavior.
File | Change Summary |
---|---|
packages/contracts-rfq/contracts/FastBridgeV2.sol |
Updated prove function signatures to replace bytes memory request with bytes32 transactionId . |
packages/contracts-rfq/test/FastBridgeV2.Src.t.sol |
Added new tests for the prove function, including overloads and various scenarios for transaction proving. |
prove
function in the FastBridgeV2
contract, which directly relates to the changes made in the main PR regarding the prove
function's parameter handling and signature updates.go
, size/xs
, needs-go-generate-services/rfq
In the meadow where bunnies play,
A change in code brightens the day.
WithtransactionId
now in sight,
The contract's logic feels just right.
Hops of joy, we dance and cheer,
For clearer paths, we hold so dear! 🐰✨
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?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 38.45493%. Comparing base (
2e808e6
) to head (bcdb258
). Report is 3 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Latest commit: |
bcdb258
|
Status: | ✅ Deploy successful! |
Preview URL: | https://636fc7d8.sanguine-fe.pages.dev |
Branch Preview URL: | https://feat-fbv2-provewithtxid.sanguine-fe.pages.dev |
Generated at commit: 7a239b53c0a70aa76fd944c2036a09e8c2e528ac, compared to commit: 2e808e6414be03d63c1d6785ef4ce9b1c64a4775
Contract | Method | Avg (+/-) | % |
---|---|---|---|
FastBridgeV2 | bridgeProofs | -87 ✅ | -12.61% |
Description
Current implementation of
prove
doesn’t do anything with the providedbytes request
, except for hashing it to derivetransactionId
. New functions should taketransactionId
directly, skipping this step on-chain:prove(bytes32 transactionId, bytes32 destTxHash)
prove(bytes memory request, bytes32 desTtxHash)
prove(bytes32 transactionId, bytes32 destTxHash, address relayer)
prove(bytes memory request, bytes32 desTtxHash, address relayer)
prove(bytes memory request, bytes32 desTtxHash, address relayer)
(added as per [Different EOA prove/claim](https://www.notion.so/Different-EOA-prove-claim-bf86ed4547174dabba20774a3882f580?pvs=21))Summary by CodeRabbit
New Features
prove
function to enhance clarity and efficiency by changing the input parameter fromrequest
totransactionId
.prove
functionality under various conditions, including self-proving and dispute handling.Bug Fixes
prove
function to separate concerns, enhancing overall functionality.