ConsenSysMesh / ConsenSysMesh/bounties.network
Bounty process takes a lot of txs
Open
- Dominant language
- CSS
- Stars
- 7
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Created bounties with DAI. Two txs to create, one tx per submission, one tx per payout, one tx per deactivation. Minimum of four on-chain txs with ETH, five with ERC-20s, puts a lot of load on the blockchain.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by mapping the on-chain transaction flow described for bounty creation, submissions, payouts, and deactivation. Done means reducing the minimum number of blockchain transactions for ETH and ERC-20 bounties while preserving the bounty process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100