Content
@
0 reply
0 recast
0 reaction
✳️ dcposch on daimo
@dcposch.eth
Two UX Original Sins Holding Ethereum Back 1. Hex addresses 2. Connect Wallet no mass adoption till we we submerge both (they'll live on, just not user-facing) why? (1/3)
7 replies
12 recasts
64 reactions
✳️ dcposch on daimo
@dcposch.eth
ADDRESSES - NO VALIDATION. you can accidentally send $10k to the USDC contract address--burnt--and UIs won't warn you. conversely, no way to prevent arbitrary inbound. every address is an everything bagel! so for now, every wallet must support any asset arriving on any chain. explain this to your parents (h/t @phil):
2 replies
0 recast
6 reactions
Gabriel Ayuso
@gabrielayuso.eth
Hex addresses should be treated like IP addresses for accounts instead of machines. We have firewalls, NATs, proxies, load balancers and a bunch of tech to manage requests sent to IP addresses. We'll need the same for hex addresses as more data moves onchain. Wallets as we know them today will go away.
0 reply
0 recast
5 reactions
Web3collective
@type
Also Metamask
1 reply
0 recast
0 reaction
Alejandro Dopico
@aadopii
Agree. Working on that @fungi
0 reply
0 recast
0 reaction
Marc
@marcb
1. Solved by ENS, no?
0 reply
0 recast
0 reaction
Saadiq
@saadiq
I get the why. Really interested in the how. The best I can think of is more custodial wallet setups for those that prefer with a back door to take full control if you're a hobbyist.
0 reply
0 recast
0 reaction
pipe.eth 🎩
@pipe
Base58 is neat, but its ugly. Hex addresses are aesthetically pleasing. Shouldn't matter much, but somehow it makes me prefer them.
1 reply
0 recast
1 reaction
