forked from MetaMask/metamask-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add web3 architecture diagram (MetaMask#859)
- Loading branch information
1 parent
9216c7a
commit 9dbef62
Showing
2 changed files
with
16 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
sidebar_position: 1 | ||
description: See the high-level web3 architecture. | ||
--- | ||
|
||
# Architecture | ||
|
||
The following diagram outlines the high-level architecture of the MetaMask web3 stack. | ||
|
||
![Architecture diagram](../assets/web3-architecture.png) | ||
|
||
Using [MetaMask SDK](../how-to/use-sdk/index.md), dapps built on multiple platforms can connect to | ||
their users' Ethereum accounts through the MetaMask browser extension and MetaMask Mobile. | ||
Dapps can send [JSON-RPC API](../reference/rpc-api.md) calls to the users' MetaMask wallet clients. | ||
MetaMask then responds to these requests directly or uses [Infura](https://www.infura.io/) (or | ||
another user-configured node provider) when the call requires access to information on a blockchain network. |