# AIP: Activate Stylus and Enable Next-Gen WebAssembly Smart Contracts (ArbOS 30)

**URL:** <https://forum.arbitrum.foundation/t/aip-activate-stylus-and-enable-next-gen-webassembly-smart-contracts-arbos-30/22970>\
**Category:** Finalized AIPs\
**Created:** [April 2, 2024, 4:48pm UTC](https://forum.arbitrum.foundation/t/aip-activate-stylus-and-enable-next-gen-webassembly-smart-contracts-arbos-30/22970 "2024-04-02T16:48:04Z")\
**Posts on this page:** 1\
**Showing post:** 40

<div class="post-metadata">

**Author:** ![cp0x](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.arbitrum.foundation/cp0x/32/5455_2.png) [@cp0x](https://forum.arbitrum.foundation/u/cp0x)\
**Post date:** [September 11, 2024, 7:46pm UTC](https://forum.arbitrum.foundation/t/aip-activate-stylus-and-enable-next-gen-webassembly-smart-contracts-arbos-30/22970/40 "2024-09-11T19:46:58Z")

</div>

> [@Stylus SDK Audit](https://forum.arbitrum.foundation/t/stylus-sdk-audit/26674/1):
>
> **Update:** Resolved at commits [a99d8c5](https://github.com/OffchainLabs/stylus-sdk-rs/commit/a99d8c5abed54dfdba8e91c9cc9c5c024dd76495) and [6e3a62e](https://github.com/OffchainLabs/arbitrum-docs/commit/6e3a62ea291c3e9e47ef3c1d4f3e5a065ad7f997). Inline documentation has been added to highlight the discrepancy with Solidity storage layout

As I understand it, due to the difference in memory slots, when calling functions of the same contract (implemented in different languages), we can get different results.

I would like to clarify if this is enough for normal contract compatibility?  
Is there another way to solve this problem other than to indicate that it is in the documentation.

---

_[View the full topic](https://forum.arbitrum.foundation/t/aip-activate-stylus-and-enable-next-gen-webassembly-smart-contracts-arbos-30/22970)._