You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered an issue while deploying a contract to the StarkNet testnet. When I set LAYOUT_TYPES to "starknet", the deployment fails during the execution of the following command:
After investigating, it seems the functions eval_composition_polynomial_inner and eval_oods_polynomial_inner are too large, which likely causes the contract size to exceed the limits for deployment.
Would it be possible to optimize these functions?
The text was updated successfully, but these errors were encountered:
Hey @swift-hl your observations are correct we resolve this issue by splitting the verifier to multi-contract logic.
Checkout this https://github.com/HerodotusDev/integrity/tree/autogenerated_split branch we implemented this already.
It will be merged into main after refactor and probably dynamic layout split addition.
As u noticed, the Cairo1 implementation of simple logic in auto-generated is main cause of the size of the contract class json.
In the past I already introduced some Cairo1 specific impl tricks to reduce the size by 4x, if we find some more tricks to do so I will optimize the auto-generated further, but now we moved to splitting it.
I encountered an issue while deploying a contract to the StarkNet testnet. When I set
LAYOUT_TYPES
to"starknet"
, the deployment fails during the execution of the following command:starkli declare ./target/dev/fact_registry_FactRegistry.contract_class.json
After investigating, it seems the functions
eval_composition_polynomial_inner
andeval_oods_polynomial_inner
are too large, which likely causes the contract size to exceed the limits for deployment.Would it be possible to optimize these functions?
The text was updated successfully, but these errors were encountered: