Sending crypto is a uniquely stressful UI moment: an irreversible transaction aimed at a 42-character address that varies by exchange and network. MetaMessage answers one question: how can we be sure we're sending to the right address?
The project ran in two parts: the original concept, published on Medium and built with Madhu Sanjeevi (Mady), and a second iteration produced as a MetaMask design challenge in July 2021.
The problem
This is a fear my friends and I have faced personally. One wrong character, one wrong network, and the money is gone. The current defense is squinting at hex strings and sending nervous test transactions.
Part one: the concept
Chat with the account owner before you send. MetaMessage adds a verification conversation to the send flow: both parties confirm the address, reach consensus, then the transaction proceeds. The inspiration is Google Pay, where it's already common to message an acknowledgment before money moves, a social confirmation layer on top of a technical one. Crypto's stakes are higher and its addresses are worse; it needs this pattern more, not less.
Part two: the MetaMask challenge
The second pass rebuilt the concept strictly inside MetaMask's UI guidelines. I re-created the MetaMask interface so the feature reads as native, not bolted on: the messaging step slots into the existing send flow, with confirmation states matching MetaMask's own patterns.
Why it holds up
For newcomers, the anxiety of the first send is a real retention cliff. A consensus step before an irreversible action is a pattern the space still hasn't shipped at wallet level. It still should.
