GNSPS / StandardBounties

Smart Contracts in Solidity to serve as a Standard for Bounties for EVM dApps

StandardBounties

Version 0.0.1

1. Rationale
2. Implementation
3. Development

A set of standard contracts to be used as interfaces for any kind of bounty, either qualitative or quantitative in nature.

Original concept & code by @mbeylin. Maintained by @gnsps & @mbeylin.

1. Rationale

Bounties can be used to facilitate transactions between two parties, where a quantitative task, qualitative task or artifact is being exchanged for ETH.

Code bug bounties are included here as an implemented extension of the generalized bounty and to serve as an example of a pure quantitative bounty that can automatically be paid out.

2. Implementation

The generalized bounty contract (StandardBounty.sol) is implemented as a State Machine as represented below:

2.1 Invariant check pattern for CodeBugBounty.sol

The pattern for invariant checks of bugs on smart contract code relies on the careful planning & implementation by the bounty creator.

If the invariants are not chosen correctly or their code is implemented poorly you'll probably just end up giving money away! Please be careful.

3. Development

All the extension bounty types (particular cases like CodeBugBounty.sol) musn't break the state diagram above. They should differ in validation of state change but not in transition rules.