I’m Muizz. Just committed to working with Stacks builders and wanted to introduce myself properly.
I’ve been in Web3 for about 6 years. Started trying to build smart contract prototypes, realized I was more interested in understanding why users keep losing money and getting confused by systems we build. Spent the last 3 years doing UX research - specifically what I call UX3 (Infrastructural UX).
What’s UX3?
Most UX work focuses on making interfaces clearer. I focus on designing safety into the protocol execution layer itself - state transitions, irreversibility constraints, permission models, behavioral flows. The idea is: if you get the infrastructure right, you prevent harm before users ever see it.
Why I’m here:
Bitcoin L2s like Stacks have unique execution constraints (Clarity semantics, finality, cross-chain interactions). I want to help builders design systems that account for these from day one, not retrofit safety later.
What I’m offering:
System audits for builders (pre-development risk mapping)
UX3 framework implementation (specific to Stacks architecture)
Open collaboration with other UX researchers in the ecosystem
Everything I learn gets published openly
Background:
Ran live on-chain experiments studying user behavior and market coordination
Research published under BlockBoard (behavioral infrastructure initiative)
Currently building resources specifically for Stacks builders
If you’re building on Stacks or doing UX/safety work in the ecosystem, I’d love to connect and collaborate. Let’s help builders ship products that real people can actually use without losing funds.
hey @Muizz welcome to the Stacks community. You should reach out to Diego and Valeria from DH3 to see if their efforts in UX for Stacks apps matches with what you’re looking for. Check out this livestream clip we did with them:
Thanks @ECBSJ ! Yeah, I saw the DH3 clip - what they’re building is really valuable, especially for builders without UX research budgets.
I can see how there’s potential collaboration:
DH3’s AI helps builders with audience research and interface-level audits (who’s the user? is the UI clear?).
I focus on infrastructure-level risks (where can users lose money due to execution design? what backend interventions prevent that?).
They’re complementary:
∙ DH3 helps builders understand their users and audit their interfaces
∙ I help builders identify protocol-level risks before they even design those interfaces
Concrete example:
A builder uses DH3 to understand their audience and audit their wallet UI for clarity. Great.
But if that wallet lets users send to wrong chains and lose funds - that’s not a UI problem. That’s an infrastructure problem (missing address validation at execution layer).
That’s where I come in - researching those upstream risks and helping builders understand what infrastructure they need to prevent harm.
Would love to connect with Diego and Valeria to see how we can work together. And looking forward to the working group discussion with the DevRel team.