Drop Arbirum Sepolia Alchemy support #3726
Merged
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
Due to eth_getLogs usage from Subscape XP drop monitoring, the Alchemy endpoint for Taho had to be blocked completely. After a release that removed the log monitoring, we were still seeing very high usage of eth_getLogs, indicating small numbers of older installs were still causing issues. Here, we drop built-in Alchemy support for Taho. Instead, we use existing public RPCs to handle all requests. Because Alchemy was blanket blocking all RPC requests from Taho (due to the aforementioned eth_getLogs issue), transaction submission was completely blocked (because the serial fallback provider prefers Alchemy providers to all others when available). This new setup should allow for public RPCs to handle transaction submission (since there will no longer be an Alchemy provider) and thus unblock any trailing XP claims.
Merged
Shadowfiend
added a commit
that referenced
this pull request
Jan 22, 2024
## What's Changed * v0.55.0 by @xpaczka in #3720 * Drop Arbirum Sepolia Alchemy support by @Shadowfiend in #3726 * Alchemy API key has changed to phase out the older API key that was having Arbitrum Sepolia load issues. **Full Changelog**: v0.55.0...v0.56.0 Latest build: [extension-builds-3729](https://github.com/tahowallet/extension/suites/19956250425/artifacts/1182217763) (as of Fri, 19 Jan 2024 22:10:22 GMT).
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.
Due to eth_getLogs usage from Subscape XP drop monitoring, the Alchemy endpoint for Taho had to be blocked completely. After a release that removed the log monitoring, we were still seeing very high usage of eth_getLogs, indicating small numbers of older installs were still causing issues.
Here, we drop built-in Alchemy support for Taho. Instead, we use existing public RPCs to handle all requests. Because Alchemy was blanket blocking all RPC requests from Taho (due to the aforementioned eth_getLogs issue), transaction submission was completely blocked (because the serial fallback provider prefers Alchemy providers to all others when available). This new setup should allow for public RPCs to handle transaction submission (since there will no longer be an Alchemy provider) and thus unblock any trailing XP claims.
Latest build: extension-builds-3726 (as of Wed, 17 Jan 2024 01:24:05 GMT).