Thread by @biconomy

What is the most exciting thing about #Web3 to you?

Decentralization? Open access? Ownership?

For us, at @biconomy the most interesting lego of Web3 is --✨𝐂𝐫𝐨𝐬𝐬-𝐜𝐡𝐚𝐢𝐧 𝐂𝐨𝐦𝐩𝐨𝐬𝐚𝐛𝐢𝐥𝐢𝐭𝐲✨

Why does it excite us so?

A🧵👇

2/

Composability accelerates digital innovation in Web3 much more rapidly than Web2 could ever achieve:

Unlike Web2, developers don't have to wait for a code to be unveiled after reaching maturity.

3/

Thanks to the smart contracts being composable, developers can build on top of apps (even nascent ones) because code is open and verifiable and trust is not required.

4/

More time to grow the Web3 tassels.

Since developers in #Web3 won't have to spend time re-building a stack from scratch, a lot of time and resources can then be directed into improvements, enhancements, and taking the innovation fringe forward.

5/

@SushiSwap building on top of @Uniswap, OR
@AlchemixFi building on top of @iearnfinance -- are some notable examples of composable money legos.

So if cross-chain composability is so essential why isn't it already in every DeFi/Web3 stack out there?

6/

To answer that we need to take you on a short tour through the under-the-hood mechanics of cross-chain protocol interaction and what makes it so hard to implement composability.

Programs that are deployed on the same chain can synchronously invoke or call on each other.

7/

But if these programs live on different chains (ex: same #dApp existing on different chains), they cannot directly invoke each other.

Instead these platforms -- generate a message (consisting of all instructions required to perform a set of actions) on the source chain.

8/

Then the message could be relayed, verified, and then translated into the source/destination chain to achieve the desired action.

This methodology of cross-chain messaging hinders composability.

𝐖𝐡𝐲?👇

9/

Because for all the synchronous actions to take place, different dApps will have to embed all of their numerous interactions into a single message.

So,

user-calls --> dApps calls --> token bridge calls --> messaging protocol.

10/

This primitive is not fit for the future of Web3/DeFi because:
- this approach requires every protocol to trust the protocol that came prior into the call chain. So, in the above example - the dApp is trusting the token bridge to safely & accurately deliver its instructions.

11/

This induces multiple single points of failure.

Meaning if one weak protocol goes bad/fails others in the call chain are bound to fail too.

12/

In addition, since there are multiple protocols involved in order to transmit one single message - having so many protocols composed with each other is extremely complex, extensive, and again prone to errors.

13/

Composability unlocks the power of #Web3 – that’s a fact.

That’s why @biconomy is making efforts to empower the #devs that pioneer Web3.

Making all components more composable - that’s the strategy, and it will lead to faster Web3 adoption.

14/

@biconomy's APIs and SDKs can be easily integrated on any dApp, regardless of its use case.

That means providing the dApp users with a smoother experience and simplified transactions.

The future is now. The future is 𝗕𝗶𝗰𝗼𝗻𝗼𝗺𝘆.