Very curious what the hell you guys are doing over there; are you changing code or hardware specs?
I wrote a script to do this very early on; if interested I can post it
You probably didn’t publish your kind 0 far enough; this is a good use of blastr
Exactly, and I think that’s where zapraisers would shine. I would love to do a zapraiser for stratum v2
I’m going to add the ability of referencing a previous note so zaps to both notes go to the same zapraiser; someone requested this for longer running zapraising efforta and I think that’s a brilliant idea
I’ll probably get to do that sometime this week 😅
this
doesn't need to be solved on layer 1; we just need better key management solutions on the protocol; identity belongs in a higher layer
furthermore, we need nip-26 to be extended to allow scoping the token further
right now we can only limit created_at and kind
we should have the capability of scoping `content` (https://github.com/nostr-protocol/nips/pull/222) and `tags`
100%
I've discussed this with fiatjaf, and he argues that nip-26 delegation token revocation can't be guaranteed;
I still think it should happen:
* nIp-26 delegate key to a new pubkey
* if pubkey abuses, delegator creates an opentimestamped event revoking and blasts the revocation to all known relays
* if delegatee continues to abuse delegator has timestamped proof that abuse was not authorized by the delegator
Financial innovation is here
Definitely will happen
One must wonder if they have such horrible black coffee to segment their customers or something
