prysm-pulse/proto
Preston Van Loon 6bf14dedcd
Better aggregated attestations pool (#3761)
* WIP of aggregated signatures in DB

* new lines at end

* taking a nap on the plane now

* fix tests

* remove duplication of attestations. so much for that airplane nap lol

* benchmark before flight lands

* gaz

* manual gaz

* fully contained checks

* quick improvement before landing

* new bitlist with fixes

* doesn't need real signatures

* it works, mostly

* print shard too

* some refactoring

* Revert "some refactoring"

This reverts commit 377ce7fbfb02321c20522da2eb27208a20a67669.

* Revert "Revert "some refactoring""

This reverts commit b46a458898acd214da44fc20dfae920d2725b6e8.

These changes are ok, just need to update the expected values

* fix tests

* lint

* lint

* upstream changes

* fix tests

* what

* resolve TODOs

* gofmt

* revert unrelated pb

* remove debug statement
2019-10-16 23:46:07 -07:00
..
beacon Better aggregated attestations pool (#3761) 2019-10-16 23:46:07 -07:00
cluster format protos with prototool (#2462) 2019-05-01 12:14:21 -07:00
eth/v1alpha1 slasher server (#3596) 2019-10-17 08:42:26 +05:30
faucet Update All Our Documentation (#2012) 2019-03-17 16:30:46 -06:00
sharding/p2p/v1 slasher server (#3596) 2019-10-17 08:42:26 +05:30
testing run minimal tests (#3454) 2019-09-12 14:24:35 -04: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 Template based protobuf parameters for ssz configurations (#3062) 2019-07-24 22:03:05 -04: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.