Ethereum

The lack of chain-specific information (such as name or ID) in the Ethereum address format creates several interoperability challenges.

e.g. L1 to L2 txs require an aliased `msg.sender`. 

How can the address format be improved to address this issue?

It's a thorny one, I remember conversations in 2021 about extending address from 20 to 32 bytes (for collision resistance + the plan to tag address with their state expiry "epochs").

Here's a bunch of links about approaches there:

Co-Founder at sablier.com, and open-source developer. I have a broad range of interests, including longevity, epistemology, physics, and psychology.

It's a thorny one, I remember conversations in 2021 about extending address from 20 to 32 bytes (for collision resistance + the plan to tag address with their state expiry "epochs").

Here's a bunch of links about approaches there: https://ethereum-magicians.org/t/thoughts-on-address-space-extension-ase/6779

Perpetual soldier of fortune, occasional internet slacker.

Cooking 0xFable — the fully on-chain trading card game for nerds

I don't remember specifics, but ultimately none of the solution were deemd truly satisfactory (there was a call with a bunch of people from the Ethereum R&D Discord and we kinda drew a blank) and I don't think that line of inquiry saw a lot of movement since.