Skip to content

Commit f49fd6c

Browse files
committed
docs: update broken link of consensus client analysis #12412
1 parent 505236a commit f49fd6c

File tree

1 file changed

+1
-1
lines changed
  • public/content/developers/docs/nodes-and-clients/run-a-node

1 file changed

+1
-1
lines changed

public/content/developers/docs/nodes-and-clients/run-a-node/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ The sync mode and client you choose will affect space requirements, but we've es
100100

101101
- Note: Erigon does not offer snap sync, but Full Pruning is possible (~500GB)
102102

103-
For consensus clients, space requirement also depends on client implementation and enabled features (e.g. validator slasher) but generally count with another 200GB needed for beacon data. With a large number of validators, the bandwidth load grows as well. You can find [details on consensus client requirements in this analysis](https://medium.com/@migalabs/analysis-of-ethereum-2-consensus-clients-dfede8e0145e).
103+
For consensus clients, space requirement also depends on client implementation and enabled features (e.g. validator slasher) but generally count with another 200GB needed for beacon data. With a large number of validators, the bandwidth load grows as well. You can find [details on consensus client requirements in this analysis](https://mirror.xyz/0x934e6B4D7eee305F8C9C42b46D6EEA09CcFd5EDc/b69LBy8p5UhcGJqUAmT22dpvdkU-Pulg2inrhoS9Mbc).
104104

105105
#### Plug-and-play solutions {#plug-and-play}
106106

0 commit comments

Comments
 (0)