Updated to v9.7 and getChainConfig #1335
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
10 Skipped Deployments
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
This update is necessary to ensure all Web3Auth examples remain compatible with the latest blockchain network specifications and security standards. By implementing chain-specific configurations, we improve the developer experience by providing optimized setups for each blockchain type (EVM, Solana, XRPL).
This work directly supports our goal of providing plug-and-play examples that demonstrate best practices for Web3Auth integration across multiple blockchain networks.
Jira Link: DEVREL-1167
Description
This PR includes several important updates to our Web3Auth examples:
These updates ensure our examples are using the most current and secure versions of all dependencies while providing proper chain-specific configurations for better compatibility and functionality.
How has this been tested?
All examples were tested individually after the updates to ensure they function correctly with the new dependency versions and chain-specific configurations. Testing was performed on:
Screenshots (if appropriate):
N/A
Types of changes
Checklist: