mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2024-12-22 03:30:35 +00:00
Update readme
This commit is contained in:
parent
69e053f6ab
commit
20c8b73730
41
README.md
41
README.md
@ -1,48 +1,17 @@
|
|||||||
# Prysm: An Ethereum Consensus Implementation Written in Go
|
# Prysm-Pulse: A PulseChain Consensus Client Written in Go
|
||||||
|
|
||||||
[![Build status](https://badge.buildkite.com/b555891daf3614bae4284dcf365b2340cefc0089839526f096.svg?branch=master)](https://buildkite.com/prysmatic-labs/prysm)
|
This is the core repository for Prysm-Pulse, a [Golang](https://golang.org/) implementation of the [Ethereum Consensus](https://ethereum.org/en/eth2/) specification, originally developed by [Prysmatic Labs](https://prysmaticlabs.com) and modified for usage with [PulseChain](https://pulsechain.com/). See the [Changelog](https://gitlab.com/pulsechaincom/prysm-pulse/-/releases) for details of the latest releases and upcoming breaking changes.
|
||||||
[![Go Report Card](https://goreportcard.com/badge/github.com/prysmaticlabs/prysm)](https://goreportcard.com/report/github.com/prysmaticlabs/prysm)
|
|
||||||
[![Consensus_Spec_Version 1.4.0](https://img.shields.io/badge/Consensus%20Spec%20Version-v1.4.0-blue.svg)](https://github.com/ethereum/consensus-specs/tree/v1.4.0)
|
|
||||||
[![Execution_API_Version 1.0.0-beta.2](https://img.shields.io/badge/Execution%20API%20Version-v1.0.0.beta.2-blue.svg)](https://github.com/ethereum/execution-apis/tree/v1.0.0-beta.2/src/engine)
|
|
||||||
[![Discord](https://user-images.githubusercontent.com/7288322/34471967-1df7808a-efbb-11e7-9088-ed0b04151291.png)](https://discord.gg/prysmaticlabs)
|
|
||||||
[![GitPOAP Badge](https://public-api.gitpoap.io/v1/repo/prysmaticlabs/prysm/badge)](https://www.gitpoap.io/gh/prysmaticlabs/prysm)
|
|
||||||
|
|
||||||
This is the core repository for Prysm, a [Golang](https://golang.org/) implementation of the [Ethereum Consensus](https://ethereum.org/en/developers/docs/consensus-mechanisms/#proof-of-stake) [specification](https://github.com/ethereum/consensus-specs), developed by [Offchain Labs](https://www.offchainlabs.com). See the [Changelog](https://github.com/prysmaticlabs/prysm/releases) for details of the latest releases and upcoming breaking changes.
|
> Credit to the [Prysmatic Labs](https://prysmaticlabs.com/) team for the original implementation of [Prysm](https://github.com/prysmaticlabs/prysm).
|
||||||
|
|
||||||
### Getting Started
|
### 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](https://docs.prylabs.network). If you still have questions, feel free to stop by our [Discord](https://discord.gg/prysmaticlabs).
|
A detailed set of installation and usage instructions as well as breakdowns of each individual component are available in the [official documentation portal](https://docs.prylabs.network). If you still have questions, feel free to join [our telegram channel](https://t.me/PulseDEV).
|
||||||
|
|
||||||
### Staking on Mainnet
|
### Staking on Mainnet
|
||||||
|
|
||||||
To participate in staking, you can join the [official eth2 launchpad](https://launchpad.ethereum.org). The launchpad is the only recommended way to become a validator on mainnet. You can explore validator rewards/penalties via Bitfly's block explorer: [beaconcha.in](https://beaconcha.in), and follow the latest blocks added to the chain on [beaconscan](https://beaconscan.com).
|
To participate in staking, you can join the [PulseChain staking launchpad](https://pulsechain.com/). The launchpad is the only recommended way to become a validator. You can explore validator rewards/penalties via the PulseChain [beacon chain explorer](https://www.pulsechain.com), and follow the latest blocks added to the chain on [block explorer](https://www.pulsechain.com).
|
||||||
|
|
||||||
|
|
||||||
## Contributing
|
|
||||||
### Branches
|
|
||||||
Prysm maintains two permanent branches:
|
|
||||||
|
|
||||||
* [master](https://github.com/prysmaticlabs/prysm/tree/master): This points to the latest stable release. It is ideal for most users.
|
|
||||||
* [develop](https://github.com/prysmaticlabs/prysm/tree/develop): This is used for development, it contains the latest PRs. Developers should base their PRs on this branch.
|
|
||||||
|
|
||||||
### Guide
|
|
||||||
Want to get involved? Check out our [Contribution Guide](https://docs.prylabs.network/docs/contribute/contribution-guidelines/) to learn more!
|
|
||||||
|
|
||||||
## License
|
## License
|
||||||
|
|
||||||
[GNU General Public License v3.0](https://www.gnu.org/licenses/gpl-3.0.en.html)
|
[GNU General Public License v3.0](https://www.gnu.org/licenses/gpl-3.0.en.html)
|
||||||
|
|
||||||
## Legal Disclaimer
|
|
||||||
|
|
||||||
[Terms of Use](/TERMS_OF_SERVICE.md)
|
|
||||||
|
|
||||||
# Bazel-in-Docker Build
|
|
||||||
|
|
||||||
To get started quickly, a bazel-in-docker script is included that allows for producing local docker image builds without setting up bazel, protoc, and the various build dependencies.
|
|
||||||
|
|
||||||
This [Dockerfile](Dockerfile.builder) and [shell script](build-in-docker.sh) will produce consistent builds using Bazel-in-Docker while still taking advantage of bazel caching for fast repeat builds.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
# run the bazel build in docker
|
|
||||||
./build-in-docker.sh
|
|
||||||
```
|
|
||||||
|
Loading…
Reference in New Issue
Block a user