Avalanche Academy: Interchain Messaging

website·Indexed 30 days ago

https://avalanche-academy.vercel.app

Educational course on Interchain Messaging (ICM) and Avalanche Warp Messaging (AWM). Covers running and configuring AWM relayers, securing cross-chain communication with signature schemes, implementing relayer incentives via fee token contracts, and using the ICM Registry and Avalanche CLI.

Tokens
67.7K
Snippets
235
Records
483
Agent score
75%

What's inside Avalanche Academy

  1. Overview of the ERC-20 Token Standard

    The ERC-20 standard allows for the representation of various fungible assets on EVM-compatible chains. Unlike the single native token of a chain, ERC-20 tokens are managed via smart contracts. Internally, these contracts maintain a mapping of addresses (EOAs or contract accounts) to their respective token balances.
    mapping(address account => uint256) private _balances;
  2. Overview of the Avalanche Starter Kit

    The Avalanche Starter Kit is a pre-configured development environment designed for building dApps on Avalanche. It provides a self-contained setup that includes Avalanche-CLI and Foundry, allowing developers to create Interchain Messaging enabled custom blockchains and develop cross-chain dApps without needing to perform manual local installations of these tools.
  3. Overview of Avalanche CLI for blockchain development

    Avalanche-CLI is a command-line tool designed for developers to build, test, and manage independent Avalanche blockchains. It allows for the creation of local networks that operate independently of the Mainnet or Fuji Testnet, enabling offline development. Key capabilities include starting and stopping local networks, performing health checks on network nodes, and creating new blockchains with specific parameters.
  4. Overview of bridging ERC-20 tokens to Avalanche L1 as native tokens

    To transfer an ERC-20 token from the C-Chain to an Avalanche L1 as a native token, you must use Interchain Messaging. The process involves deploying an ERC-20 contract on the C-Chain, deploying Interchain Token Transferer contracts on both chains, registering the remote token, and adding collateral. The reference implementation for these contracts is available in the avalanche-interchain-token-transfer repository.
  5. Overview of Avalanche Warp Messaging (AWM)

    Avalanche Warp Messaging (AWM) is a general cross-Avalanche L1 communication protocol designed to make all Avalanche blockchains natively interoperable. It allows Avalanche L1s to communicate via authenticated messages by providing signing and verification primitives within AvalancheGo. Because it operates at the protocol level, AWM is not EVM-specific and can be integrated by any Virtual Machine (VM) on Avalanche to send and receive messages across L1s without relying on third-party intermediaries or centralized trust assumptions.
  6. Overview of Avalanche Interchain Messaging (AWM)

    Avalanche Interchain Messaging and Avalanche Warp Messaging (AWM) provide an audited development framework for building cross-Subnet Solidity dApps. This protocol enables native interoperability between Avalanche blockchains, allowing multiple chains with specialized Virtual Machines (VMs) to communicate, which improves overall network scalability and flexibility.
  7. Overview of Avalanche Interchain Token Transfer (ICTT)

    Avalanche Interchain Token Transfer (ICTT) enables the transfer of assets across multiple Avalanche blockchains. This is achieved through a multi-chain system where specialized blockchains communicate via Interchain Messaging and Avalanche Warp Messaging (AWM), allowing developers to build cross-Avalanche L1 dApps using an audited development framework.
  8. Overview of the Avalanche Warp Messaging (AWM) Relayer

    An AWM Relayer is a critical component of Interchain Messaging responsible for delivering warp messages between Subnets. It monitors the source Subnet for outgoing warp messages, aggregates the necessary signatures, and delivers the message to the destination Subnet via a transaction. While the Avalanche CLI automatically manages a relayer for local network deployments, production environments require a manually configured and operated relayer. The reference implementation is a standalone application written in Go by Ava Labs.
  9. Overview of Avalanche L1 Permissioning

    Permissioning is an optional feature for Avalanche L1 blockchains that allows creators to restrict network access to authorized parties. This is typically used to achieve privacy and confidentiality (e.g., in finance or healthcare), ensure regulatory compliance through data handling controls, or improve cost-efficiency by preventing transaction fee spikes from events like NFT drops. Permissions can be managed by a centralized entity or a decentralized autonomous organization (DAO).
  10. Overview of methods to create an Avalanche L1 blockchain

    There are multiple ways to deploy an Avalanche L1 blockchain depending on the desired level of control and ease of setup:

    1. AvaCloud: A Blockchain-as-a-Service (BaaS) provider. This is the most straightforward and easiest method for developers to get started.
    2. Avalanche-CLI: A command-line interface tool used for deploying and managing blockchains (covered in the Multi-Chain Architecture course).