To onboard small-ish content creators.

1) create nsec that I don't see

2) publish their stuff + a #communikey around it

3) show them the interactions + zaps

4) hand over*

*eeds a part in the code that you run inside the enclave that lets the onboarded creator export the nsec and proveably tell him this is the first time this happens

Reply to this note

Please Login to reply.

Discussion

Sounds doable on the enclave side. How would creator prove they are who they say they are to the enclave?

Wait, do they need to?

If they can export the nsec, see it its the first that happens, then we don't need a third party, no?

If it's not the first time, well they should ask questions, lol.

So you create an nsec for Taylor Swift and start reposting her insta pics on nostr, those get zapped, eventually you tell her about those sats and invite to take over the nsec. Is that the set up? Wouldn't you want to prove to enclave, somehow, that it's her? Otherwise someone could front-run her?

Also Taylor Swift can sue you out existence for that, lol. Any creator can.

I said small-ish creators.

Not mind-controlled slaves acting on the world stage.

That's a non-starter for any creator of any size. You'd need an explicit contract with them first allowing you to use their image in this way. If not even a tiny creator could sue you for a lot and win.

The creators that care about their IP are :110percent: the wrong ones to onboard.

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.

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.

Confidential compute --> content creator bounties? Cool idea nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhku6t9dshxummnw3erztnrdakj7qpq49p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq3hga3p!

nostr:nevent1qvzqqqqqqypzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qqsf6clq48hy5ta5wryf52hva0ca2upje660gaxmhmdmvgqshdf5y9gjtepcv