docs: use only RpcProvider

[PhilippeR26]

Motivation and Resolution

Following removal of Starknet sequencers, users shall only use RpcSequencer.
The guides are here updated in accordance.
It's also the opportunity to migrate in the guides from Pythonic Devnet to Starknet-devnet-rs.

Usage related changes

N/A

Development related changes

N/A

Checklist:

• Rebased to the last commit of the target branch (or merged it into my branch)
• All tests are passing

[netlify]

✅ Deploy Preview for starknetjs ready!

Name	Link
🔨 Latest commit	0ba3744
🔍 Latest deploy log	https://app.netlify.com/sites/starknetjs/deploys/656ebe09fbbaa80008d18f68
😎 Deploy Preview	https://deploy-preview-857--starknetjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[penovicp]

I would suggest documenting that new RpcProvider({ nodeUrl: constants.NetworkName.SN_GOERLI }) and new RpcProvider() are also possible and note that when using them a random public node will be selected, but also advise that using a specific nodeUrl is the better approach.

It might also make sense to mostly use one of those two options in most of the documentation or something like new RpcProvider({ nodeUrl: `${someNodeUrl}` }) and use specific nodeUrl values within www/docs/guides/connect_network.md to simplify documentation maintenance (e.g. the Nethermind URLs will soon change).

[ivpavici]

I would suggest documenting that new RpcProvider({ nodeUrl: constants.NetworkName.SN_GOERLI }) and new RpcProvider() are also possible and note that when using them a random public node will be selected, but also advise that using a specific nodeUrl is the better approach.

It might also make sense to mostly use one of those two options in most of the documentation or something like new RpcProvider({ nodeUrl: `${someNodeUrl}` }) and use specific nodeUrl values within www/docs/guides/connect_network.md to simplify documentation maintenance (e.g. the Nethermind URLs will soon change).

This is the new Juno link, but didn't test it yet if it's live: https://free-rpc.nethermind.io/mainnet-juno/v0_5

[PhilippeR26]

This is the new Juno link, but didn't test it yet if it's live: https://free-rpc.nethermind.io/mainnet-juno/v0_5

It's live (I have a script to batch check quickly a list of nodes). Is it a difference with
https://limited-rpc.nethermind.io/mainnet-juno/v0_5?

[ivpavici]

This is the new Juno link, but didn't test it yet if it's live: https://free-rpc.nethermind.io/mainnet-juno/v0_5

It's live (I have a script to batch check quickly a list of nodes). Is it a difference with https://limited-rpc.nethermind.io/mainnet-juno/v0_5?

This is the new Juno link, but didn't test it yet if it's live: https://free-rpc.nethermind.io/mainnet-juno/v0_5

It's live (I have a script to batch check quickly a list of nodes). Is it a difference with https://limited-rpc.nethermind.io/mainnet-juno/v0_5?

yes I think they will turn off the old link... so if it works, maybe best to update to the new one!

[PhilippeR26]

I would suggest documenting that new RpcProvider({ nodeUrl: constants.NetworkName.SN_GOERLI }) and new RpcProvider() are also possible and note that when using them a random public node will be selected, but also advise that using a specific nodeUrl is the better approach.

It might also make sense to mostly use one of those two options in most of the documentation or something like new RpcProvider({ nodeUrl: `${someNodeUrl}` }) and use specific nodeUrl values within www/docs/guides/connect_network.md to simplify documentation maintenance (e.g. the Nethermind URLs will soon change).

Honestly, I wasn't aware of this random access.
I will have a look at this, and update.

[PhilippeR26]

I completely rewrote connect_network.md, and I modified all node names as proposed.

[github-actions]

🎉 This PR is included in version 5.24.4 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 7.0.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀