Use Ethereum Style Addresses

[JakeHartnell]

We're an Ethereum project. : )

0x is the standard.

We don't have to remove support for Bech32, but it's not the preference.

Now, when we do this and how we do this is an open question and needs further discussion.

[ethanfrey]

Does keplr or leap allow us to use 0x addresses?

I'd rather go 100% 0x. Having a mix of both is a huge headache (eg. which text format are the contracts using to save it when they get it from verify_address)

[ethanfrey]

How to generate the Ethereum Address from PubKey, with tip about uncompressed key

And we should also support checksumed addresses.

For the client tooling, we will also want to use the m/44’/60’/0’/0/x HD derivation path.

[ethanfrey]

Things to test:

• Change address derivation / format and code compiles
  • Update address verify contract import, so it always provides lowercase hex string (not variable case)
• Update test code to use new hex addresses.
  • cw-multi-test
  • cw-orch
• Ensure following client libraries work:
  • cosmrs
  • cosmjs (or interchain.js??)
• Test Keplr compatibility (or other cosmos wallet)

[ethanfrey]

One issue - instanite2 addresses.
build_instantiate_2_address defines a proper way to get the raw address bytes from the data. We use the same format just encode it 0x style not bech32 style.

However Eth 0x addresses are only defined in 20 bytes, not the 32-byte variant we use for contracts. We would have to change everything to 20 bytes for contracts as well, thus breaking some of the aboe compatibility

Also, alloy-primatives seems to be a solid library with MIT license that provides this functionality