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

fix: 🐛 improve chain id import in ethereum transaction #625

Merged
merged 3 commits into from
Mar 31, 2023
Merged

Conversation

albertolerda
Copy link
Member

Now chain id can also be imported from KEYS or DATA.
Chain ID can have encoding 'string' or 'integer'.

When the chain id is set, we look at ACK and see if the
variable references a value which is loaded. In this case:

  • if the encoding is 'integer' his numeric value is imported.
  • if the encoding is 'string' we try to import its numeric value,
    if it fails we import it as O.from_string (backward compatibility)

If the name is not loaded from keys or data, we use the value inside
the zencode script

matteo-cristino and others added 3 commits March 31, 2023 13:03
Now chain id can also be imported from KEYS or DATA.
Chain ID can have encoding 'string' or 'integer'.

When the chain id is set, we look at ACK and see if the
variable references a value which is loaded. In this case:
- if the encoding is 'integer' his numeric value is imported.
- if the encoding is 'string' we try to import its numeric value,
  if it fails we import it as `O.from_string` (backward compatibility)

If the name is not loaded from keys or data, we use the value inside
the zencode script
@jaromil jaromil merged commit 6d3b53b into master Mar 31, 2023
@jaromil jaromil deleted the fix/cid branch March 31, 2023 14:18
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 this pull request may close these issues.

3 participants