Bounty Pallet: approve bounty with curator call #5928
Assignees
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 5, 2024
…allet (#5961) Resolves issue #5928 Adds `approve_bounty_with_curator` call to the `bounties` pallet to combine functions of `approve_bounty` and `propose_curator` into one call. Also adds a new status `ApprovedWithCurator` required to distinguish if bounty was approved with curator when skipping through `Funded` status and moving to `CuratorProposed` status. If `unassign_curator` is called after `approve_bounty_with_curator` the process will fall back to the old flow of calling `propose_curator` separately. --------- Co-authored-by: DavidK <davidk@parity.io> Co-authored-by: command-bot <> Co-authored-by: Ankan <10196091+Ank4n@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of #5500
Goal:
Approve bounties and curators with a single referendum.
Solution:
Introduce
approve_bounty_with_curator(..)call that would behave as a batch of the existingapprove_bountyandpropose_curatorcalls.The text was updated successfully, but these errors were encountered: