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

docs: mention Nethermind as rpc provider #39

Merged
merged 1 commit into from
Sep 25, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion book/src/providers.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Currently, two providers are supported: [JSON-RPC](#json-rpc) and the [sequencer
Starkli is centric around JSON-RPC, and the JSON-RPC provider is considered canonical. Users are strongly recommended to use JSON-RPC. There are a few options to obtain access to a JSON-RPC endpoint:

- hosting your own node with [`pathfinder`](https://github.com/eqlabs/pathfinder) or [`juno`](https://github.com/NethermindEth/juno); or
- using a third-party JSON-RPC API provider like [Infura](https://www.infura.io/), [Alchemy](https://www.alchemy.com/), or [Chainstack](https://chainstack.com/build-better-with-starknet/).
- using a third-party JSON-RPC API provider like [Infura](https://www.infura.io/), [Alchemy](https://www.alchemy.com/), [Chainstack](https://chainstack.com/build-better-with-starknet/), or [Nethermind](https://starknetrpc.nethermind.io/).

Once you have a URL to a JSON-RPC endpoint, you can use it via the `--rpc <URL>` option for commands that expect it. For example:

Expand Down
Loading