Recovery transparency must improve without turning status data into a path to key material.
Application developers need a clear user-facing boundary, while wallet security requires recovery controls to remain narrow.
Who you’d be doing this for
“Our compliance lead keeps asking what a locked-out user can actually do, and I’m stitching together answers from different flows.”
Ratna Ngo · Blockchain Application Developer
Builds embedded-wallet onboarding and account-recovery experiences for a regulated payments application.
What is at stake
Pilot developers cannot consistently explain what users can recover or export from an embedded wallet. You have to weigh a useful developer surface against keeping recovery controls tightly bounded.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- developer clarity vs. key-material isolation
- stable API contracts vs. early learning
- user-facing explanation vs. custody boundaries
- fast pilot access vs. security review
Why Stripe
Privy sits between embedded-wallet applications and secure wallet infrastructure, so recovery boundaries shape developer trust in its APIs.
Written with these in mind
Not your kind of problem? 88 more at Stripe, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.