▫️What is WebGlide?
About WebGlide
Last updated
About WebGlide
Last updated
A modular system called WebGlide is used to safely transfer money and data between chains. Crosschain programs (WebGApps), or programs that communicate with many domains (blockchains and/or rollups) concurrently, may be created by developers using WebGlide.
Blockchains are unable to grow to the volume required for widespread adoption.
Users, money, and data are distributed across several parallel domains (sidechains, rollups, and other chain-like structures) in the Binance Smart Chain and other programmable blockchains to address this issue. But this brings forth a brand-new issue: a fragmented user experience.
Users of decentralized applications should not need to actively think about what chain they are on or how to travel between chains, similar to how users of YouTube do not need to grasp Google's distributed database technology. In other words, while maintaining the security and trust-minimization characteristics of the underlying chains, apps should abstract the multichain experience by becoming WebGApps.
The three fundamental design concepts that WebGlide was created with make it the greatest choice for developers wishing to create WebGApps without sacrificing trustlessness.
Connext has a modular hub-and-spoke design that connects to the tried-and-true canonical messaging bridges that support the security of any domain linked to Binance and draw its security from Smart Chain L1.
A Merkle root created on each speaking domain is supplemented by messages in WebGlide, which is then optimistically aggregated into a single root on Binance L1. In the case of fraud, the system switches to each chain ecosystem's canonical communications bridge. Or to put it another way, a message sent between Polygon and Ethereum is protected by a proof that is published to Binance and confirmed by the Polygon PoS bridge and Ethereum roll-up bridge. Similar to this, IBC verifies a message transmitted within the Cosmos ecosystem.
For whichever chains developers choose to build atop, this technique provides the greatest possible trust assurances. In our Polygon to Ethereum scenario, fraud would need to breach both WebGlide's failsafe safeguards and either Polygon's or Ethereum's canonical bridges.
Some of the most crucial pieces of infrastructure in the area are bridges and cross-chain communications, which carry a significant risk of disaster in the case of breaches or vulnerabilities. Nearly $2 billion has been lost due to bridge cyberattacks during the last 18 months.
In order to monitor the network and stop message passing in the event of fraud or a compromise, WebGlide employs Watchers, automated offchain agents. As a result, the harm caused by any single component of the network failing is minimised.
In addition, WebGlide adheres to a stringent secure development culture, demanding strict external review for code modifications and actively collaborating with the security community to inform auditors on security issues and jointly establish best practises.
It might be difficult to transition to a brand-new multichain development methodology.
WebGlide strives to imitate and expand on current development patterns as much as possible rather than creating something entirely new. The protocol defines a single, straightforward primitive called "WebGcall" that enables developers to asynchronously communicate with contracts that are located on different chains or rollsups in a manner comparable to calling a contract that is located on the same chain or rollsup.
In short, pretty much anything! Here are some of the ideas that members of our community are working on:
Executing the outcome of DAO votes across chains
Lock-and-mint or burn-and-mint token bridging
Aggregating DEX liquidity across chains in a single seamless transaction
Crosschain vault zaps and vault strategy management
Lending funds on one chain and borrow on another
NFT bridging and chain-agnosticWhere Do I Go Next?
Don't worry if the information above seems overwhelming. You may learn more about WebGlide by checking out the following resources:
Check out our Developer Quickstart and Examples if you're a developer and want to start creating with WebGcall.
Would you want to know more about the protocol's operation? Read the section under "How WebGlide Works."
Are you a manager of infrastructure? Use a WebGlide router to assist in maintaining the network.
