Five on Nostr: SatShoot concentrates on finding the best client or freelancer with minimized ...
SatShoot concentrates on finding the best client or freelancer with minimized reliance on third parties:
- reviews
- public zaps as payments
- outbox model
- client-side wot
- app-scoped follows
It is a simple scenario whereby freelancers bid on problems, not a bounty type of flow. Specs available [here](https://github.com/Pleb5/satshoot/blob/main/apps/satshoot/EVENT_STRUCTURE.md) .
Payment flow in SatShoot is very simple, you always pay as much as you want but cannot reverse it(LN, nip60 Cashu ecash). There's option to pledge a split from freelancer earnings which is tied to reputation.
Escrow could play a part in it, it's just not a focus yet. Talked about this with VntonIO (nprofile…tj7x) before, he has a Cashu escrow service project going.
More on SatShoot design and plans:
It is hard to do nostr right and get a decent UX at the same time. It's doable but takes time and effort.
The core experience needs to be nailed first and foremost which is going to be there with the next version soon enough. Many details of the deal flow is pushed to the margins where parties can flexibly agree on exact terms.
The reason I did not go the bounties direction is that most of the time teams need to invest heavily without knowing that the work will be compensated. There are exceptions (eg bug bounties) but I wanted to solve something that seemed as a more pressing problem to me:
An unstoppable freelance market for earning sats. The strongest use-case is software development. So there's a natural incentive to integrate SatShoot with nostr-git and nostr-based project management like kanbanstr. Pledge splits can be extended to multiple parties that integrate SatShoot-like job posting.
That's my plan in a nutshell.
- reviews
- public zaps as payments
- outbox model
- client-side wot
- app-scoped follows
It is a simple scenario whereby freelancers bid on problems, not a bounty type of flow. Specs available [here](https://github.com/Pleb5/satshoot/blob/main/apps/satshoot/EVENT_STRUCTURE.md) .
Payment flow in SatShoot is very simple, you always pay as much as you want but cannot reverse it(LN, nip60 Cashu ecash). There's option to pledge a split from freelancer earnings which is tied to reputation.
Escrow could play a part in it, it's just not a focus yet. Talked about this with VntonIO (nprofile…tj7x) before, he has a Cashu escrow service project going.
More on SatShoot design and plans:
It is hard to do nostr right and get a decent UX at the same time. It's doable but takes time and effort.
The core experience needs to be nailed first and foremost which is going to be there with the next version soon enough. Many details of the deal flow is pushed to the margins where parties can flexibly agree on exact terms.
The reason I did not go the bounties direction is that most of the time teams need to invest heavily without knowing that the work will be compensated. There are exceptions (eg bug bounties) but I wanted to solve something that seemed as a more pressing problem to me:
An unstoppable freelance market for earning sats. The strongest use-case is software development. So there's a natural incentive to integrate SatShoot with nostr-git and nostr-based project management like kanbanstr. Pledge splits can be extended to multiple parties that integrate SatShoot-like job posting.
That's my plan in a nutshell.