Add EIP-55 checksum support and validation utilities for EVM addresses#2233
Add EIP-55 checksum support and validation utilities for EVM addresses#2233iron-prog wants to merge 3 commits into
Conversation
Up to standards ✅🟢 Issues
|
WalkthroughAdds EIP-55 checksum generation and verification to EvmAddress, plus normalization and validation helpers (normalize, is_valid, is_checksum_valid) and unit tests; imports keccak256 and implements to_checksum_address() to produce ChangesEIP-55 Checksum Validation for EvmAddress
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 1df5ce9b-8a4d-4fc6-a6e8-fcb6fef6ba15
📒 Files selected for processing (2)
src/hiero_sdk_python/crypto/evm_address.pytests/unit/evm_address_test.py
f4bfb95 to
5469ffd
Compare
|
@iron-prog Can you link the issue you are trying to solve with this PR? This can be done within the description. Tapping edit allows you to add an issue. Format should be "Fixes: #Issue_Number Thank you |
|
Created and linked issue #2234 for this feature |
|
Hello, this is the OfficeHourBot. This is a reminder that the Hiero Python SDK Office Hours are scheduled in approximately 4 hours (14:00 UTC). This session provides an opportunity to ask questions regarding this Pull Request. Details:
Disclaimer: This is an automated reminder. Please verify the schedule here for any changes. From, |
|
Hi there! I'm the LinkedIssueBot.
Thank you, |
There was a problem hiding this comment.
Actionable comments posted: 4
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 2606c85a-2e05-4342-8766-4acbfcd5a5c8
📒 Files selected for processing (2)
src/hiero_sdk_python/crypto/evm_address.pytests/unit/evm_address_test.py
3709a28 to
49f6a3e
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 0534818d-b981-4cdd-abb8-ea8557926269
📒 Files selected for processing (2)
src/hiero_sdk_python/crypto/evm_address.pytests/unit/evm_address_test.py
6ee8922 to
c074dbc
Compare
There was a problem hiding this comment.
Hey @iron-prog , implementation looks good. One small non blocking polish item I'd suggest is few of the newly added unit tests still do not have docstrings, while the surrounding evm_address_test.py tests generally do. Since the contributor testing guide asks for clear test names plus brief docstrings, it may be worth adding one line docstrings to the new validation/normalization tests before merge for consistency.
There was a problem hiding this comment.
Thanks for the suggestion I've update the all test cases with valid doctoring
Signed-off-by: iron-prog <dt915725@gmail.com>
59dbe85 to
628b0cf
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 94d3a6df-5277-40db-971e-f766997b6192
📒 Files selected for processing (2)
src/hiero_sdk_python/crypto/evm_address.pytests/unit/evm_address_test.py
|
@iron-prog, Thanks for the PR moving this to draft, unless the proposal get merge in the sdk-collaboration-hub. |
|
Hi @iron-prog, This pull request has had no commit activity for 10 days. Are you still working on it?
If you're no longer working on this, please comment Reach out on discord or join our office hours if you need assistance. From the Python SDK Team |
|
I am currently busy in ongoing final university exams. Please feel free to leave architectural reviews on this (hiero-ledger/sdk-collaboration-hub#256) the meantime. I will address all feedback and proceed with the implementation right after my exams are over. Thanks!" |
|
@manishdait @chaitanyamedidar my exams are over now I'm back on this , since i did recieve any architechral feedback on the proposal , so I wanted to gently ping the maintainers to see if there are any initial thoughts, concerns, or changes required for the design. |
Description:
Add EIP-55 checksum support and validation utilities for EVM addresses to improve correctness and developer experience.
Related issue(s):
Fixes: #2234
Notes for reviewer:
Notes for reviewer:
Checklist