Parameterize CLB configuration with validation options

[uhbif19]

TODO:

• Changing protocolVersion (some changes in Plutus (and ledger?) behavior is linked to it, for example this bug fix)
• Zeroing fees and collateral (like Hydra ledger does)
• Support disabling ledger Predicates Parameterize CLB configuration with validation options #24 (comment)
• Not enforcing fee and transaction size bounds
• Not validating scripts at all
• Not validating specific script (idea: validate Tx, see if only ignored script failed, reapply with validating scripts disabled)
• Add tests

[euonymos]

Also - don't use cryptography (if it's possible).

[uhbif19]

@euonymos

More info on options.

There is config to disable validation for any ledger rules. But to use it we need to go deeper than applyTx .

As for feature of fee disabling discussed on last meeting: seems like there is at least two ways to do it, this one, and making fees zero.

Also there are some "events" some of which may cover some of our needs.

[uhbif19]

@euonymos Updated TODO list.

Also - don't use cryptography (if it's possible).

You mean in cabal? Or I do not understand.

[euonymos]

No, we use an instance of Cardano.Ledger.Crypto.Crypto, which is StandardCrypto. By using mock hashes we can probably speed everything up a bit. Take a look here.
`

[euonymos]

Disabling ledger predicates might be an issue. Adding any instrumentation to the ledger is not an option (and we don't want to maintain our fork). AFAIK there is no way to "turn off" any rules, we have to find ways to circumvent them in other ways, like using parameters.

[euonymos]

There is config to disable validation for any ledger rules.

Do you mean this?

[uhbif19]

I mean ValidateSuchThat ([Label] -> Bool) constructor for ValidationPolicy. It is passed inside applyTx, so we can use any. It seems like exactly what we need, if works correctly.

There are two Labels in this file so I am not sure which one :D Second is just string, so I assumed only rule as whole can be disabled.

[euonymos]

ValidationPolicy

I mean ValidateSuchThat ([Label] -> Bool) constructor for ValidationPolicy. It is passed inside applyTx, so we can use any. It seems like exactly what we need, if works correctly.

Sorry, I see it's passed for applyBlock and applyTMiick, but not for applyTx. (Cannot check the latest ledger's code though right now, using what I have locally).

[uhbif19]

@euonymos

Sure. That is why we need to inline it: https://github.com/mlabs-haskell/clb/pull/33/commits

[uhbif19]

My initial approach did not work, using ValidateSuchThat did not seem to change behavior.

So I tried to parse L.ApplyTxError to get kind of error and retry sendTx in that case, but I failed to win its pattern matching, all its entries look like LS.UtxowFailure (LB.UtxoFailure (LB.AlonzoInBabbageUtxoPredFailure (LA.UtxosFailure (LS.ExpiredUTxO {})))) (where LS/LB... are different versions of ledgers).