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
04f4a7f156
prysm-pulse/proto
History
Nishant Das 000a42deac Make State Requests only Request for Finalized State (#1955) 
* remove hash field for state request

* change to finalized state root

* refactor code for bug

* add in saving of finalized state

* add method to db

* adding finalized state root

* add new changes

* add in new changes

* add in return vars

* goimports

* review comments

* error message

* fix broken build

* fix cache state tests

* lint
2019-03-12 16:44:21 -04:00
..
beacon Make State Requests only Request for Finalized State (#1955) 2019-03-12 16:44:21 -04:00
cluster Post ChainStart Validator Activation (#1934) 2019-03-12 00:05:55 -04:00
common Clean Up Batched Request (#1932) 2019-03-07 16:43:48 -06:00
faucet Clean Up Batched Request (#1932) 2019-03-07 16:43:48 -06:00
sharding/p2p/v1 Clean Up Batched Request (#1932) 2019-03-07 16:43:48 -06:00
testing Clean Up Batched Request (#1932) 2019-03-07 16:43:48 -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.