This repository was archived by the owner on Sep 8, 2025. It is now read-only.

Description
- Right now user can click
add bsn/fp multiple times. Because a different combination of bsn and fp will lead to a different transaction hash. It is okays
- But when user already hit the
renew the timelock and has it in verified state, he won't be able to renew it once again (at least with the same UTXO) as it will lead to the same transaction hash
- We can solve it using a new UTXO usage OR completely disable the
renew feature after first one is validated
- @jrwbabylonlab my proposal is to go with the simpler approach - once
renew is vefiried we do not allow the user to renew once again
- If there's a need from other users to have an ability to use a
renew later on with the different UTXO we can reiterate on this problem