# (Dev discussion/Issue) WASM implementation

**URL:** <https://forum.scrt.network/t/dev-discussion-issue-wasm-implementation/1303>\
**Category:** Secret Network\
**Created:** [February 20, 2020, 5:22pm UTC](https://forum.scrt.network/t/dev-discussion-issue-wasm-implementation/1303 "2020-02-20T17:22:30Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![guy](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.scrt.network/guy/32/56_2.png) [@guy](https://forum.scrt.network/u/guy)\
**Post date:** [March 10, 2020, 9:27am UTC](https://forum.scrt.network/t/dev-discussion-issue-wasm-implementation/1303/10 "2020-03-10T09:27:14Z")

</div>

Now that WASM is implemented in testnet (using CosmWasm), we’re looking at integrating it into SGX, and it’s more challenging than expected.

The main concern is that CosmWasm uses Wasmer, which is a JIT compiler. This is great, but it doesn’t seem to work inside of SGX currently (might change with SGX2), which means we have to revert back to an interpreter. We’re looking at integrating WASMI, which is the interpreter we used in Discovery. WASMI is enclave friendly, but CosmWasm right now is tightly integrated with Wasmer, so we’re now starting to explore how hard it would be to break that connection.

---

_[View the full topic](https://forum.scrt.network/t/dev-discussion-issue-wasm-implementation/1303)._