mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 04:47:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
7d0e5a9dc4
prysm-pulse/proto
History
Nishant Das 7d0e5a9dc4 Use Latest Vote Map (#4102) 
* add latest vote map
* fix all tests
* remove db crud methods
* Merge branch 'master' into latestVoteMap
* preston's review
* Merge branch 'latestVoteMap' of https://github.com/prysmaticlabs/geth-sharding into latestVoteMap
2019-11-25 16:34:20 +00:00
..
beacon Use Latest Vote Map (#4102) 2019-11-25 16:34:20 +00:00
cluster Update ChainHead (#4053) 2019-11-19 13:33:13 -06:00
eth/v1alpha1 Use Latest Vote Map (#4102) 2019-11-25 16:34:20 +00:00
faucet Update All Our Documentation (#2012) 2019-03-17 16:30:46 -06:00
sharding/p2p/v1 Use Latest Vote Map (#4102) 2019-11-25 16:34:20 +00:00
testing Update run time to v0.9 (#3935) 2019-11-11 17:03:43 -05:00
BUILD.bazel Template based protobuf parameters for ssz configurations (#3062) 2019-07-24 22:03:05 -04:00
README.md switch ethereum 2.0 to ethereum serenity (#714) 2018-11-01 07:02:01 -04:00
ssz_proto_library.bzl Update run time to v0.9 (#3935) 2019-11-11 17:03:43 -05: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.