Repository navigation
docs(guides): lava public node is gone, show how to use a Lava API key - #1726
Merged
Merged
Conversation
The Lava public node for Mainnet (`rpc.starknet.lava.build`) is discontinued: it now answers HTTP 410. To use Lava, a free account on gateway.lavanet.xyz is now needed to get an API key. With a key, Lava picks a node from a pool for each request, so the RPC version can change between two requests (0.8.1, 0.9.0 and 0.10.3 were seen). Ending the URL with `/rpc/v0_9` fixes the version to 0.9.0 (35 requests out of 35). `/rpc/v0_10` is ignored by Lava. Changes in the provider guide: the Lava row of the Mainnet table, the Mainnet example (public node removed, `/rpc/v0_9` added) and the note under the tables.
This file contains hidden or 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
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 Resolution
The provider guide showed a public Lava node for Mainnet. It is discontinued (HTTP 410): Lava now needs a free account to get an API key.
With a key, Lava picks a node from a pool for each request, so the RPC version changes (10 requests without ending: 0.8.1 seven times, 0.9.0 twice, 0.10.3 once). Ending the URL with
/rpc/v0_9fixes the version (35 requests out of 35 gave 0.9.0)./rpc/v0_10is ignored by Lava. Starknet.js v11 handles only RPC 0.9 and 0.10, so a URL without ending would fail most of the time.Lava on Sepolia is not tested, its line in the guide is unchanged.
RPC version (if applicable)
Not applicable, documentation only.
Usage related changes
/rpc/v0_9added) and the note under the tables are updated.Development related changes
Checklist: