Wait wait wait, I'd have credentials for accessing the enclave, right?

The point is to pass on those credentials and not the nsec.

Also, if the service provider tries to rug us than we can still see that someone already exported the nsec.

Reply to this note

Please Login to reply.

Discussion

Ah got it, you pass the bunker url to creator, and they try to export and that only succeeds once. Sounds good!

Yup :Check:

If I made a noob error in that logic, tell me por favor :prayinghands:

If not, I can use this!

Sounds fine, will see what I can do. One issue at this point is that if enclave is restarted, all the state is gone, so storage of long term assets is a challenge, especially while it's not yet production ready. But we will solve that, so eventually your idea is gonna work.

Ow damn, yeah didn't think of that, of course.

Yeah, no stress. Def don't need this tomorrow :winkwithtongue:

For example, I have no idea if the service can just swap out the whole enclave for another or something.

But even if that's possible, they gain nothing except a bad rep.

If the code is well written, enclave operator can only turn it off, not mess with it in any other way.