Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(dot/parachain): rename statement #3470

Merged
merged 37 commits into from
Sep 17, 2023

Conversation

axaysagathiya
Copy link
Contributor

@axaysagathiya axaysagathiya commented Sep 5, 2023

Changes

  • Polkadot has two types with the same name Statement.

    • Statement of type enum and Statement of type struct
  • In our code, we have named the enum Statement as Statement and struct Statement as SignedFullStatement

  • Now the issue is Polkadot also has a struct named SignedFullStatement.

  • So to avoid confusion I have renamed Statement to StatementVDT(type: enum) and SignedFullStatement to Statement(type: struct)

  • SignedFullStatement will be added in the future.

Tests

go test -tags integration github.com/ChainSafe/gossamer

Issues

Primary Reviewer

@kishansagathiya @edwardmack @kanishkatn

kanishkatn and others added 30 commits August 4, 2023 11:39
Co-authored-by: Kishan Sagathiya <[email protected]>
…ement/1 protocol (#3354)

- Added `StatementFetchingRequest` and `StatementFetchingResponse`  varying data types.

- implemented 'network.Message` interface in `StatementFetchingRequest` and 'network.ResponseMessage` interface in `StatementFetchingResponse` as they will be passed into `func (rrp *RequestResponseProtocol) Do(to peer.ID, req Message, res ResponseMessage) error` function as `req` and `res`.

- I didn't want to create a new YAML file here. so I decided to rename the YAML file name and variable(in which data of the YAML file getting unmarshalled) name so that I can use them in this PR.
…chunk/1 protocol (#3362)

- Added `ChunkFetchingRequest` and `ChunkFetchingResponse` types.

- implemented network.Message interface in `ChunkFetchingRequest` and 'network.ResponseMessage' interface in `ChunkFetchingResponse`
…available_data/1 protocol (#3368)

- Added AvailableDataFetchingRequest and AvailableDataFetchingResponse types.
- Implemented 'network.Message' interface in AvailableDataFetchingRequest and 'network.ResponseMessage' interface in AvailableDataFetchingResponse as they will be passed into this function as req and res.
…g statement and collation (#3374)

added New() method and decode test for below varying data types. 
- statement
- statement distribution message
- collation protocol
- collator protocol message
…pov/1 protocol (#3365)

- Added PoVFetchingRequest and PoVFetchingResponse types.
- Implemented 'network.Message' interface in PoVFetchingRequest and 'network.ResponseMessage' interface in PoVFetchingResponse as they will be passed into this function as req and res.
#3277)

- Added parachain service
- Registered collation and validation protocol
- Confirmed that we can communicate with collators by talking to them in `run()` function
Implemented following parachain host runtime calls
- ParachainHost_persisted_validation_data
- ParachainHost_validation_code
This commit adds all the functions required for parachain candidate validations.

With this commit, we are able to take candidate receipts and
- get validation data for it,
- perform basic checks on it,
- run respective parachain's validate_block on parachain's runtime,
- get validate results from parachain's runtime and verify those validation results again relaychain runtime,
- and declare candidate as valid or invalid in the end.

This commit also includes tests for candidate validation.
…3382)

Co-authored-by: Kanishka <[email protected]>
Co-authored-by: Kishan Mohanbhai Sagathiya <[email protected]>
Co-authored-by: Axay Sagathiya <[email protected]>
User wazero runtime instance instead of wasmer runtime instance
@axaysagathiya axaysagathiya changed the title Chore(dot/parachain): rename statement chore(dot/parachain): rename statement Sep 5, 2023
@codecov
Copy link

codecov bot commented Sep 15, 2023

Codecov Report

Merging #3470 (b778b9e) into feat/parachain (33e9f9a) will increase coverage by 0.25%.
The diff coverage is 90.90%.

@@                Coverage Diff                 @@
##           feat/parachain    #3470      +/-   ##
==================================================
+ Coverage           49.61%   49.86%   +0.25%     
==================================================
  Files                 244      244              
  Lines               29403    29403              
==================================================
+ Hits                14588    14662      +74     
+ Misses              13256    13182      -74     
  Partials             1559     1559              

@axaysagathiya axaysagathiya merged commit 788a160 into feat/parachain Sep 17, 2023
@axaysagathiya axaysagathiya deleted the axay/chore/rename-statement branch September 17, 2023 09:17
timwu20 pushed a commit that referenced this pull request Jun 15, 2024
timwu20 pushed a commit that referenced this pull request Jun 17, 2024
timwu20 pushed a commit that referenced this pull request Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants