[Feature] Add child bounty ID offset mechanism #8
Description
Currently, when using bounties.usepapi.app, you can create a transaction that will make a child bounty with a given ID (let's say X).
Suppose you create another bounty transaction, which consequently will generate another child bounty. In that case, the app will automatically calculate the value based on the on-chain data, without considering that you have a transaction that plans to already generate the child bounty with ID X. Therefore, the new transaction will also consider a child bounty ID X.
This can result in the second transaction to fail. It happened already for a bounty -> https://polkadot.subscan.io/event/28421936-68
A simple solution could be to add a manual offset that a user can input, which is added to the child bounty ID calculated by the app.
A more complex solution would be to fetch the bounty to see its owner, check whether it is a multisig, then check the pending extrinsics of the multisig and their contents (for which you'll need an indexer, etc.). So just adding an offset field would be simple enough :)