Accept 0x addresses from CLI (and optionally RPC)

[adlrocha]

Issue type

Bug

Have you reproduced the bug with the latest dev version?

Yes

Version

v0.5.0

Custom code

Yes

OS platform and distribution

No response

Describe the issue

Right now, it is really confusing to determine when one should use 0x and t4 addresses from the agent. The reason for this is that we use Address throughout all of the IPC agent except when we interact with the ETH RPC. This implies the use of fvm_shared::Address as the underlying type. However, the address used to interact with the subnet, and all the Ethereum tooling, expects a 0x. This leads to many users using their 0x instead of f4 address as arguments. Even our config expects a 0x address for the default accounts in fevm instead of the underlying f4.

A potential implementation could be through a top-level Address wrapper type that can be converted into both f4 and 0x as described in #407.

Repro steps

N/A

Relevant log output

No response

[jsoares]

Also important to take into account (currently) split key stores and the potential need to search for an appropriate key using the converted format.

[adlrocha]

@mturilin, this is the issue that I mentioned yesterday that may fit perfectly our first PDR.

[adlrocha]

Fixed in #344