Global Feed Post Login
Replying to Avatar Blake

If anyone is interested in Nostr Proof of Work, I have a draft NIP and functional implementation of a POW service provider that can remotely generate POW for your events before signing and publishing.

The general feedback and support was on Nostr, and the Github issue responses were more concerned based.

I built this entirely in anticipation for mass Nostr spam protection - in case we needed it urgently. We seem to be doing ok with spam now, however it’s possible we may need to revisit minimum POW for events when publishing - as a relay opt-in.

And just to clarify, I don’t like burnt CPU cycles either. Paying sats directly to a relay works well - however unless you pay for 10+ relays.. your events are not decentralised (as most relays move toward becoming paid to publish). POW helps address the issue of low value spam and flooding - it doesn’t solve everything.

https://github.com/nostr-protocol/nips/issues/340

Avatar
Heri Sim 2y ago

Why not captcha for every few events?

Reply to this note

Please Login to reply.

Discussion

Avatar
Blake 2y ago

I suggested that as a joke in the past.

I don’t think the UX works - do you have to perform a CAPTCHA per relay you publish to for every three events? Relays would otherwise have to trust some shared CAPTCHA service session or result.

Plus CAPTCHA doesn’t work well, and is dying slowly. It was a rat race of computer vs computer.

Thread collapsed