[chore] update example scripts

[aarmoa]

• Renamed example scripts to keep the numbers consistent

Summary by CodeRabbit

• New Features
  • Added a new JSON file containing a list of Ethereum-style addresses for reference or use in examples.

[coderabbitai]

Walkthrough

A new JSON file named ofac.json was introduced under the examples/chain/exchange/query/57_GrantAuthorization/injective_data/ directory. This file contains a flat array of 76 Ethereum-style hexadecimal addresses, with no additional metadata or structure.

Changes

File(s)	Change Summary
examples/chain/exchange/query/57_GrantAuthorization/injective_data/ofac.json	Added a JSON file with 76 Ethereum hex addresses

Poem

In a folder deep where data flows,
A list of addresses now grows.
Seventy-six in lines so neat,
Hex strings lined up, no repeat.
Rabbits hop and wiggle their nose,
"New data to nibble!"—so the story goes.

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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

🧹 Nitpick comments (2)

examples/chain/exchange/query/57_GrantAuthorization/injective_data/ofac.json (2)

2-75: Enforce consistent address casing or use EIP-55 checksum format.

Most entries are lowercase, but some (e.g., line 71) use mixed-case. To avoid typos and improve integrity checks, convert all addresses to checksum-case per EIP-55 or uniformly lowercase.

---

1-76: Add context or metadata for the OFAC address list.

As a bare array, the purpose and source of these addresses aren’t self-evident. Consider wrapping them in an object with a descriptive key (e.g., { "ofac_addresses": […] }), adding a JSON schema, or including a README to document their provenance and usage.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f6dd233 and ae27d1f.

📒 Files selected for processing (1)

• examples/chain/exchange/query/57_GrantAuthorization/injective_data/ofac.json (1 hunks)

🔇 Additional comments (2)

examples/chain/exchange/query/57_GrantAuthorization/injective_data/ofac.json (2)

1-76: OFAC list addition looks correct.

The JSON is valid, properly formatted, and the array contains the intended Ethereum-style addresses.

---

2-75: Verify uniqueness of the address list.

With dozens of entries, it’s prudent to ensure no duplicates slipped in. You can run:

#!/bin/bash
# Description: Check for duplicate addresses in ofac.json
jq -r '.[]' examples/chain/exchange/query/57_GrantAuthorization/injective_data/ofac.json \
  | sort | uniq -d