ethers provider

[Naveed-Jameel]

what is the difference between ethers.jsonRpcprovider() and ethers.web3provider()?

[alymurtazamemon]

@Naveed-Jameel These are similar things both connect with metamask, just the difference is web3Provider just takes window.ethereum and automatically gets the HTTP endpoint of RPC_URL from metamask, on the other hand, jsonRpcProvider takes RPC_URL in the parameter just like we were giving alchemy url.

[othaime-en]

Hi @Naveed-Jameel
Backstory: To interact with ethereum, you need to be connected to a node. In most cases, you use a third-party node provider to access the ethereum network. ethersjs normally terms this as provider and there are several of them including web3provider and jsonRpcProvider.
These are all ways to access the blockchain and there isn't much difference except the environment or where your node is hosted. If you are on a browser, the most common provider is web3Provider because it is used by metamask and most of the time developers use this as their default wallet choice. Web3Provider works best on a browser.
On the other hand, jsonRpcProvider is okay when you are using ethers in any other environment such as the hardhat or local environment. Using jsonRpcProvider is easy, you only need to get an RPC_URL from a node provider like alchemy and you are good to go.

[Naveed-Jameel]

one more thing on testnet like rinkeby we get rpc-url from alchemy or infura etc.
on main ethereum net from where we get rpc-url ?

[othaime-en]

Hey @Naveed-Jameel The same provider. Alchemy can also provide you with a mainnet rpc-url