You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/protocol/flow-networks/index.md
+49-12Lines changed: 49 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,17 @@ sidebar_position: 1
5
5
6
6
## About Flow Networks
7
7
8
-
:::note
9
-
10
-
This page provides information on Flow network RPCs. Flow EVM network RPCs can be found [here](../../build/evm/networks)
11
-
12
-
:::
8
+
Flow supports two virtual machine environments: **Flow Cadence** (native Flow smart contracts) and **Flow EVM** (EVM-equivalent smart contracts). Both environments share the same underlying Flow blockchain infrastructure and use FLOW as the native token for gas fees.
13
9
14
10
In addition to Mainnet, developers have access to the Testnet environment, which serves as an essential testing ground for applications and smart contracts prior to their deployment on Mainnet. This ensures that any potential issues can be identified and resolved in a controlled setting, mitigating risks associated with live deployment.
15
11
16
12
Furthermore, during network upgrades, Testnet receives updates ahead of Mainnet. This preemptive update process allows developers to comprehensively test their apps against the latest versions of the nodes, enhancements to the Cadence programming language, and core contract upgrades. This strategy guarantees that when these updates are eventually applied to Mainnet, applications and smart contracts will operate seamlessly, enhancing overall network stability and user experience.
17
13
18
-
### How To Access These Networks?
14
+
## Flow Cadence Networks
15
+
16
+
Flow Cadence networks provide access to the native Flow blockchain using the Cadence programming language. Access Nodes are the node type that are most useful for developers, as they provide access to the Flow network via the following API endpoints.
@@ -27,25 +27,62 @@ For more information on how to access these networks, refer to the following gui
27
27
-[Flow Testnet](./accessing-testnet.md)
28
28
-[Flow Mainnet](./accessing-mainnet.md)
29
29
30
+
### Flow Access API
30
31
31
-
### Network
32
-
33
-
There are two primary ways to access onchain data within the Flow network; Access Nodes and Light nodes. Access Nodes are the node type that are most useful for developers, as they provide access to the Flow network via the following API endpoints:
32
+
There are two primary ways to access onchain data within the Flow network: Access Nodes and Light nodes. Access Nodes are the node type that are most useful for developers, as they provide access to the Flow network via the following API endpoints:
-[Status Page](https://status.onflow.org/) - Network status page
39
38
40
-
### Rate limits
39
+
## Flow EVM Networks
40
+
41
+
Flow EVM is an EVM-equivalent blockchain that combines the advantages of Flow, including security, low-cost gas, and native VRF with compatibility with existing blockchain applications tools and contracts. Flow EVM uses the standard Ethereum JSON-RPC API.
| Block Explorer |https://evm-testnet.flowscan.io|
66
+
67
+
### EVM Specification
68
+
69
+
- Flow EVM is a virtual EVM-based blockchain using the latest EVM byte-code interpreter
70
+
- Utilizes `FLOW` token for transactions
71
+
- The [EVM Gateway](https://github.com/onflow/flow-evm-gateway) exposes the standard EVM API (Ethereum JSON-RPC)
72
+
- Read more about the implementation in [FLIP 223: EVM integration interface](https://github.com/onflow/flips/blob/main/protocol/20231116-evm-support.md)
73
+
74
+
For detailed information about supported JSON-RPC methods, see the [Flow EVM Network Information](../../build/evm/networks.md) page.
75
+
76
+
## Rate limits
41
77
42
78
Rate limits for Flow Public Access nodes hosted by QuickNode are detailed [here](https://www.quicknode.com/docs/flow#endpoint-rate-limits).
43
79
44
-
###Running Your Own Node
80
+
## Running Your Own Node
45
81
46
-
If you’re getting started you don’t need to run your own node and you can use the above public nodes. The public access nodes are rate-limited, so as your product matures you might want to run your own node. There are multiple options available:
82
+
If you're getting started, you don't need to run your own node and you can use the above public nodes. The public access nodes are rate-limited, so as your product matures you might want to run your own node. There are multiple options available:
47
83
48
84
- Start with a [Light (Observer) Node](../node-ops/light-nodes/observer-node.md).
85
+
- For Flow EVM applications, you can run your own [EVM Gateway](../node-ops/evm-gateway/evm-gateway-setup.md) to provide a dedicated private RPC endpoint, remove rate limits, and optionally sponsor gas fees for your users.
49
86
- You can also use a third-party provider like [Quicknode](https://www.quicknode.com/docs/flow).
50
87
51
88
Check out [Running a Node](../node-ops/light-nodes/observer-node.md) for more information.
0 commit comments