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

feat: add light client module for Celestia DA light client #6053

Merged
merged 15 commits into from
Apr 10, 2024

Conversation

crodriguezvega
Copy link
Contributor

@crodriguezvega crodriguezvega commented Mar 22, 2024

Description

closes: #5965


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against the correct branch (see CONTRIBUTING.md).
  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/).
  • Added relevant godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

Copy link
Contributor

coderabbitai bot commented Mar 22, 2024

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor Author

@crodriguezvega crodriguezvega left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test I added is failing because of this check when trying to create a 07-celestia light client. Currently we have a custom 07-celestia ClientState but we reuse 07-tendermint ConsensusState, so maybe we need to create a custom 07-celestia ConsensusState` as well?

@@ -20,26 +20,6 @@ func (*ClientState) ClientType() string {
return ModuleName
}

// GetLatestHeight implements exported.ClientState.
func (cs *ClientState) GetLatestHeight() exported.Height {
Copy link
Contributor Author

@crodriguezvega crodriguezvega Mar 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed these functions from ClientState and call instead .BaseClient directly in the light client module. I think it is cleaner that way, but the drawback is that the backport to v8.2.x will require more work.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will we need to backport this feature?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we will have to backport these changes to the release branch of the DA light client that is compatible with ibc-go v8.3.x (and that version doesn't include the 02-client routing refactor).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be less overhead to take whats on the target branch now and separate that to a different branch for v8.3.x before merging this PR. It's no harm at least to replicate the feat/celestia-da-client before this PR is merged in case that might be helpful.

upgradeClientProof,
upgradeConsensusStateProof []byte,
) error {
// TODO: do we need to implement this?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: do we need to implement this functionality?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can add an issue for this and discuss later with celestia team

testing/simapp/app.go Outdated Show resolved Hide resolved
if clientState.ClientType() != consensusState.ClientType() {
return errorsmod.Wrap(ErrInvalidClientType, "client type for client state and consensus state do not match")
}
// if clientState.ClientType() != consensusState.ClientType() {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Temporary hack to be able to run the tests.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened #6061.

@crodriguezvega crodriguezvega added the priority PRs that need prompt reviews label Mar 25, 2024
@crodriguezvega
Copy link
Contributor Author

I made this r4r although the check in MsgCreateClient ValidateBasic is commented out, but since this PR is going to a feat branch we can merge this and discuss in the meantime how to deal with it.

…dule

# Conflicts:
#	modules/light-clients/07-celestia/celestia_test.go
#	modules/light-clients/07-celestia/client_state.go
#	modules/light-clients/07-celestia/update_test.go
Copy link
Member

@AdityaSripal AdityaSripal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

Just a question why did nmt need to be added to every single go.mod file event the ones in app/?

upgradeClientProof,
upgradeConsensusStateProof []byte,
) error {
// TODO: do we need to implement this?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can add an issue for this and discuss later with celestia team

@chatton
Copy link
Contributor

chatton commented Apr 3, 2024

Approved.

Just a question why did nmt need to be added to every single go.mod file event the ones in app/?

@AdityaSripal looks like these are being pulled in as indirect dependencies due to the local pin of ibc-go, not explicitly added to each go.mod.

@damiannolan
Copy link
Member

Approved.
Just a question why did nmt need to be added to every single go.mod file event the ones in app/?

@AdityaSripal looks like these are being pulled in as indirect dependencies due to the local pin of ibc-go, not explicitly added to each go.mod.

I think they can be removed if feat/celestia-da-client is merged back into this branch witht the separate go module.

Carlos Rodriguez and others added 2 commits April 4, 2024 10:28
Copy link

sonarqubecloud bot commented Apr 9, 2024

Quality Gate Passed Quality Gate passed for 'ibc-go'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

Copy link
Member

@damiannolan damiannolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to merge this now and continue with follow ups.

We should make a decision soon about what to do about queries etc, as client state and consensus state queries will 07-tendermint types as that's what's actually being stored on disk. Maybe this isn't a problem but its kinda unexpected behaviour unless its explicitly marked as something that is expected - seeing as 07-celestia should be a light weight wrapper around 07-tendermint. cc @AdityaSripal

@crodriguezvega crodriguezvega merged commit d57f8d4 into feat/celestia-da-client Apr 10, 2024
83 checks passed
@crodriguezvega crodriguezvega deleted the carlos/da-light-client-module branch April 10, 2024 10:03
@crodriguezvega
Copy link
Contributor Author

Happy to merge this now and continue with follow ups.

We should make a decision soon about what to do about queries etc, as client state and consensus state queries will 07-tendermint types as that's what's actually being stored on disk. Maybe this isn't a problem but its kinda unexpected behaviour unless its explicitly marked as something that is expected - seeing as 07-celestia should be a light weight wrapper around 07-tendermint. cc @AdityaSripal

I will open an issue to keep track of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority PRs that need prompt reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants