Hi @Aniket-Engg, thanks for promptly tackling this! However, we should just remove the function - we should have a function with the same functionality: transferring all balance to the owner, and not letting the bounty continue to be used.

function abortBounty() public onlyOwner {
     _asyncTransfer(owner(), address(this).balance);
    _claimed = true;
  }

Should it be something like this? @nventuro

That's a good starting point. A couple ideas:

• Let's rename _claimed to ongoing, now that a bounty may not be claimable due to the owner canceling it.
• I think cancel is a better verb choice than abort in this context, since there's no ongoing process to abort. We should also emit a Canceled event.
• We should add a require in cancelBounty so that it can only be canceled once.

Let me know what you think!

what are your thoughts behind choosing ongoing when bounty is getting cancelled? @nventuro

Currently, a bounty may be not claimed, claimed, or destroyed. A cancelled bounty is obviously not claimed, so we need a better word. I suggested 'ongoing', but 'claimable' may be better (a canceled bounty is not claimable).

claimable looks fine.
should we also add an event emission in claim function too? @nventuro

@nventuro Please check the changes and let me know your views. I will add tests for cancelBounty once it is final.

I am also loving being a part of it. Thanks for your appreciation. 😊