Adjust the fee calculation when reference script bytes are present in the input UTXOs of a transaction

[satran004]

To fix #450

1. A script reference can be part of the regular inputs in a script transaction. For example, if the reference script is part of the spending UTXO, a reference input is not required.

2. Update the FeeCalculator to calculate the reference script size in inputs and adjust the fee accordingly.

3. If both a script reference and a script witness (transaction.getWitnessSet().getPlutusXScript()) are present, ExtraneousScriptWitnessesUTXOW is thrown. To fix this, DuplicateScriptWitnessChecker is introduced, which returns a composable function to remove any duplicate witnesses.

4. A new API removeDuplicateScriptWitnesses(boolean flag) has been added to QuickTxBuilder to enable the removal of duplicate witnesses in the above scenario. By default, this flag is false, but it can be enabled by calling the above method if required.

Result<String> result1 = quickTxBuilder.compose(scriptTx)
    ...
    .removeDuplicateScriptWitnesses(true)
    .completeAndWait(System.out::println);

5. A new overloaded method in Tx api.

public T payToContract(String address, Amount amount, PlutusData datum, Script refScript)

[nemo83]

🔥

[sonarqubecloud]

Quality Gate passed

Issues
10 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud