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: remove inaccurate statement about PoW chains #20877

Merged
merged 4 commits into from
Jul 5, 2024

Conversation

0xkrane
Copy link
Contributor

@0xkrane 0xkrane commented Jul 4, 2024

Description

Removing a statement that says most VM-based blockchains use PoW. This change is purely a docs change and not a code change.

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Documentation
    • Removed mentions of CometBFT offering significant gains in throughput for application-specific blockchains from the introductory documentation.

Copy link
Contributor

coderabbitai bot commented Jul 4, 2024

Walkthrough

Walkthrough

The change involves removing a sentence in the documentation about CometBFT BFT's significant gains in throughput when utilized with application-specific blockchains. This update reflects the intention to no longer highlight this particular performance aspect in that context.

Changes

Files Change Summary
docs/learn/intro/01-why-app-specific.md Removed a sentence mentioning CometBFT BFT's significant throughput gains in application-specific blockchains.

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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.

@0xkrane 0xkrane marked this pull request as ready for review July 4, 2024 17:18
@0xkrane 0xkrane requested a review from a team as a code owner July 4, 2024 17:18
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.

Actionable comments posted: 0

Outside diff range and nitpick comments (2)
docs/learn/intro/01-why-app-specific.md (2)

71-71: Remove trailing space.

There is an unnecessary trailing space at the end of the line.

- * Developers of application-specific blockchains can choose to operate with a novel consensus engine such as CometBFT BFT. 
+ * Developers of application-specific blockchains can choose to operate with a novel consensus engine such as CometBFT BFT.
Tools
Markdownlint

71-71: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


71-71: Remove unnecessary comma.

The conjunction "so that" does not require a comma.

- * An application-specific blockchain only operates a single application, so that the application does not compete with others for computation and storage.
+ * An application-specific blockchain only operates a single application so that the application does not compete with others for computation and storage.
Tools
Markdownlint

71-71: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 54586b2 and 8592424.

Files selected for processing (1)
  • docs/learn/intro/01-why-app-specific.md (1 hunks)
Additional context used
Path-based instructions (1)
docs/learn/intro/01-why-app-specific.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

LanguageTool
docs/learn/intro/01-why-app-specific.md

[typographical] ~72-~72: The conjunction “so that” does not require a comma.
Context: ...chain only operates a single application, so that the application does not compete with o...

(SO_THAT_UNNECESSARY_COMMA)

Markdownlint
docs/learn/intro/01-why-app-specific.md

71-71: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)

Additional comments not posted (1)
docs/learn/intro/01-why-app-specific.md (1)

72-72: Approved: Removal of inaccurate statement.

The removal of the statement about VM-based blockchains and PoW aligns with the PR objective.

Tools
LanguageTool

[typographical] ~72-~72: The conjunction “so that” does not require a comma.
Context: ...chain only operates a single application, so that the application does not compete with o...

(SO_THAT_UNNECESSARY_COMMA)

@tac0turtle tac0turtle enabled auto-merge July 5, 2024 08:25
@tac0turtle tac0turtle added this pull request to the merge queue Jul 5, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Jul 5, 2024
@sontrinh16
Copy link
Member

@0xkrane hey can u resolve the conflict so we can go on merge this PR

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.

Actionable comments posted: 1

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8592424 and e6a421a.

Files selected for processing (1)
  • docs/learn/intro/01-why-app-specific.md (1 hunks)
Additional context used
Path-based instructions (1)
docs/learn/intro/01-why-app-specific.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

LanguageTool
docs/learn/intro/01-why-app-specific.md

[typographical] ~72-~72: The conjunction “so that” does not require a comma.
Context: ...chain only operates a single application, so that the application does not compete with o...

(SO_THAT_UNNECESSARY_COMMA)

Additional comments not posted (2)
docs/learn/intro/01-why-app-specific.md (2)

71-71: Confirm the removal of the inaccurate statement.

The removal of the sentence mentioning CometBFT's significant gains in throughput for application-specific blockchains appears to correct an inaccuracy. Ensure the rest of the paragraph maintains clarity and correctness.


Line range hint 1-72:
Documentation is clear and accurate.

The document is well-structured and effectively explains the benefits and shortcomings of application-specific blockchains. No additional grammatical errors are found.

Tools
LanguageTool

[typographical] ~72-~72: The conjunction “so that” does not require a comma.
Context: ...chain only operates a single application, so that the application does not compete with o...

(SO_THAT_UNNECESSARY_COMMA)

@@ -68,7 +68,7 @@ The list above contains a few examples that show how much flexibility applicatio

Decentralized applications built with Smart Contracts are inherently capped in performance by the underlying environment. For a decentralized application to optimise performance, it needs to be built as an application-specific blockchain. Next are some of the benefits an application-specific blockchain brings in terms of performance:

* Developers of application-specific blockchains can choose to operate with a novel consensus engine such as CometBFT. Compared to Proof-of-Work (used by most virtual-machine blockchains today), it offers significant gains in throughput.
* Developers of application-specific blockchains can choose to operate with a novel consensus engine such as CometBFT.
* An application-specific blockchain only operates a single application, so that the application does not compete with others for computation and storage. This is the opposite of most non-sharded virtual-machine blockchains today, where smart contracts all compete for computation and storage.
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove unnecessary comma.

The conjunction “so that” does not require a comma.

- an application-specific blockchain only operates a single application, so that the application does not compete with others for computation and storage.
+ an application-specific blockchain only operates a single application so that the application does not compete with others for computation and storage.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* An application-specific blockchain only operates a single application, so that the application does not compete with others for computation and storage. This is the opposite of most non-sharded virtual-machine blockchains today, where smart contracts all compete for computation and storage.
* An application-specific blockchain only operates a single application so that the application does not compete with others for computation and storage. This is the opposite of most non-sharded virtual-machine blockchains today, where smart contracts all compete for computation and storage.
Tools
LanguageTool

[typographical] ~72-~72: The conjunction “so that” does not require a comma.
Context: ...chain only operates a single application, so that the application does not compete with o...

(SO_THAT_UNNECESSARY_COMMA)

@tac0turtle tac0turtle added this pull request to the merge queue Jul 5, 2024
Merged via the queue into cosmos:main with commit 25d2043 Jul 5, 2024
65 of 66 checks passed
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.

4 participants