Content pfp
Content
@
0 reply
0 recast
0 reaction

. pfp
.
@chaskin.eth
Ethereum and its L2s are about to feel like one unified network Step 1 -> finalizing the address format standard and we’re getting close Before: 0x6A1... -> Which chain for tokens? πŸ€·β€β™‚οΈ After: 0x6A1...:Base:8453 -> Clearly on Base!
7 replies
1 recast
46 reactions

moritz πŸ’§πŸ”‘ pfp
moritz πŸ’§πŸ”‘
@moritz
nice! so this is different from ERC-3770 right? the format feels more intuitive to me https://eips.ethereum.org/EIPS/eip-3770
1 reply
0 recast
3 reactions

Paul Dowman πŸ”΄βœ¨ pfp
Paul Dowman πŸ”΄βœ¨
@pauldowman.eth
I don't understand chain vs root. Isn't the root part redundant? And isn't ...:ethereum:11155111 contradictory?
1 reply
0 recast
2 reactions

cqb pfp
cqb
@cqb
It's there a specific erc for this format?
1 reply
0 recast
0 reaction

Giuliano Giacaglia pfp
Giuliano Giacaglia
@giu
This is a big deal imo
0 reply
0 recast
0 reaction

oliver pfp
oliver
@oliverk120.eth
which fork could this be part of?
1 reply
0 recast
0 reaction

Gordo pfp
Gordo
@gordo
Nice, waiting of it
0 reply
0 recast
0 reaction

raquo pfp
raquo
@raquo.eth
so every client needs to bake in support for chain names to use this? why not use chainid?
0 reply
0 recast
0 reaction