I am not sure what changed, but the claim transactions that Thunderhub constructs right now are not created with the desired x sat/vbyte the user specifies but with x sat absolute fee.
This PR fixes the bug by using targetFee from boltz-core which allows specifying a sat/vbyte fee as parameter
I am not sure what changed, but the claim transactions that Thunderhub constructs right now are not created with the desired x sat/vbyte the user specifies but with x sat absolute fee.
This PR fixes the bug by using
targetFee
fromboltz-core
which allows specifying a sat/vbyte fee as parameter