@csvensson

Interesting to see with Tempo how they're showing user transaction receipts in a way that resembles Stripe payment receipts. Question I have in my mind is if this will be adequate for users. Are they ok with seeing 0x566f…b45f as a sender? The philosophy of the @enscribe team is that these addresses must be replaced with decentralised names, akin to how ip addresses have been replaced by DNS addresses for web users. But, we could be wrong. Perhaps people will be ok with these truncated hex addresses, after all, bank accounts are numeric digits or alphanumeric in the case of SWIFT/BIC codes. My belief is that we have the capabilities to eliminate hex addresses for users with technology we have now in web3. Therefore we should do it. Sure, people may be ok with some hex in a receipt, but it's even better if the intent of the thing that that person was interacting with is in an intuitive, human readable form. ctd

2 replies

1 recast

1 reaction