Skip to content
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

Investigate keyCount in MerkleRootChaining test #64

Open
jstolarek opened this issue Jul 25, 2024 · 0 comments
Open

Investigate keyCount in MerkleRootChaining test #64

jstolarek opened this issue Jul 25, 2024 · 0 comments
Labels
optimization Improving execution speed and costs testing Code testing

Comments

@jstolarek
Copy link
Contributor

jstolarek commented Jul 25, 2024

In the offchain/test/Test/MerkleRootChaining.purs test there's a keyCount value. During various recent changes (CTL upgrade, plutus-tx upgrade) we had to lower this value several times to avoid exceeding transaction size limit. The original value was somewhere around 70, now it's 25. Why is this needed? Have the keys themselves grown larger, or have our script sizes increased? Indeed, some of the scripts have increased in size during plutus-tx upgrade, which might account for the increase in the transaction size. Is this an indicator we should be using reference scripts here? We should investigate what exactly is going on.


IOG Jira: https://input-output.atlassian.net/browse/ETCM-8035

@tgunnoe tgunnoe transferred this issue from another repository Jul 25, 2024
@jstolarek jstolarek added optimization Improving execution speed and costs testing Code testing labels Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimization Improving execution speed and costs testing Code testing
Projects
None yet
Development

No branches or pull requests

1 participant