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

Deploy RFQ to Base #2397

Merged
merged 2 commits into from
Apr 1, 2024
Merged

Deploy RFQ to Base #2397

merged 2 commits into from
Apr 1, 2024

Conversation

aureliusbtc
Copy link
Contributor

@aureliusbtc aureliusbtc commented Mar 29, 2024

Description
A clear and concise description of the features you're adding in this pull request.

Additional context
Add any other context about the problem you're solving.

Metadata

  • Fixes #[Link to Issue]

Summary by CodeRabbit

  • New Features
    • Introduced a new blockchain network with chain ID 8453.
    • Added a FastBridge smart contract for bridging transactions across chains with various features.
    • Enhanced the network setup and smart contract deployment processes with new configuration and deployment scripts for the base network.

Copy link
Contributor

coderabbitai bot commented Mar 29, 2024

Walkthrough

The recent update introduces a new base configuration for RPC and verifier settings across various scripts in the contracts-rfq package. These changes enhance the network setup and deployment process for the base network.

Changes

Files Change Summary
foundry.toml, .../fb-config.sh, .../fb-deploy.sh Added a new base configuration for RPC and verifier settings in foundry.toml, updated configuration script invocation in fb-config.sh, and included a new deployment command for the base network in fb-deploy.sh.

"In the digital meadows, under the byte-sized sun,
A rabbit hopped, with code it spun.
Across the chains, it built a bridge, so wide,
Where transactions flow, from side to side.
🌉✨ With each hop, it proudly said,
'Let's connect the world, no chain left unread.'"

  • 🐰 CodeRabbit

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

codecov bot commented Mar 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.93412%. Comparing base (6e47707) to head (aacabd2).
Report is 14 commits behind head on master.

Additional details and impacted files
@@                 Coverage Diff                 @@
##              master       #2397         +/-   ##
===================================================
+ Coverage   46.88083%   46.93412%   +0.05328%     
===================================================
  Files            399         389         -10     
  Lines          30569       29388       -1181     
  Branches          83         132         +49     
===================================================
- Hits           14331       13793        -538     
+ Misses         14707       14133        -574     
+ Partials        1531        1462         -69     
Flag Coverage Δ
cctp-relayer ?
promexporter ?
solidity 53.76344% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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 Status

Configuration used: .coderabbit.yaml

Commits Files that changed from the base of the PR and between 3b91887 and 4638ec7.
Files selected for processing (5)
  • packages/contracts-rfq/deployments/base/.chainId (1 hunks)
  • packages/contracts-rfq/deployments/base/FastBridge.json (1 hunks)
  • packages/contracts-rfq/foundry.toml (1 hunks)
  • packages/contracts-rfq/script/fb-config.sh (1 hunks)
  • packages/contracts-rfq/script/fb-deploy.sh (1 hunks)
Additional Context Used
Additional comments not posted (5)
packages/contracts-rfq/deployments/base/.chainId (1)

1-1: The chain ID 8453 is set correctly for the base network deployment. Ensure this aligns with the network specifications and intended deployment targets.

packages/contracts-rfq/script/fb-deploy.sh (1)

19-19: The deployment command for the "base" network is correctly added. Consider enhancing the script with error handling for the deployment command to ensure smooth operation and adding comments for clarity on the usage and purpose of this specific deployment command.

packages/contracts-rfq/script/fb-config.sh (1)

20-20: The configuration command for the "base" network is correctly added. Similar to the deployment script, consider adding error handling for this configuration command and documenting its purpose and usage for better maintainability and clarity.

packages/contracts-rfq/foundry.toml (1)

23-23: The addition of base network configurations for RPC and verifier settings in foundry.toml is correctly implemented. Ensure that the environment variables ${BASE_RPC}, ${BASE_VERIFIER_KEY}, and ${BASE_VERIFIER_URL} are correctly set in the deployment environment for successful integration.

Also applies to: 29-29

packages/contracts-rfq/deployments/base/FastBridge.json (1)

1-1219: The FastBridge.json file is correctly structured, including the smart contract's address, constructor arguments, and a comprehensive ABI. Ensure to verify the ABI against the smart contract's source code for completeness and correctness, especially for critical functionalities like bridging and role management.

Copy link

cloudflare-workers-and-pages bot commented Mar 29, 2024

Deploying sanguine-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: aacabd2
Status: ✅  Deploy successful!
Preview URL: https://265baa08.sanguine-fe.pages.dev
Branch Preview URL: https://base-rfq.sanguine-fe.pages.dev

View logs

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 Status

Configuration used: .coderabbit.yaml

Commits Files that changed from the base of the PR and between 4638ec7 and 47b22f3547bb967bf4becdadf0ed0328656bf1ec.
Files selected for processing (1)
  • packages/contracts-rfq/foundry.toml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • packages/contracts-rfq/foundry.toml
Additional Context Used

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 Status

Configuration used: .coderabbit.yaml

Commits Files that changed from the base of the PR and between 4638ec7 and aacabd2.
Files selected for processing (3)
  • packages/contracts-rfq/foundry.toml (1 hunks)
  • packages/contracts-rfq/script/fb-config.sh (1 hunks)
  • packages/contracts-rfq/script/fb-deploy.sh (1 hunks)
Files skipped from review as they are similar to previous changes (3)
  • packages/contracts-rfq/foundry.toml
  • packages/contracts-rfq/script/fb-config.sh
  • packages/contracts-rfq/script/fb-deploy.sh
Additional Context Used

@trajan0x trajan0x merged commit b73538e into master Apr 1, 2024
49 of 51 checks passed
@trajan0x trajan0x deleted the base/rfq branch April 1, 2024 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants