Hi @xglreal this problem really exists and we're actively working on a fix.
> How to fix this problem? Unfortunately, there is no sysctematical fix to this problem. We'll explore if there is a hot/quick fix to just enlarge the memory space so it can hold larger function input. > Or what the max size of payload file? Around 700KB. > Or how to increase the size of wasm that the enclave can accept? The problem originates in Teaclave's design. In current design, payloads are transmitted in *string*, which is bad for performance. We need to modify the APIs of Teaclave and it's internal protocol to support large function payload. If you want to try to reduce the size of wasm file, you may try [wasm-gc](https://crates.io/crates/wasm-gc/0.1.6) and add this snippet in `Cargo.toml`: ``` [profile.release] lto = true opt-level = "s" ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/533#issuecomment-889945307
