faddat/send via grpc

[faddat]

• rename project "metorite"
• finish renaming
• correct naming
• refactor

Summary by CodeRabbit

Release Notes

• New Features

  • Renamed the tool from "Hardhat" to "Meteorite" across all documentation and configurations.
  • Introduced a new transaction broadcasting mechanism with enhanced error handling.

• Bug Fixes

  • Improved error handling for address validation in transaction messages.

• Documentation

  • Updated all references from "Hardhat" to "Meteorite" in the README and LICENSE files.
  • Adjusted installation and usage instructions to reflect the new tool name.

• Chores

  • Updated configuration files to align with the new project identity and structure.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve a comprehensive renaming of the project from "Hardhat" to "meteorite," affecting various files including .gitignore, LICENSE.md, README.md, and several configuration files. The modifications also include updates to the go.mod file to reflect the new module name and changes in dependencies. Additionally, the broadcast package has undergone significant refactoring to streamline transaction handling, and various import paths have been updated to align with the new project name.

Changes

File	Change Summary
.gitignore	Removed entry for hardhat, added entry for meteorite.
LICENSE.md	Replaced "Hardhat" with "meteorite" in multiple contexts, including intellectual property and licensing statements.
README.md	Renamed "Hardhat" to "meteorite" throughout the document, including installation commands and usage guidelines.
broadcast/broadcast.go	Updated SendTransactionViaRPC method to accept a single TransactionParams parameter; added Transaction method; modified error handling and signing logic.
configurations/kujira/nodes.toml	Updated ibc_memo URL from hardhat to meteorite, added memo field, and reformatted rpc field to single-line.
configurations/kujira2/nodes.toml	Updated ibc_memo URL from hardhat to meteorite, minor formatting changes.
configurations/osmosis/nodes.toml	Updated ibc_memo URL from hardhat to meteorite, added memo field, and reformatted rpc field.
go.mod	Changed module name from github.com/somatic-labs/hardhat to github.com/somatic-labs/meteorite, updated dependencies.
lib/lib.go	Changed import path for types, renamed GetInitialSequence to GetAccountInfo, updated return types to uint64.
lib/privkey.go	Updated import path for types.
main.go	Introduced broadcastLoop function for transaction broadcasting; restructured error handling; removed sendTransaction method.
modules/bank/send.go	Updated import paths for lib and types, modified error handling for address validation.
modules/ibc/transfer.go	Updated import paths for lib and types.
modules/wasm/wasm.go	Updated import paths for lib and types.
nodes.toml	Changed msg_type from "store_code" to "bank_send" and updated wasm_file path to reflect the new project name.
types/txparams.go	Updated TransactionParams struct: changed Config field type and updated MsgParams field type.

Poem

In the meadow where rabbits play,
"Meteorite" has come to stay.
With hops and jumps, we cheer with glee,
A name so bright, as bright can be!
From "Hardhat" days, we now have grown,
In our new home, we feel right at home! 🐰✨

---

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.

CodeRabbit Configuration 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.