What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
🌟 Feature
What is the current behaviour (you can also link to an open issue here)?
Current when encoding parts in tuples that are uintN, it is not possible to pass a plain number. The number always needs to be encoded as hex first, as tuples only accept string type.
What is the new behaviour (if this is a feature change)?
Fix this behaviour by allowing to pass number for encoding.
What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
🌟 Feature
What is the current behaviour (you can also link to an open issue here)?
Current when encoding parts in tuples that are
uintN, it is not possible to pass a plainnumber. The number always needs to be encoded as hex first, as tuples only acceptstringtype.What is the new behaviour (if this is a feature change)?
Fix this behaviour by allowing to pass
numberfor encoding.Other information:
Closes #393