Back to MCP directory
publicPublicdnsLocal runtime

prysm

Prysm 是一个用 Go 语言编写的以太坊共识层实现,由 Offchain Labs 开发。它遵循以太坊的权益证明(PoS)共识机制规范,旨在为以太坊网络提供高效、可靠的验证节点服务。Prysm 支持用户通过官方以太坊启动板参与主网质押,成为验证者并获得奖励。项目提供了详细的安装和使用指南,并鼓励开发者通过贡献指南参与开发。Prysm 采用 GNU 通用公共许可证 v3.0 授权,用户可通过 Discord 社区获取支持。

article

README

Prysm: An Ethereum Consensus Implementation Written in Go

Build status Go Report Card Consensus_Spec_Version 1.4.0 Execution_API_Version 1.0.0-beta.2 Discord GitPOAP Badge


📖 Overview

This is the core repository for Prysm, a Golang implementation of the Ethereum Consensus specification, developed by Offchain Labs.

See the Changelog for details of the latest releases and upcoming breaking changes.


🚀 Getting Started

A detailed set of installation and usage instructions as well as breakdowns of each individual component are available in the official documentation portal.

💬 Need help? Join our Discord Community for support.


🏆 Staking on Mainnet

To participate in staking, you can join the official Ethereum launchpad. The launchpad is the only recommended way to become a validator on mainnet.

🔍 Explore validator rewards/penalties:


🤝 Contributing

🔥 Branches

Prysm maintains two permanent branches:

  • master - This points to the latest stable release. It is ideal for most users.
  • develop - This is used for development and contains the latest PRs. Developers should base their PRs on this branch.

🛠 Contribution Guide

Want to get involved? Check out our Contribution Guide to learn more!


📜 License

License: GPL v3

This project is licensed under the GNU General Public License v3.0.


⚖️ Legal Disclaimer

📜 Terms of Use

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client