Introducing the Safe Wrap
Introducing the Safe Wrap
A Powerful New Way to Build on Safe
The Safe wrap lets dApps interact with the Safe smart contracts from any platform – web apps, mobile, gaming and beyond. It includes the same functionality as the current Safe JavaScript SDK, meaning developers can use the wrap to deploy a new Safe, create Safe transactions, and sign off-chain signatures.
So what makes the Safe wrap special?
It's portable. While the Safe JS SDK can only be installed in JavaScript applications, the Safe wrap can be used in any environment supported by Polywrap, including JavaScript, Rust, Python, with many others to come. For example, it can be possible to use the same Safe wrap in a JS application or a Rust application. This is more cost-effective and convenient for maintainers, as they only need to look after one, highly reusable codebase instead of multiple ones.
The same Safe wrap is reusable in mobile apps, web, gaming, servers and more.
It's updateable. Wraps don’t get bundled into apps at build time. Instead, wraps are stored on IPFS where they’re fetched by Polywrap client libraries at run time. This means that apps remain lightweight and wraps can optionally be updated dynamically.
Wraps can be fetched from IPFS and downloaded into apps, all at runtime.
It's hyper-composable. The Safe wrap is just one of a growing universe of language-agnostic wraps. These wraps can be easily combined within the same app. Today, some of the available wraps include NEAR, Substrate, Uniswap and more.
Recently, we composed the Safe{Core}, Ethers, and Gelato Relay wraps together to form an Account Abstraction (AA) wrap. The AA wrap lets developers integrate account abstraction functionality into their applications.
Wraps can be easily combined with other wraps. Here, the Ethers, Safe{Core} and Gelato Relay wraps are composed to result in a powerful, new Account Abstraction wrap.
It’s secure. Polywrap is built on WebAssembly, a portable bytecode standard that makes it possible to execute wraps in a self-contained environment. As a result, wraps can only read and modify items that they have been granted access to.
Wraps are containerized and can only read/write items that they have been granted access to.
The Polywrap DAO would like to thank Consider It Done Tech (CIDT) for their amazing work building this wrap with the support of the Safe Foundation.
What's next?
We think the Safe wrap will make it significantly easier to build applications that leverage Safe. We encourage developers building on Safe to get in touch with us and check out the Safe wrap repo and Polywrap docs.