Using custom networks with MetaMask

In spite of the fact that there is just a single Ethereum blockchain, generally called "Mainnet", there is a wide range of Ethereum-compatible networks, filling an assortment of needs. As a matter of course, MetaMask upholds associating with six distinct networks: Mainnet, four mainstream test networks (Goerli, Kovan, Rinkeby, Ropsten), and a "Localhost" network utilized by programming engineers.
Notwithstanding, MetaMask can interface with any Ethereum-compatible organization. We call these networks custom networks since they are normally modified to take care of a specific issue. As of rendition 9.1.0 of the MetaMask program augmentation (the component is forthcoming for the versatile application), sites can request that you interface with a specific organization in MetaMask and add its data on the off chance that it doesn't exist yet.
The most widely recognized use case for custom networks at the hour of composing are supposed "Layer-2" or "L2" networks, whose object is "proportional" Ethereum. Generally, the administrators of these networks will as a rule request that you store assets or resources on Mainnet to utilize them on the Layer-2 organization, which may offer less expensive and quicker exchanges. Instances of these networks incorporate Optimism, Polygon, SKALE, and xDAI.

Before you utilize a custom organization with MetaMask, it's critical to comprehend the dangers of adding and interfacing with custom networks. MetaMask doesn't confirm custom networks. You are answerable for checking any custom organization added to MetaMask. We emphatically prescribe perusing this article to guarantee that you don't put your security or assets in danger.
At MetaMask, we accept that custom networks — particularly Layer 2 networks — have a significant task to carry out in Ethereum's future. Be that as it may, their advantages don't come without hazards. Here are some significant things to remember when utilizing custom networks: more know