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

Update - Tx Boost URL to non-alpha, OKX wallet available on all devices #1901

Merged
merged 3 commits into from
Sep 7, 2023

Conversation

Adamj1232
Copy link
Member

Description

Update the Tx_boost (transaction protection) to the non-alpha url
Update OKX wallet to be available on all devices - Closes: #1900

Checklist

  • Increment the version field in package.json of the package you have made changes in following semantic versioning and using alpha release tagging
  • Check the box that allows repo maintainers to update this PR
  • Test locally to make sure this feature/fix works
  • Run yarn check-all to confirm there are not any associated errors
  • Confirm this PR passes Circle CI checks
  • Add or update relevant information in the documentation

@Adamj1232 Adamj1232 changed the title Update - tx boost url to non-alpha Update - Tx Boost URL to non-alpha, OKX wallet available on all devices Sep 6, 2023
Copy link
Member

@cmeisl cmeisl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved with question on rpcUrl description

@@ -156,15 +156,15 @@ type Chain = {
namespace?: 'evm' // string indicating chain namespace. Defaults to 'evm' but will allow other chain namespaces in the future
// PLEASE NOTE: Some wallets require an rpcUrl, label, and token for actions such as adding a new chain.
// It is recommended to include rpcUrl, label, and token for full functionality.
rpcUrl?: string // Recommended to include. Used for network requests.
rpcUrl?: string // Recommended to include. Used for network requests (eg Alchemy or Infura end point).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are other companies specifically called out? Are devs confused by what this value should be?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note was originally made to the core README was made in response to a pull request by Alchemy. It provides clarity that Alchemy's RPC can be used as an alternative to Infura in our examples. Rather than adding Alchemy's RPC to all examples and quickstarts, we wanted users to know that both Alchemy and Infura are valid RPC providers for W3O, ensuring flexibility and provider-agnostic compatibility. I updated the whole Chain type here to ensure they were aligned.

@Adamj1232 Adamj1232 merged commit 5b8f9df into develop Sep 7, 2023
2 checks passed
@Adamj1232 Adamj1232 deleted the update/tx_boost_url branch September 7, 2023 18:32
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.

otherProviderFlagsExist for metamask is unnecessary
2 participants