You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ioctl still has many commands that rely solely on the io1 address format. Assuming we want to keep ioctl as the only tool that can manage io1 addresses if needed, it should support both the 0x and io1 address formats for input and output.
Let us know any background or context that would help us better understand the request (for example the particular use-case that prompted this request)
The text was updated successfully, but these errors were encountered:
What would you like to be added
ioctl
still has many commands that rely solely on theio1
address format. Assuming we want to keep ioctl as the only tool that can manage io1 addresses if needed, it should support both the0x
and io1 address formats for input and output.Notable examples:
io1
-only output:ioctl account list
io1
-only input:ioctl ioctl ioid device ...
Why is this needed
See IIP40
How important you think this is for IoTeX
Additional information
Let us know any background or context that would help us better understand the request (for example the particular use-case that prompted this request)
The text was updated successfully, but these errors were encountered: