Crypto design challenges

Did you accidentally approve a token on a contract you probably shouldn't have? Unfortunately, scenarios like this happen more often than they should. Wallets need an emergency resources in times like this. Perhaps modern wallets could have a sort of emergency "oh shit" button.

So you might be thinking.. okay this is totally wrong and even the Bitcoin whitepaper established that cryptographic proof should be used instead of trust for decentralized systems. And that the ethos in the crypto community today is "Don't trust, Verify."

A core part of all wallets is a way to list transactions. Too many wallets today treat this as a list of data without much thought about what it means for the user and within the context of trust.

How can we attach a knowledge graph to the wallet? A set of public and private preferences, a list of friends, a list of dApps you trust and how much, a list of blocked addresses, dApps and more. This graph data would ideally be a mix of public and private data stored off-chain.

Show me how much money I just lost on gas with this failed transaction. Don't make me go to Etherscan to try to piece it all together; it can be rather confusing to discern on Etherscan with gas price, transaction fee, gas fee and gas usage, especially with EIP-1559.

The next billion crypto users shouldn't have to pay to make crypto usable. They shouldn't have to deal with long addresses that could lead to huge issues like them losing funds. What's the Gmail of wallet addressing?

Web3 guidance & curation: This is the discovery phase for slightly more advanced users that are now asking "What can I do with my crypto?" There are opportunities to help people discover what exists, what is safe to use and guide people along the way. It's 1998 and people rely on AOL or the Yahoo! homepage to show them what's out there. What's the ... See more

Be hyper transparent around transaction status. We expect things today to be instant but the blockchain is one of the only pieces of modern technology that can feel very slow at times. We need to take great care in displaying transaction status. The average user should never have to visit Etherscan/Polygonscan/etc just to see how much time is left ... See more

With that, we'll have to be careful about introducing thoughtful abstraction—simplifying and hiding complexity without diluting the essence of web3 or taking away control when it might be valued.