Fix/contract address validation

[Poafs1]

Summary by CodeRabbit

Release Notes

• New Features

  • Added utility function for validating fixed-length hexadecimal addresses

• Improvements

  • Enhanced contract address validation logic
  • Updated address validation methods to support more precise checks

• Bug Fixes

  • Improved address validation to prevent incorrect address inputs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
celatone-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 14, 2025 9:49am

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
celatone-frontend-main	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 9:49am
initia-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 9:49am
neutron-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 9:49am
osmosis-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 9:49am
sei-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 9:49am
terra-celatone-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jan 14, 2025 9:49am

[coderabbitai]

Walkthrough

This pull request introduces a new utility function for validating fixed-length hexadecimal addresses, specifically focusing on 20-byte addresses. The changes span multiple files, including CHANGELOG.md, utility validation functions, and EVM contract verification pages. The primary modification involves replacing the existing isHexWalletAddress with a more precise isHex20Bytes validation method, enhancing the address validation mechanism for EVM contract addresses.

Changes

File	Change Summary
CHANGELOG.md	Added new feature entry for fixed bytes hex address utility
src/lib/pages/evm-contract-verify/index.tsx	Replaced isHexWalletAddress with isHex20Bytes for contract address validation
src/lib/pages/evm-contract-verify/types.ts	Updated import and validation logic for contract addresses
src/lib/utils/validate.ts	Added new methods isHexFixedBytes and isHex20Bytes for address validation

Sequence Diagram

sequenceDiagram
    participant User
    participant ContractVerifyPage
    participant ValidationUtil
    
    User->>ContractVerifyPage: Enter contract address
    ContractVerifyPage->>ValidationUtil: Validate address with isHex20Bytes
    ValidationUtil-->>ContractVerifyPage: Validation result
    ContractVerifyPage->>ContractVerifyPage: Update form state

Loading

Possibly related PRs

• feat: add constructor args to EVM contract verify #1189: Introduces constructor arguments handling in EVM contract verification
• Fix(pages): EVM Verification #1190: Bug fix for EVM contract details verification process
• fix(components): contract address controller input validation #1191: Fixes contract address input validation

Suggested reviewers

• evilpeach

Poem

🐰 Hex addresses dance with grace,
Twenty bytes in a digital space,
Validation's art, now precise and bright,
Bytes aligned, everything's just right!
A rabbit's code, clean and neat, 🔍
Makes contract checks a coding treat! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c78ba28 and 62e0359.

📒 Files selected for processing (4)

• CHANGELOG.md (1 hunks)
• src/lib/pages/evm-contract-verify/index.tsx (3 hunks)
• src/lib/pages/evm-contract-verify/types.ts (2 hunks)
• src/lib/utils/validate.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (javascript)

🔇 Additional comments (5)

src/lib/utils/validate.ts (2)

50-58: LGTM! Well-structured validation function.

The implementation correctly validates fixed-length hex addresses by:

1. Checking exact format with regex
2. Validating hex content

---

66-68: LGTM! Clear specialized validator for 20-byte addresses.

Good use of the base validator with a specific length constant.

src/lib/pages/evm-contract-verify/types.ts (1)

2-2: LGTM! Clean validator function replacement.

Successfully migrated from isHexWalletAddress to isHex20Bytes while maintaining the same validation behavior.

Also applies to: 89-93

src/lib/pages/evm-contract-verify/index.tsx (1)

22-22: LGTM! Consistent validator usage.

Successfully replaced all instances of isHexWalletAddress with isHex20Bytes for contract address validation.

Also applies to: 50-52, 156-157

CHANGELOG.md (1)

42-42: LGTM! Clear and accurate changelog entry.

The entry properly documents the addition of the fixed bytes hex address utility.

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

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.