Main ethereum network metamask

Metamask connecting to main ethereum network

Metamask is browser-based crypto wallet that also acts as block browser that could be used to navigate distributed softwares and chains. It is primarily designed to interact with Ethereum network and could be easily connected to the Ethereum Mainnet.

Users can do this to use it simply as their primary Ehtereum wallet. It could be easily used to access decentralized apps made on top of Ethereum blockchain without requiring any other service provider. In the following article of Nominex, we will show how Metamask connecting to main ethereum network.

How to connect Metamask to the Ethereum Mainnet?

Users can easily use Metamask to interact with the blockchain networks they want to interact. As we mentioned earlier, Metamask is primary made to connect to Ethereum Mainnet and for this users don’t have to do anything particular.

They simply should install Metamask plugin on their browser and set up an account to become able to interact with Ethereum Mainnet.

However, to make sure they are choosing the right network, which in this case is Ethereum blockchain network, they can follow these sterps:

• Opening Metamask and click on the Account button:

• In the following window, they should simply go to the “Settings” tab:

• Then by clicking on “Networks” they can enter into networks window on the Metamask:

• In the Networks tab, you can see Ethereum Mainnet in first place as the default network of Metamask.

Since Metamask is an Ethereum wallet by default, it does not require any connection to this network, unless when users want to go back to use it as their mainnet, when they changed the Settings of their Metamask wallet.

How do I connect my MetaMask to private network?

While Metamask is designed to be used for exploring Ethereum network and various decentralized applications that are built on top of Ethereum blockchain, it also can used to explore other blockchain networks as well.

For this, users should also go into Networks tab on their Metamask. While Metamask connecting to main Ehtereum network does not require any change in default settings of Metamask, adding private networks requires entering network’s parameters manually.

The main steps in the previous operation should be followed to achieve the Metamask networks page, which is placed on user’s account:

• By click the “Add Network” button, user simply enters into Metamask networks page:

In this page, however, user should enter exactly the network’s parameters and specifications to connect Metamask to it. Details of each network is different and users have to enter suitable details, which could be accessed on the official website of the blockchain network.

For example, if they want to connect their Metamask wallet into Binance Smart Chain, they should enter these details in the following form:

How do you add ETH to MetaMask?

Metamask is a primary Ethereum wallet that could be easily used to manage ETH funds. For this reason, adding ETH into Metamask wallet is a very easy task that could be easily done.

When users buy Ether from any cryptocurrency exchange, they should enter their wallet address on the exchange recipient address. To copy their Metamask wallet address, they simply have to visit their Metamask account and choose their wallet address to copy it in the clipboard:

Then, they only require to go to the exchange website and enter this address as the recipient address in the transfer page. After entering the amount, they can easily send their ETH to their Metamask account.

How do you get ethereum on MetaMask wallet?

The process of receiving ETH on Metamask wallet is simply the same process of deposit ETH into Metamask account. For this users should only achieve their wallet address that is located on their account. To access their wallet address, they should simply do the following steps:

• Open their account in their Metamask wallet
• Hover the mouse over the account name at the top of the window
• When the “Copy to Clipboard” highlight appears, they should copy the wallet address

That’s all, the wallet address is now copied into their clipboard, and should be pasted by the one who want to send them ETH. This address, then, should be used by sender in whatever wallet they use to send ETH in the recipient field.

Metamask connecting to main Ethereum network advantages

By using Metamask, users can take advantages of this useful and popular Ethereum wallet and block explorer. As you might know, Ethereum is not simply a cryptocurrency, but also a blockchain service provider that could be used by developer to make decentralized applications.

The applications, which are distributed softwares built on the top of Ethereum network, use tokens as their payment method. In other words, their users should pay Gas Fee to access their services.

Metamask connecting to main Ethereum network helps them to easily use these dApps and pay required fee using deposited ETH on their Metamask wallet. That is not only easy, but also could be considered as the main way to access these applications on the Ethereum mainnet.

Closing Thoughts

Metamask is a useful browser-based wallet that could also act as block explorer that could be used to navigate blockchain networks such as Ethereum Mainnet or Binanace chains.

However, it is primarily designed to explore Ethereum network and users by setting up their account, automatically connect to the Ethereum Mainnet.

In other words, Metamask connecting to main Ethereum network is not required to be complete manually. Users with ETH in their Metamask wallets can easily use it as their main block explorer to operate various types of decentralized apps.

With using this wallet, they also can pay from their balance when they are using a certain dApp. Since Metamask operates as a plugin, they can easily use it right when they need to pay tokens or ETH for access any dApp.

Источник

# Ethereum Provider API

Tip Recommended Reading

We recommend that all web3 site developers read the Basic Usage section.

Recent Breaking Provider Changes

If you are an Ethereum application developer and are looking for information about our January 2021 provider API changes, please see our Migration Guide for more details.

MetaMask injects a global API into websites visited by its users at window.ethereum . This API allows websites to request users’ Ethereum accounts, read data from blockchains the user is connected to, and suggest that the user sign messages and transactions. The presence of the provider object indicates an Ethereum user. We recommend using @metamask/detect-provider

(opens new window) to detect our provider, on any platform or browser.

The Ethereum JavaScript provider API is specified by EIP-1193

# Table of Contents

# Basic Usage

For any non-trivial Ethereum web application — a.k.a. dapp, web3 site etc. — to work, you will have to:

• Detect the Ethereum provider ( window.ethereum )
• Detect which Ethereum network the user is connected to
• Get the user’s Ethereum account(s)

The snippet at the top of this page is sufficient for detecting the provider. You can learn how to accomplish the other two by reviewing the snippet in the Using the Provider section.

The provider API is all you need to create a full-featured web3 application.

That said, many developers use a convenience library, such as ethers

(opens new window) , instead of using the provider directly. If you are in need of higher-level abstractions than those provided by this API, we recommend that you use a convenience library.

# Chain IDs

These are the IDs of the Ethereum chains that MetaMask supports by default. Consult chainid.network

Hex	Decimal	Network
0x1	1	Ethereum Main Network (Mainnet)
0x3	3	Ropsten Test Network
0x4	4	Rinkeby Test Network
0x5	5	Goerli Test Network
0x2a	42	Kovan Test Network

# Properties

# ethereum.isMetaMask

This property is non-standard. Non-MetaMask providers may also set this property to true .

true if the user has MetaMask installed.

# Methods

# ethereum.isConnected()

Note that this method has nothing to do with the user’s accounts.

You may often encounter the word «connected» in reference to whether a web3 site can access the user’s accounts. In the provider interface, however, «connected» and «disconnected» refer to whether the provider can make RPC requests to the current chain.

Returns true if the provider is connected to the current chain, and false otherwise.

If the provider is not connected, the page will have to be reloaded in order for connection to be re-established. Please see the connect and disconnect events for more information.

# ethereum.request(args)

Use request to submit RPC requests to Ethereum via MetaMask. It returns a Promise that resolves to the result of the RPC method call.

The params and return value will vary by RPC method. In practice, if a method has any params , they are almost always of type Array .

If the request fails for any reason, the Promise will reject with an Ethereum RPC Error.

MetaMask supports most standardized Ethereum RPC methods, in addition to a number of methods that may not be supported by other wallets. See the MetaMask RPC API documentation for details.

# Example

# Events

The MetaMask provider implements the Node.js EventEmitter

(opens new window) API. This sections details the events emitted via that API. There are innumerable EventEmitter guides elsewhere, but you can listen for events like this:

# connect

The MetaMask provider emits this event when it first becomes able to submit RPC requests to a chain. We recommend using a connect event handler and the ethereum.isConnected() method in order to determine when/if the provider is connected.

# disconnect

The MetaMask provider emits this event if it becomes unable to submit RPC requests to any chain. In general, this will only happen due to network connectivity issues or some unforeseen error.

Once disconnect has been emitted, the provider will not accept any new requests until the connection to the chain has been re-restablished, which requires reloading the page. You can also use the ethereum.isConnected() method to determine if the provider is disconnected.

# accountsChanged

The MetaMask provider emits this event whenever the return value of the eth_accounts RPC method changes. eth_accounts returns an array that is either empty or contains a single account address. The returned address, if any, is the address of the most recently used account that the caller is permitted to access. Callers are identified by their URL origin, which means that all sites with the same origin share the same permissions.

This means that accountsChanged will be emitted whenever the user’s exposed account address changes.

We plan to allow the eth_accounts array to be able to contain multiple addresses in the near future.

# chainChanged

See the Chain IDs section for MetaMask’s default chains and their chain IDs.

The MetaMask provider emits this event when the currently connected chain changes.

All RPC requests are submitted to the currently connected chain. Therefore, it’s critical to keep track of the current chain ID by listening for this event.

We strongly recommend reloading the page on chain changes, unless you have good reason not to.

# message

The MetaMask provider emits this event when it receives some message that the consumer should be notified of. The kind of message is identified by the type string.

RPC subscription updates are a common use case for the message event. For example, if you create a subscription using eth_subscribe , each subscription update will be emitted as a message event with a type of eth_subscription .

# Errors

All errors thrown or returned by the MetaMask provider follow this interface:

The ethereum.request(args) method throws errors eagerly. You can often use the error code property to determine why the request failed. Common codes and their meaning include:

• 4001
  • The request was rejected by the user
• -32602
  • The parameters were invalid
• -32603
  • Internal error

For the complete list of errors, please see EIP-1193

(opens new window) package implements all RPC errors thrown by the MetaMask provider, and can help you identify their meaning.

# Using the Provider

This snippet explains how to accomplish the three most common requirements for web3 sites:

• Detect the Ethereum provider ( window.ethereum )
• Detect which Ethereum network the user is connected to
• Get the user’s Ethereum account(s)

# Experimental API

There is no guarantee that the methods and properties defined in this section will remain stable. Use it at your own risk.

We expose some experimental, MetaMask-specific methods under the ethereum._metamask property.

# Experimental Methods

# ethereum._metamask.isUnlocked()

This method returns a Promise that resolves to a boolean indicating if MetaMask is unlocked by the user. MetaMask must be unlocked in order to perform any operation involving user accounts. Note that this method does not indicate if the user has exposed any accounts to the caller.

# Legacy API

You should never rely on any of these methods, properties, or events in practice.

This section documents our legacy provider API. MetaMask only supported this API before the provider API was standardized via EIP-1193

(opens new window) in 2020. Because of this, you may find web3 sites that use this API, or other providers that implement it.

# Legacy Properties

# ethereum.chainId (DEPRECATED)

This property is non-standard, and therefore deprecated.

If you need to retrieve the current chain ID, use ethereum.request(< method: 'eth_chainId' >) . See also the chainChanged event for more information about how to handle chain IDs.

The value of this property can change at any time.

A hexadecimal string representing the current chain ID.

# ethereum.networkVersion (DEPRECATED)

You should always prefer the chain ID over the network ID.

The value of this property can change at any time.

A decimal string representing the current blockchain’s network ID.

# ethereum.selectedAddress (DEPRECATED)

The value of this property can change at any time.

Returns a hexadecimal string representing the user’s «currently selected» address.

The «currently selected» address is the first item in the array returned by eth_accounts .

Источник