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

Converting back to the original form #3

Open
vbakke opened this issue Dec 28, 2017 · 0 comments
Open

Converting back to the original form #3

vbakke opened this issue Dec 28, 2017 · 0 comments

Comments

@vbakke
Copy link
Owner

vbakke commented Dec 28, 2017

Given the nature of this conversion, I think terms like asciiToTrytes and trytesToAscii will be confusing. Since they will not match perfectly both ways. (The square peg, round hole issue.)

Why do we convert?

We don't convert for fun. And I think we always want to convert back to the original form. For example, text message to trytes for the transaction, should be converted back to text. Iota seed that may need to be converted to bytes for AES encryption, but is of no use, unless it is converted back to the original seed.

Native

I suggest that we emphasis a native side, and an encoded/converted side. And that the function names emphasis this issue.

Good example is how @todofixthis renamed function to encode() and decode() in iota.lib.py.

@vbakke vbakke mentioned this issue Dec 28, 2017
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

No branches or pull requests

1 participant