-
Notifications
You must be signed in to change notification settings - Fork 442
feat(tm2/pkg): allow customizable bech32 prefix #4873
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
🛠 PR Checks Summary🔴 Maintainers must be able to edit this pull request (more info) Manual Checks (for Reviewers):
Read More🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers. ✅ Automated Checks (for Contributors):🔴 Maintainers must be able to edit this pull request (more info) ☑️ Contributor Actions:
☑️ Reviewer Actions:
📚 Resources:Debug
|
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
8c434f6 to
fbaf94d
Compare
|
Could you please check the CI failures so we can proceed to the next step? Thank you |
done @notJoon |
notJoon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good. I remember there was a related discussion in PR #4008, and this appears to be policy-related, it would be better to handle the details in the next step.
Additionally, how about adding a test case that uses IsValid for addresses with custom prefixes?
We could, but that is somewhat annoying because if you modify the prefix it modifies is across all tests. |
Allow customizable bech32 prefixes.