mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-23 11:57:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
6b4396bbfd
prysm-pulse/proto
History
Preston Van Loon 2148a83b02
Update cluster pk manager to assign multiple keys to validators (#2112) 
* checkpoint

* move lock

* checkpoint

* checkpoint

* chkpt

* update readme so i know what im supposed to do

* ckpt

* checkpoint

* checkpoint

* chkpt

* Fix image build

* handle errors

* add port to pod

* lint

* Update beacon-config.config.yaml

* lint
2019-04-14 17:53:34 -04:00
..
beacon Add deposit index to beacon state (#2232) 2019-04-14 18:17:39 +10:00
cluster Update cluster pk manager to assign multiple keys to validators (#2112) 2019-04-14 17:53:34 -04:00
common Update All Our Documentation (#2012) 2019-03-17 16:30:46 -06:00
faucet Update All Our Documentation (#2012) 2019-03-17 16:30:46 -06:00
sharding/p2p/v1 Support multiple pubkeys for committee assignments (#2164) 2019-04-05 10:10:13 -05:00
testing Update All Our Documentation (#2012) 2019-03-17 16:30:46 -06:00
README.md switch ethereum 2.0 to ethereum serenity (#714) 2018-11-01 07:02:01 -04:00

README.md

Ethereum Serenity Protocol Buffers

This package defines common protobuf messages and services used by Ethereum Serenity clients. Following the structure of:

proto/
  beacon/
    p2p/
      v1/
    rpc/
      v1/
  sharding/
    p2p/
      v1/
  testing/

We specify messages available for p2p communication common to beacon chain nodes and sharding clients.

For now, we are checking in all generated code to support native go dependency management. The generated pb.go files can be derived from bazel's bin directory.

For example, when we build the testing go proto library bazel build //proto/testing:ethereum_testing_go_proto there is a pb.go generated at bazel-bin/proto/testing/linux_amd64_stripped/ethereum_testing_go_proto\~/github.com/prysmaticlabs/prysm/proto/testing/test.pb.go. This generated file can be copied, or you can use you protoc locally if you prefer.