Using native types instead of strings

[benesjan]

Describe the Feature

In larger codebases it makes sense to use types which are as descriptive as possible. In ethers currently string type is used in areas where it would make sense to use a more specific type. Typical example might be working with Ethereum addresses in a string form, or having storage slot value in a hex string form. It would make sense to define an EthAddress type instead and always use some integer format for slot values etc..

This is for example causing issues when user wants to set a storage slot value in hardhat and then it fails if the user is not aware that he can't have the value 0 padded. If that value was a number that issue could not occur.

Code Example

No response

[ricmoo]

The input types aim to be as generic as possible and return types as strict.

Nominal Typing is not yet available in TypeScript, but sounds like it may be coming. There is a work-around being discussed, but it prolly won’t make it into v6. But feel free to discuss it in that thread. :)

[benesjan]

I understand why it's desirable for the input to be as generic as possible but I think it can promote bad coding practices and it makes it harder to read the code.