Investigate the potential for rate limits on RPC providers due to the consolidation of outgoing requests through a smaller number of mixnet service providers. As the mixnet may support multiple clients, this consolidation increases the likelihood of exceeding rate limit or throttling thresholds. This issue may vary across different providers and blockchains. The goal is to understand the impact on our chosen providers, explore mitigation strategies, and, as relevant, provide an immediate solution appropriate for the characteristics of the currnet mixnet deployment phase. The solution may not be one-size fits all, as blockchains can vary and not all have subscribable RPC provider services, for example.
Assess how much of an issue this may be for providers we're using. For any published rate limits, document what they are.
Utilize a high-availability service such as GetBlock.io, which supports many multiple blockchains via a common API.
Consider management of private API keys for secure access.
Consider fallback providers for a given endpoint. For example, like this feature of the very popular Ethers(js) library.
Investigate the potential for rate limits on RPC providers due to the consolidation of outgoing requests through a smaller number of mixnet service providers. As the mixnet may support multiple clients, this consolidation increases the likelihood of exceeding rate limit or throttling thresholds. This issue may vary across different providers and blockchains. The goal is to understand the impact on our chosen providers, explore mitigation strategies, and, as relevant, provide an immediate solution appropriate for the characteristics of the currnet mixnet deployment phase. The solution may not be one-size fits all, as blockchains can vary and not all have subscribable RPC provider services, for example.