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

docs: update ADR 27 #5815

Merged
merged 5 commits into from
Mar 11, 2024
Merged

docs: update ADR 27 #5815

merged 5 commits into from
Mar 11, 2024

Conversation

crodriguezvega
Copy link
Contributor

@crodriguezvega crodriguezvega commented Feb 5, 2024

Description

closes: #4121

Commit Message / Changelog Entry

type: commit message

see the guidelines for commit messages. (view raw markdown for examples)


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/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Provide a commit message to be used for the changelog entry in the PR description for review.
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

Summary by CodeRabbit

  • Documentation
    • Refined governance process for adding new IBC light client contracts.
    • Specified format for storing Wasm bytecode.
    • Clarified bytecode checksum storage and light client proxy functionality.

Copy link
Contributor

@DimitrisJim DimitrisJim left a comment

Choose a reason for hiding this comment

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

sweet! Left one minor nit that can easily be ignored if you want. Thanks!

Copy link

sonarcloud bot commented Mar 7, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

Co-authored-by: DimitrisJim <d.f.hilliard@gmail.com>
Copy link
Contributor

coderabbitai bot commented Mar 11, 2024

Walkthrough

The update to the IBC-Wasm documentation refines the governance process for adding new IBC light client contracts, specifies the format for Wasm bytecode storage, adjusts client message verification, clarifies bytecode checksum storage, and enhances the explanation of light client proxy functionality, improving system integrity and functionality.

Changes

File Change Summary
docs/architecture/adr-027-ibc-wasm.md Updated governance process, specified Wasm bytecode storage format, adjusted client message verification, clarified bytecode checksum storage, and detailed light client proxy operation.

Assessment against linked issues

Objective Addressed Explanation
Update ADR 27 following audit implementations (#4121)
Address structural issues in 08-wasm module and improve flexibility and maintainability (#5084) The changes indirectly support the restructuring goals by enhancing clarity and governance, but direct resolution of structural issues is unclear.
Enhance conditional client functionality and dependency management in IBC (#5112) The update does not directly address the introduction or enhancement of conditional clients as described.
Implement ICS20 V2 support for Multi Denom in the Cosmos IBC module (#5793) The changes focus on governance and operational processes rather than specific ICS20 V2 support or Multi Denom functionality.

Related issues

  • cosmos/ibc-go#5084: The refinement in governance and operational processes may indirectly support the restructuring goals for the 08-wasm module, suggesting a potential link.
  • cosmos/ibc-go#5112: Although the changes don't directly address conditional clients, the enhanced clarity and governance might indirectly benefit the implementation and management of conditional clients.

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-tests 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 tests 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 tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 6

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between d14bdff and 59dcfb9.
Files selected for processing (1)
  • docs/architecture/adr-027-ibc-wasm.md (5 hunks)
Additional comments: 10
docs/architecture/adr-027-ibc-wasm.md (10)
  • 7-7: The term "ibc-go" is correct in this context, referring to the specific module within the Cosmos SDK. The suggested replacements are not applicable.
  • 4-14: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [18-18]

The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.

  • 27-27: The term "ibc-go" is correct in this context, referring to the specific module within the Cosmos SDK. The suggested replacements are not applicable.
  • 4-14: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [36-36]

The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.

  • 4-14: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [40-40]

The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.

  • 4-14: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [47-47]

The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.

  • 58-58: The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.
  • 94-94: The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.
  • 4-14: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [100-100]

The term "CosmWasm" is correctly spelled and refers to a specific framework for building smart contracts in the Cosmos ecosystem.

  • 4-14: > 📝 NOTE

This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [150-150]

The term "bytecode" is correctly spelled as one word in the context of computing and programming languages.

docs/architecture/adr-027-ibc-wasm.md Outdated Show resolved Hide resolved
crodriguezvega and others added 2 commits March 11, 2024 20:00
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 5

Configuration used: .coderabbit.yml

Commits Files that changed from the base of the PR and between 59dcfb9 and 3af8508.
Files selected for processing (1)
  • docs/architecture/adr-027-ibc-wasm.md (5 hunks)

Comment on lines 4 to 14

- 26/11/2020: Initial Draft
- 26/05/2023: Update after 02-client refactor and re-implementation by Strangelove
- 13/12/2023: Update after upstreaming of module to ibc-go

## Status

*Draft, needs updates*
*Accepted and applied in v0.1.0 of 08-wasm*

## Abstract

Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [1-1]

The term "Wasm based" should be hyphenated to "Wasm-based" for grammatical correctness.

- Wasm based light client
+ Wasm-based light client

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [15-15]

Consider adding a comma after "SDK" for better readability and changing "hardcoded" to "hard-coded" for consistency.

- In the Cosmos SDK light clients are currently hardcoded in Go.
+ In the Cosmos SDK, light clients are currently hard-coded in Go.

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [16-16]

The phrase "a multi step process" should be hyphenated to "a multi-step process" for grammatical correctness.

- a multi step process
+ a multi-step process

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [32-32]

The phrase "time consuming" should be hyphenated to "time-consuming" for grammatical correctness.

- time consuming process
+ time-consuming process

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [151-151]

The term "initialise" is a valid spelling in British English, but considering the document may target an international audience, aligning with American English spelling could improve consistency.

- initialise
+ initialize

@crodriguezvega crodriguezvega merged commit 6b21eef into main Mar 11, 2024
23 checks passed
@crodriguezvega crodriguezvega deleted the carlos/4121-update-adr-27 branch March 11, 2024 19:35
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.

Update ADR 27
3 participants