What is the Spanning Network?
The Spanning Network is a powerful cross-chain API that enables developers to build applications on chains that best suit their technical needs. These multi-home applications will become the basis for the future of the web; check out our demos of a multichain ERC20 and ERC721 here.
Through the use of Ownership bridging, the Spanning Network can communicate state change requests from a user on their preferred network to an application on another network. This allows for Spanning to verify the authenticity of the request and to ensure that the request is valid.
How the Spanning Network Works
We rely on a series of Spanning Delegates to build the Spanning Network. Spanning Delegates are responsible for authenticating a sender, the sender's originating domain, and other header information before passing the authenticated information to the Spanning Network relayer, Blockchain OS (BOS).
BOS routes the message to the correct destination network and pays any associated gas fees to settle the transaction request.
The destination Spanning Delegate receives the verified transaction request and header information from BOS and executes the transaction. During the execution of the transaction, the verified header information (like the original message sender's address) is served by the Spanning Delegate to the requested application. Once the transaction is complete the verified header information is destroyed.
Why Ownership Bridging?
Ownership bridging is superior to the traditional interoperability approach of asset bridging for a few reasons:
- No extra steps to using an application on another network. No intermediate transaction, no new wallets or accounts, no purchasing new gas tokens. Simply call the function of a contract on another chain via a Spanning Delegate and relax.
- Assets are held directly in owners' names. An owner can directly own an asset on another chain, not a derivative or wrapped version of it. This means there is no 3rd party custody agent that has to be trusted.
- Everyone gets access to the same code path, utility, and liquidity. Now that applications and assets can live on a single network, they are no longer subject to the fracturing in utility and liquidity that occurs when assets are wrapped or logic is copied/pasted to new places.
Example Use Cases
Spanning applications have true seamless multichain capabilities. This unlocks a variety of use cases that weren't possible before. Here are some examples:
- Deploy a single NFT contract on Ethereum and airdrop that NFT to users on a variety of networks across Web 3.
- Have your game's character NFTs on Ethereum but save significant amounts of gas for your users by running the gaming logic on Avalanche.
- Deploy multichain access tokens for gated content, Discord membership, or voting rights for your DAO that can now be directly owned by users on any network. Make your community truly decentralized by having it span across multiple networks.
- Build a crafting system for your game that combines low-value raw materials on Polygon but issues the high-value reward back to a user on Ethereum, creating a much more fluid experience for your users.
- Design a multichain NFT trading order book that can directly trade an NFT on Polygon for tokens or NFTs on Avalanche.
If you have an idea or would like help designing the architecture for your multichain application, please reach out via our partnership form.
Learn more about the subsystems:
- Spanning Addresses The core data structure of the Spanning Network.
- Spanning Delegates The endpoints of the Spanning Network.
- Blockchain OS The relay system of the Spanning Network.
Dive right in: