-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parameterize CLB configuration with validation options #24
Comments
Also - don't use cryptography (if it's possible). |
More info on options. There is config to disable validation for any ledger rules. But to use it we need to go deeper than 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. |
@euonymos Updated TODO list.
You mean in cabal? Or I do not understand. |
No, we use an instance of |
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. |
I mean There are two |
Sorry, I see it's passed for |
Sure. That is why we need to inline it: https://github.com/mlabs-haskell/clb/pull/33/commits |
My initial approach did not work, using So I tried to parse |
TODO:
protocolVersion
(some changes in Plutus (and ledger?) behavior is linked to it, for example this bug fix)The text was updated successfully, but these errors were encountered: