Web3 UX still hurts — and the fix isn't another wallet

We just finished a year-long engagement with a tokenization protocol. The chain is fast (240ms blocks), the audits are clean (zero high-severity findings), and the institutional integrations work. The hardest part was none of that.

The hardest part was getting an asset manager's compliance officer to feel comfortable clicking a "Sign" button.

The wallet is the wound

Every wallet asks the user a question they cannot answer: do you trust this transaction? The hex-encoded calldata that appears in MetaMask is, charitably, a riddle. Unlocking the next wave of on-chain adoption is not a chain problem. It's a problem of intent legibility.

What we shipped instead

For Lumen, we built an institutional wallet that decodes calldata into plain English before the signature, with a typed schema per protocol method. The calldata view is still there — it has to be — but it's collapsed by default. Above it: "You are about to transfer 5,000 USDC to the Lumen treasury. This action is reversible within 24 hours through compliance recovery."

That last sentence is the real product. The chain is plumbing.

The lesson

If your Web3 product asks the user to read hex, you are asking the user to do your work. Spend the engineering on a typed intent layer. Spend the design on the moment of consent. Everything else is downstream.