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/get-started/running-node/l2-networks.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ nethermind \
148
148
149
149
## Taiko
150
150
151
-
A [Taiko node](https://docs.taiko.xyz/taiko-alethia-protocol/taiko-alethia-nodes) consists of two parts: taiko-client, analogous to a consensus client in Ethereum paired with an L2 execution client.
151
+
A [Taiko node](https://docs.taiko.xyz/taiko-alethia-protocol/protocol-architecture/taiko-alethia-nodes) consists of two parts: [taiko-client](https://github.com/taikoxyz/taiko-mono/tree/main/packages/taiko-client#readme), analogous to a consensus client in Ethereum paired with an L2 execution client.
152
152
153
153
:::warning Important
154
154
Similar to the L1 node, the L2 instance of Nethermind also requires a [properly configured](consensus-clients.md#configuring-json-rpc-interface) Engine API to communicate to taiko-client.
To run Nethermind on Taiko, see [Layer 2 networks](l2-networks.md#taiko).
90
90
@@ -117,4 +117,3 @@ As the Energy Web Chain is an Aura-based network, running a node does not requir
117
117
:::
118
118
119
119
To run Nethermind on the Energy Web Chain, see the [Energy Web Chain documentation](https://energy-web-foundation.gitbook.io/energy-web/ew-dos-technology-components-2023/trust-layer-energy-web-chain/ewc-guides-and-tutorials/running-a-local-node).
0 commit comments