Avalanche Warp Messaging | Pika Protocol, Galleon DAO Integrate LI.FI's Widget | NEAR Now MetaMask Compatible More!

Last Week In The Multi-Chain Ecosystem (19 - 25 Dec 2022)

and

Dec 26, 2022

Welcome to LI.FI’s Cross Chain Insider newsletter. If you want to join this community of cross-chain aficionados learning about bridges, interoperability, and the multi-chain ecosystem, subscribe below:

You can also check out LI.FI’s research articles, and follow us on Twitter!

Bridge Updates

1) Avalanche Warp Messaging (AWM) Launched 🔺

Avalanche released Avalanche Warp Messaging (AWM) as part of the Banff 5 update for its core implementation. AWM enables subnet-to-subnet messaging without relying on bridges.

2) Pika Protocol Integrates LI.FI’s Widget 🦎

Pika Protocol, a decentralized perpetual swap exchange on Optimism Layer-2, has integrated our widget inside their dApp. The integration allows Pika users to bridge and swap assets seamlessly across 16 EVM-compatible chains without leaving the platform.

3) Symbiosis V2 Launched 👾

Symbiosis, a cross-chain AMM, has launched its V2 update offering improved efficiency with single-sided AMM pools and enabling a serving network (s-chain) starting with Boba BNB L2.

4) OpenOcean Launches Cross-Chain Swap 👏🏻

OpenOcean, a web3 DEX aggregator, has launched its 1-click cross-chain swap with support for multiple chains. The cross-chain swap is made possible through the integrations of two bridges — cBridge and Multichain.

5) Galleon DAO Integrates LI.FI’s Widget 🔥

Galleon Dao, an asset management guild, has integrated LI.FI’s widget inside their dApp. Galleon users can now bridge and swap any asset seamlessly without leaving the dApp across 15+ EVM-compatible chains and Layer-2s.

6) Rubic Exploited for ~$1.41M ⚠️

Rubic, a cross-chain tech aggregator, suffered a $1.41M exploit on 25 Dec 2022. According to PeckShield, “the hack is made possible due to mistakenly adding USDC into supported routers. Also, with a lack of validation in routerCallNative, the hacker can drain all funds from users who have approvals to the RubicProxy.”

Rubic has paused all the contracts connected with the platform and plans to compensate affected users and resume operations after a round of audits. If you’ve used Rubic in the past, revoke contract via Revoke.

Multi-Chain Ecosystem Updates

1) NEAR is Now Compatible with MetaMask 🦊

Proximity Labs has released NETH, a smart contract that allows users to interact with dApps on NEAR with their Ethereum wallets. NETH is the first solution to offer MetaMask compatibility on a non-EVM chain.

2) Axelar $60M Ecosystem Fund 💸

Axelar Network launched a $60M Ecosystem Startup Funding Program to accelerate the development of dApps and protocols. The fund involves A-list crypto-native investors that will help identify projects building on Axelar with the goal of onboarding the masses.

3) Cross Chain Monitoring Tool 🧐

Ali Taslimi introduced Cross Chain Monitoring Tool, which enables users to compare 10+ blockchains in different sectors such as NFTs, DEXs, and metrics such as transaction fees, NFT sales, etc.

What’s Popping on Twitter?

Avalanche’s subnet ecosystem just got a major upgrade! Native communication between subnets is now possible via Avalanche Warp Messaging (AWM).

Avalanche 🔺 @avalancheavax

#Avalanche Warp Messaging (AWM) is here–bringing fast, native communications to all Subnets. 🔺 Build your own VM and interoperate with other Subnets 🔺 Compound dApp capabilities by messaging contracts on other Subnets 🔺 No reliance on Bridges 🔺 More! medium.com/avalancheavax/…

medium.comAvalanche Warp Messaging (AWM) Launches with the First Native Subnet-to-Subnet Message on Avalanche…Banff 5 (AvalancheGo@v1.9.5) is live–featuring AWM, which allows developers to use high-performance, interoperable blockchain networks…

In Avalanche’s Banff 5 update to its core implementation, the team has rolled out Avalanche Warp Messaging (AWM), a tool that enables native communication between Avalanche updates.

This feature is critical for Subnets as it provides native, cross-chain communication capabilities out-of-the-box, enabling them to transfer assets and/or data between Subnets without having to build their own bridge.

How does AWM work?

Avalanche allows Subnets to have their own validator set. AWM leverages the Subnets’ validator sets and empowers them to attest to the validity of an arbitrary message by collectively producing a BLS Multi-Signature. This attestation is verifiable by any other Subnet, allowing them to accept/reject messages from any Subnet based on their assessment of the validity of the BLS Multi-Signature.

Moreover, AWM offers Subnets the functionality of building their own Warp Messaging Rulesets. This means Subnets don’t have to adhere to any standards and can build their own ruleset to determine which Subnets they want to accept messages from. Additionally, Subnets can also specify the % weight a BLS Multi-Signature must have to ensure the validity of messages. For example, a Subnet Subnet A can customize its Warm Messaging Ruleset to say that no messages from Subnet B should be accepted, but any message with at least 70% weight of the BLS Multi-Signature from Subnet C can be accepted.

As a result, Avalanche Subnets can now be a unique sovereign network with its own rules regarding membership and token economics, and can also decide which other Subnets it wants to interact with.

Closing Thoughts

The first native Subnet-to-Subnet message via AWM has already been sent between “let there” and “be messaging” Subnets on Avalanche Mainnet. VM builders can leverage AWM in the Golang and Rust VM SDKs already; however, the much-anticipated AWM support for subnet-EVM chains will be released over the coming weeks.

While questions can be raised on whether AWM is trustless since the implementation leverages Subnets’ validator sets and relies on them to attest messages correctly, it offers Subnets the much-needed functionality of interchain communication.

What are your views on AWM? Will it increase the adoption of Avalanche Subnets?