chore: add crisis changelog

[tac0turtle]

Description

add crisis changelog for visibility

---

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

• New Features

  • Introduced simulation of nested messages in the base application.
  • Added a Linux-only backend for the crypto/keyring module.
  • Enabled importing hex keys via standard input in the client/keys module.

• Improvements

  • Enhanced error handling across various modules.
  • Introduced new methods for improved usability.

• Bug Fixes

  • Resolved issues with simulation tests and address queries for consistent behavior.

• API Breaking Changes

  • Renamed methods and altered signatures in several modules, impacting existing implementations.

• Deprecated Features

  • Marked certain features for deprecation in favor of more efficient alternatives.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request primarily involve updates to the CHANGELOG.md for the Cosmos SDK, detailing new features, improvements, bug fixes, and breaking changes. Key additions include new methods for simulating nested messages and importing hex keys, enhancements in error handling, and several method signature updates. The changelog emphasizes semantic versioning and provides a structured format for documenting these changes.

Changes

File	Change Summary
CHANGELOG.md	Updated with new features, improvements, bug fixes, breaking changes, and deprecated features.
.../baseapp.py	New method simulate_nested_messages() added.
.../crypto/keyring.py	New backend linux_keyring_backend() added.
.../client/keys.py	New method import_hex_key() added.
.../cli.py	Method signature updated from query_address_by_acc_num(account_id) to query_address_by_acc_num(account_id, id).
.../sims.py	Method signature updated from skip_sims_test() to skip_sims_test(validator_list).
.../client.py	Method signature updated from get_validator_address() to get_validator_address(account_id).

Possibly related PRs

• chore: sync changelog with latest releases #21658: This PR also updates CHANGELOG.md, focusing on the organization and clarity of documented changes, which aligns with the updates made in the main PR.
• chore: add releases to changelog #21831: This PR adds releases to CHANGELOG.md, which is directly related to the changes made in the main PR regarding the documentation of new features and improvements.
• chore: bring v0.52.0-beta.2 changelog to main #22188: This PR brings the v0.52.0-beta.2 changelog to the main branch, which is relevant as it involves updates to the changelog similar to those in the main PR.

Suggested labels

C:x/tx

Suggested reviewers

• sontrinh16
• hieuvubk
• akhilkumarpilli

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (5)

CHANGELOG.md (5)

Line range hint 1-14: Unreleased changes section needs more details

The unreleased changes section is currently empty. It would be helpful to add a placeholder or brief description of what to expect in this section, even if no specific changes are listed yet. This helps readers understand the purpose of this section.

Consider adding a brief explanation like:

## [Unreleased]

Changes in the unreleased version will be listed here. This section will be updated as new features, improvements, and bug fixes are added to the development branch.

---

Line range hint 16-36: Important breaking changes in v0.47.0

The v0.47.0 release contains significant breaking changes, including the migration to CometBFT and numerous API changes. Users should pay close attention to the upgrade guide and migration instructions.

Given the extent of the changes, it's crucial to:

1. Thoroughly test applications against this new version before upgrading.
2. Update all dependencies to versions compatible with CometBFT.
3. Review and update any custom modules or implementations that may be affected by the API changes.

Consider adding a warning at the top of this section to emphasize the significance of these changes and the need for careful migration planning.

---

Line range hint 38-55: New features and improvements highlight potential performance enhancements

The addition of features like state sync and optimistic execution suggests potential performance improvements. However, these new features may require careful configuration and testing.

1. For the state sync feature, ensure that operators understand how to configure and use it effectively.
2. The optimistic execution feature is marked as experimental. Consider adding a note recommending thorough testing before enabling this feature in production environments.

In the description of the optimistic execution feature, consider adding a brief explanation of its potential benefits and risks to help users make informed decisions about its use.

---

Line range hint 57-76: Significant API and behavior changes

This section highlights important changes that may affect existing applications and workflows. The changes to PreBlock, BeginBlock, and EndBlock are particularly noteworthy.

1. Developers should carefully review their application's use of these block execution hooks and update accordingly.
2. The change in ValidateBasic() behavior for sdk.Msg is a significant shift. Ensure that all custom message types are updated to handle validation in their message handlers instead.

Consider grouping related changes together for easier comprehension. For example, all changes related to block execution could be listed consecutively.

---

Line range hint 78-98: CLI Breaking Changes and Deprecations

The changes to CLI commands and the deprecation of certain features may impact existing scripts and workflows.

1. Users should review and update any scripts or automation that rely on the changed or deprecated CLI commands.
2. The removal of the --amino flag for sign and multi-sign commands is particularly noteworthy. Ensure that any signing processes are updated to use the new methods.

Consider adding a brief note about the rationale behind the removal of Amino signing, and provide guidance on the recommended approach for signing transactions in this version.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between abaccb4 and d2a8a16.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

CHANGELOG.md (1)

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