chore: add data for Polygon go-live

[lumtis]

Summary by CodeRabbit

• New Features

  • Added support for the Polygon mainnet in the Zeta Protocol, enhancing network flexibility.
  • Introduced new constants for Polygon mainnet configurations in the SALT_NUMBERS object.

• Dependency Updates

  • Updated the @zetachain/networks package to version ^9.0.0, bringing new features and improvements.

[coderabbitai]

Walkthrough

The recent changes enhance the ZetaProtocolMainNetwork by adding support for the Polygon mainnet, expanding the flexibility of the protocol. This update includes modifications to type and array declarations in the lib/address.tools.ts file and introduces new constants for Polygon in lib/contracts.constants.ts. Additionally, the @zetachain/networks package version has been updated to ensure access to the latest features. Overall, these adjustments improve compatibility and functionality across multiple blockchain networks.

Changes

Files	Change Summary
lib/address.tools.ts	Expanded ZetaProtocolMainNetwork to include polygon_mainnet; updated zetaProtocolMainNetworks array.
lib/contracts.constants.ts	Added polygon_mainnet to SALT_NUMBERS with properties for configuration, enhancing support for Polygon.
package.json	Updated @zetachain/networks package version from ^8.0.0 to ^9.0.0 for new features and improvements.

Poem

In the fields of code we hop,
New networks bloom, no need to stop.
Polygon joins the playful race,
With zeta dreams in cyberspace.
Burrows deep, we build and cheer,
For every change that brings us near! 🐇✨

---

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
• Mastodon
• Reddit
• LinkedIn

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.10%. Comparing base (2ea8f56) to head (971ad5c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #246   +/-   ##
=======================================
  Coverage   58.10%   58.10%           
=======================================
  Files          16       16           
  Lines         401      401           
  Branches       28       28           
=======================================
  Hits          233      233           
  Misses        165      165           
  Partials        3        3           

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b921999 and 9240486.

Files ignored due to path filters (2)

• data/addresses.mainnet.json is excluded by !data/**
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (3)

• lib/address.tools.ts (1 hunks)
• lib/contracts.constants.ts (1 hunks)
• package.json (1 hunks)

Additional comments not posted (4)

lib/contracts.constants.ts (1)

9-14: LGTM! The addition of the polygon_mainnet constant is consistent.

The properties for polygon_mainnet are initialized correctly.

lib/address.tools.ts (2)

69-69: LGTM! The addition of polygon_mainnet to the ZetaProtocolMainNetwork type is consistent.

The type declaration is updated correctly.

---

70-70: LGTM! The addition of polygon_mainnet to the zetaProtocolMainNetworks array is consistent.

The array is updated correctly.

package.json (1)

29-29: LGTM! The update of @zetachain/networks package version is consistent.

The dependency version is updated correctly.

[skosito]

@lumtis i think some parts are included on main, eg. package is updated, but approved