Feat/sync dev with v1 55 0

[aarmoa]

• PR to sync dev branch with the changes in the release v1.55.0

Summary by CodeRabbit

• New Features

  • Enhanced transaction broadcasting with more flexible mode selection
  • Added ability to specify synchronous or asynchronous broadcast modes

• Improvements

  • Updated chain client interface to support more granular message broadcasting
  • Improved logging for OFAC list download process

• Documentation

  • Updated example code to demonstrate new broadcasting method

• Chores

  • Updated OFAC list with new and modified Ethereum addresses

[coderabbitai]

Caution

Review failed

The pull request is closed.

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint (1.62.2)

level=warning msg="[lintersdb] The name "gas" is deprecated. The linter has been renamed to: gosec."
level=warning msg="[lintersdb] The linter named "megacheck" is deprecated. It has been split into: gosimple, staticcheck, unused."

Walkthrough

This pull request introduces a new BroadcastMsg method to the ChainClient interface, enhancing the transaction broadcasting functionality. The changes modify how messages are broadcast to the blockchain, providing more flexibility by allowing explicit specification of broadcast modes (synchronous or asynchronous). The modifications impact multiple files across the project, including the chain client implementation, test files, and example scripts. The changes standardize the message broadcasting approach across different components and improve the overall transaction submission process.

Changes

File	Change Summary
client/chain/chain.go	Added BroadcastMsg method, updated SyncBroadcastMsg and AsyncBroadcastMsg to use new method
client/chain/chain_test.go	Enhanced test setup with setUpChainTest and tearDownChainTest functions
client/chain/chain_test_support.go	Added BroadcastMsg method to MockChainClient
client/chain/ofac.go	Added log statement for OFAC list file writing path
examples/chain/*/example.go	Updated message broadcasting to use BroadcastMsg with explicit broadcast mode
injective_data/ofac.json	Updated OFAC list with address modifications

Sequence Diagram

sequenceDiagram
    participant Client
    participant ChainClient
    participant Blockchain
    
    Client->>ChainClient: BroadcastMsg(mode, messages)
    ChainClient->>Blockchain: Submit Transaction
    alt Synchronous Mode
        Blockchain-->>ChainClient: Wait for Block Inclusion
        ChainClient-->>Client: Return Transaction Response
    else Asynchronous Mode
        Blockchain-->>ChainClient: Immediate Response
        ChainClient-->>Client: Return Immediate Response
    end

Loading

Possibly related PRs

• feat/tx_broadcast_refactoring #272: Relates to the introduction of the BroadcastMsg method and modifications to transaction broadcasting functionality

Suggested reviewers

• nicolasbaum

Poem

🐰 Broadcast bunnies hop with glee,
Messages flying, wild and free!
Sync or async, they'll find their way,
Through blockchain meadows, bright as day
New methods dancing, code so bright! 🚀

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96a8635 and d5d2b42.

📒 Files selected for processing (13)

• client/chain/chain.go (4 hunks)
• client/chain/chain_test.go (4 hunks)
• client/chain/chain_test_support.go (1 hunks)
• client/chain/ofac.go (1 hunks)
• examples/chain/13_BroadcastMsgWithoutSimulation/example.go (2 hunks)
• examples/chain/oracle/1_MsgRelayPriceFeedPrice/example.go (2 hunks)
• examples/chain/permissions/1_CreateNamespace/example.go (2 hunks)
• examples/chain/permissions/2_DeleteNamespace/example.go (2 hunks)
• examples/chain/permissions/3_UpdateNamespace/example.go (2 hunks)
• examples/chain/permissions/4_UpdateNamespaceRoles/example.go (2 hunks)
• examples/chain/permissions/5_RevokeNamespaceRoles/example.go (2 hunks)
• examples/chain/permissions/6_ClaimVoucher/example.go (2 hunks)
• injective_data/ofac.json (2 hunks)

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.