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
nitro-testnode-sequencer-1 | Caused by:
nitro-testnode-sequencer-1 | No implementation for floating point operation ConvertIntOp(F64, I64, false) in user
It looks like our stylus contract is too compllicated to be deployed because it requires something unimplemented. I think the floating point operation has been implemented in the replay binary by using the soft-float wasm binary. Wondering if there is any solutions for us to call other WASMs or stylus contracts? Or maybe combine several WASMs into a single stylus contract? And if these operations are universal, can we support them in the stylus's native execution environment?
Expected behavior cargo stylus check works
The text was updated successfully, but these errors were encountered:
Describe the bug
Nitro: 3.12
I am writing our own stylus contract and running a nitro testnode for testing.
I got the error:
It looks like our stylus contract is too compllicated to be deployed because it requires something unimplemented. I think the floating point operation has been implemented in the replay binary by using the
soft-float
wasm binary. Wondering if there is any solutions for us to call other WASMs or stylus contracts? Or maybe combine several WASMs into a single stylus contract? And if these operations are universal, can we support them in the stylus's native execution environment?Expected behavior
cargo stylus check
worksThe text was updated successfully, but these errors were encountered: