Editing Exploit markets (section)

= Optional crowd sourcing =

The contracts can specify that patch updates can be given by anyone rather than always by the vendor with as little or as much controls in place as required (manual approval or must pass test suites.)

Edit: Most likely this won’t work. There’s no way to autonomously prove that additional bugs haven’t been added to the software. At best you can use a smart contract to automatically decide to flag a patch as being ready to a group of human oracles based on tests passing but that is really no different to how software is already written. I’ve left the original scheme in bellow.

'''1. good_samaritan_tx = Commit to Hash(patch_code + pay_out_address) as H4.'''

'''2. samaritan_claim_tx''' Input = patch_code + payout_address such that Hash(patch_code + payout address) == H4 output = anything sig = Signed with payout address.

'''3. Patch code is validated against the exploit and if it defeats it the transaction is valid.'''<span id="private-exploit-sales"></span>