Code bounties on nostr: pubkeys pledge certain amounts for specific tasks. when the work is done, Zaps are used to confirm that pledgors sent sats to the assigned pubkey that finished the task. Since the zapper key in this case is controlled by the pubkey who finished the task, it cant be faked. UI to show top bounties and tasks. Could also list top pubkeys who fulfull pledges or not.

Reply to this note

Please Login to reply.

Discussion

Whats nice about this is that it’s completely decentralized and requires no escrow, ratings are based on web of trust and zap-based pledge fulfillment.

This would also support multiple implementations of the same bounty, pledgors can choose which implementation they want to pay out to, anyone can assign themselves to the bounty to claim it. All done in a decentralized way. This is really cool. Not sure why I didn’t think about this until now. Thanks #coffeechain

Maybe this solves some of your bounty concerns nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 ?

Yes, I like it. Just need some buttons to click. Those other bounty sites were too burdensome for everybody.

This is fivestr or 99designstr.

One could also implement followup payouts, to encourage people to still try.

when pledgor doesn’t pay out, what happens?

Public record of it, lower rating, and they don't get work in the future.

correct, clients could calculate an “estimated payout” based on the pledgor ratings

Sorry, still confused

Who’s the pledgor?

Who’s the pledgee?

Is someone pledging to pay someone to do work? (dev gets paid after work is done)

Is is a dev pledging to do work for an amount of sats? (dev gets paid first before they start the work)

pledgor is the one pledging funds, anyone can add to a bounty to become a pledgor. No money is sent, it’s just a promise at this point.

Anyone can claim the bounty and become a pledgee (person receiving some, all, or none of the pledges).

Once any pledgor is satisfied with any of the proposed bounties (or if that was the one that was merged), the pledgors are at that point obligated to zap the dev’s bounty claim. Once the pledgor does this, the devs zapper will send a zap for the claim note, and clients can use this to confirm that the pledgor fulfilled the pledge.

If they don’t, everyone will be able to see that and their rating could be affected.

There are some attacks like using a fake zapper to claim bounties and lie about not receiving a zap, but for the most part it should work ok…

I’m a trust worthy simple man sign me up nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s

Their rating will go down, any client can calculate this

Sign me up. ⚡️

I got this idea after seeing your damus bounty 😅

I had a hunch. 😄 Great idea. Gamification, incentives, bragging rights.

Would love be cool to see open issues count dropping, as I commit bounties and watch them get picked off.

Good idea, the intermediate audit communication may be a bit problematic because of the non-standardized service.

nostr:npub1zumzudhtu2558fgvycnjlc7pq9l4m338vghgcfzafftz9qg45ruslzpl4x

hahaha, we were just talking about creating a platform for it where users can contribute via zaps to the features they wanna see implemented in their favourite nostr apps. The more the zaps, the higher the priority. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s

now, to bootstrap the bootstrap!

How can I use this today? What are zaps?