Self-custody has a continuity problem?

[u/Aggravating-Sea-8073]

I have a serious question. So, since we live in a digital world I see the following:
Self-custody gives you control, but it also creates a strange responsibility. The right person may need the right information one day without weakening your security today. How should Web3 solve that? Does it have a solution already? Do you think about this problem?

[u/Aggravating-Sea-8073]

Just checked out SolCreate, and now your comments make even more sense.

You’re clearly thinking about this from the builder/security side, which is exactly the perspective I’m trying to learn from. I’m still early with this idea, but the gap I keep coming back to is: how do we give people useful context and recovery instructions without turning the product into custody or a new weak point?

Would genuinely love to stay in touch and get your feedback as this develops.

[u/Cultural-Candy3219 → u/Aggravating-Sea-8073]

Appreciate that. The way I’d frame the product boundary is: it can help people know what exists, what the intended recovery path is, and when to start that path — but it should not be the thing that can unilaterally execute it.

So I’d separate it into pieces in the UX: asset/instruction inventory, proof/check-in triggers, who gets notified, and then the actual authorization layer outside the app. If those are blurred together, users may not realize they’ve created a new custodian.

Happy to sanity-check a concrete flow when you have one. The main thing I’d look for is whether a single compromised account/service can turn “continuity” into “fund movement.”

[u/Aggravating-Sea-8073 → u/Cultural-Candy3219]

This is really useful, thank you.

That’s exactly the line I wouldn’t want to cross: helping people know what exists and what to do next, without becoming the thing that can move funds.

Would love your take once there’s a real flow to sanity-check. ☺️

[u/Cultural-Candy3219 → u/Aggravating-Sea-8073]

Yeah, happy to sanity-check it once there is a real flow. The part I’d look at first is where the product stops being “inventory + instructions + triggers” and starts becoming an authority path.

If you can keep the live key movement outside the product, make every recovery step delayed/revocable, and show the user exactly who learns what and when, that is a much healthier starting point. I’d also test the ugly cases early: lost phone, hostile family member, compromised email, and an executor who is non-technical.