Bright Disputes

scroll

Bright Disputes

Sole Product Designer • End-to-End UX/UI & Logic Mapping MVP

Designing Trust: Making Zero-Knowledge Proofs Accessible to Non-Technical Users.

My challenge was to make invisible cryptography trusted by non-technical users. I translated complex Zk-Snark logic into a clear, linear voting interface that allows Juries to resolve high-stakes disputes without needing to understand the math.

Complexity Breeds Distrust

Users needed to stake real money on disputes, but the underlying tech (Zk-Snarks) was mathematically complex and invisible. The core friction was trust: "How do I know my vote is counted if I can't see it?" If the interface felt opaque, users wouldn't stake funds, and the system would fail.

A screen showing a maket view in TMS web app
A screen showing a maket view in TMS web app
A screen showing a maket view in TMS web app

From Complexity to Clarity

Usability: Successfully simplified a complex cryptographic process into a linear 4-step flow. Delivery: Delivered high-fidelity prototypes that enabled the team to implement Polkadot.js integration ahead of schedule. Validation: Enabled the successful demo of privacy-preserving voting on the AlephZero testnet.

Visualizing the "Black Box"

The challenge was displaying votes that the user cannot see yet. I used a "Locked" card state to represent encrypted votes. This visual metaphor builds trust that privacy is active without requiring the user to understand the cryptography behind it.

A screen showing a current truck route in TMS driver mobile app on top picture of pallets
A screen showing a current truck route in TMS driver mobile app on top picture of pallets
A screen showing a current truck route in TMS driver mobile app on top picture of pallets

Humanizing the CLI Integration.

The "Verify" button isn't just a toggle—it triggers a heavy off-chain calculation via CLI. I designed clear Feedback Loops ("Loading" -> "Verified") to bridge the gap between the browser interface and the command-line proof generation, managing user expectations during latency.

Mapping UI to Smart Contracts.

I designed the input fields to map 1:1 with the Ink! Smart Contract constructor. The interface validates wallet address formats and strictly separates "Staking" fees, ensuring that when a user hits "Create," the payload matches the chain's validation logic perfectly, preventing failed transactions.