Replies: 2 comments
-
@yvan-sraka @adrien-zinger any ideas ? I don't see what it could be except gas limits. Did we set memory limits ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
It may not be included if there are too many more profitable transactions in the pool. Or if the operation containing the bytecode is greater than the max size of a block (102400 bytes in the current config) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the maximum transaction size for sending a smart contract to be executed?
I seem to have hit the limit a few times, first when including two smart contract deploys (so two different contracts' bytecodes in addition to the deploy contract) as well as when I included too many print statements (so too many strings) in a contract.
When this happens, nothing alerts me in
massa-client
or in the node logs, it seems the transaction is silently dropped.What are the limits, and can we build a check into
massa-client
that alerts the user their smart contract.wasm
file may be too large?Beta Was this translation helpful? Give feedback.
All reactions