Oddbean new post about | logout
 It'd be sweet if you could lock up ecash to the commit that closes out a GitHub issue. 
Whoever signs the commit that closes the issue could unlock the payment.  
 Workflow if maintainer is trusted:
1) maintainer creates a GitHub issue
2) maintainer assigns a cashu-address to the issue (maintainer knows SK)
3) bounties accumulate on issue
4) developer does work and closes issue
5) maintainer claims the ecash and redistributes to developer 
 What if cashu token is revoked? Should the bounty fluctuate? Should maintainer claims the token immediately and essentially "escrow" them?

Is this basically just an escrow file for locked cashu tokens? 
 Maybe something like this
1) maintainer creates a GitHub issue
2) public key created by maintainer for that issue
3) dev who wants to work on issue "claims" the issue and generates a new key, issue key + dev key (like a multi sig key)
4) cashu-address created from new key to solicit funds to do the work
5) dev does work and merges issue
6) maintainer reveals SK to dev to claim the cashu tokens. 
 Essentially the dev would wait for tokens to accrue before doing work. 
People contributing ecash can revoke the tokens at any time (e.g. maybe another dev comes along who will do it faster)

"Defunct" Tokens will never be claimed unless maintainer + dev collude and the tokens aren't revoked