Skip to content
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

[FEATURE] Use .utf8 instead of hex-encoding/decoding #17

Open
turbolent opened this issue Sep 13, 2023 · 0 comments · May be fixed by #18
Open

[FEATURE] Use .utf8 instead of hex-encoding/decoding #17

turbolent opened this issue Sep 13, 2023 · 0 comments · May be fixed by #18
Assignees

Comments

@turbolent
Copy link
Member

Issue to be solved

The templates to add a contract and update a contract assume the code parameter is hex-encoded.

Hex-encoding and hex-decoding is inefficient and unnecessary.

Suggest A Solution

Replace the use of .decodeHex() with .utf8.

This is a breaking change: Users of the templates need to be updated to pass the code as-is, without hex-encoding it.

What are you currently working on that this is blocking?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant