Use case: Web3

Polywrap enables the easy integration of Web3 protocols into any application, including both read and write capabilities.

Web3's Problem

We see traditional SDKs as a fundamental bottleneck for web3's adoption, let us explain...

In web3, any application should be able to interact with smart contract protocols such as Uniswap or Aave. To do this, application developers utilize software development kits (SDKs) to simplify this process.

However, traditional SDKs come with a number of issues:

Difficult to compose.

A lack of standards makes traditional SDKs difficult to mix-and-match.

Today, protocol SDKs like Uniswap, Safe and Ethers aren't standardized. This means that a lot of complex, custom code needs to be written to compose them in dApps.

Not portable.

SDKs are language-specific, but the modern landscape of applications is more varied than ever: web, mobile, server, games, etc.

Not upgradable.

When traditional SDKs undergo patch updates, the entire application needs to be rebuilt and redeployed, which doesn't scale to large web3 ecosystems.

---

Polywrap's Solution ✨

Wraps offer a much better strategy for code reuse and composability than traditional SDKs. Wraps are:

Composable.

Wraps are developed in a standardized way. Standardization means Wraps can be easily composed, resulting in even more sophisticated Wraps.

Portable.

Wraps can run on any platform that has the Polywrap client installed. Now, web3 dev teams can build their SDKs as Wraps, and application developers can integrate these Wraps across all platforms.

Updatable.

Wraps do not have to be bundled into applications. Instead they can be safely fetched and run at runtime. This allows applications to stay in-sync with web3 protocol upgrades.

Web3 Hosting

Wraps can be easily deployed to the InterPlanetary File System (IPFS), and published to a decentralized domain like the Ethereum Name Service (ENS).