Developers setting themselves a bounty

I've got an idea which is linked to the way Bountysource already works but in the opposite:
Instead of people with no coding abilities looking for coders, alluring them with bounty, couldn't we do the opposite? Coders offering a solution in exchange of a bounty that they set themselves.

That way we could attract more coders: since they set themselves their bounty they know that the price is good, whereas the actual way favours setting too low bounty (the non-coders have problems figuring out the real amount of work for this or that bug)

Start by reviewing how Bountysource currently handles bounty creation, assignment, and payment. Define the user flow, eligibility rules, pricing or escrow behavior, and acceptance criteria before identifying implementation files. Done requires an agreed product design and maintainer decision, not just a code change.

Written by the indexing model from the issue text.