- Is there a transaction size threshold for a Daml transaction?
- If yes, who enforces it and how? The participant? The domain? Both (possibly in different ways)?
- If either can, can the relevant node(s) operator configure the threshold?
- What error would a Ledger API client receive if such threshold is exceeded? I had a look at the error code pages for both Canton and the Ledger API server and I couldn’t tell.
I tried to create a lot of contracts using Daml Script but the failure I receive is
NOT_SEQUENCED_TIMEOUT, which is reasonable but doesn’t help me with regards to this question (I’m also not sure whether I can apply the suggested remediation of lowering the minimum ledger time is feasible using Daml Script).
I also tried to provide inputs to the transaction itself which are too large, and that fails with a
RESOURCE_EXHAUSTED: gRPC message exceeds maximum size, which at least in part answers my question (for the very specific case of large transaction inputs). But my questions remain open.