prysm-pulse/proto
metanull-operator 1222ebb6db Graffiti flag (#4213)
* Implementation of graffiti flag without tests.
* Updated to pass graffiti as string instead of []byte all the way to the ProposeBlock RPC call. This ensures that the ToBytes32() call is handled in ProposeBlock as opposed to relying on the caller to ensure that the value passed is only 32 bytes. This adds work by doing that conversion on each proposed block for a static value of graffiti, but it also helps protect against an RPC call to ProposeBlock that has more than 32 bytes for graffiti.
* Added test case for validator.
* Added GraffitiFlag to validate usage test.
* Updated data structures and logic to convert graffiti flag from string to byte array earlier in the process. Now converting when setting up ValidatorService.
* Updated test case to correctly set up validator using byte array.
* Merge branch 'master' into graffitiFlag
2019-12-07 19:13:56 +00:00
..
beacon Graffiti flag (#4213) 2019-12-07 19:13:56 +00:00
cluster Update ChainHead (#4053) 2019-11-19 13:33:13 -06: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 Apply Patch Rules to Use EthereumAPIs Generated Protos in Prysm (#4112) 2019-11-27 05:08:18 +00: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

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.