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

feat: add bitgert mainnet #2992

Merged
merged 1 commit into from
Nov 10, 2024
Merged

feat: add bitgert mainnet #2992

merged 1 commit into from
Nov 10, 2024

Conversation

Zhangnong
Copy link
Contributor

@Zhangnong Zhangnong commented Nov 9, 2024


PR-Codex overview

This PR focuses on adding support for the Bitgert Mainnet to the codebase, including its definitions and export in the appropriate files.

Detailed summary

  • Updated .changeset/five-geese-press.md to include a patch for viem and mention the addition of Bitgert Mainnet.
  • Exported bitgert from src/chains/index.ts.
  • Created bitgert chain definition in src/chains/definitions/bitgert.ts with relevant properties like id, name, nativeCurrency, rpcUrls, and blockExplorers.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Copy link

vercel bot commented Nov 9, 2024

@Zhangnong is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

changeset-bot bot commented Nov 9, 2024

🦋 Changeset detected

Latest commit: 78dcf9f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
viem Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@jxom jxom merged commit 49f7e08 into wevm:main Nov 10, 2024
21 of 35 checks passed
@github-actions github-actions bot mentioned this pull request Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants