All chains
    Preparing search index...
    unassign_curator: TxDescriptor<
        { child_bounty_id?: number; parent_bounty_id: number },
    >

    Unassign curator from a child-/bounty.

    This function can only be called by the RejectOrigin or the child-/bounty curator.

    • If this function is called by the RejectOrigin, or by the parent curator in the case of a child bounty, we assume that the curator is malicious or inactive. As a result, we will slash the curator when possible.
    • If the origin is the child-/bounty curator, we take this as a sign they are unable to do their job and they willingly give up. We could slash them, but for now we allow them to recover their deposit and exit without issue. (We may want to change this if it is abused).
    • If successful, the child-/bounty status is updated to CuratorUnassigned. To reactivate the bounty, a new curator must be proposed and must accept the role.
    • parent_bounty_id: Index of parent bounty.
    • child_bounty_id: Index of child-bounty.

    Emits [Event::CuratorUnassigned] if successful.