ethux.design · generative design system
A contract address is already
a specification.
Input a contract address. The system classifies its functions against 38 Ethereum UX problem framings, then generates design system components that address the UX decisions it forces.
Try an example:
How it works
Fetch ABI
The contract ABI is fetched from Etherscan. Every function is extracted and classified.
Match framings
Function names are matched against 38 problem framings across 8 opportunity areas. 8 are Critical severity.
Generate components
Design system components are rendered for each matched framing — demonstrating the UX decisions the contract forces.
Problem framings index — 38 framings across 8 areas
View all →User Onboarding
The moment someone decides to try Ethereum, a clock starts. Within five minutes, they will either complete their first action or leave permanently. These are the walls between curiosity and that first transaction.
Transaction Clarity
Every wallet transaction is a trust decision. Users are asked to approve things they can't read, in formats that obscure risk. These are the gaps between what the user sees and what actually happens.
Cross-chain Flow
Ethereum now spans dozens of networks. Users see fragmented balances, manual chain switching, and bridges that feel like sending money into a void. The protocol solved scaling. The UX hasn't caught up.
Safety & Security
One bad experience, one lost transaction, and a user is gone for good. Solutions should empower user agency with transparent, controllable defenses rather than opaque restrictions users never opted into.
Mobile & Connectivity
More than half of web traffic is mobile. Yet connecting a wallet from a phone browser remains one of the most broken flows in the ecosystem.
Accessibility
Over 75% of cryptocurrency users are non-native English speakers. Most dapps are English-only, jargon-heavy, and fail basic accessibility standards. This is the largest unaddressed audience in the ecosystem.
Protocol Design
Some UX problems can't be solved at the wallet layer. They originate in protocol design decisions that ripple outward as confusion, friction, and risk for end users.
Daily Operations
The tasks people do every day: sending tokens, checking balances, managing gas. These should be the most polished flows in the ecosystem. They are often the most frustrating.