Joystream / Joystream/joystream
SPIKE: qn effort / scoping for Bounties v2
Open
Nobody has claimed this yet.
audit-3-debt
post-mainnet
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Scope
- Estimate the effort required to upgrade to v2 Bounties on the QN Side
New state machine: https://joystream.gitbook.io/testnet-workspace/system/bounties/v2#state-machine
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Bounties v2 state machine and locate the current QN-side bounty implementation in the Joystream repository. Compare the existing flow with the v2 states and produce an effort estimate and scope for the required upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100