From 472fb73f26d09c87a5c455129ea206e692563319 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Thu, 27 Mar 2025 18:53:51 +0100 Subject: [PATCH 01/27] add glossary for avalanche ecosystem key terms --- .../avalanche-fundamentals/glossary.mdx | 29 +++++++++++++++++++ .../academy/avalanche-fundamentals/meta.json | 1 + 2 files changed, 30 insertions(+) create mode 100644 content/academy/avalanche-fundamentals/glossary.mdx diff --git a/content/academy/avalanche-fundamentals/glossary.mdx b/content/academy/avalanche-fundamentals/glossary.mdx new file mode 100644 index 00000000000..87a7bdb7e15 --- /dev/null +++ b/content/academy/avalanche-fundamentals/glossary.mdx @@ -0,0 +1,29 @@ +--- +title: Avalanche Glossary +description: Key terms and concepts in the Avalanche ecosystem +updated: 2024-05-31 +authors: [ashucoder9] +icon: Book +--- +> **Note:** For general blockchain and DeFi terminology, please refer to the [Blockchain Glossary](/academy/blockchain-fundamentals/glossary). + +| Term | Abbreviation | Previous Term | Description | +|------|--------------|---------------|-------------| +| Avalanche Consensus | | | A family of consensus protocols that power the Avalanche network, known for high throughput, fast finality, and energy efficiency. The X-Chain uses the core Avalanche consensus protocol, while the P-Chain and C-Chain use the Snowman variant. [Learn more](/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro). | +| Avalanche L1 | L1 | Subnet | An independent, sovereign blockchain network on Avalanche that can have its own validator set, tokenomics, and rules. Avalanche L1s work together to form the broader Avalanche Network. [Learn more](/docs/quick-start/avalanche-l1s). | +| Avalanche Virtual Machine | AVM | | The virtual machine implementation that powers the X-Chain, handling operations on Avalanche Native Tokens. | +| Contract Chain | C-Chain | | An implementation of the Ethereum Virtual Machine (EVM) that supports the deployment and execution of smart contracts written in Solidity. Uses the Coreth Virtual Machine. [Learn more](/docs/quick-start/primary-network#c-chain). | +| Coreth | | | The virtual machine implementation that powers the C-Chain, enabling Ethereum compatibility on Avalanche. | +| Exchange Chain | X-Chain | | Responsible for operations on digital smart assets known as Avalanche Native Tokens. Uses the Avalanche Virtual Machine (AVM). [Learn more](/docs/quick-start/primary-network#x-chain). | +| Interchain Messaging | ICM | Teleporter | A protocol that enables communication between blockchains on Avalanche, allowing for secure message passing between different L1s. [Learn more](/academy/interchain-messaging). | +| Interchain Token Transfer | ICTT | | A system that allows tokens to be transferred seamlessly between different Avalanche L1s, enabling greater interoperability within the ecosystem. [Learn more](/academy/interchain-token-transfer). | +| Platform Chain | P-Chain | | Responsible for all validator and Avalanche L1-level operations, including staking, creating new blockchains, and other platform-level functions. Uses the Platform Virtual Machine. [Learn more](/docs/quick-start/primary-network#p-chain). | +| Platform Virtual Machine | | | The virtual machine implementation that powers the P-Chain, handling staking, validator, and Avalanche L1 operations. | +| Primary Network | | | A special Avalanche L1 that runs three blockchains: the P-Chain, C-Chain, and X-Chain. All validators on the Primary Network must stake at least 2,000 AVAX. [Learn more](/docs/quick-start/primary-network). | +| Snowman Consensus | | | A linear chain-optimized variant of the Avalanche consensus protocol used specifically by the P-Chain and C-Chain. Designed for smart contract chains and platform operations. [Learn more](/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus). | + +## Why Terminology Matters + +Understanding these terms is essential for effective communication within the Avalanche ecosystem. The recent terminology changes better reflect the technical architecture and capabilities of the Avalanche platform as it continues to evolve. + +As you progress through this course, you'll gain a deeper understanding of these concepts and how they fit into the broader Avalanche ecosystem. \ No newline at end of file diff --git a/content/academy/avalanche-fundamentals/meta.json b/content/academy/avalanche-fundamentals/meta.json index 8d2809658b4..6a24676482f 100644 --- a/content/academy/avalanche-fundamentals/meta.json +++ b/content/academy/avalanche-fundamentals/meta.json @@ -4,6 +4,7 @@ "root": true, "pages": [ "index", + "glossary", "---Primer on Avalanche Consensus---", "...02-avalanche-consensus-intro", "---Multi-Chain Architecture---", From 6527b5c27cdffb261ae366391831ccbf4c14eaf7 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Thu, 27 Mar 2025 18:54:21 +0100 Subject: [PATCH 02/27] add glossary for blockchain general key terms --- .../blockchain-fundamentals/glossary.mdx | 48 +++++++++++++++++++ .../academy/blockchain-fundamentals/meta.json | 1 + 2 files changed, 49 insertions(+) create mode 100644 content/academy/blockchain-fundamentals/glossary.mdx diff --git a/content/academy/blockchain-fundamentals/glossary.mdx b/content/academy/blockchain-fundamentals/glossary.mdx new file mode 100644 index 00000000000..12db8950f12 --- /dev/null +++ b/content/academy/blockchain-fundamentals/glossary.mdx @@ -0,0 +1,48 @@ +--- +title: Blockchain Glossary +description: General terms and concepts in blockchain technology and decentralized finance +updated: 2024-05-31 +authors: [ashucoder9] +icon: Book +--- + +| Term | Abbreviation | Description | +|------|--------------|-------------| +| Annual Percentage Rate | APR | The annual return you will receive on an investment, without accounting for the effects of compounding. | +| Annual Percentage Yield | APY | The annual return you will receive on an investment when returns are compounded. Unlike APR, APY includes the effects of compounding. | +| Arbitrage | | The practice of buying and selling assets between different markets to profit from price discrepancies. For example, buying a token on one exchange where it's cheaper and selling it on another where it's more expensive. | +| Automated Market Maker | AMM | A protocol that uses liquidity pools and mathematical formulas to automatically determine asset prices and enable trading without traditional order books. | +| Block | | A collection of transactions that are grouped together and added to the blockchain. Each block typically contains a reference to the previous block, creating a chain. | +| Blockchain | | A distributed ledger technology that records transactions across multiple computers in a way that ensures security, transparency, and immutability. | +| Compounding | | The process where earnings from an asset are reinvested to generate additional returns over time, creating exponential growth. | +| Consensus Mechanism | | The method by which network participants agree on the valid state of the blockchain. Examples include Proof of Work, Proof of Stake, and Avalanche Consensus. | +| Cross-Chain Interoperability Protocol | CCIP | A protocol that enables communication between different blockchains. Allows for the transfer of messages, tokens, and data across separate blockchain networks. Most commonly associated with Chainlink's cross-chain communication solution. | +| Cryptocurrency | | A digital or virtual currency that uses cryptography for security and operates independently of a central authority. | +| Decentralized Application | dApp | An application that runs on a decentralized network rather than being controlled by a single entity or authority. | +| Decentralized Autonomous Organization | DAO | An organization governed by rules encoded as smart contracts on a blockchain, without centralized leadership. Members collectively make decisions through voting mechanisms. | +| Decentralized Exchange | DEX | A peer-to-peer marketplace where users can trade cryptocurrencies directly with each other without an intermediary. These exchanges use smart contracts to execute trades. | +| Decentralized Finance | DeFi | A financial system built on blockchain technology that aims to recreate and improve upon traditional financial services without central authorities or intermediaries. | +| Gas | | The fee required to perform a transaction or execute a contract on a blockchain network. Gas is used to allocate resources of the blockchain's virtual machine. | +| Hash | | A function that converts input data to a fixed-size string of characters. Blockchain uses hash functions to ensure data integrity and security. | +| Liquidity | | The ease with which an asset can be converted to cash or traded without affecting its market price. Higher liquidity means the asset can be exchanged more easily. | +| Liquidity Pool | | A collection of tokens or assets locked in a smart contract, providing liquidity for decentralized exchanges and other DeFi applications. | +| Mining | | The process by which new transactions are verified and added to a blockchain using a Proof of Work consensus mechanism. Miners solve complex puzzles to earn rewards. | +| Multi-signature | Multisig | A security feature that requires multiple signatures (approvals) to execute a transaction. This provides enhanced security for wallets and contracts. | +| Node | | A computer that participates in a blockchain network by maintaining a copy of the blockchain, relaying information, and validating transactions. Nodes work together to ensure the network's security and functionality. | +| Non-Fungible Token | NFT | A unique digital asset that represents ownership of a specific item or piece of content on the blockchain. Unlike cryptocurrencies, NFTs are not interchangeable. | +| Private Key | | A secret code that allows access to cryptocurrency holdings. It's used to sign transactions and should never be shared. | +| Public Key | | A cryptographic code derived from a private key that serves as a public address where others can send cryptocurrency. | +| Smart Contract | | Self-executing code on a blockchain that automatically implements the terms of an agreement when predetermined conditions are met, without requiring intermediaries. | +| Stablecoin | | A type of cryptocurrency designed to minimize price volatility by pegging its value to a stable asset (like fiat currency) or using algorithmic methods to control supply. | +| Staking | | The process of actively participating in transaction validation on a proof-of-stake blockchain by locking up cryptocurrency to support network operations. | +| Token | | A digital asset built on an existing blockchain. Tokens can represent various assets or utilities within a specific ecosystem or platform. | +| Validator | | A specialized type of node that actively participates in the consensus process by validating transactions, producing blocks, and securing the network. Validators typically stake cryptocurrency as collateral to ensure honest behavior. | +| Verifiable Random Function | VRF | A cryptographic function that provides verifiable randomness. Used in blockchain protocols to generate unpredictable but verifiable random values. Important for applications requiring fair random selection like lottery systems, NFT distributions, or validator selection in some consensus mechanisms. | +| Virtual Machine | VM | A computing environment that executes code and maintains state. In blockchain, VMs define a blockchain's application logic, including state transitions, transaction rules, and smart contract execution. VMs serve as the blueprint for a blockchain's functionality. | +| Wallet | | A digital tool that allows users to store and manage their cryptocurrency assets. Wallets can be hardware devices, software applications, or services. | + +## Why Understanding Terminology Matters + +Blockchain technology introduces many new concepts and terms. Understanding this terminology is essential for effectively navigating the blockchain ecosystem, participating in projects, and communicating with others in the space. + +As you progress through this course, you'll encounter and gain a deeper understanding of these concepts and how they interconnect within the broader blockchain landscape. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/meta.json b/content/academy/blockchain-fundamentals/meta.json index a8f20f1d596..74fa111c558 100644 --- a/content/academy/blockchain-fundamentals/meta.json +++ b/content/academy/blockchain-fundamentals/meta.json @@ -4,6 +4,7 @@ "root": true, "pages": [ "index", + "glossary", "---What is a Blockchain?---", "...02-what-is-a-blockchain", "---Payments---", From 29cdb2f91d0c747170d4326c57f673975f87e393 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 7 Apr 2025 20:16:08 +0200 Subject: [PATCH 03/27] create the glossary ui component and glossary.json --- components/ui/glossary-term.tsx | 77 +++++++++++++++++ content/glossary.json | 148 ++++++++++++++++++++++++++++++++ 2 files changed, 225 insertions(+) create mode 100644 components/ui/glossary-term.tsx create mode 100644 content/glossary.json diff --git a/components/ui/glossary-term.tsx b/components/ui/glossary-term.tsx new file mode 100644 index 00000000000..0c638b728a1 --- /dev/null +++ b/components/ui/glossary-term.tsx @@ -0,0 +1,77 @@ +"use client" + +import React, { useState, useEffect } from "react" +import Link from "next/link" +import { Tooltip, TooltipContent, TooltipTrigger } from "@/components/ui/tooltip" +import glossaryData from "@/content/glossary.json" +import { GlossaryTerm as GlossaryTermType } from "@/types/glossary" + +interface GlossaryTermProps { + children: React.ReactNode + termKey?: string // Optional term key if different from the children text + className?: string +} + +export function GlossaryTerm({ + children, + termKey, + className = "" +}: GlossaryTermProps) { + const [term, setTerm] = useState(null) + + useEffect(() => { + // Get term from glossary data + const searchTerm = termKey || (typeof children === 'string' ? children : null) + + if (searchTerm) { + const foundTerm = glossaryData.terms.find( + (t) => t.term.toLowerCase() === searchTerm.toLowerCase() + ) + setTerm(foundTerm || null) + } + }, [children, termKey]) + + if (!term) { + // If term not found in glossary, just render the children without tooltip + return {children} + } + + return ( + + + {children} + + +
+
+

{term.term}

+ {term.abbreviation && ( + + {term.abbreviation} + + )} +
+ + {term.previousTerm && ( +
+ Previously known as: {term.previousTerm} +
+ )} + +

{term.description}

+ + {term.learnMoreUrl && ( + + Learn more → + + )} +
+ + + ) +} + +export default GlossaryTerm \ No newline at end of file diff --git a/content/glossary.json b/content/glossary.json new file mode 100644 index 00000000000..7506f1e19fe --- /dev/null +++ b/content/glossary.json @@ -0,0 +1,148 @@ +{ + "terms": [ + { + "term": "Avalanche Consensus", + "abbreviation": null, + "previousTerm": null, + "description": "A family of consensus protocols that power the Avalanche network, known for high throughput, fast finality, and energy efficiency. The X-Chain uses the core Avalanche consensus protocol, while the P-Chain and C-Chain use the Snowman variant.", + "learnMoreUrl": "/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro", + "category": "avalanche" + }, + { + "term": "Avalanche L1", + "abbreviation": "L1", + "previousTerm": "Subnet", + "description": "An independent, sovereign blockchain network on Avalanche that can have its own validator set, tokenomics, and rules. Avalanche L1s work together to form the broader Avalanche Network.", + "learnMoreUrl": "/docs/quick-start/avalanche-l1s", + "category": "avalanche" + }, + { + "term": "Avalanche Virtual Machine", + "abbreviation": "AVM", + "previousTerm": null, + "description": "The virtual machine implementation that powers the X-Chain, handling operations on Avalanche Native Tokens.", + "learnMoreUrl": null, + "category": "avalanche" + }, + { + "term": "Contract Chain", + "abbreviation": "C-Chain", + "previousTerm": null, + "description": "An implementation of the Ethereum Virtual Machine (EVM) that supports the deployment and execution of smart contracts written in Solidity. Uses the Coreth Virtual Machine.", + "learnMoreUrl": "/docs/quick-start/primary-network#c-chain", + "category": "avalanche" + }, + { + "term": "Coreth", + "abbreviation": null, + "previousTerm": null, + "description": "The virtual machine implementation that powers the C-Chain, enabling Ethereum compatibility on Avalanche.", + "learnMoreUrl": null, + "category": "avalanche" + }, + { + "term": "Exchange Chain", + "abbreviation": "X-Chain", + "previousTerm": null, + "description": "Responsible for operations on digital smart assets known as Avalanche Native Tokens. Uses the Avalanche Virtual Machine (AVM).", + "learnMoreUrl": "/docs/quick-start/primary-network#x-chain", + "category": "avalanche" + }, + { + "term": "Interchain Messaging", + "abbreviation": "ICM", + "previousTerm": "Teleporter", + "description": "A protocol that enables communication between blockchains on Avalanche, allowing for secure message passing between different L1s.", + "learnMoreUrl": "/academy/interchain-messaging", + "category": "avalanche" + }, + { + "term": "Interchain Token Transfer", + "abbreviation": "ICTT", + "previousTerm": null, + "description": "A system that allows tokens to be transferred seamlessly between different Avalanche L1s, enabling greater interoperability within the ecosystem.", + "learnMoreUrl": "/academy/interchain-token-transfer", + "category": "avalanche" + }, + { + "term": "Platform Chain", + "abbreviation": "P-Chain", + "previousTerm": null, + "description": "Responsible for all validator and Avalanche L1-level operations, including staking, creating new blockchains, and other platform-level functions. Uses the Platform Virtual Machine.", + "learnMoreUrl": "/docs/quick-start/primary-network#p-chain", + "category": "avalanche" + }, + { + "term": "Platform Virtual Machine", + "abbreviation": null, + "previousTerm": null, + "description": "The virtual machine implementation that powers the P-Chain, handling staking, validator, and Avalanche L1 operations.", + "learnMoreUrl": null, + "category": "avalanche" + }, + { + "term": "Primary Network", + "abbreviation": null, + "previousTerm": null, + "description": "A special Avalanche L1 that runs three blockchains: the P-Chain, C-Chain, and X-Chain. All validators on the Primary Network must stake at least 2,000 AVAX.", + "learnMoreUrl": "/docs/quick-start/primary-network", + "category": "avalanche" + }, + { + "term": "Snowman Consensus", + "abbreviation": null, + "previousTerm": null, + "description": "A linear chain-optimized variant of the Avalanche consensus protocol used specifically by the P-Chain and C-Chain. Designed for smart contract chains and platform operations.", + "learnMoreUrl": "/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus", + "category": "avalanche" + }, + { + "term": "Annual Percentage Rate", + "abbreviation": "APR", + "previousTerm": null, + "description": "The annual return you will receive on an investment, without accounting for the effects of compounding.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Annual Percentage Yield", + "abbreviation": "APY", + "previousTerm": null, + "description": "The annual return you will receive on an investment when returns are compounded. Unlike APR, APY includes the effects of compounding.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Arbitrage", + "abbreviation": null, + "previousTerm": null, + "description": "The practice of buying and selling assets between different markets to profit from price discrepancies. For example, buying a token on one exchange where it's cheaper and selling it on another where it's more expensive.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Automated Market Maker", + "abbreviation": "AMM", + "previousTerm": null, + "description": "A protocol that uses liquidity pools and mathematical formulas to automatically determine asset prices and enable trading without traditional order books.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Block", + "abbreviation": null, + "previousTerm": null, + "description": "A collection of transactions that are grouped together and added to the blockchain. Each block typically contains a reference to the previous block, creating a chain.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Blockchain", + "abbreviation": null, + "previousTerm": null, + "description": "A distributed ledger technology that records transactions across multiple computers in a way that ensures security, transparency, and immutability.", + "learnMoreUrl": null, + "category": "blockchain" + } + ] +} \ No newline at end of file From 0e3cdf7a98f710d1b19b8de5267b8104e49cad4b Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Tue, 8 Apr 2025 10:21:20 +0200 Subject: [PATCH 04/27] update glossary with all the blockchain/avalanche references --- content/glossary.json | 280 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 280 insertions(+) diff --git a/content/glossary.json b/content/glossary.json index 7506f1e19fe..66cac9b0760 100644 --- a/content/glossary.json +++ b/content/glossary.json @@ -143,6 +143,286 @@ "description": "A distributed ledger technology that records transactions across multiple computers in a way that ensures security, transparency, and immutability.", "learnMoreUrl": null, "category": "blockchain" + }, + { + "term": "Compounding", + "abbreviation": null, + "previousTerm": null, + "description": "The process where earnings from an asset are reinvested to generate additional returns over time, creating exponential growth.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Consensus Mechanism", + "abbreviation": null, + "previousTerm": null, + "description": "The method by which network participants agree on the valid state of the blockchain. Examples include Proof of Work, Proof of Stake, and Avalanche Consensus.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Cross-Chain Interoperability Protocol", + "abbreviation": "CCIP", + "previousTerm": null, + "description": "A protocol that enables communication between different blockchains. Allows for the transfer of messages, tokens, and data across separate blockchain networks. Most commonly associated with Chainlink's cross-chain communication solution.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Cryptocurrency", + "abbreviation": null, + "previousTerm": null, + "description": "A digital or virtual currency that uses cryptography for security and operates independently of a central authority.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Decentralized Application", + "abbreviation": "dApp", + "previousTerm": null, + "description": "An application that runs on a decentralized network rather than being controlled by a single entity or authority.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Decentralized Autonomous Organization", + "abbreviation": "DAO", + "previousTerm": null, + "description": "An organization governed by rules encoded as smart contracts on a blockchain, without centralized leadership. Members collectively make decisions through voting mechanisms.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Decentralized Exchange", + "abbreviation": "DEX", + "previousTerm": null, + "description": "A peer-to-peer marketplace where users can trade cryptocurrencies directly with each other without an intermediary. These exchanges use smart contracts to execute trades.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Decentralized Finance", + "abbreviation": "DeFi", + "previousTerm": null, + "description": "A financial system built on blockchain technology that aims to recreate and improve upon traditional financial services without central authorities or intermediaries.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Gas", + "abbreviation": null, + "previousTerm": null, + "description": "The fee required to perform a transaction or execute a contract on a blockchain network. Gas is used to allocate resources of the blockchain's virtual machine.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Hash", + "abbreviation": null, + "previousTerm": null, + "description": "A function that converts input data to a fixed-size string of characters. Blockchain uses hash functions to ensure data integrity and security.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Liquidity", + "abbreviation": null, + "previousTerm": null, + "description": "The ease with which an asset can be converted to cash or traded without affecting its market price. Higher liquidity means the asset can be exchanged more easily.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Liquidity Pool", + "abbreviation": null, + "previousTerm": null, + "description": "A collection of tokens or assets locked in a smart contract, providing liquidity for decentralized exchanges and other DeFi applications.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Mining", + "abbreviation": null, + "previousTerm": null, + "description": "The process by which new transactions are verified and added to a blockchain using a Proof of Work consensus mechanism. Miners solve complex puzzles to earn rewards.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Multi-signature", + "abbreviation": "Multisig", + "previousTerm": null, + "description": "A security feature that requires multiple signatures (approvals) to execute a transaction. This provides enhanced security for wallets and contracts.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Node", + "abbreviation": null, + "previousTerm": null, + "description": "A computer that participates in a blockchain network by maintaining a copy of the blockchain, relaying information, and validating transactions. Nodes work together to ensure the network's security and functionality.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Non-Fungible Token", + "abbreviation": "NFT", + "previousTerm": null, + "description": "A unique digital asset that represents ownership of a specific item or piece of content on the blockchain. Unlike cryptocurrencies, NFTs are not interchangeable.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Private Key", + "abbreviation": null, + "previousTerm": null, + "description": "A secret code that allows access to cryptocurrency holdings. It's used to sign transactions and should never be shared.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Public Key", + "abbreviation": null, + "previousTerm": null, + "description": "A cryptographic code derived from a private key that serves as a public address where others can send cryptocurrency.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Smart Contract", + "abbreviation": null, + "previousTerm": null, + "description": "Self-executing code on a blockchain that automatically implements the terms of an agreement when predetermined conditions are met, without requiring intermediaries.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Stablecoin", + "abbreviation": null, + "previousTerm": null, + "description": "A type of cryptocurrency designed to minimize price volatility by pegging its value to a stable asset (like fiat currency) or using algorithmic methods to control supply.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Staking", + "abbreviation": null, + "previousTerm": null, + "description": "The process of actively participating in transaction validation on a proof-of-stake blockchain by locking up cryptocurrency to support network operations.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Token", + "abbreviation": null, + "previousTerm": null, + "description": "A digital asset built on an existing blockchain. Tokens can represent various assets or utilities within a specific ecosystem or platform.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Fungible Token", + "abbreviation": null, + "previousTerm": null, + "description": "A type of token where all units are identical and interchangeable, like cryptocurrencies. Each token has the same value and properties as any other token of the same type.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Validator", + "abbreviation": null, + "previousTerm": null, + "description": "A specialized type of node that actively participates in the consensus process by validating transactions, producing blocks, and securing the network. Validators typically stake cryptocurrency as collateral to ensure honest behavior.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Verifiable Random Function", + "abbreviation": "VRF", + "previousTerm": null, + "description": "A cryptographic function that provides verifiable randomness. Used in blockchain protocols to generate unpredictable but verifiable random values. Important for applications requiring fair random selection like lottery systems, NFT distributions, or validator selection in some consensus mechanisms.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Virtual Machine", + "abbreviation": "VM", + "previousTerm": null, + "description": "A computing environment that executes code and maintains state. In blockchain, VMs define a blockchain's application logic, including state transitions, transaction rules, and smart contract execution. VMs serve as the blueprint for a blockchain's functionality.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Wallet", + "abbreviation": null, + "previousTerm": null, + "description": "A digital tool that allows users to store and manage their cryptocurrency assets. Wallets can be hardware devices, software applications, or services.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Proof of Work", + "abbreviation": "PoW", + "previousTerm": null, + "description": "A consensus mechanism that requires network participants to expend computational energy to solve complex mathematical puzzles in order to validate transactions and create new blocks.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Proof of Stake", + "abbreviation": "PoS", + "previousTerm": null, + "description": "A consensus mechanism where validators are selected to create new blocks based on the amount of cryptocurrency they have staked as collateral, rather than computational work.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Ledger", + "abbreviation": null, + "previousTerm": null, + "description": "A comprehensive record-keeping system that documents all transactions in a chronological and immutable way, ensuring transparency and traceability.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Bitcoin", + "abbreviation": "BTC", + "previousTerm": null, + "description": "The first and most well-known cryptocurrency, created in 2009 by an anonymous person or group using the pseudonym Satoshi Nakamoto.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Ethereum", + "abbreviation": "ETH", + "previousTerm": null, + "description": "A decentralized, open-source blockchain platform that enables smart contracts and decentralized applications (dApps) to be built and run without downtime, fraud, control, or interference from a third party.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Avalanche", + "abbreviation": "AVAX", + "previousTerm": null, + "description": "A high-performance, scalable blockchain platform for decentralized applications and custom blockchain networks, known for its high throughput, low latency, and energy-efficient consensus mechanism.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Slashing", + "abbreviation": null, + "previousTerm": null, + "description": "A penalty mechanism in Proof of Stake networks where validators lose a portion of their staked cryptocurrency for malicious behavior or failing to follow the protocol rules.", + "learnMoreUrl": null, + "category": "blockchain" + }, + { + "term": "Consensus", + "abbreviation": null, + "previousTerm": null, + "description": "The process by which all nodes in a distributed network agree on the state of the system. In blockchain, consensus ensures all participants have the same copy of the ledger.", + "learnMoreUrl": null, + "category": "blockchain" } ] } \ No newline at end of file From 231a9118dce75eb2f12d162e3c21941d3872fb00 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Tue, 8 Apr 2025 13:41:39 +0200 Subject: [PATCH 05/27] blockchain fundamentals academy course updated with glossary terms --- .../01-what-is-a-blockchain.mdx | 4 +++- .../02-decentralized-computer.mdx | 6 ++++-- .../03-decentralized-applications.mdx | 4 +++- .../02-what-is-a-blockchain/04-use-cases.mdx | 10 ++++++---- .../03-payments-use-case/01-payments-use-case.mdx | 10 ++++++---- .../02-account-balances-transfers.mdx | 2 ++ .../03-payments-use-case/03-ledger.mdx | 8 +++++--- .../04-signatures/01-signatures.mdx | 2 ++ .../04-signatures/xx-signature-schemes.mdx | 4 +++- .../01-tx-ordering-through-consensus.mdx | 2 ++ .../02-longest-chain-consensus.mdx | 2 ++ .../xx-tx-lifecycle.mdx | 4 +++- .../05-sybil-protection/01-sybil-protection.mdx | 2 ++ .../05-sybil-protection/02-proof-of-work.mdx | 4 +++- .../05-sybil-protection/03-proof-of-stake.mdx | 4 +++- .../06-smart-contracts/01-smart-contracts.mdx | 2 ++ content/academy/blockchain-fundamentals/index.mdx | 10 ++++++---- .../xx-decentralization.mdx | 9 +++++---- .../xx-regulation/01-regulation.mdx | 2 ++ .../academy/blockchain-fundamentals/xx-tokens.mdx | 14 ++++++++------ 20 files changed, 72 insertions(+), 33 deletions(-) diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx index 86006ed7f8c..b96a6211929 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx @@ -6,7 +6,9 @@ authors: [martineckardt] icon: Book --- -Blockchains introduce a lot of new concepts. In this chapter we will approach the concept from a high level and see how it compares with other kinds of computers we are used to: +import GlossaryTerm from '@/components/ui/glossary-term' + +Blockchains introduce a lot of new concepts. In this chapter we will approach the concept from a high level and see how it compares with other kinds of computers we are used to: - **Decentralized Computer:** How is a blockchain different from computers we know? - **Decentralized Applications:** What are dApps? diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx index 6ab3349c475..88d4a196fd1 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx @@ -6,17 +6,19 @@ authors: [martineckardt] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' + We interact with various types of computers every day, each designed to serve specific functions based on its unique characteristics. Smartphones, for example, are portable and convenient, offering powerful computing capabilities in a compact form. They are ideal for tasks that require mobility, such as communication, navigation, and media consumption. However, their small screen size and limited processing power compared to larger computers make them less suitable for tasks that require intensive computing power or extensive multitasking. PCs, on the other hand, provide more robust processing power and versatility. They are well-suited for tasks like video editing, gaming, or software development, where performance and the ability to use larger screens and peripherals like a mouse and keyboard are crucial. Yet, they lack the portability of smartphones and often require more space and power to operate. ![](/common-images/blockchain-basics/decentralized-computer/different-kinds-of-computer.png) Web servers represent another type of computer, designed to handle large volumes of data and manage multiple simultaneous requests from users across the internet. They are optimized for reliability, speed, and the ability to run continuously without interruption, making them crucial for hosting websites, online services, and cloud computing platforms. While web servers excel at handling complex backend processes and large-scale operations, they are not intended for direct user interaction or tasks requiring a graphical user interface, which is where PCs and smartphones come in. Each type of computer has its strengths and weaknesses, and they often work together within the broader digital ecosystem, each performing tasks that suit their design and capabilities best. -The internet, as we know it today, is built on a centralized architecture, where data and services are controlled and maintained by a few large entities like data centers and internet service providers. However, the advent of blockchain technologies has opened up new possibilities for a more decentralized internet, often referred to as Web 3.0 or the decentralized web. +The internet, as we know it today, is built on a centralized architecture, where data and services are controlled and maintained by a few large entities like data centers and internet service providers. However, the advent of blockchain technologies has opened up new possibilities for a more decentralized internet, often referred to as Web 3.0 or the decentralized web. ## Blockchains are Decentralized Computers -Blockchain can be thought of as a new kind of computer. The key advantage of this new kind of computer is decentralization, meaning that no single entity has control over the entire system. Instead, control is distributed across many participants, which enhances security and transparency, as all transactions are verified by consensus and recorded on an immutable ledger. +Blockchain can be thought of as a new kind of computer. The key advantage of this new kind of computer is decentralization, meaning that no single entity has control over the entire system. Instead, control is distributed across many participants, which enhances security and transparency, as all transactions are verified by consensus and recorded on an immutable ledger. ![](/common-images/blockchain-basics/decentralized-computer/blockchain-computer.png) diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx index 25fec5e7d99..bc4355a988f 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx @@ -6,11 +6,13 @@ authors: [martineckardt] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' + Programs and apps are software applications designed to run on different types of computers, such as smartphones, PCs, and web servers. On smartphones, apps are typically designed for specific tasks like messaging, gaming, or social media, optimized for touch interfaces and mobile connectivity. PCs run more complex programs, such as word processors, video editors, or development tools, which take advantage of larger screens, more powerful hardware, and the ability to handle multitasking. Web servers, on the other hand, run server-side applications that power websites, process data, and handle multiple user requests simultaneously. These programs often provide the backend services that apps on smartphones and PCs rely on to function. ![](/common-images/blockchain-basics/decentralized-computer/decentralized-applications.png) -Similarly, smart contracts or decentralized applications (dApps) are programs that run on a blockchain. A smart contract is a self-executing program with the terms of the agreement directly written into code, operating without the need for a trusted central authority. dApps are more complex, often consisting of multiple smart contracts that together offer a full application experience on the blockchain. Like traditional apps, these blockchain-based programs can perform a wide range of tasks, from managing digital assets to running decentralized finance (DeFi) protocols. +Similarly, smart contracts or decentralized applications (dApps) are programs that run on a blockchain. A smart contract is a self-executing program with the terms of the agreement directly written into code, operating without the need for a trusted central authority. dApps are more complex, often consisting of multiple smart contracts that together offer a full application experience on the blockchain. Like traditional apps, these blockchain-based programs can perform a wide range of tasks, from managing digital assets to running Decentralized Finance (DeFi) protocols. ![](/common-images/blockchain-basics/decentralized-computer/decentralized-applications-connected.png) diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx index 63abbae1e01..082db915a01 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx @@ -6,10 +6,12 @@ authors: [martineckardt] icon: BookOpen --- -Blockchains have unique properties that make them an excellent fit for certain use cases where security, transparency, and decentralization are paramount: +import GlossaryTerm from '@/components/ui/glossary-term' + +Blockchains have unique properties that make them an excellent fit for certain use cases where security, transparency, and decentralization are paramount: ### Finance -Blockchains enable secure, transparent transactions without the need for intermediaries. This is the foundation of cryptocurrencies and decentralized finance (DeFi) platforms. The immutability of blockchain records ensures that financial transactions are tamper-proof and can be audited at any time, making it ideal for high-stakes environments where trust is critical. +Blockchains enable secure, transparent transactions without the need for intermediaries. This is the foundation of cryptocurrency and Decentralized Finance (DeFi) platforms. The immutability of blockchain records ensures that financial transactions are tamper-proof and can be audited at any time, making it ideal for high-stakes environments where trust is critical. ### Supply Chain Management Blockchain can provide an immutable record of a product's journey from origin to consumer, increasing transparency and reducing fraud. This helps ensure that every step of the supply chain is accurately tracked and verified. @@ -19,6 +21,6 @@ Blockchain's transparency and security ensure that votes are accurately counted ## Downsides -However, the same properties that make blockchains so powerful in these areas also introduce significant challenges. Blockchains are inherently less efficient than traditional databases because they require consensus among distributed nodes, which can slow down transaction speeds and increase the complexity of operations. This makes blockchain less suitable for use cases where high speed and efficiency are critical, such as real-time data processing or high-frequency trading. Additionally, the complexity of developing and maintaining blockchain systems can be a barrier, particularly for applications that don't require the levels of security and decentralization that blockchains offer. +However, the same properties that make blockchains so powerful in these areas also introduce significant challenges. Blockchains are inherently less efficient than traditional databases because they require consensus among distributed nodes, which can slow down transaction speeds and increase the complexity of operations. This makes blockchain less suitable for use cases where high speed and efficiency are critical, such as real-time data processing or high-frequency trading. Additionally, the complexity of developing and maintaining blockchain systems can be a barrier, particularly for applications that don't require the levels of security and decentralization that blockchains offer. -When deciding whether to use blockchain, consider whether your use case requires the specific advantages of decentralization, transparency, and security. Blockchain is well-suited for applications where trust between parties is a major concern and where an immutable record of transactions is essential. However, if your application demands high throughput, real-time processing, or simplicity, a traditional centralized system might be more appropriate. In short, blockchain is a powerful tool for the right situations, but its use should be carefully considered against the specific needs of your application. \ No newline at end of file +When deciding whether to use blockchain consider whether your use case requires the specific advantages of decentralization, transparency, and security. Blockchain is well-suited for applications where trust between parties is a major concern and where an immutable record of transactions is essential. However, if your application demands high throughput, real-time processing, or simplicity, a traditional centralized system might be more appropriate. In short, blockchain is a powerful tool for the right situations, but its use should be carefully considered against the specific needs of your application. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx index a4115d4a43d..7dde5216096 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx @@ -6,16 +6,18 @@ authors: [martineckardt] icon: Book --- -In this chapter we will dive deeper in the payments use case. We will explore how blockchain technology can be used to build a decentralized payment system. We will look at the different components of a payment system, such as account balances, transactions, and user interactions. We will also discuss the benefits of using blockchain technology for payments, such as security, transparency, and decentralization. +import GlossaryTerm from '@/components/ui/glossary-term' + +In this chapter we will dive deeper in the payments use case. We will explore how blockchain technology can be used to build a decentralized payment system. We will look at the different components of a payment system, such as account balances, transactions, and user interactions. We will also discuss the benefits of using blockchain technology for payments, such as security, transparency, and decentralization. | Use Case | Data Structures | User Interactions | |----------------------- |------------------ |-------------------- | | Payments | Account Balances | Transfer Funds | -| Decentralized Finance | Loans, ... | Borrow, Repay, .. | +| Decentralized Finance | Loans, ... | Borrow, Repay, .. | | Voting Systems | Votes | Vote | | Supply Chain | Shipments | Hand Over, Deliver | | Identity Management | Certificates | Issue, Proof | -Many of the concepts we will discuss in this chapter are applicable to other use cases as well. For example, the idea of account balances and transactions is not unique to payments but can be found in other applications like decentralized finance (DeFi) or supply chain management. Similarly, user interactions such as transferring funds or voting can be applied to various use cases, each with its unique requirements and challenges. +Many of the concepts we will discuss in this chapter are applicable to other use cases as well. For example, the idea of account balances and transactions is not unique to payments but can be found in other applications like Decentralized Finance (DeFi) or supply chain management. Similarly, user interactions such as transferring funds or voting can be applied to various use cases, each with its unique requirements and challenges. -So while we are discussing this specific use case, try to think about how these concepts could be adapted to other scenarios. This will help you understand the broader implications of blockchain technology and how it can be used to solve a wide range of problems across different industries and domains. \ No newline at end of file +So while we are discussing this specific use case, try to think about how these concepts could be adapted to other scenarios. This will help you understand the broader implications of blockchain technology and how it can be used to solve a wide range of problems across different industries and domains. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx index 203537c91ae..59d639b16b1 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx @@ -6,6 +6,8 @@ authors: [martineckardt] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' + ## Account Balances Account Balances refer to the current amount of money or assets held in a specific account at a given time. This number reflects the total value after all credits (additions) and debits (subtractions) have been accounted for, indicating how much the account holder has available to use or withdraw. For example, in a bank account, the balance represents the amount of money that the account holder can access, whether for spending, saving, or transferring. diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx index 0da665af228..1ff2ebbc526 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx @@ -6,14 +6,16 @@ authors: [martineckardt] icon: BookOpen --- -A ledger is a comprehensive record-keeping system that documents all transactions. It maintains a detailed and chronological list of transactions, capturing every transfers across accounts. This ensures that every action is accurately tracked and traceable, providing a clear and complete view of the system's activity. +import GlossaryTerm from '@/components/ui/glossary-term' + +A ledger is a comprehensive record-keeping system that documents all transactions. It maintains a detailed and chronological list of transactions, capturing every transfers across accounts. This ensures that every action is accurately tracked and traceable, providing a clear and complete view of the system's activity. ![](/common-images/blockchain-basics/payments/ledger.png) ## Immutability -An immutable ledger means that once a transaction is recorded, it cannot be altered or deleted. This immutability ensures that the historical record of all transactions remains intact and unchangeable, which is crucial for maintaining transparency and trust. Even if errors are made or transactions are invalid, the ledger preserves the original data, preventing tampering or unauthorized modifications. +An immutable ledger means that once a transaction is recorded, it cannot be altered or deleted. This immutability ensures that the historical record of all transactions remains intact and unchangeable, which is crucial for maintaining transparency and trust. Even if errors are made or transactions are invalid, the ledger preserves the original data, preventing tampering or unauthorized modifications. ## Append-Only -An append-only ledger operates by adding new transactions to the end of the record without altering any previous entries. This means that while the ledger grows with each new transaction, past transactions remain unchanged and preserved. Invalid transactions, which fail to execute due to issues like insufficient funds, are still recorded in the ledger to maintain a complete history. To reverse the effects of a transaction, a new transaction must be appended that counteracts the previous one, ensuring the integrity and consistency of the ledger’s overall state. \ No newline at end of file +An append-only ledger operates by adding new transactions to the end of the record without altering any previous entries. This means that while the ledger grows with each new transaction, past transactions remain unchanged and preserved. Invalid transactions, which fail to execute due to issues like insufficient funds, are still recorded in the ledger to maintain a complete history. To reverse the effects of a transaction, a new transaction must be appended that counteracts the previous one, ensuring the integrity and consistency of the ledger's overall state. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx b/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx index 7f50d95d341..09ed08fb1b2 100644 --- a/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx +++ b/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx @@ -6,4 +6,6 @@ authors: [martineckardt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + Coming soon \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx b/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx index dd74452ba25..0be66ce5374 100644 --- a/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx +++ b/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx @@ -6,7 +6,9 @@ authors: [martineckardt] icon: Notebook --- -While transactions on ledgers in the analogue world were often authorized by hand-written signatures, that is not going to work for the adoption in blockchain. To utilize the concept of a ledger in the modern age, we leverage cryptography instead. +import GlossaryTerm from '@/components/ui/glossary-term' + +While transactions on ledgers in the analogue world were often authorized by hand-written signatures, that is not going to work for the adoption in blockchain. To utilize the concept of a ledger in the modern age, we leverage cryptography instead. import SignatureSchemes from "@/content/common/cryptography/signature-schemes.mdx" diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx index 65d4bb85fa2..635a13efb9d 100644 --- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx +++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx @@ -5,3 +5,5 @@ updated: 2024-05-31 authors: [martineckardt] icon: Book --- + +import GlossaryTerm from '@/components/ui/glossary-term' diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx index 4f43b11f2cc..9fcbc16517d 100644 --- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx +++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx @@ -5,3 +5,5 @@ updated: 2024-05-31 authors: [martineckardt] icon: BookOpen --- + +import GlossaryTerm from '@/components/ui/glossary-term' diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx index ca93dbda5e5..6029cd91003 100644 --- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx +++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx @@ -6,6 +6,8 @@ authors: [martineckardt] icon: Notebook --- +import GlossaryTerm from '@/components/ui/glossary-term' + ## Creation @@ -18,7 +20,7 @@ icon: Notebook ## Verification -## Consensus +## Consensus ## Finalization \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx index 7abfabfc7c0..58a3f52959c 100644 --- a/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx +++ b/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx @@ -6,3 +6,5 @@ authors: [martineckardt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx index 052d2e32488..bd2d034e970 100644 --- a/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx +++ b/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx @@ -4,4 +4,6 @@ description: TBD updated: 2024-05-31 authors: [martineckardt] icon: BookOpen ---- \ No newline at end of file +--- + +import GlossaryTerm from '@/components/ui/glossary-term' \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx index 6455b23167f..b050dfe46e0 100644 --- a/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx +++ b/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx @@ -6,9 +6,11 @@ authors: [martineckardt] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' + - Carrots and Sticks -## Staking Rewards +## Staking Rewards - Carrot diff --git a/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx b/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx index d947feb9d16..909bdfc9ade 100644 --- a/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx +++ b/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx @@ -5,3 +5,5 @@ updated: 2024-05-31 authors: [martineckardt] icon: Book --- + +import GlossaryTerm from '@/components/ui/glossary-term' diff --git a/content/academy/blockchain-fundamentals/index.mdx b/content/academy/blockchain-fundamentals/index.mdx index 4f2c705818b..1ad2dae869d 100644 --- a/content/academy/blockchain-fundamentals/index.mdx +++ b/content/academy/blockchain-fundamentals/index.mdx @@ -6,9 +6,11 @@ authors: [ashucoder9] icon: Smile --- -Welcome to the Blockchain Fundamentals, an online course introducing you to blockchain! This course will provide you with a comprehensive understanding of the basic concepts of blockchains. +import GlossaryTerm from '@/components/ui/glossary-term' -By the end of these courses, you'll have the knowledge and skills to leverage the power of blockchain technology for your own projects and applications. We're excited to have you join us on this journey and can't wait to see what you'll create with Avalanche! +Welcome to the Blockchain Fundamentals, an online course introducing you to blockchain! This course will provide you with a comprehensive understanding of the basic concepts of blockchains. + +By the end of these courses, you'll have the knowledge and skills to leverage the power of blockchain technology for your own projects and applications. We're excited to have you join us on this journey and can't wait to see what you'll create with Avalanche! ## Course Content @@ -17,14 +19,14 @@ We will cover the following topics in this course: - What is a Blockchain? - Deep Dive into Payments - Cryptography: Signature schemes -- Consensus Mechanisms +- Consensus Mechanisms - ... ## Prerequisites This course is for people with some blockchain knowledge. Check out this [guide](/guides/what-is-a-blockchain) to review what a blockchain is. -Familiarity with the basic design of modern distributed software systems and common blockchain systems such as Bitcoin and Ethereum is also recommended. You do not need to know how to write code to successfully complete this course. +Familiarity with the basic design of modern distributed software systems and common blockchain systems such as Bitcoin and Ethereum is also recommended. You do not need to know how to write code to successfully complete this course. Having these prerequisites will help you better understand the course material and engage in the activities. If you don't know whether you have the necessary foundation for this course, please contact the course instructor for guidance. diff --git a/content/academy/blockchain-fundamentals/xx-decentralization.mdx b/content/academy/blockchain-fundamentals/xx-decentralization.mdx index ab7dc24fe75..fb3b378dcc9 100644 --- a/content/academy/blockchain-fundamentals/xx-decentralization.mdx +++ b/content/academy/blockchain-fundamentals/xx-decentralization.mdx @@ -6,13 +6,14 @@ authors: [martineckardt] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' ## Moving from a centralized Entity to a Collective of Validators -Blockchain systems achieve decentralization through the use of a network of validators, sometimes referred to as nodes, miners, or stakers, depending on the underlying consensus mechanism. Validators are responsible for verifying and securing transactions, maintaining the integrity of the blockchain, and ensuring that the system remains decentralized and trustless. Decentralization is achieved by distributing the responsibility of maintaining the network across numerous independent participants. +Blockchain systems achieve decentralization through the use of a network of validators, sometimes referred to as nodes, miners, or stakers, depending on the underlying consensus mechanism. Validators are responsible for verifying and securing transactions, maintaining the integrity of the blockchain, and ensuring that the system remains decentralized and trustless. Decentralization is achieved by distributing the responsibility of maintaining the network across numerous independent participants. -Decentralization in blockchain is achieved through a network of validators. These are independent entities that run the blockchain software, perform computations, and ensure the integrity of the blockchain. Here’s how it works: +Decentralization in blockchain is achieved through a network of validators. These are independent entities that run the blockchain software, perform computations, and ensure the integrity of the blockchain. Here's how it works: Computation Execution: Each validator independently performs the same computation. For example, let's consider a simple computation: 5 + 3. -Consensus Process: After performing the computation, validators share their results with each other. They then use a process called consensus to agree on the correct result. You can think of it as a election, where all validators vote on the correct answer. -The consensus process ensures that all validators reach an agreement on the correct result, given that the majority is honest. This agreement is crucial for maintaining the integrity and security of the blockchain. If a validator tries to cheat or provide an incorrect result, the other validators will detect the discrepancy, and the cheating validator will be penalized. \ No newline at end of file +Consensus Process: After performing the computation, validators share their results with each other. They then use a process called consensus to agree on the correct result. You can think of it as a election, where all validators vote on the correct answer. +The consensus process ensures that all validators reach an agreement on the correct result, given that the majority is honest. This agreement is crucial for maintaining the integrity and security of the blockchain. If a validator tries to cheat or provide an incorrect result, the other validators will detect the discrepancy, and the cheating validator will be penalized. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx b/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx index 143aa7a6bff..c8ae80be25d 100644 --- a/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx +++ b/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx @@ -5,3 +5,5 @@ updated: 2024-05-31 authors: [martineckardt] icon: Book --- + +import GlossaryTerm from '@/components/ui/glossary-term' diff --git a/content/academy/blockchain-fundamentals/xx-tokens.mdx b/content/academy/blockchain-fundamentals/xx-tokens.mdx index 4acd8bc15ef..f35a06a0b3c 100644 --- a/content/academy/blockchain-fundamentals/xx-tokens.mdx +++ b/content/academy/blockchain-fundamentals/xx-tokens.mdx @@ -6,14 +6,16 @@ authors: [martineckardt] icon: Notebook --- -Tokens are a concept that existed in societies for a long time. +import GlossaryTerm from '@/components/ui/glossary-term' -Tokens can be used to represent value. The most common valuable tokens we use every day are fiat currencies, like the US dollar. But there are also other kinds of tokens, such as points or miles in loyalty programs. Today we can also tokenize other assets, such as property titles. +Tokens are a concept that existed in societies for a long time. -## Fungible Tokens +Tokens can be used to represent value. The most common valuable tokens we use every day are fiat currencies, like the US dollar. But there are also other kinds of tokens, such as points or miles in loyalty programs. Today we can also tokenize other assets, such as property titles. -Fungibility means that different tokens can be considered of equal value. Let's take for example two one dollar bills. Most people will not care if they get one or the other. They both offer the same utility. +## Fungible Tokens -## Non-Fungible Tokens +Fungibility means that different tokens can be considered of equal value. Let's take for example two one dollar bills. Most people will not care if they get one or the other. They both offer the same utility. -Non-fungible tokens are not considered equal. The most prominent use cases are Art-NFTs. While the tokens may follow a standard of how they can be transfered, they may not be interchangeable. Two pieces of art may have very different values. \ No newline at end of file +## Non-Fungible Tokens + +Non-Fungible Tokens are not considered equal. The most prominent use cases are Art-NFTs. While the tokens may follow a standard of how they can be transfered, they may not be interchangeable. Two pieces of art may have very different values. \ No newline at end of file From 17861f3d9b8a8d58b82aadda3eeae62eee29d4fb Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:42:36 +0200 Subject: [PATCH 06/27] update glossary --- content/glossary.json | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/content/glossary.json b/content/glossary.json index 66cac9b0760..d113b3816b4 100644 --- a/content/glossary.json +++ b/content/glossary.json @@ -423,6 +423,22 @@ "description": "The process by which all nodes in a distributed network agree on the state of the system. In blockchain, consensus ensures all participants have the same copy of the ledger.", "learnMoreUrl": null, "category": "blockchain" + }, + { + "term": "Etna Upgrade", + "abbreviation": null, + "previousTerm": null, + "description": "The largest network upgrade of Avalanche to date, which introduced Layer 1 blockchains (L1s) to replace the Subnet model, allowing validators to operate without staking 2,000 AVAX on the Primary Network and instead pay a continuous fee.", + "learnMoreUrl": "/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx", + "category": "avalanche" + }, + { + "term": "ACP-77", + "abbreviation": null, + "previousTerm": null, + "description": "An Avalanche Community Proposal that outlines a new framework for creating low-cost, independent Layer 1 blockchains that can easily interoperate with each other. It introduced validator management changes allowing L1s to operate with validators that don't need to stake AVAX.", + "learnMoreUrl": "https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md", + "category": "avalanche" } ] } \ No newline at end of file From 9832607de824c441c6380598b50d9768d833e8ee Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:45:11 +0200 Subject: [PATCH 07/27] add the avalanche fundamentals academy with glossaryterms --- .../01-avalanche-consensus-intro.mdx | 6 ++++-- .../02-consensus-mechanisms.mdx | 6 ++++-- .../03-snowman-consensus.mdx | 10 ++++++---- .../04-tps-vs-ttf.mdx | 6 ++++-- .../01-multi-chain-architecture.mdx | 6 ++++-- .../02-subnet.mdx | 6 ++++-- .../03-benefits.mdx | 6 ++++-- .../01-creating-a-blockchain.mdx | 6 ++++-- .../03-create-on-avacloud.mdx | 5 +++-- .../01-vms-and-blockchains.mdx | 6 ++++-- .../05-vms-and-blockchains/03-blockchains.mdx | 12 +++++++----- .../06-vm-customization/00-vm-customization.mdx | 10 ++++++---- .../06-vm-customization/01-configuration.mdx | 10 ++++++---- content/academy/avalanche-fundamentals/index.mdx | 16 +++++++++------- 14 files changed, 69 insertions(+), 42 deletions(-) diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx index 773599dd178..b88e11e9828 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx @@ -6,9 +6,11 @@ authors: [martineckardt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + -Avalanche Consensus is a novel consensus protocol that is used in the Avalanche network. It is a leaderless, decentralized, and scalable consensus protocol that is used to achieve consensus on the state of the network. +Avalanche Consensus is a novel consensus protocol that is used in the Avalanche network. It is a leaderless, decentralized, and scalable consensus protocol that is used to achieve consensus on the state of the network. @@ -17,5 +19,5 @@ Avalanche Consensus is a novel consensus protocol that is used in the Avalanche In this section, you will go through the following topics: - **Consensus Mechanisms:** Understand what consensus mechanisms are and how they work -- **Snowman Consensus:** Learn about the Snowman consensus protocol +- **Snowman Consensus:** Learn about the Snowman consensus protocol - **TPS vs TTF:** Understand the difference between transactions per second (TPS) and time to finality (TTF) diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx index 7e1e698bb17..4c94a0ce900 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx @@ -6,7 +6,9 @@ authors: [ashucoder9] icon: BookOpen --- -Consensus plays a crucial role in [blockchain networks](/guides/what-is-a-blockchain) by resolving conflicts and ensuring that all validators agree on the current state of the distributed ledger. The main objective of a consensus mechanism is to create a single version of truth that is universally accepted by network participants. +import GlossaryTerm from '@/components/ui/glossary-term' + +Consensus plays a crucial role in [blockchain networks](/guides/what-is-a-blockchain) by resolving conflicts and ensuring that all validators agree on the current state of the distributed ledger. The main objective of a Consensus Mechanism is to create a single version of truth that is universally accepted by network participants. Validators can reach a consensus by following a set of steps called a consensus protocol. This way, they collectively decide on the state of the system and all state changes. Different consensus mechanisms have different approaches. All aim to ensure that validators reach a majority agreement on network state. @@ -22,7 +24,7 @@ Consensus is needed to agree on the order of state changes in a blockchain. This A Double Spending Attack is when a user attempts to spend more crypto that they own by creating multiple transactions that reference the same funds. -Let's look at an Example: Alice owns 5 AVAX +Let's look at an Example: Alice owns 5 AVAX ![](/course-images/avalanche-fundamentals/2.png) diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx index db262fb017f..f1f5b9e34a4 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx @@ -6,9 +6,11 @@ authors: [ashucoder9] icon: BookOpen --- -Protocols in the Avalanche family operate through repeated sub-sampled voting. When a validator is determining whether a block should be accepted, it asks a small, random subset of validators on their preferences. Based on the responses the validator gets, it might change its own preference. +import GlossaryTerm from '@/components/ui/glossary-term' -Let's visualize this with an example. You are a validator in a set of validators that is performing the Avalanche Consensus protocol to agree on whether to send the funds to Charlie (yellow) or to Bob (blue). It is important to understand that none of the validators really cares whether it is going to be yellow or blue, as long as all correctly operating validators decide for the same outcome at the end of the process. The starting preference is chosen random by each validator. +Protocols in the Avalanche Consensus family operate through repeated sub-sampled voting. When a validator is determining whether a Block should be accepted, it asks a small, random subset of validators on their preferences. Based on the responses the validator gets, it might change its own preference. + +Let's visualize this with an example. You are a validator in a set of validators that is performing the Snowman Consensus protocol to agree on whether to send the funds to Charlie (yellow) or to Bob (blue). It is important to understand that none of the validators really cares whether it is going to be yellow or blue, as long as all correctly operating validators decide for the same outcome at the end of the process. The starting preference is chosen random by each validator. ## Changing Preference @@ -16,7 +18,7 @@ You start by sampling the current preference of five other nodes and they reply: ![](/course-images/avalanche-fundamentals/5.png) -Avalanche consensus dictates, that a validator changes its preference if a α-majority of the sampled validators agrees on another option and it goes along with this popular choice. +Avalanche Consensus dictates, that a validator changes its preference if a α-majority of the sampled validators agrees on another option and it goes along with this popular choice. Let's set the alpha value to 3 in our example, meaning that we change our preference when 3 out of 5 sampled nodes have another preference. Since 3 out of 5 have replied with blue (Bob) we are changing our own preference to Bob. @@ -52,7 +54,7 @@ With these parameters we can illustrate the consensus algorithm as pseudo code: ## Finalization -In the common case when a transaction has no conflicts, finalization happens very quickly. When conflicts exist, honest validators quickly cluster around conflicting transactions, entering a positive feedback loop until all correct validators prefer that transaction. This leads to the acceptance of non-conflicting transactions and the rejection of conflicting transactions. +In the common case when a transaction has no conflicts, finalization happens very quickly. When conflicts exist, honest validators quickly cluster around conflicting transactions, entering a positive feedback loop until all correct validators prefer that transaction. This leads to the acceptance of non-conflicting transactions and the rejection of conflicting transactions. Avalanche Consensus guarantees (with high probability based on system parameters) that if any honest validator accepts a transaction, all honest validators will come to the same conclusion. diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx index b6460c66f0a..7247b5949d8 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx @@ -6,7 +6,9 @@ authors: [ashucoder9] icon: BookOpen --- -To measure blockchain performance we can use two metrics: +import GlossaryTerm from '@/components/ui/glossary-term' + +To measure blockchain performance we can use two metrics: - Throughput: How many transaction are finalized per second measured in transactions per second (TPS) - Time to Finality: How long does it take a transaction to go from being submitted to validators to being unchangeable. @@ -31,7 +33,7 @@ Our goal is to build highways with many lanes (high throughput) but that bring u |---|---|---| |Bitcoin|7 TPS|60 min| |Ethereum|30 TPS|6.4 min| -|Avalanche / Avalanche L1|2500 TPS|~0.8 seconds| +|Avalanche / Avalanche L1|2500 TPS|~0.8 seconds| **TPS** → **Transactions per Second** diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx index a1486fbd4d6..687f69a0e04 100644 --- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx +++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx @@ -6,12 +6,14 @@ authors: [ashucoder9] icon: Book --- -Multi-chain systems are a significant innovation, which provide greater scalability, customizability, and independence. At the core of multi-chain systems is the ability to run multiple blockchains simultaneously. Each blockchain is optimized for specialized use cases, thereby boosting the network's overall performance. +import GlossaryTerm from '@/components/ui/glossary-term' + +Multi-chain systems are a significant innovation, which provide greater scalability, customizability, and independence. At the core of multi-chain systems is the ability to run multiple blockchains simultaneously. Each blockchain is optimized for specialized use cases, thereby boosting the network's overall performance. ## What You Will Learn In this section, you will go through the following topics: -- **Avalanche L1s:** Understand what Avalanche L1s are and how they work +- **Avalanche L1s:** Understand what Avalanche L1s are and how they work - **Setup Core Wallet:** Learn how to setup the Core wallet browser extension - **Use Dexalot:** Use your first Avalanche L1 diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx index eeacc88b900..cef03306662 100644 --- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx +++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx @@ -6,9 +6,11 @@ authors: [ashucoder9] icon: BookOpen --- -An Avalanche L1 is a network with its own set of rules regarding membership, token economics, and execution layer. It is composed of a Subset of Avalanche validators collaborating to achieve consensus on the state of one or more blockchains. Validators can be members of numerous Avalanche L1s. +import GlossaryTerm from '@/components/ui/glossary-term' -Avalanche enables multiple interconnected Avalanche L1s. Each Avalanche L1 is independent while maintaining the capacity to communicate with other Avalanche L1s. All validators are part of the Avalanche L1 known as the Primary Network. +An Avalanche L1 is a network with its own set of rules regarding membership, token economics, and execution layer. It is composed of a Subset of Avalanche validators collaborating to achieve consensus on the state of one or more blockchains. Validators can be members of numerous Avalanche L1s. + +Avalanche enables multiple interconnected Avalanche L1s. Each Avalanche L1 is independent while maintaining the capacity to communicate with other Avalanche L1s. All validators are part of the Avalanche L1 known as the Primary Network. ![](/common-images/multi-chain-architecture/subnets.png) diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx index ec1d896c996..4289fc1c477 100644 --- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx +++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx @@ -6,12 +6,14 @@ authors: [ashucoder9] icon: BookOpen --- -Avalanche L1s are autonomous. Their creators can define their execution logic, set their own fees, manage their state, handle their networking, and ensure their security. They operate independently from other Avalanche L1s and the Primary Network, effectively enabling the greater Avalanche network to scale while delivering the benefits of lower latency, higher transactions per second (TPS), and lower transaction costs. +import GlossaryTerm from '@/components/ui/glossary-term' + +Avalanche L1s are autonomous. Their creators can define their execution logic, set their own fees, manage their state, handle their networking, and ensure their security. They operate independently from other Avalanche L1s and the Primary Network, effectively enabling the greater Avalanche network to scale while delivering the benefits of lower latency, higher transactions per second (TPS), and lower transaction costs. ## Scalability Through Multi-Chain Systems -A blockchain has a limited capacity for computation and data storage. Therefore, the transactions it can process in a given time frame are limited. We can use the analogy of a highway to visualize this concept. A highway can only handle a certain number of cars at a time. If too many cars try to enter the highway at once, traffic congestion will occur and they have to wait to enter the highway. +A blockchain has a limited capacity for computation and data storage. Therefore, the transactions it can process in a given time frame are limited. We can use the analogy of a highway to visualize this concept. A highway can only handle a certain number of cars at a time. If too many cars try to enter the highway at once, traffic congestion will occur and they have to wait to enter the highway. In order to scale horizontally and to offer more blockspace, a subset of validators can opt-in to validate an additional blockchain in parallel with the Primary Network: we call this an Avalanche L1. The idea is similiar to building many highways in parallel and create additional space for cars to drive on. This allows for more transactions to be processed in parallel, and therefore increases the overall throughput of the network. diff --git a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx index 35f74284653..ecda9b375d4 100644 --- a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx +++ b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx @@ -6,9 +6,11 @@ authors: [martineckardt] icon: Book --- -Now that we've gone over what an Avalanche L1 is and what the benefits of creating an Avalanche L1 on Avalanche are, you are probably eager to test out the functionality of Avalanche L1s by creating one yourself! +import GlossaryTerm from '@/components/ui/glossary-term' -There are many ways to create a blockchain on Avalanche. In this section, you will learn how to create a blockchain using the AvaCloud, a Blockchain-as-a-Service provider. This is the most straight forward way. Of course there are many other ways to create a blockchain on Avalanche, but this is the easiest way to get started. +Now that we've gone over what an Avalanche L1 is and what the benefits of creating an Avalanche L1 on Avalanche are, you are probably eager to test out the functionality of Avalanche L1s by creating one yourself! + +There are many ways to create a blockchain on Avalanche. In this section, you will learn how to create a blockchain using the AvaCloud, a Blockchain-as-a-Service provider. This is the most straight forward way. Of course there are many other ways to create a blockchain on Avalanche, but this is the easiest way to get started. You will learn how to deploy a blockchain with Avalanche-CLI in the course Multi-Chain Architecture. diff --git a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx index 408e884783e..9360fea7766 100644 --- a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx +++ b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx @@ -7,8 +7,9 @@ icon: Terminal --- import { Step, Steps } from 'fumadocs-ui/components/steps'; +import GlossaryTerm from '@/components/ui/glossary-term' -In this section, we will get our first taste of deploying an Avalanche L1. +In this section, we will get our first taste of deploying an Avalanche L1. @@ -57,4 +58,4 @@ Click the next button, hit the Submit Devnet button on the next page, and you wi -In the next section, we will finally connect to our Avalanche L1 and deploy a smart contract on it! +In the next section, we will finally connect to our Avalanche L1 and deploy a Smart Contract on it! diff --git a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx index 537d600faaf..3c89ca53220 100644 --- a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx +++ b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx @@ -6,14 +6,16 @@ authors: [martineckardt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + -Virtual Machines are defining the behaviour of a blockchain. They can be the execution environment for smart contracts and decentralized applications. In this section, you will learn about the Virtual Machines used in Avalanche. +Virtual Machines are defining the behaviour of a blockchain. They can be the execution environment for smart contracts and decentralized applications. In this section, you will learn about the Virtual Machines used in Avalanche. ## What You Will Learn In this section, you will go through the following topics: - **State Machine:** Understand what a State Machine is and how it works -- **Blockchain:** Learn about the role of VMs in blockchains +- **Blockchain:** Learn about the role of VMs in blockchains - **Variety of VMs:** Learn how Avalanche supports different VMs \ No newline at end of file diff --git a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx index 1375c07d204..1734c2f85f1 100644 --- a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx +++ b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx @@ -6,19 +6,21 @@ authors: [ashucoder9] icon: BookOpen --- -Let’s look at how VMs work in blockchain. Each validator operates an instance of our hypothetical soda dispenser. So, they have their own instance of a machine running on their server. They do this so they do not have to trust a single party with the operation of a soda dispenser, and to make it easy for everyone to verify the outcome of operations. +import GlossaryTerm from '@/components/ui/glossary-term' -When a user wishes to execute an operation on this distributed soda dispenser, they transmit the transaction to the network. The validators then reach consensus on the sequence in which transactions are carried out. In Avalanche, validators use Avalanche Consensus, which we talked about earlier. +Let's look at how VMs work in blockchain. Each validator operates an instance of our hypothetical soda dispenser. So, they have their own instance of a machine running on their server. They do this so they do not have to trust a single party with the operation of a soda dispenser, and to make it easy for everyone to verify the outcome of operations. + +When a user wishes to execute an operation on this distributed soda dispenser, they transmit the transaction to the network. The validators then reach consensus on the sequence in which transactions are carried out. In Avalanche, validators use Avalanche Consensus, which we talked about earlier. -Next, each validator executes the operation on their instance of the VM independently. Because each instance of our Virtual Machine behaves identically, validators maintain a uniform view of the machine’s state, so they balance and the number of available soda per flavor. +Next, each validator executes the operation on their instance of the VM independently. Because each instance of our Virtual Machine behaves identically, validators maintain a uniform view of the machine's state, so they balance and the number of available soda per flavor. ![](/course-images/avalanche-fundamentals/28.png) Subsequently, each validator executes the operation on their instance independently. Again, because each instance behaves identically, validators maintain a uniform view of the system's state, encompassing balance and available soda quantities. -Let’s take the example further. Assume we have 100 validators in our Soda Dispenser Avalanche L1. I submit multiple operations to the validators: +Let's take the example further. Assume we have 100 validators in our Soda Dispenser Avalanche L1. I submit multiple operations to the validators: - Insert a quarter - A little while later, I Insert another quarter @@ -26,6 +28,6 @@ Let’s take the example further. Assume we have 100 validators in our Soda Disp Each of the validators executes the operations on their own machine. After the first quarter the state of the machine states that the balance is 25 cents. After the second operation the balance is 50 cents. After choosing lemonade, the balance goes back to zero and the amount of available lemonades decreases from 8 to 7 on each instance running on each validators server. -This is the fundamental principle of Blockchains in Avalanche: A collective of validators operate identical virtual machines, come to consensus on the order of transactions, execute them, and have a uniform view on the machine's current state. +This is the fundamental principle of Blockchains in Avalanche: A collective of validators operate identical virtual machines, come to consensus on the order of transactions, execute them, and have a uniform view on the machine's current state. \ No newline at end of file diff --git a/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx b/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx index 85391e3c310..ea2798b4bf7 100644 --- a/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx +++ b/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx @@ -6,17 +6,19 @@ authors: [ashucoder9] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + -For some use cases, it may be necessary to use a customized VM too. This is the case if an application cannot be built on a regular EVM on the C-Chain, or if it would result in gas costs too high to be economical for its users or creators. +For some use cases, it may be necessary to use a customized VM too. This is the case if an application cannot be built on a regular EVM on the Contract Chain, or if it would result in gas costs too high to be economical for its users or creators. -Depending on a builder's needs, Avalanche allows for different VM customizations: +Depending on a builder's needs, Avalanche allows for different VM customizations: ![](/course-images/avalanche-fundamentals/32.png) -Customizing the EVM on the Ethereum network is difficult, requiring a wide consensus that the proposed change is mutually beneficial for all network participants. This can make customizations for unique use cases challenging, if not impossible. Additionally, Ethereum doesn't give users the option to add different chains. +Customizing the EVM on the Ethereum network is difficult, requiring a wide consensus that the proposed change is mutually beneficial for all network participants. This can make customizations for unique use cases challenging, if not impossible. Additionally, Ethereum doesn't give users the option to add different chains. -In Avalanche, every Avalanche L1 has autonomy over their Virtual Machines. Their creators can customize VMs to fit their unique requirements. This is one of the biggest advantages of multi-chain systems. +In Avalanche, every Avalanche L1 has autonomy over their Virtual Machines. Their creators can customize VMs to fit their unique requirements. This is one of the biggest advantages of multi-chain systems. In this section, we will see the three way to customize Virtual Machines at a high level. In later courses, we will dive deeper and learn how to actually customize each. diff --git a/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx b/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx index ddc3226c1ae..ce40e2fae49 100644 --- a/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx +++ b/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx @@ -6,13 +6,15 @@ authors: [ashucoder9] icon: BookOpen --- -When building a VM, it is possible to define certain parameters that can change the behavior of the VM. In our soda dispenser analogy these may be the products and prices offered by the dispenser. We might want to have two dispenser blockchains that offer different products and prices. If the VM is built in a way that it has parameters for the products and prices, it can be easily reused for different use items. +import GlossaryTerm from '@/components/ui/glossary-term' + +When building a VM, it is possible to define certain parameters that can change the behavior of the VM. In our soda dispenser analogy these may be the products and prices offered by the dispenser. We might want to have two dispenser blockchains that offer different products and prices. If the VM is built in a way that it has parameters for the products and prices, it can be easily reused for different use items. ![](/course-images/avalanche-fundamentals/33.png) -This is a massive advantage over one-chain-fits-all systems, where the parameters have to be a compromise between all network participants. In Avalanche it is possible to have different blockchain with the same VM, but different parameters. +This is a massive advantage over one-chain-fits-all systems, where the parameters have to be a compromise between all network participants. In Avalanche it is possible to have different blockchain with the same VM, but different parameters. -Using VM Configuration we can easily create EVM-chains for different use cases such as trading a cheap gaming NFT or valuable Real estate on chain. These blockchains may differ in fees (low fees for cheap NFTs, high fees for valuable goods) and security levels (low security for cheap NFTs, high security for valuable goods). +Using VM Configuration we can easily create EVM-chains for different use cases such as trading a cheap gaming NFT or valuable Real estate on chain. These blockchains may differ in fees (low fees for cheap NFTs, high fees for valuable goods) and security levels (low security for cheap NFTs, high security for valuable goods). @@ -20,7 +22,7 @@ Examples of the configurable parameters of the subnetEVM include: **trxAllowList:** Define a whitelist of accounts that restrict which account's transactions are accepted by the VM. -**contractDeployerAllowlist:** Defined a whitelist of accounts that restricts which account can deploy contracts on the blockchain +**contractDeployerAllowlist:** Defined a whitelist of accounts that restricts which account can deploy smart contracts on the blockchain Using these parameters we VM can adapt the VM to our requirements without writing a single line of code. This is by far the easiest, but also least flexible way to customize a VM to one's requirements. diff --git a/content/academy/avalanche-fundamentals/index.mdx b/content/academy/avalanche-fundamentals/index.mdx index 31e0a093150..598cf86c7fa 100644 --- a/content/academy/avalanche-fundamentals/index.mdx +++ b/content/academy/avalanche-fundamentals/index.mdx @@ -6,17 +6,19 @@ authors: [ashucoder9] icon: Smile --- -Welcome to the Avalanche Fundamentals, an online course introducing you to the exciting world of the Avalanche technology! This course will provide you with a comprehensive understanding of the basic concepts making Avalanche unique. +import GlossaryTerm from '@/components/ui/glossary-term' + +Welcome to the Avalanche Fundamentals, an online course introducing you to the exciting world of the Avalanche technology! This course will provide you with a comprehensive understanding of the basic concepts making Avalanche unique. Throughout, you'll learn the key features and benefits of the platform, plus how to build on it. You can also ask our expert instructors questions. -By the end of these courses, you'll have the knowledge and skills to leverage the power of blockchain technology for your own projects and applications. We're excited to have you join us on this journey and can't wait to see what you'll create with Avalanche! +By the end of these courses, you'll have the knowledge and skills to leverage the power of blockchain technology for your own projects and applications. We're excited to have you join us on this journey and can't wait to see what you'll create with Avalanche! ## Prerequisites This course is for people with some blockchain knowledge. Check out this [guide](/guides/what-is-a-blockchain) to review what a blockchain is. -Familiarity with the basic design of modern distributed software systems and common blockchain systems such as Bitcoin and Ethereum is also recommended. You do not need to know how to write code to successfully complete this course. +Familiarity with the basic design of modern distributed software systems and common blockchain systems such as Bitcoin and Ethereum is also recommended. You do not need to know how to write code to successfully complete this course. Having these prerequisites will help you better understand the course material and engage in the activities. If you don't know whether you have the necessary foundation for this course, please contact the course instructor for guidance. @@ -25,10 +27,10 @@ Having these prerequisites will help you better understand the course material a By the end of this course, you will: -- Understand how Avalanche consensus works and what makes it different. -- Understand how Avalanche L1s enable scalability, customizability, and independence. -- Understand the Primary Network, a special Avalanche L1, and how to interact with it. -- Understand how Virtual Machines enable developers to create more optimized and capable blockchain systems and to tackle completely new use cases unachievable with previous solutions. +- Understand how Avalanche Consensus works and what makes it different. +- Understand how Avalanche L1s enable scalability, customizability, and independence. +- Understand the Primary Network, a special Avalanche L1, and how to interact with it. +- Understand how Virtual Machines enable developers to create more optimized and capable blockchain systems and to tackle completely new use cases unachievable with previous solutions. You can evaluate your own understanding of the material through quizzes and claim a certificate for successful completion at the end. From 1c8e784a63f79e5366c6cc7d2ba81080fc4325fa Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:46:37 +0200 Subject: [PATCH 08/27] update the common content with glossaryterms --- .../create-default-blockchain.mdx | 17 +++++++++-------- .../cryptography/multi-signature-schemes.mdx | 6 ++++-- .../common/cryptography/signature-schemes.mdx | 3 ++- content/common/evm-precompiles/precompiles.mdx | 6 ++++-- .../etna-upgrade-motivation.mdx | 9 +++++---- .../transaction-fees.mdx | 8 +++++--- content/common/primary-network/p-chain.mdx | 4 +++- 7 files changed, 32 insertions(+), 21 deletions(-) diff --git a/content/common/avalanche-starter-kit/create-default-blockchain.mdx b/content/common/avalanche-starter-kit/create-default-blockchain.mdx index d7115fd7820..d476cd778bc 100644 --- a/content/common/avalanche-starter-kit/create-default-blockchain.mdx +++ b/content/common/avalanche-starter-kit/create-default-blockchain.mdx @@ -1,15 +1,16 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'; +import GlossaryTerm from '@/components/ui/glossary-term' -> In the following commands, make sure to substitute the name of your Avalanche L1 for `` (including the `<>`). You can choose whatever name you want, but I recommend using `myblockchain` as the name to avoid the need for some manual configuration. +> In the following commands, make sure to substitute the name of your Avalanche L1 for `` (including the `<>`). You can choose whatever name you want, but I recommend using `myblockchain` as the name to avoid the need for some manual configuration. ### Start Avalanche L1 Configuration -To create an Avalanche L1 configuration run the following command: +To create an Avalanche L1 configuration run the following command: ```bash -avalanche blockchain create --sovereign=false +avalanche blockchain create --sovereign=false ``` For example: @@ -23,7 +24,7 @@ avalanche blockchain create myblockchain --sovereign=false ### Select Virtual Machine -You will be prompted a wizard to configure your Avalanche L1. In the first question, select `Subnet-EVM`: +You will be prompted a wizard to configure your Avalanche L1. In the first question, select `Subnet-EVM`: ```bash ? Which Virtual Machine would you like to use?: @@ -62,10 +63,10 @@ subnet-evm-v0.6.8 installation successful ✓ Successfully created blockchain configuration ``` -This command creates the config files `genesis.json` and `sidecar.json` inside: `~/.avalanche-cli/subnets/`. If you want, you can retrieve the current config with the following command: +This command creates the config files `genesis.json` and `sidecar.json` inside: `~/.avalanche-cli/subnets/`. If you want, you can retrieve the current config with the following command: ```bash -avalanche blockchain describe +avalanche blockchain describe ``` @@ -75,7 +76,7 @@ avalanche blockchain describe ### To deploy your Avalanche L1, run ```bash -avalanche blockchain deploy +avalanche blockchain deploy ``` So in our case: @@ -245,7 +246,7 @@ fuji-c = "https://api.avax-test.network/ext/bc/C/rpc" ### Make RPC-Endpoint publicly accessible -The final part of the output shows the wallet connection details. You can use these to connect your wallet like Core or Metasmask to you newly created Avalanche L1. +The final part of the output shows the wallet connection details. You can use these to connect your wallet like Core or Metasmask to you newly created Avalanche L1. import PublishPort from "@/content/common/codespaces/publish-port.mdx"; diff --git a/content/common/cryptography/multi-signature-schemes.mdx b/content/common/cryptography/multi-signature-schemes.mdx index 2ef61db6b05..506a193f904 100644 --- a/content/common/cryptography/multi-signature-schemes.mdx +++ b/content/common/cryptography/multi-signature-schemes.mdx @@ -1,4 +1,6 @@ -Multi-signature schemes, also known as multi-sigs, are cryptographic methods enabling multiple parties to collectively authorize a specific action or operation, typically by requiring a predefined number of authorized participants to provide their digital signatures. In a multi-signature scheme, each authorized party possesses their own private key, and to validate the action. A specified subset of these parties must produce their unique signatures. +import GlossaryTerm from '@/components/ui/glossary-term' + +Multi-signature schemes, also known as Multi-signature, are cryptographic methods enabling multiple parties to collectively authorize a specific action or operation, typically by requiring a predefined number of authorized participants to provide their digital signatures. In a multi-signature scheme, each authorized party possesses their own Private Key, and to validate the action. A specified subset of these parties must produce their unique signatures. ![](/common-images/cryptography/multi-signature-schemes.png) @@ -8,7 +10,7 @@ Multi-signature schemes enhance security by reducing the reliance on a single en ## BLS Multi-Signature Scheme -The [BLS (Boneh-Lynn-Shacham) multi-signature scheme](https://iacr.org/archive/asiacrypt2001/22480516.pdf) is notable for its compact size, making it a highly efficient for blockchain application. Furthermore, it supports signature and public key aggregation. +The [BLS (Boneh-Lynn-Shacham) multi-signature scheme](https://iacr.org/archive/asiacrypt2001/22480516.pdf) is notable for its compact size, making it a highly efficient for Blockchain application. Furthermore, it supports signature and public key aggregation. - Signature aggregation compresses all signatures into a single short signature, which makes the transportation and verification much more efficient. - Public Key aggregation allows the verification algorithm to only use a short aggregated public key. diff --git a/content/common/cryptography/signature-schemes.mdx b/content/common/cryptography/signature-schemes.mdx index a101dc6858e..8ffa4f11b0d 100644 --- a/content/common/cryptography/signature-schemes.mdx +++ b/content/common/cryptography/signature-schemes.mdx @@ -1,11 +1,12 @@ import { buttonVariants } from '@/components/ui/button'; import { cn } from '@/utils/cn'; +import GlossaryTerm from '@/components/ui/glossary-term' Signature schemes are cryptographic schemes, that allow us to sign some piece of data, and someone else can verify our signature. Think of signature schemes as a very modern version of signing for example a contract, which does not rely on your unique hand movement, but on math. There are many different signature schemes. They vary in efficiency and security. The main goal of signature schemes is to ensure the authenticity, non-repudiation, and integrity of digital messages. -- **Authenticity:** Authenticity ensures that the signature authenticates the origin of the message and verifies that it was indeed created by the claimed sender. A valid signature on a message proves that the signer owns the private key associated with the public key used for the signature. +- **Authenticity:** Authenticity ensures that the signature authenticates the origin of the message and verifies that it was indeed created by the claimed sender. A valid signature on a message proves that the signer owns the Private Key associated with the Public Key used for the signature. - **Non-Repudiation:** Non-repudiation ensures that the signer cannot deny their involvement in the transaction. In other words, they cannot later claim that they didn't authorize or sign the message. Therefore, signing the message is a binding commitment. diff --git a/content/common/evm-precompiles/precompiles.mdx b/content/common/evm-precompiles/precompiles.mdx index f7df77c7c50..6e1383deac2 100644 --- a/content/common/evm-precompiles/precompiles.mdx +++ b/content/common/evm-precompiles/precompiles.mdx @@ -1,11 +1,13 @@ +import GlossaryTerm from '@/components/ui/glossary-term' + Precompiled contracts are a way to execute code written in the low-level coding language Go from the EVM. Go is much faster and more efficient than Solidity. If you are familiar with Python programming, you might be familiar with a similar concept. Many Python functions and libraries are written in the programming language C, since it is much more efficient than Python. Python developers can import these precompile modules and call these functions just as if they were written in Python. The only difference is that the modules are faster and more efficient. ![Precompiles](/common-images/evm-precompiles/precompiles.png) -Precompiles can be called from a Solidity smart contract in the same way, as if they were another contract written in Solidity. The EVM keeps a list of addresses reserved and mapped to the precompiles. When a smart contract calls a function of a contract with an address on that list, the EVM executes the precompile written in Go instead of the smart contract. -For instance, if we mapped the address 0x030...01 to the SHA256 precompile that hashes its input using the SHA256 Hash Function, we can call the Precompile like this: +Precompiles can be called from a Solidity Smart Contract in the same way, as if they were another contract written in Solidity. The EVM keeps a list of addresses reserved and mapped to the precompiles. When a smart contract calls a function of a contract with an address on that list, the EVM executes the precompile written in Go instead of the smart contract. +For instance, if we mapped the address 0x030...01 to the SHA256 precompile that Hashes its input using the SHA256 Hash Function, we can call the Precompile like this: ```solidity // SPDX-License-Identifier: MIT diff --git a/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx b/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx index b5c9387f61f..a2dc4acc24f 100644 --- a/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx +++ b/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx @@ -1,14 +1,15 @@ import YouTube from '@/components/content-design/youtube'; +import GlossaryTerm from '@/components/ui/glossary-term' -The Etna upgrade will be the largest network upgrade of Avalanche to date. This upgrade will introduce a new concept called Layer 1 blockchains (L1s), which will replace the current Subnet model. In this article we will discuss the current limitations of Subnets, and how the changes suggested in [ACP-77](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md) will address these limitations in the Etna Upgrade. +The Etna Upgrade will be the largest network upgrade of Avalanche to date. This upgrade will introduce a new concept called Layer 1 blockchains (L1s), which will replace the current Subnet model. In this article we will discuss the current limitations of Subnets, and how the changes suggested in ACP-77 ([ACP-77 Proposal](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md)) will address these limitations in the Etna Upgrade. ## How Subnets Work Today -The Avalanche network has a large set of validators who all participate in running and validating the Primary Network. The Primary Network consists of the C-Chain, P-Chain, and X-Chain, and is where most of the transactions on Avalanche are processed. +The Avalanche network has a large set of Validators who all participate in running and validating the Primary Network. The Primary Network consists of the Contract Chain, Platform Chain, and Exchange Chain, and is where most of the transactions on Avalanche are processed. -A blockchain has a limited capacity for computation and data storage. Therefore, the transactions it can process in a given time frame are limited. We can use the analogy of a highway to visualize this concept. A highway can only handle a certain number of cars at a time. If too many cars try to enter the highway at once, traffic congestion will occur and they have to wait to enter the highway. +A Blockchain has a limited capacity for computation and data storage. Therefore, the transactions it can process in a given time frame are limited. We can use the analogy of a highway to visualize this concept. A highway can only handle a certain number of cars at a time. If too many cars try to enter the highway at once, traffic congestion will occur and they have to wait to enter the highway. ![Subnets](/common-images/multi-chain-architecture/etna-upgrade/subnets.png) @@ -70,6 +71,6 @@ After the Etna upgrade validator sets are distinct. Therefore, congestion and fa ## Conclusion -The Etna upgrade is the largest network upgrade of Avalanche to date. This change will enable more developers to get inexpensive block space for their applications, provide better fault isolation, while also enabling institutions to launch their own L1s with better compliance. +The Etna Upgrade is the largest network upgrade of Avalanche to date. This change will enable more developers to get inexpensive block space for their applications, provide better fault isolation, while also enabling institutions to launch their own L1s with better compliance. You can learn more in depth about ACP-77 by reading the [ACP-77 Proposal](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md). diff --git a/content/common/multi-chain-architecture/transaction-fees.mdx b/content/common/multi-chain-architecture/transaction-fees.mdx index 07e49c93660..b1d9df6bb4d 100644 --- a/content/common/multi-chain-architecture/transaction-fees.mdx +++ b/content/common/multi-chain-architecture/transaction-fees.mdx @@ -1,8 +1,10 @@ -NFT collectors, DeFi traders, and blockchain gamers have independently spent significant sums to execute their transactions. These unrelated activities converge on the blockchain, competing for the finite capacity of the next blockspace. In an effort to avoid delays or being outpaced by others, participants can be compelled to pay substantial fees to secure prompt transaction processing. +import GlossaryTerm from '@/components/ui/glossary-term' -But why are there transaction fees (also commonly known as gas fees) at all? Let's recap the reason for fees and how they work. +NFT collectors, Decentralized Finance traders, and Blockchain gamers have independently spent significant sums to execute their transactions. These unrelated activities converge on the blockchain, competing for the finite capacity of the next blockspace. In an effort to avoid delays or being outpaced by others, participants can be compelled to pay substantial fees to secure prompt transaction processing. -In the Ethereum Virtual Machine (EVM), transaction fees play a crucial role in regulating access to the limited processing resources within the blockchain network. The blockchain has a limit of how much computation it can process in a given time frame. Imagine the Ethereum network as a highway with lanes representing block space. Each transaction is like a vehicle that needs space on these lanes. +But why are there transaction fees (also commonly known as Gas fees) at all? Let's recap the reason for fees and how they work. + +In the Etehereum Virtual Machine, transaction fees play a crucial role in regulating access to the limited processing resources within the blockchain network. The blockchain has a limit of how much computation it can process in a given time frame. Imagine the Ethereum network as a highway with lanes representing block space. Each transaction is like a vehicle that needs space on these lanes. ![](/course-images/multi-chain-architecture/transaction-fees/low-demand.png) diff --git a/content/common/primary-network/p-chain.mdx b/content/common/primary-network/p-chain.mdx index b5ec50550f6..b4e5211e4fe 100644 --- a/content/common/primary-network/p-chain.mdx +++ b/content/common/primary-network/p-chain.mdx @@ -1,4 +1,6 @@ -In the Avalanche Network, the P-Chain of the Primary Network is responsible for all validator and Avalanche L1-level operations. The P-Chain supports the creation of new blockchains and Avalanche L1s, the addition of validators to Avalanche L1s, staking operations, and other platform-level operations. +import GlossaryTerm from '@/components/ui/glossary-term' + +In the Avalanche Network, the Platform Chain of the Primary Network is responsible for all Validator and Avalanche L1-level operations. The P-Chain supports the creation of new blockchains and Avalanche L1s, the addition of validators to Avalanche L1s, Staking operations, and other platform-level operations. ![P-Chain](/common-images/primary-network/p-chain.png) From c50afd7be3b112d76db5e564c38b77e015df42a4 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:48:14 +0200 Subject: [PATCH 09/27] update the academy icm with glossaryterms --- .../01-interopability-between-blockchains.mdx | 9 +++++---- .../03-multi-chain-networks.mdx | 5 +++-- .../01-introduction.mdx | 8 +++++--- content/academy/interchain-messaging/index.mdx | 18 ++++++++++-------- 4 files changed, 23 insertions(+), 17 deletions(-) diff --git a/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx b/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx index 49460440cf5..872950c3749 100644 --- a/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx +++ b/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx @@ -5,16 +5,17 @@ updated: 2024-05-31 authors: [martineckardt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' -Interoperability between blockchains refers to the ability of different blockchain networks to communicate and interact with one another in a seamless and coordinated manner. It allows these separate blockchain systems to share data, assets, or functionalities, enabling them to work together as if they were part of a single unified network. +Interoperability between Blockchains refers to the ability of different blockchain networks to communicate and interact with one another in a seamless and coordinated manner. It allows these separate blockchain systems to share data, assets, or functionalities, enabling them to work together as if they were part of a single unified network. These interactions can take many forms, including: -- Asset Bridging (Tokens, NFTs, etc.) -- DAO Voting across Chains -- Cross-Chain Liquidity Pools +- Asset Bridging (Tokens, Non-Fungible Tokens, etc.) +- Decentralized Autonomous Organization Voting across Chains +- Cross-Chain Liquidity Pools As you will see soon, these different interactions are based on the same fundamentals of blockchains exchanging messages. diff --git a/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx b/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx index 02fd8d2e492..6e9c7c5a148 100644 --- a/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx +++ b/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx @@ -5,12 +5,13 @@ updated: 2024-05-31 authors: [martineckardt] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' ![](/common-images/multi-chain-architecture/subnets.png) -Avalanche is a multi-chain network, meaning the network has multiple chains being validated in parallel, while other networks, such as Bitcoin and Ethereum only have single chain. +Avalanche is a multi-chain network, meaning the network has multiple chains being validated in parallel, while other networks, such as Bitcoin and Ethereum only have single chain. -This feature provides greater scalability, independence, and customizability. Each blockchain is optimized for specialized use cases, boosting the network's overall performance. +This feature provides greater scalability, independence, and customizability. Each Blockchain is optimized for specialized use cases, boosting the network's overall performance. ## Transations per Second (TPS) and Time to Finality (TTF) diff --git a/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx b/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx index bdb76d1c804..833239b1e5e 100644 --- a/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx +++ b/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx @@ -6,14 +6,16 @@ authors: [0xstt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + As decentralized applications (dApps) expand across multiple blockchains, some Layer 1 (L1) networks lack direct support from essential services like **Chainlink VRF (Verifiable Random Functions)**. This presents a significant challenge for developers who rely on verifiable randomness for use cases such as gaming, lotteries, NFT minting, and other decentralized functions that require unbiased, unpredictable random numbers. -The challenge arises because not every L1 network has integrated with Chainlink, meaning developers on those chains are left without native access to VRF services. Without verifiable randomness, critical aspects of dApps, such as fairness and security, can be compromised. +The challenge arises because not every Avalanche L1 network has integrated with Chainlink, meaning developers on those chains are left without native access to VRF services. Without verifiable randomness, critical aspects of dApps, such as fairness and security, can be compromised. ### Why ICM is Necessary -To address this gap, **Interchain Messaging (ICM)** provides a solution by allowing L1 networks that don’t have direct Chainlink support to still access these services. Through ICM, any blockchain can request VRF outputs from a Chainlink-supported network (e.g., Fuji) and receive the results securely on their own L1. +To address this gap, **Interchain Messaging (ICM)** provides a solution by allowing L1 networks that don't have direct Chainlink support to still access these services. Through Interchain Messaging, any blockchain can request VRF outputs from a Chainlink-supported network (e.g., Fuji) and receive the results securely on their own L1. This cross-chain solution unlocks the ability to use Chainlink VRF on unsupported networks, bypassing the need for native integration and ensuring that dApp developers can continue building secure and fair decentralized applications. -In the following sections, we will explore how to use ICM to access Chainlink VRF services across different chains by deploying two key smart contracts: one on the Chainlink-supported network and another on the target L1. \ No newline at end of file +In the following sections, we will explore how to use Interchain Messaging to access Chainlink VRF services across different chains by deploying two key smart contracts: one on the Chainlink-supported network and another on the target L1. \ No newline at end of file diff --git a/content/academy/interchain-messaging/index.mdx b/content/academy/interchain-messaging/index.mdx index 9dd587278cf..e543a8ca920 100644 --- a/content/academy/interchain-messaging/index.mdx +++ b/content/academy/interchain-messaging/index.mdx @@ -6,13 +6,15 @@ authors: [martineckardt] icon: Smile --- -In this course, you will learn how to build cross-L1 Solidity dApps with Interchain Messaging and Avalanche Warp Messaging. +import GlossaryTerm from '@/components/ui/glossary-term' + +In this course, you will learn how to build cross-L1 Solidity dApps with Interchain Messaging and Avalanche Warp Messaging. ## Why Take This Course? -A significant innovation in blockchain is the development of multi-chain systems, like Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. At the core of these multi-chain systems is the ability to run multiple blockchains that communicate. Each chain's VM is optimized for specialized use cases, thereby boosting the network's overall performance. +A significant innovation in blockchain is the development of multi-chain systems, like Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. At the core of these multi-chain systems is the ability to run multiple blockchains that communicate. Each chain's VM is optimized for specialized use cases, thereby boosting the network's overall performance. -Cross-chain communication is a crucial building block of multi-chain systems. Utilizing Interchain Messaging and Avalanche Warp Messaging is an incredible easy way to build cross-L1 dApps, since developers can build on top an extensive and audited development framework. +Cross-chain communication is a crucial building block of multi-chain systems. Utilizing Interchain Messaging and Avalanche Warp Messaging is an incredible easy way to build cross-L1 dApps, since developers can build on top an extensive and audited development framework. ## Course Content @@ -26,7 +28,7 @@ In the first section, we cover some basic concepts of interoperability in multi- ### Avalanche Interchain Messaging -In this section, we learn what Avalanche Interchain Messaging is and what is abstracted away from the general dApp developer. You will also build your first cross-L1 dApps. +In this section, we learn what Avalanche Interchain Messaging is and what is abstracted away from the general dApp developer. You will also build your first cross-L1 dApps. ### Securing Cross-Chain Communication @@ -42,8 +44,8 @@ Avalanche blockchains can natively interoperate between one another using AWM. Y This course is meant for people with a solid understanding of the basic concepts of Avalanche. You should be familiar with these concepts: -- **Virtual Machines:** What they are and what VM customization means -- **Avalanche L1s & Blockchains:** What the difference between a VM, Blockchain, and an Avalanche L1 is +- **Virtual Machines:** What they are and what VM customization means +- **Avalanche L1s & Blockchains:** What the difference between a VM, Blockchain, and an Avalanche L1 is If any of this is unclear, we strongly recommend taking the Avalanche Fundamentals and Multi-Chain Architecture courses first. @@ -62,6 +64,6 @@ By the end of this course, students will: - Understand the challenges of cross-chain communication - Know what separates Avalanche Warp Messaging from other cross-chain communication protocols - Understand the differences between Avalanche Warp Messaging and Teleporter -- Apply their knowledge by building cross-Avalanche L1 dApps, such as asset bridges +- Apply their knowledge by building cross-Avalanche L1 dApps, such as asset bridges -Overall, this course aims to provide an advanced understanding of Teleporter. By completing this course, students will be better prepared to build advanced cross-Avalanche L1 blockchain applications. \ No newline at end of file +Overall, this course aims to provide an advanced understanding of Teleporter. By completing this course, students will be better prepared to build advanced cross-Avalanche L1 blockchain applications. \ No newline at end of file From 4ee4a5e84de06a05d4199ea2bea45f94ab51ba36 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:48:38 +0200 Subject: [PATCH 10/27] update the academy ictt with glossaryterms --- .../03-tokens/01-tokens.mdx | 8 +++++--- .../03-tokens/02-native-tokens.mdx | 10 ++++++---- .../03-tokens/07-erc-20-tokens.mdx | 10 ++++++---- .../01-erc-20-to-erc-20-bridge.mdx | 9 +++++---- .../04-deploy-remote.mdx | 11 ++++++----- .../interchain-token-transfer/index.mdx | 18 ++++++++++-------- 6 files changed, 38 insertions(+), 28 deletions(-) diff --git a/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx index 38002f14648..f059f58f1be 100644 --- a/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx +++ b/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx @@ -6,10 +6,12 @@ authors: [martineckardt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + ## What You Will Learn In this section, you will go through the following topics: -- **What is a token**: Learn how tokens serve to represent ownership. -- **Types of tokens**: Learn about ERC20 tokens, Native tokens and Wrapped tokens. -- **Transfers**: Learn differences on transfering the different types of tokens between accounts or with smart contracts. +- **What is a token**: Learn how tokens serve to represent ownership. +- **Types of tokens**: Learn about ERC20 tokens, Native tokens and Wrapped tokens. +- **Transfers**: Learn differences on transfering the different types of tokens between accounts or with Smart Contracts. diff --git a/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx index 474e4e9c448..5c4484306ac 100644 --- a/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx +++ b/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx @@ -6,12 +6,14 @@ authors: [ashucoder9] icon: BookOpen --- -A native token in a blockchain running the Ethereum Virtual Machine (EVM) refers to the primary digital currency or cryptocurrency native to the EVM blockchain. Every EVM layer 1 chain has it's own native token: +import GlossaryTerm from '@/components/ui/glossary-term' -- Ethereum: ETH -- Avalanche C-Chain: AVAX +A native token in a blockchain running the EVM refers to the primary digital currency or cryptocurrency native to the EVM blockchain. Every EVM layer 1 chain has it's own native token: + +- Ethereum: ETH +- Avalanche C-Chain: AVAX - Dexalot: ALOT - many more... -The native token serves as both a means of value transfer within the EVM network and as the gas token for executing transfers or smart contracts. Therefore, native tokens play a crucial role in the EVM chain by enabling participants to interact with and utilize the platform's decentralized features, serving as the foundational unit of value. +The native token serves as both a means of value transfer within the EVM network and as the gas token for executing transfers or smart contracts. Therefore, native tokens play a crucial role in the EVM chain by enabling participants to interact with and utilize the platform's decentralized features, serving as the foundational unit of value. \ No newline at end of file diff --git a/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx index 5c8d9fa4ba2..6079a4eb4c2 100644 --- a/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx +++ b/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx @@ -6,9 +6,11 @@ authors: [ashucoder9] icon: BookOpen --- -There is only a single native token to a chain. However, to allow to represent a wide range of assets on EVM-chains, the ERC-20 token standard was developed. "ERC" stands for Ethereum Request for Comment, and "20" is the proposal identifier. +import GlossaryTerm from '@/components/ui/glossary-term' -ERC-20 tokens are fungible, meaning each token is identical and can be exchanged on a one-to-one basis. These tokens are typically created and managed through smart contracts that adhere to the ERC-20 standard, which defines a set of rules and functions that ensure interoperability between different tokens and decentralized applications (DApps). +There is only a single native token to a chain. However, to allow to represent a wide range of assets on EVM-chains, the ERC-20 token standard was developed. "ERC" stands for Ethereum Request for Comment, and "20" is the proposal identifier. + +ERC-20 tokens are fungible, meaning each token is identical and can be exchanged on a one-to-one basis. These tokens are typically created and managed through Smart Contracts that adhere to the ERC-20 standard, which defines a set of rules and functions that ensure interoperability between different tokens and decentralized applications (DApps). At the base of an ERC-20 token smart contract, there is a simple mapping of addresses to numbers, which represent the amount of tokens an address holds (balance). @@ -22,7 +24,7 @@ abstract contract ERC20 is Context, IERC20, IERC20Metadata, IERC20Errors { ``` These addresses may belong to EOA or contract accounts. Both of these can hold and transfer ERC-20 tokens. -ERC-20 tokens can represent various assets, from digital currencies to tokenized assets, and they play a crucial role in the crypto ecosystem by enabling the creation of decentralized applications with diverse functionalities, such as token sales, decentralized finance (DeFi) protocols, and more. +ERC-20 tokens can represent various assets, from digital currencies to tokenized assets, and they play a crucial role in the crypto ecosystem by enabling the creation of decentralized applications with diverse functionalities, such as token sales, decentralized finance (DeFi) protocols, and more. ## Interface @@ -54,7 +56,7 @@ Click [here](https://eips.ethereum.org/EIPS/eip-20) to review the ERC20 standard ## Transfer Tokens -Transferring ERC-20 tokens between accounts involves calling the 'transfer' function, specifying the recipient’s address and the amount to transfer. +Transferring ERC-20 tokens between accounts involves calling the 'transfer' function, specifying the recipient's address and the amount to transfer. To facilitate more complex interactions, such as those involving smart contracts, the ERC-20 standard includes the `approve()` and `transferFrom()` functions. We will check how to implement those so smart contracts can use funds according to its code. diff --git a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx index 0ef807f796b..988afe5386e 100644 --- a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx +++ b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx @@ -8,12 +8,13 @@ icon: Book import { Step, Steps } from 'fumadocs-ui/components/steps'; import Link from 'next/link'; import { buttonVariants } from '@/components/ui/button.tsx' +import GlossaryTerm from '@/components/ui/glossary-term' ## Transfer an ERC-20 Token → Avalanche L1 as an ERC-20 Token -This chapter will show you how to send an ERC-20 Token on C-Chain to an Avalanche L1 using Interchain Messaging and Foundry. This demo is conducted on a local network, but can be applied to Fuji Testnet and Avalanche Mainnet directly. +This chapter will show you how to send an ERC-20 Token on Contract Chain to an Avalanche L1 using Interchain Messaging and Foundry. This demo is conducted on a local network, but can be applied to Fuji Testnet and Avalanche Mainnet directly. -**All Avalanche Interchain Token Transfer contracts and interfaces implemented in this chapter implementation are maintained in the [`avalanche-interchain-token-transfer`](https://github.com/ava-labs/avalanche-interchain-token-transfer/tree/main/contracts/src) repository.** +**All Avalanche Interchain Token Transfer contracts and interfaces implemented in this chapter implementation are maintained in the [`avalanche-interchain-token-transfer`](https://github.com/ava-labs/avalanche-interchain-token-transfer/tree/main/contracts/src) repository.** Deep dives on each template interface can be found [here](https://github.com/ava-labs/avalanche-interchain-token-transfer/blob/main/contracts/README.md). @@ -21,8 +22,8 @@ _Disclaimer: The avalanche-interchain-token-transfer contracts used in this tuto ## What we will do -1. Deploy an ERC-20 Contract on C-Chain -2. Deploy the Interchain Token Transferer Contracts on C-Chain and Avalanche L1 +1. Deploy an ERC-20 Contract on Contract Chain +2. Deploy the Interchain Token Transfer Contracts on Contract Chain and Avalanche L1 3. Register Remote Token contract with the Home Transferer contract 4. Add Collateral and Start Sending Tokens diff --git a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx index 9d5a096593f..3515b0ecaf4 100644 --- a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx +++ b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx @@ -7,12 +7,13 @@ icon: Terminal --- import { Step, Steps } from 'fumadocs-ui/components/steps'; +import GlossaryTerm from '@/components/ui/glossary-term' -To ensure the wrapped token is bridged into the destination chain (in this case, C-Chain) you'll need to deploy a _remote_ contract that implements the `IERC20Bridge` interface, as well as inheriting the properties of `TeleporterTokenRemote`. In order for the bridged tokens to have all the normal functionality of a locally deployed ERC20 token, this remote contract must also inherit the properties of a standard `ERC20` contract. +To ensure the wrapped token is bridged into the destination chain (in this case, C-Chain) you'll need to deploy a _remote_ contract that implements the `IERC20Bridge` interface, as well as inheriting the properties of `TeleporterTokenRemote`. In order for the bridged tokens to have all the normal functionality of a locally deployed ERC20 token, this remote contract must also inherit the properties of a standard `ERC20` contract. -### Get the `Teleporter Registry` address of your Avalanche L1 +### Get the `Teleporter Registry` address of your Avalanche L1 ```bash avalanche blockchain describe myblockchain @@ -40,7 +41,7 @@ export TELEPORTER_REGISTRY_L1=0x82EeEf8e31D4Bf95916219D7949D66c468Ac0681 -### Get the Source Blockchain ID +### Get the Source Blockchain ID Get the `Source Blockchain ID` in hexidecimal format from the output of `avalanche blockchain describe myblockchain` above, which in this example is the BlockchainID of your Avalanche L1: @@ -77,11 +78,11 @@ export SOURCE_BLOCKCHAIN_ID_HEX= -### Deploy the Remote Contract +### Deploy the Remote Smart Contract Using the [`forge create`](https://book.getfoundry.sh/reference/forge/forge-create) command, we will deploy the `ERC20TokenRemote.sol` contract, passing in the following constructor arguments: -- Interchain Messaging Registry Address **(for C-Chain)** +- Interchain Messaging Registry Address **(for C-Chain)** - Interchain Messaging Manager (our funded address) - Source Blockchain ID (hexidecimal representation of our Avalanche L1's Blockchain ID) - Token Home Address (address of NativeTokenHome.sol deployed on Avalanche L1 in the last step) diff --git a/content/academy/interchain-token-transfer/index.mdx b/content/academy/interchain-token-transfer/index.mdx index dd407036198..5b5ebab6214 100644 --- a/content/academy/interchain-token-transfer/index.mdx +++ b/content/academy/interchain-token-transfer/index.mdx @@ -6,15 +6,17 @@ authors: [ashucoder9] icon: Smile --- -In this course, you will learn how to transfer assets across multiple Avalanche blockchains with Avalanche Interchain Token Transfer ICTT. +import GlossaryTerm from '@/components/ui/glossary-term' + +In this course, you will learn how to transfer assets across multiple Avalanche blockchains with Avalanche Interchain Token Transfer ICTT. ## Why Take This Course? -A significant innovation in blockchain is the development of multi-chain systems, like Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. At the core of these multi-chain systems is the ability to run multiple blockchains that communicate. Each chain's VM is optimized for specialized use cases, thereby boosting the network's overall performance. +A significant innovation in blockchain is the development of multi-chain systems, like Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. At the core of these multi-chain systems is the ability to run multiple blockchains that communicate. Each chain's VM is optimized for specialized use cases, thereby boosting the network's overall performance. -Cross-chain communication is a crucial building block of multi-chain systems. Utilizing Avalanche Interchain Messaging and Interchain Token Transfer is an incredibly easy way to build cross-Avalanche L1 dApps, since developers can build on top of an extensive, audited development framework. +Cross-chain communication is a crucial building block of multi-chain systems. Utilizing Avalanche Interchain Messaging and Interchain Token Transfer is an incredibly easy way to build cross-Avalanche L1 dApps, since developers can build on top of an extensive, audited development framework. -Transfering tokens between multiple chains is a common use case in multi-chain systems. This course will help you understand how to transfer assets between multiple Avalanche blockchains using the Avalanche Interchain Token Transfer protocol. +Transfering tokens between multiple chains is a common use case in multi-chain systems. This course will help you understand how to transfer assets between multiple Avalanche blockchains using the Avalanche Interchain Token Transfer protocol. ## Course Content @@ -24,7 +26,7 @@ In this section, you will learn how to set up your development environment with ### Tokens -In this section, you will learn about the different types of tokens that can be transferred between Avalanche blockchains. We will cover ERC-20 and native tokens and interact with them on chain. Furthermore, you will learn what wrapped native tokens are and how they can be used to transfer assets between chains. +In this section, you will learn about the different types of tokens that can be transferred between Avalanche blockchains. We will cover ERC-20 and native tokens and interact with them on chain. Furthermore, you will learn what wrapped native tokens are and how they can be used to transfer assets between chains. ### Token Bridging @@ -36,7 +38,7 @@ In this chapter we will look at the design of Avalanche Interchain Token Transfe ### ERC-20 to ERC-20 bridge -You will learn how to set up a bridge to bridge an ERC-20 token from one L1 blockchain to another. +You will learn how to set up a bridge to bridge an ERC-20 token from one L1 blockchain to another. ### Token on multiple chains @@ -48,7 +50,7 @@ In this chapter you will learn how to bridge a native token as an ERC-20 token t ### Send and Call -In this chapter you will learn how to call smart contracts with the tokens after sending them to another chain. +In this chapter you will learn how to call smart contracts with the tokens after sending them to another chain. ### Cross-Chain Token Swaps @@ -61,7 +63,7 @@ In this chapter you will learn how to swap tokens on another chain. This course is intended for people with knowledge about Cross-Chain communication protocols, and a solid understanding of the basic concepts of Avalanche. You should be familiar with these concepts: 1. Avalanche Architecture: Be familiar with Avalanche blockchains. -2. Interchain Messaging: Know how to communicate between two Avalanche blockchains with ICM. +2. Interchain Messaging: Know how to communicate between two Avalanche blockchains with ICM. If some of this is not clear, we strongly recommend taking the Avalanche Fundamentals, Multi-Chain Architecture, and Interchain Messaging courses first. From 019530ab9e037a8cb481657badafdca9b151b3bb Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:49:17 +0200 Subject: [PATCH 11/27] update the guides with glossaryterms --- content/guides/etna-changes.mdx | 9 +++--- content/guides/l1-validator-fee.mdx | 5 ++-- content/guides/subnet-vs-l1-validators.mdx | 5 ++-- content/guides/use-privy-on-l1.mdx | 8 +++-- content/guides/what-is-a-blockchain.mdx | 34 ++++++++++++---------- 5 files changed, 34 insertions(+), 27 deletions(-) diff --git a/content/guides/etna-changes.mdx b/content/guides/etna-changes.mdx index eda400baf65..a0505f5fb89 100644 --- a/content/guides/etna-changes.mdx +++ b/content/guides/etna-changes.mdx @@ -6,14 +6,15 @@ authors: [meagfitzgerald] topics: [Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1] comments: true --- +import GlossaryTerm from '@/components/ui/glossary-term' -This guide outlines the operational impact on existing network participants expected from the activation of the AvalancheGo "Etna" upgrade. +This guide outlines the operational impact on existing network participants expected from the activation of the AvalancheGo "Etna Upgrade" upgrade. ## Vocabulary, New and Old - **L1**: An Avalanche Layer 1 Network. An L1 is a sovereign network that has its own dynamic set of validators, rules for network participation, and defines its own validator rewards incentives. - **L1-validator**: A validator that only validates an Avalanche layer 1 blockchain. These validators are not required to stake 2000 AVAX, or validate the Avalanche Primary Network. They instead pay a continuous fee in order to participate in L1 validation. -- **ACP-77**: The Avalanche Community Proposal that outlines a new framework for creating low-cost, independent blockchains that can _easily_ interoperate with each other. You can read the full proposal [here](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md). +- **ACP-77**: The Avalanche Community Proposal that outlines a new framework for creating low-cost, independent blockchains that can _easily_ interoperate with each other. You can read the full proposal [here](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md). - **The Primary Network**: The Avalanche X,P, and C-Chains, a.k.a. the 3 primary blockchains that most validators currently sync on Avalanche Mainnet. ## What is Changing? @@ -27,7 +28,7 @@ Subnets have always operated this way, scaling Avalanche's network _horizontally ### For Validators -L1 validators will no longer be required to sync the Primary Network’s X or C-Chain, drastically reducing the cost of operating a validator. +L1 validators will no longer be required to sync the Primary Network's X or C-Chain, drastically reducing the cost of operating a validator. L1 validators will no longer be required to stake 2000 AVAX. Instead they will pay a substantially cheaper continuous fee calculated based on the number of L1 validators. The AVAX-denominated fee is a nominal amount per second and provides significant cost-savings for L1 validators. @@ -46,7 +47,7 @@ If the L1 is permissionless, the validator earns staking rewards by staking the ### For Existing L1s -Existing Avalanche Subnets _that wish_ to remove the 2000 AVAX per validator requirement will need to convert their Subnet’s control from a _P-Chain Owner Key_ to a _ValidatorManager_ smart contract via the workflow outlined in ACP-77. +Existing Avalanche Subnets _that wish_ to remove the 2000 AVAX per validator requirement will need to convert their Subnet's control from a _P-Chain Owner Key_ to a _ValidatorManager_ smart contract via the workflow outlined in ACP-77. - A detailed guide on how to convert existing L1s will be released prior to Testnet activation. diff --git a/content/guides/l1-validator-fee.mdx b/content/guides/l1-validator-fee.mdx index 5f1a0f2e467..be4b12537bc 100644 --- a/content/guides/l1-validator-fee.mdx +++ b/content/guides/l1-validator-fee.mdx @@ -6,10 +6,11 @@ authors: [meagfitzgerald] topics: [ Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1, L1 Validators, Continuous L1 Validation Fee] comments: true --- +import GlossaryTerm from '@/components/ui/glossary-term' ## What are L1 Validators? -Introduced with ACP-77, [Avalanche L1 Validators](https://build.avax.network/guides/subnet-vs-l1-validators) enable the creation of sovereign L1 +Introduced with ACP-77, [Avalanche L1 Validators](https://build.avax.network/guides/subnet-vs-l1-validators) enable the creation of sovereign L1 networks with minimal dependency on the Avalanche Primary Network. Unlike Subnet validators, L1 validators do not stake AVAX, but instead pay a continuous dynamic fee called the L1 Validator Fee. @@ -29,7 +30,7 @@ disk, and any messages from them will be invalid until they are revived. Inactiv AvalancheGo calculates the accrued fees for a block based on the formula: fee rate (in nAVAX/sec) \* duration since the prior block (in seconds) for every block. For each L1 validator, AvalancheGo tracks a value called the [`endAccumulatedFee`](https://github.com/ava-labs/avalanchego/blob/ab4619873028fd975dfa6e89e53e555dd53e0cdb/vms/platformvm/state/l1_validator.go#L116-L124), which represents the total fees that will accumulate -in the future at the current rate. Once this value is reached, the validator will be marked as “inactive” due to the fact that its balance will not +in the future at the current rate. Once this value is reached, the validator will be marked as "inactive" due to the fact that its balance will not cover the fees accrued until this final block. When a validator registers with `RegisterL1ValidatorTx`, the balance of AVAX is allocated to that validator, and is continuously charged by the diff --git a/content/guides/subnet-vs-l1-validators.mdx b/content/guides/subnet-vs-l1-validators.mdx index 2304d0023d5..a1b88da2b9d 100644 --- a/content/guides/subnet-vs-l1-validators.mdx +++ b/content/guides/subnet-vs-l1-validators.mdx @@ -6,10 +6,11 @@ authors: [meagfitzgerald] topics: [Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1, L1 Validators, Subnet Validators] comments: true --- +import GlossaryTerm from '@/components/ui/glossary-term' -The Etna Upgrade introduced L1s to the Avalanche network, providing an enhanced sovereign network design to the original Subnet model. +The Etna Upgrade introduced L1s to the Avalanche network, providing an enhanced sovereign network design to the original Subnet model. -**L1 Validators**, introduced with ACP-77, represent a departure from this model, enabling the creation of sovereign L1 networks with minimal dependency on the Primary Network. +**L1 Validators**, introduced with ACP-77, represent a departure from this model, enabling the creation of sovereign L1 networks with minimal dependency on the Primary Network. Unlike Subnet validators, L1 validators do not stake AVAX but instead pay a dynamic monthly fee, initially set at approximately 1.3 AVAX. They are exempt from validating the Primary Network, reducing their resource requirements and making L1 validation more accessible. This approach fosters economic inclusivity and sovereignty, allowing developers to define custom validation logic via smart contracts and operate independent networks without staking the Primary Network. diff --git a/content/guides/use-privy-on-l1.mdx b/content/guides/use-privy-on-l1.mdx index 2f441eb2972..e411c8393e2 100644 --- a/content/guides/use-privy-on-l1.mdx +++ b/content/guides/use-privy-on-l1.mdx @@ -6,6 +6,8 @@ authors: [satatocom] topics: [Avalanche L1, Avalanche Starter Kit, Magic Link, Social Login, Embedded Wallets] --- +import GlossaryTerm from '@/components/ui/glossary-term' + In this guide, you will learn how to use Privy to easily onboard your users and create transactions without the need for any Web3 wallet. ## What is Privy? @@ -56,7 +58,7 @@ npm i ethers@latest ### Define Your Avalanche L1 -In this guide, we are using the `Echo L1` as an example Avalanche L1. However, you can use any Avalanche L1 that has a public RPC URL. If the L1 has an explorer page, you can see better what is happening, but it is not required. +In this guide, we are using the `Echo L1` as an example Avalanche L1. However, you can use any Avalanche L1 that has a public RPC URL. If the L1 has an explorer page, you can see better what is happening, but it is not required. ```typescript export const echo = defineChain({ @@ -163,7 +165,7 @@ As you can see, Privy has generated an embedded wallet for our user. We’ve dis {balance} ECH ``` -We’ve used the user object of Privy to retrieve the user ID and wallet address. To fetch the user’s balance, we need to create an HTTP client for our Avalanche L1, which we’ve already defined earlier. +We've used the user object of Privy to retrieve the user ID and wallet address. To fetch the user's balance, we need to create an HTTP client for our Avalanche L1, which we've already defined earlier. ```typescript const client = createPublicClient({ @@ -186,7 +188,7 @@ const { logout } = useLogout(); ### Fund the New Wallet Using the Faucet -We’ve funded the new wallet that was generated for our user with some ECH tokens from the [Echo AWM Testnet Faucet](https://test.core.app/tools/testnet-faucet/?subnet=echo&token=echo). +We've funded the new wallet that was generated for our user with some ECH tokens from the [Echo AWM Testnet Faucet](https://test.core.app/tools/testnet-faucet/?subnet=echo&token=echo). ![](/guide-images/use-privy-on-l1/4.png) diff --git a/content/guides/what-is-a-blockchain.mdx b/content/guides/what-is-a-blockchain.mdx index f23e7e38a24..2cf123c31cc 100644 --- a/content/guides/what-is-a-blockchain.mdx +++ b/content/guides/what-is-a-blockchain.mdx @@ -6,6 +6,8 @@ authors: [martin_eckardt] topics: [Blockchain Basics] --- +import GlossaryTerm from '@/components/ui/glossary-term' + ## Introduction to Different Types of Computers Computers are integral to our daily lives, and they come in various forms, each designed to serve specific purposes. Here's a quick overview: @@ -16,38 +18,38 @@ Computers are integral to our daily lives, and they come in various forms, each All these computers are *centralized*. This means they are controlled by a single entity or organization. For example, your PC is controlled by you, cloud computers are managed by cloud service providers, and mobile devices are typically controlled by their manufacturers and network providers. Centralization implies that these entities have the power to manage, restrict access to, or shut down these computers if needed. ## Introducing the Blockchain Computer -A **blockchain** is a new kind of computer with a unique and defining property: **decentralization**. Unlike traditional centralized computers controlled by a single entity, a blockchain operates without any central authority. This means no single entity can: +A **blockchain** is a new kind of computer with a unique and defining property: **decentralization**. Unlike traditional centralized computers controlled by a single entity, a blockchain operates without any central authority. This means no single entity can: - Turn it off - Restrict access to it - Interfere with the execution of the programs running on it -Furthermore, the computation is transparent. Anyone can see the programs running on the blockchain and verify their correctness. This transparency ensures that the blockchain operates fairly and securely. +Furthermore, the computation is transparent. Anyone can see the programs running on the blockchain and verify their correctness. This transparency ensures that the blockchain operates fairly and securely. ## How Decentralization Works -Decentralization in blockchain is achieved through a network of **validators**. These are independent entities that run the blockchain software, perform computations, and ensure the integrity of the blockchain. Here’s how it works: +Decentralization in blockchain is achieved through a network of **validators**. These are independent entities that run the blockchain software, perform computations, and ensure the integrity of the blockchain. Here's how it works: -1. **Computation Execution**: Each validator independently performs the same computation. For example, let's consider a simple computation: `5 + 3`. -2. **Consensus Process**: After performing the computation, validators share their results with each other. They then use a process called **consensus** to agree on the correct result. You can think of it as a election, where all validators vote on the correct answer. +1. **Computation Execution**: Each validator independently performs the same computation. For example, let's consider a simple computation: `5 + 3`. +2. **Consensus Process**: After performing the computation, validators share their results with each other. They then use a process called **consensus** to agree on the correct result. You can think of it as a election, where all validators vote on the correct answer. -The consensus process ensures that all validators reach an agreement on the correct result, given that the majority is honest. This agreement is crucial for maintaining the integrity and security of the blockchain. If a validator tries to cheat or provide an incorrect result, the other validators will detect the discrepancy, and the cheating validator will be penalized. +The consensus process ensures that all validators reach an agreement on the correct result, given that the majority is honest. This agreement is crucial for maintaining the integrity and security of the blockchain. If a validator tries to cheat or provide an incorrect result, the other validators will detect the discrepancy, and the cheating validator will be penalized. ## Efficiency of Blockchain Computation -While the decentralized nature of blockchain ensures security and integrity, it also makes it **inefficient** compared to traditional computers. Here’s why: +While the decentralized nature of blockchain ensures security and integrity, it also makes it **inefficient** compared to traditional computers. Here's why: -- **Redundant Computation**: Every validator must perform the same computation independently. -- **Consensus Overhead**: Validators need to communicate and agree on the results, which adds extra steps and time. +- **Redundant Computation**: Every validator must perform the same computation independently. +- **Consensus Overhead**: Validators need to communicate and agree on the results, which adds extra steps and time. -Due to the redundancy and additional processes, performing computations on a blockchain is much more expensive than on a PC or cloud computer. For instance, while a PC can perform a simple addition in a fraction of a second with minimal cost, a blockchain requires multiple validators to do the same computation and agree on the result, leading to higher computational costs and time. +Due to the redundancy and additional processes, performing computations on a blockchain is much more expensive than on a PC or cloud computer. For instance, while a PC can perform a simple addition in a fraction of a second with minimal cost, a blockchain requires multiple validators to do the same computation and agree on the result, leading to higher computational costs and time. -So, while it's decentralized nature offers significant advantages in terms of security and resistance to control, it also comes at the cost of efficiency and higher computation expenses. As we continue to develop and optimize blockchain technology, we aim to balance these trade-offs and explore its vast potential in various applications. +So, while it's decentralized nature offers significant advantages in terms of security and resistance to control, it also comes at the cost of efficiency and higher computation expenses. As we continue to develop and optimize blockchain technology, we aim to balance these trade-offs and explore its vast potential in various applications. ## Use Cases for Blockchain -Blockchain technology excels in use cases where decentralization, security, and transparency are paramount, making the trade-off for reduced efficiency worthwhile. +Blockchain technology excels in use cases where decentralization, security, and transparency are paramount, making the trade-off for reduced efficiency worthwhile. -- In *financial services*, blockchain enables secure, transparent, and tamper-proof transactions without the need for intermediaries like banks. -- *Supply chain management* benefits from blockchain by providing an immutable ledger that tracks the provenance and movement of goods, enhancing traceability and reducing fraud. -- *Voting systems* can leverage blockchain to ensure the integrity and transparency of the electoral process, making it resistant to tampering and fraud. +- In *financial services*, blockchain enables secure, transparent, and tamper-proof transactions without the need for intermediaries like banks. +- *Supply chain management* benefits from blockchain by providing an immutable ledger that tracks the provenance and movement of goods, enhancing traceability and reducing fraud. +- *Voting systems* can leverage blockchain to ensure the integrity and transparency of the electoral process, making it resistant to tampering and fraud. -However, for tasks that prioritize high efficiency and speed over decentralization, such as real-time data processing or complex computational tasks, traditional centralized systems are more suitable. In these cases, the overhead of consensus mechanisms and redundant computations in blockchain would introduce unnecessary latency and cost. Thus, the decision to use blockchain should be guided by the specific needs for security, transparency, and decentralization versus the demand for efficiency and speed. \ No newline at end of file +However, for tasks that prioritize high efficiency and speed over decentralization, such as real-time data processing or complex computational tasks, traditional centralized systems are more suitable. In these cases, the overhead of consensus mechanisms and redundant computations in blockchain would introduce unnecessary latency and cost. Thus, the decision to use blockchain should be guided by the specific needs for security, transparency, and decentralization versus the demand for efficiency and speed. \ No newline at end of file From 46d01480e8dea6370c1c041093580e8602add049 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:54:43 +0200 Subject: [PATCH 12/27] update the l1-tokenomics with glossaryterms --- .../l1-tokenomics/04-staking/01-staking-tokens.mdx | 9 +++++---- .../04-staking/03-staking-contract-post-etna.mdx | 5 +++-- .../05-transaction-fees/01-introduction.mdx | 6 ++++-- .../02-transaction-fee-configuration.mdx | 8 +++++--- 4 files changed, 17 insertions(+), 11 deletions(-) diff --git a/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx b/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx index 613d7cb4f8d..c6bd17c3e1f 100644 --- a/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx +++ b/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx @@ -5,15 +5,16 @@ updated: 2024-09-03 authors: [0xstt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' -In many networks, such as Ethereum, the same token is used for both staking and paying for gas. However, in the Avalanche network, staking tokens and gas tokens can be separated, as they fulfill different purposes within the blockchain ecosystem. +In many networks, such as Ethereum, the same token is used for both Staking and paying for Gas. However, in the Avalanche network, staking tokens and gas tokens can be separated, as they fulfill different purposes within the blockchain ecosystem. ### Staking Tokens -Staking tokens are used for securing public, permissionless Avalanche L1s through a proof-of-stake (PoS) consensus mechanism. Holders of staking tokens can: +Staking tokens are used for securing public, permissionless Avalanche L1s through a Proof of Stake consensus mechanism. Holders of staking tokens can: -- Run validators -- Participate in the consensus process by staking a certain amount of tokens as collateral +- Run Validators +- Participate in the Consensus process by staking a certain amount of tokens as collateral Validators propose and validate new blocks on your L1 blockchain. Staking tokens play a crucial role in: diff --git a/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx b/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx index 5db83c25660..bfdd796d33e 100644 --- a/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx +++ b/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx @@ -6,8 +6,9 @@ authors: [0xstt] icon: Book --- import { Steps, Step } from 'fumadocs-ui/components/steps'; +import GlossaryTerm from '@/components/ui/glossary-term' -The contracts in the [`validator-manager`](https://github.com/ava-labs/teleporter/tree/validator-manager/contracts/validator-manager) branch define the Validator Manager used to manage Subnet-only Validators, as defined in [ACP-77](https://github.com/avalanche-foundation/ACPs/tree/main/ACPs/77-reinventing-subnets). `ValidatorManager.sol` is the top-level abstract contract that provides the basic functionality. The other contracts are related as follows: +The contracts in the [`validator-manager`](https://github.com/ava-labs/teleporter/tree/validator-manager/contracts/validator-manager) branch define the Validator Manager used to manage Subnet-only Validators, as defined in ACP-77. `ValidatorManager.sol` is the top-level abstract contract that provides the basic functionality. The other contracts are related as follows: ## Deploying -Three concrete `ValidatorManager` contracts are provided - `PoAValidatorManager`, `NativeTokenStakingManager`, and `ERC20TokenStakingManager`. `NativeTokenStakingManager`, and `ERC20TokenStakingManager` implement `PoSValidatorManager`, which itself implements `ValidatorManager`. These are implemented as [upgradeable](https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable) contracts. There are numerous [guides](https://blog.chain.link/upgradable-smart-contracts/) for deploying upgradeable smart contracts, but the general steps are as follows: +Three concrete `ValidatorManager` contracts are provided - `PoAValidatorManager`, `NativeTokenStakingManager`, and `ERC20TokenStakingManager`. `NativeTokenStakingManager`, and `ERC20TokenStakingManager` implement `PoSValidatorManager`, which itself implements `ValidatorManager`. These are implemented as [upgradeable](https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable) contracts. There are numerous [guides](https://blog.chain.link/upgradable-smart-contracts/) for deploying upgradeable Smart Contracts, but the general steps are as follows: Deploy the implementation contract diff --git a/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx b/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx index 24264901b3f..4b515bd6180 100644 --- a/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx +++ b/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx @@ -6,12 +6,14 @@ authors: [0xstt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + ### Background -When creating an Avalanche L1 we cannot only configure our custom native token, but also how the transaction fees (also known as gas fees) are determined. This allows Avalanche L1s to define the desired or maximal throughput of the blockchain differently. +When creating an Avalanche L1 we cannot only configure our custom native token, but also how the transaction fees (also known as gas fees) are determined. This allows Avalanche L1s to define the desired or maximal throughput of the blockchain differently. ![](/course-images/multi-chain-architecture/subnet-fee-comparison.png) -In the context of the EVM, gas is a unit that measures the computational effort required to execute specific operations. Each operation performed by a contract or transaction on an EVM chain consumes a certain number of gas units based on its complexity. Operations that require more computational resources cost more gas. The EVM calculates the required gas units automatically, and developers are encouraged to optimize their contract code to reduce gas consumption. +In the context of the EVM, Gas is a unit that measures the computational effort required to execute specific operations. Each operation performed by a contract or transaction on an EVM chain consumes a certain number of gas units based on its complexity. Operations that require more computational resources cost more gas. The EVM calculates the required gas units automatically, and developers are encouraged to optimize their contract code to reduce gas consumption. ```bash Transaction Cost = Gas Units * Gas Price ``` diff --git a/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx b/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx index 9e24335c6df..2b10ec516ed 100644 --- a/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx +++ b/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx @@ -6,6 +6,8 @@ authors: [0xstt] icon: Book --- +import GlossaryTerm from '@/components/ui/glossary-term' + ## Configuration Format The fees are configured in the `chainConfig` in the `feeConfig` field: @@ -36,13 +38,13 @@ The fees are configured in the `chainConfig` in the `feeConfig` field: } ``` -## Gas Configuration Parameters +## Gas Configuration Parameters ### `gasLimit` -Sets the maximum amount of gas consumed per block. This restriction caps the computational capacity of a single block and thereby limits the maximum gas usage allowed for any single transaction. For reference, the C-Chain value is set to 15,000,000. +Sets the maximum amount of gas consumed per block. This restriction caps the computational capacity of a single block and thereby limits the maximum gas usage allowed for any single transaction. For reference, the C-Chain value is set to 15,000,000. -You might notice that the `gasLimit` field appears twice. This is because Avalanche introduced its own fee configuration under the `feeConfig` key while maintaining compatibility with the standard EVM configuration. Ensure that both fields have the same decimal and hexadecimal equivalent values. +You might notice that the `gasLimit` field appears twice. This is because Avalanche introduced its own fee configuration under the `feeConfig` key while maintaining compatibility with the standard EVM configuration. Ensure that both fields have the same decimal and hexadecimal equivalent values. ### `targetBlockRate` From b59094d9edaecdca1bf30f891f615cce0f691d6b Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:56:14 +0200 Subject: [PATCH 13/27] update the academy customizing-evm with glossaryterms --- .../02-intro-to-evm/01-origin-of-evm.mdx | 6 +++-- .../01-what-are-precompiles.mdx | 7 +++--- .../06-precompiles/02-why-precompiles.mdx | 7 +++--- .../02-generating-precompile.mdx | 8 +++--- .../03-implement-set-counter.mdx | 1 + content/academy/customizing-evm/index.mdx | 25 ++++++++++--------- 6 files changed, 30 insertions(+), 24 deletions(-) diff --git a/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx b/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx index 64795401def..7083a607a70 100644 --- a/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx +++ b/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx @@ -6,9 +6,11 @@ authors: [ashucoder9, owenwahlgren] icon: BookOpen --- -The **Ethereum Virtual Machine (EVM)** is a fundamental component of Ethereum’s infrastructure, responsible for executing smart contracts across the network. The origins of the EVM can be traced back to the creation of the Ethereum blockchain itself, proposed in a whitepaper by **Vitalik Buterin** in late 2013. +import GlossaryTerm from '@/components/ui/glossary-term' -Buterin and the founding Ethereum team envisioned a platform where developers could build **decentralized applications (dApps)** on a blockchain. To accomplish this, they needed a way to execute arbitrary, complex computations in a secure and decentralized manner. This is how the concept of the EVM was born. +The **Ethereum Virtual Machine (EVM)** is a fundamental component of Ethereum's infrastructure, responsible for executing Smart Contracts across the network. The origins of the EVM can be traced back to the creation of the Ethereum blockchain itself, proposed in a whitepaper by **Vitalik Buterin** in late 2013. + +Buterin and the founding Ethereum team envisioned a platform where developers could build **decentralized applications (dApps)** on a blockchain. To accomplish this, they needed a way to execute arbitrary, complex computations in a secure and decentralized manner. This is how the concept of the EVM was born. The EVM, an integral part of the Ethereum ecosystem, operates as a **quasi-Turing complete machine**. This means it can run nearly any algorithm, given enough resources. It's isolated from the main network, providing a sandboxed environment for smart contract execution. diff --git a/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx b/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx index 72f414595e5..f90cec7f228 100644 --- a/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx +++ b/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx @@ -5,6 +5,7 @@ updated: 2024-05-31 authors: [ashucoder9] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' Precompiled contracts allow the execution of code written in the low-level programming language Go from the EVM, which is significantly faster and more efficient than Solidity. @@ -12,9 +13,9 @@ Precompiled contracts allow the execution of code written in the low-level progr If you're familiar with Python, you might recognize a similar concept where many Python functions and libraries are implemented in C for efficiency. Python developers can import these precompiled modules and call functions as if they were written in Python. The main difference is that the modules execute faster and more efficiently. -Precompiles can be called from a Solidity smart contract just like any other contract. The EVM maintains a list of reserved addresses mapped to precompiles. When a smart contract calls a function of a contract at one of these addresses, the EVM executes the precompile written in Go instead of the Solidity contract. +Precompiles can be called from a Solidity Smart Contract just like any other contract. The EVM maintains a list of reserved addresses mapped to precompiles. When a smart contract calls a function of a contract at one of these addresses, the EVM executes the precompile written in Go instead of the Solidity contract. -For example, if we map the address `0x030...01` to the SHA256 precompile that hashes its input using the SHA256 hash function, we can call the precompile as follows: +For example, if we map the address `0x030...01` to the SHA256 precompile that Hashes its input using the SHA256 hash function, we can call the precompile as follows: ```solidity // SPDX-License-Identifier: MIT @@ -40,7 +41,7 @@ Note that there is no implementation of the precompile in Solidity itself. This ### PrecompiledContract Interface -When implementing a precompile in the Avalanche L1-EVM, the following function of the `StatefulPrecompiledContract` interface must be implemented in Go: +When implementing a precompile in the Avalanche L1-EVM, the following function of the `StatefulPrecompiledContract` interface must be implemented in Go: ```go // StatefulPrecompiledContract is the interface for executing a precompiled contract diff --git a/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx b/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx index 14b30461e23..7323ecbf3f5 100644 --- a/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx +++ b/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx @@ -5,14 +5,15 @@ updated: 2024-05-31 authors: [ashucoder9] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' Adding precompiles to the EVM offers several significant advantages, which we will outline in this chapter. ## Performance Optimization -Precompiles primarily optimize the performance of specific computations. Introducing a new precompile can greatly reduce the computational resources required for certain tasks, thereby enhancing the performance of smart contracts and decentralized applications (DApps) that rely on these tasks. +Precompiles primarily optimize the performance of specific computations. Introducing a new precompile can greatly reduce the computational resources required for certain tasks, thereby enhancing the performance of Smart Contracts and Decentralized Applications (DApps) that rely on these tasks. -For instance, the SHA256 hash function (0x02) and the RIPEMD160 hash function (0x03) serve as examples of precompiles that significantly boost performance. Implementing these functions within a smart contract would be computationally expensive and slow, whereas as precompiles, they execute quickly and efficiently. +For instance, the SHA256 Hash function (0x02) and the RIPEMD160 hash function (0x03) serve as examples of precompiles that significantly boost performance. Implementing these functions within a smart contract would be computationally expensive and slow, whereas as precompiles, they execute quickly and efficiently. ## Security @@ -26,7 +27,7 @@ Precompiles are implemented in Go, allowing access to the rich ecosystem of exis Consider the implementation of the SHA256 hash algorithm to understand the complexity involved in reimplementing it in Solidity. -## Gas Efficiency +## Gas Efficiency Introducing a new precompile to the EVM can enhance gas efficiency for specific computations, thereby lowering execution costs. This makes it feasible to incorporate more complex operations into smart contracts, expanding their functionality without significantly increasing transaction costs. diff --git a/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx b/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx index 5bee640c39b..d1c83b6556e 100644 --- a/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx +++ b/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx @@ -5,12 +5,13 @@ updated: 2024-05-31 authors: [ashucoder9] icon: Terminal --- +import GlossaryTerm from '@/components/ui/glossary-term' In this step, we will again utilize the precompile generation script to generate all the Go files based on the ABI for your calculator. ## Run Generation Script -Change to the root directory of your precompile-evm project and run the command to generate the go files: +Change to the root directory of your precompile-evm project and run the command to generate the go files: ```bash # Change to root @@ -22,7 +23,7 @@ cd .. Now you should have a new directory called `calculatorplus` in the root directory of your project. -If you check our the generated contract.go file you will see right away that it is much longer than in our hash function precompile from earlier. This is due to the fact that our calculator precompile has more functions and parameters. Browse through the code and see if you can spot the new elements: +If you check our the generated contract.go file you will see right away that it is much longer than in our hash function precompile from earlier. This is due to the fact that our calculator precompile has more functions and parameters. Browse through the code and see if you can spot the new elements: ```go title="contract.go" // Code generated @@ -299,5 +300,4 @@ func createCalculatorplusPrecompile() contract.StatefulPrecompiledContract { panic(err) } return statefulContract -} -``` \ No newline at end of file +} \ No newline at end of file diff --git a/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx b/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx index 84e1882c8cb..e7f6b225044 100644 --- a/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx +++ b/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx @@ -5,6 +5,7 @@ updated: 2024-05-31 authors: [ashucoder9] icon: Terminal --- +import GlossaryTerm from '@/components/ui/glossary-term' Having seen how strings are stored in `StringStore`, its time for us to store integers with Counter. The thought process for this section can be defined as follows: diff --git a/content/academy/customizing-evm/index.mdx b/content/academy/customizing-evm/index.mdx index c79f026b8cc..38ad7059620 100644 --- a/content/academy/customizing-evm/index.mdx +++ b/content/academy/customizing-evm/index.mdx @@ -6,13 +6,14 @@ authors: [ashucoder9, owenwahlgren] icon: Smile --- import { Step, Steps } from 'fumadocs-ui/components/steps'; +import GlossaryTerm from '@/components/ui/glossary-term' ## Why take this Course? -A significant innovation in blockchain is the development of multi-chain systems, such as Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. At the core of these multi-chain systems is the ability to run multiple blockchains powered by different virtual machines simultaneously. Each VM of a chain is optimized for specialized use cases, thereby boosting the network's overall performance. +A significant innovation in blockchain is the development of multi-chain systems, such as Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. At the core of these multi-chain systems is the ability to run multiple blockchains powered by different Virtual Machines simultaneously. Each VM of a chain is optimized for specialized use cases, thereby boosting the network's overall performance. -Configuring and modifying the EVM is an efficient way to create a specialized virtual machine, as it allows developers to build upon years of active community work and leverage the extensive ecosystem surrounding the EVM, including wallets, explorers, and development frameworks. +Configuring and modifying the EVM is an efficient way to create a specialized virtual machine, as it allows developers to build upon years of active community work and leverage the extensive ecosystem surrounding the EVM, including wallets, explorers, and development frameworks. ## Course Content @@ -20,7 +21,7 @@ Configuring and modifying the EVM is an efficient way to create a specialized vi ### EVM Basics & Precompiles -In the first section of the course we will go through some basic concepts of the EVM, such as the account-based model, keys, addresses, transactions, and blocks. Furthermore, we will explain what a precompile is and show you how to interact with a precompile on the Fuji testnet. +In the first section of the course we will go through some basic concepts of the EVM, such as the account-based model, keys, addresses, transactions, and Blocks. Furthermore, we will explain what a precompile is and show you how to interact with a precompile on the Fuji testnet. ### Development Environment Setup @@ -37,27 +38,27 @@ The following sections contain hands-on exercises where you customize the EVM. T - Learn how the Avalanche Network Runner Works - Create a your own Avalanche Network - - Create an EVM Blockchain on your network - - Connect Core Wallet to your blockchain + - Create an EVM blockchain on your network + - Connect Core Wallet to your blockchain - Learn what the genesis block is and how the data is structured - - Create a custom gas fee structure for your blockchain + - Create a custom gas fee structure for your blockchain - Define the initial token allocation at launch - Configure pre-installed precompiles - - Create the blockchain and connect to it + - Create the blockchain and connect to it - Learn about the basic building blocks of a precompile by building a precompile for the md5 hash function: + Learn about the basic building blocks of a precompile by building a precompile for the md5 hash function: - Generate boilerplate code for the precompile from a solidity interface - Learn how to unpack inputs and pack outputs into 32 byte arrays - Configure and register your md5 precompile - - Create a new blockchain, connect to it and interact with your precompile + - Create a new blockchain, connect to it and interact with your precompile @@ -98,8 +99,8 @@ The following sections contain hands-on exercises where you customize the EVM. T This course is intended for people with a solid understanding of the basic concepts of Avalanche. You should be familiar with these concepts: -1. **Virtual Machines**: What they are and what VM customization means -2. **Blockchains**: What the components are of a blockchain and how they interact, specifically how Avalanche L1s leverage precompiles. +1. **Virtual Machines**: What they are and what VM customization means +2. **Blockchains**: What the components are of a blockchain and how they interact, specifically how Avalanche L1s leverage precompiles. If some of this is not clear, I strongly recommend taking the [Avalanche Fundamentals](/academy/avalanche-fundamentals) and [Multi-Chain Architecture](/academy/multi-chain-architecture) courses first. @@ -116,7 +117,7 @@ You will need a general understanding of software development. You won't have to By the end of this course, students will be able to: - Understand what Precompiles are and when to use them. -- Understand how developing precompiles allows developers to create more optimized and capable blockchain systems, enabling them to address entirely new use cases that were previously unattainable. +- Understand how developing precompiles allows developers to create more optimized and capable blockchain systems, enabling them to address entirely new use cases that were previously unattainable. - Apply the knowledge gained in the course by building multiple precompiles From f67f8a4d63d4f3fcb5d59e67e5b3ce726fb7a753 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:57:19 +0200 Subject: [PATCH 14/27] update the docs with glossaryterms --- content/docs/quick-start/avalanche-l1s.mdx | 52 ++++++++++---------- content/docs/quick-start/primary-network.mdx | 24 ++++----- content/docs/tooling/create-avalanche-l1.mdx | 22 +++++---- 3 files changed, 52 insertions(+), 46 deletions(-) diff --git a/content/docs/quick-start/avalanche-l1s.mdx b/content/docs/quick-start/avalanche-l1s.mdx index dc8af4074ba..7a75693c52a 100644 --- a/content/docs/quick-start/avalanche-l1s.mdx +++ b/content/docs/quick-start/avalanche-l1s.mdx @@ -3,67 +3,69 @@ title: Avalanche L1s description: Explore the multi-chain architecture of Avalanche ecosystem. --- -An Avalanche L1 is a sovereign network which defines its own rules regarding its membership and token economics. It is composed of a dynamic subset of Avalanche validators working together to achieve consensus on the state of one or more blockchains. Each blockchain is validated by exactly one Avalanche L1, while an Avalanche L1 can validate many blockchains. +import GlossaryTerm from '@/components/ui/glossary-term' -Avalanche's [Primary Network](/docs/quick-start/primary-network) is a special Avalanche L1 running three blockchains: +An Avalanche L1 is a sovereign network which defines its own rules regarding its membership and token economics. It is composed of a dynamic subset of Avalanche validators working together to achieve consensus on the state of one or more blockchains. Each blockchain is validated by exactly one Avalanche L1, while an Avalanche L1 can validate many blockchains. -- The Platform Chain [(P-Chain)](/docs/quick-start/primary-network#p-chain) -- The Contract Chain [(C-Chain)](/docs/quick-start/primary-network#c-chain) -- The Exchange Chain [(X-Chain)](/docs/quick-start/primary-network#x-chain) +Avalanche's [Primary Network](/docs/quick-start/primary-network) is a special Avalanche L1 running three blockchains: + +- The Platform Chain [(P-Chain)](/docs/quick-start/primary-network#p-chain) +- The Contract Chain [(C-Chain)](/docs/quick-start/primary-network#c-chain) +- The Exchange Chain [(X-Chain)](/docs/quick-start/primary-network#x-chain) ![image](/images/subnet1.png) -Every validator of an Avalanche L1 **must** sync the P-Chain of the Primary Network for interoperability. +Every validator of an Avalanche L1 **must** sync the P-Chain of the Primary Network for interoperability. -Node operators that validate an Avalanche L1 with multiple chains do not need to run multiple machines for validation. For example, the Primary Network is an Avalanche L1 with three coexisting chains, all of which can be validated by a single node, or a single machine. +Node operators that validate an Avalanche L1 with multiple chains do not need to run multiple machines for validation. For example, the Primary Network is an Avalanche L1 with three coexisting chains, all of which can be validated by a single node, or a single machine. ## Advantages ### Independent Networks -- Avalanche L1s use virtual machines to specify their own execution logic, determine their own fee regime, maintain their own state, facilitate their own networking, and provide their own security. -- Each Avalanche L1's performance is isolated from other Avalanche L1s in the ecosystem, so increased usage on one Avalanche L1 won't affect another. -- Avalanche L1s can have their own token economics with their own native tokens, fee markets, and incentives determined by the Avalanche L1 deployer. -- One Avalanche L1 can host multiple blockchains with customized [virtual machines](/docs/quick-start/virtual-machines). +- Avalanche L1s use virtual machines to specify their own execution logic, determine their own fee regime, maintain their own state, facilitate their own networking, and provide their own security. +- Each Avalanche L1's performance is isolated from other Avalanche L1s in the ecosystem, so increased usage on one Avalanche L1 won't affect another. +- Avalanche L1s can have their own token economics with their own native tokens, fee markets, and incentives determined by the Avalanche L1 deployer. +- One Avalanche L1 can host multiple blockchains with customized [virtual machines](/docs/quick-start/virtual-machines). ### Native Interoperability -Avalanche Warp Messaging enables native cross-Avalanche L1 communication and allows Virtual Machine (VM) developers to implement arbitrary communication protocols between any two Avalanche L1s. +Avalanche Warp Messaging enables native cross-Avalanche L1 communication and allows Virtual Machine (VM) developers to implement arbitrary communication protocols between any two Avalanche L1s. ### Accommodate App-Specific Requirements -Different blockchain-based applications may require validators to have certain properties such as large amounts of RAM or CPU power. +Different blockchain-based applications may require validators to have certain properties such as large amounts of RAM or CPU power. -an Avalanche L1 could require that validators meet certain [hardware requirements](/docs/nodes/run-a-node/manually#hardware-and-os-requirements) so that the application doesn't suffer from low performance due to slow validators. +an Avalanche L1 could require that validators meet certain [hardware requirements](/docs/nodes/run-a-node/manually#hardware-and-os-requirements) so that the application doesn't suffer from low performance due to slow validators. ### Launch Networks Designed With Compliance -Avalanche's L1 architecture makes regulatory compliance manageable. As mentioned above, an Avalanche L1 may require validators to meet a set of requirements. +Avalanche's L1 architecture makes regulatory compliance manageable. As mentioned above, an Avalanche L1 may require validators to meet a set of requirements. -Some examples of requirements the creators of an Avalanche L1 may choose include: +Some examples of requirements the creators of an Avalanche L1 may choose include: -- Validators must be located in a given country. -- Validators must pass KYC/AML checks. -- Validators must hold a certain license. +- Validators must be located in a given country. +- Validators must pass KYC/AML checks. +- Validators must hold a certain license. ### Control Privacy of On-Chain Data -Avalanche L1s are ideal for organizations interested in keeping their information private. +Avalanche L1s are ideal for organizations interested in keeping their information private. -Institutions conscious of their stakeholders' privacy can create a private Avalanche L1 where the contents of the blockchains would be visible only to a set of pre-approved validators. +Institutions conscious of their stakeholders' privacy can create a private Avalanche L1 where the contents of the blockchains would be visible only to a set of pre-approved validators. Define this at creation with a [single parameter](/docs/nodes/configure/avalanche-l1-configs#private-avalanche-l1). ### Validator Sovereignty -In a heterogeneous network of blockchains, some validators will not want to validate certain blockchains because they simply have no interest in those blockchains. +In a heterogeneous network of blockchains, some validators will not want to validate certain blockchains because they simply have no interest in those blockchains. -The Avalanche L1 model enables validators to concern themselves only with blockchain networks they choose to participate in. This greatly reduces the computational burden on validators. +The Avalanche L1 model enables validators to concern themselves only with blockchain networks they choose to participate in. This greatly reduces the computational burden on validators. ## Develop Your Own Avalanche L1 -Avalanche L1s on Avalanche are deployed by default with [Subnet-EVM](https://github.com/ava-labs/subnet-evm#subnet-evm), a fork of go-ethereum. It implements the Ethereum Virtual Machine and supports Solidity smart contracts as well as most other Ethereum client functionality. +Avalanche L1s on Avalanche are deployed by default with [Subnet-EVM](https://github.com/ava-labs/subnet-evm#subnet-evm), a fork of go-ethereum. It implements the Ethereum Virtual Machine and supports Solidity smart contracts as well as most other Ethereum client functionality. -To get started, check out our [L1 Launcher](/tools/l1-launcher) or the tutorials in the [Avalanche CLI](/docs/tooling/create-avalanche-l1) section. +To get started, check out our [L1 Launcher](/tools/l1-launcher) or the tutorials in the [Avalanche CLI](/docs/tooling/create-avalanche-l1) section. diff --git a/content/docs/quick-start/primary-network.mdx b/content/docs/quick-start/primary-network.mdx index af1c813950a..b748f5a91b1 100644 --- a/content/docs/quick-start/primary-network.mdx +++ b/content/docs/quick-start/primary-network.mdx @@ -3,19 +3,21 @@ title: Primary Network description: Learn about the Avalanche Primary Network and its three blockchains. --- -Avalanche is a heterogeneous network of blockchains. As opposed to homogeneous networks, where all applications reside in the same chain, heterogeneous networks allow separate chains to be created for different applications. +import GlossaryTerm from '@/components/ui/glossary-term' -The Primary Network is a special [Avalanche L1](/docs/quick-start/avalanche-l1s) that runs three blockchains: +Avalanche is a heterogeneous network of blockchains. As opposed to homogeneous networks, where all applications reside in the same chain, heterogeneous networks allow separate chains to be created for different applications. -- The Platform Chain [(P-Chain)](/docs/quick-start/primary-network#p-chain) -- The Contract Chain [(C-Chain)](/docs/quick-start/primary-network#c-chain) -- The Exchange Chain [(X-Chain)](/docs/quick-start/primary-network#x-chain) +The Primary Network is a special [Avalanche L1](/docs/quick-start/avalanche-l1s) that runs three blockchains: + +- The Platform Chain [(P-Chain)](/docs/quick-start/primary-network#p-chain) +- The Contract Chain [(C-Chain)](/docs/quick-start/primary-network#c-chain) +- The Exchange Chain [(X-Chain)](/docs/quick-start/primary-network#x-chain) [Avalanche Mainnet](/docs/quick-start/networks/mainnet) is comprised of the Primary Network and all deployed Avalanche L1s. -A node can become a validator for the Primary Network by staking at least **2,000 AVAX**. +A node can become a validator for the Primary Network by staking at least **2,000 AVAX**. ![Primary network](/images/primary-network1.png) @@ -25,20 +27,20 @@ All validators of the Primary Network are required to validate and secure the fo ### C-Chain -The **C-Chain** is an implementation of the Ethereum Virtual Machine (EVM). The [C-Chain's API](/docs/api-reference/c-chain/api) supports Geth's API and supports the deployment and execution of smart contracts written in Solidity. +The **C-Chain** is an implementation of the Ethereum Virtual Machine (EVM). The [C-Chain's API](/docs/api-reference/c-chain/api) supports Geth's API and supports the deployment and execution of smart contracts written in Solidity. -The C-Chain is an instance of the [Coreth](https://github.com/ava-labs/coreth) Virtual Machine. +The C-Chain is an instance of the Coreth Virtual Machine. ### P-Chain The **P-Chain** is responsible for all validator and Avalanche L1-level operations. The [P-Chain API](/docs/api-reference/p-chain/api) supports the creation of new blockchains and Avalanche L1s, the addition of validators to Avalanche L1s, staking operations, and other platform-level operations. -The P-Chain is an instance of the Platform Virtual Machine. +The P-Chain is an instance of the Platform Virtual Machine. ### X-Chain -The **X-Chain** is responsible for operations on digital smart assets known as **Avalanche Native Tokens**. A smart asset is a representation of a real-world resource (for example, equity, or a bond) with sets of rules that govern its behavior, like "can't be traded until tomorrow." The [X-Chain API](/docs/api-reference/x-chain/api) supports the creation and trade of Avalanche Native Tokens. +The **X-Chain** is responsible for operations on digital smart assets known as **Avalanche Native Tokens**. A smart asset is a representation of a real-world resource (for example, equity, or a bond) with sets of rules that govern its behavior, like "can't be traded until tomorrow." The [X-Chain API](/docs/api-reference/x-chain/api) supports the creation and trade of Avalanche Native Tokens. One asset traded on the X-Chain is AVAX. When you issue a transaction to a blockchain on Avalanche, you pay a fee denominated in AVAX. -The X-Chain is an instance of the Avalanche Virtual Machine (AVM). +The X-Chain is an instance of the Avalanche Virtual Machine (AVM). diff --git a/content/docs/tooling/create-avalanche-l1.mdx b/content/docs/tooling/create-avalanche-l1.mdx index e51fcee30bb..703d47d7ac0 100644 --- a/content/docs/tooling/create-avalanche-l1.mdx +++ b/content/docs/tooling/create-avalanche-l1.mdx @@ -3,9 +3,11 @@ title: Create Avalanche L1 description: This page demonstrates how to create an Avalanche L1 using Avalanche-CLI. --- -This tutorial walks you through the process of using Avalanche-CLI to create an Avalanche L1, deploy it to a local network, and connect to it with Core wallet. +import GlossaryTerm from '@/components/ui/glossary-term' -The first step of learning Avalanche L1 development is learning to use [Avalanche-CLI](https://github.com/ava-labs/avalanche-cli). +This tutorial walks you through the process of using Avalanche-CLI to create an Avalanche L1, deploy it to a local network, and connect to it with Core wallet. + +The first step of learning Avalanche L1 development is learning to use [Avalanche-CLI](https://github.com/ava-labs/avalanche-cli). Installation[​](#installation "Direct link to heading") ------------------------------------------------------- @@ -26,7 +28,7 @@ You can also add the command to your system path by running: export PATH=~/bin:$PATH ``` -To make this change permanent, add this line to your shell’s initialization file (e.g., `~/.bashrc` or `~/.zshrc`). For example: +To make this change permanent, add this line to your shell's initialization file (e.g., `~/.bashrc` or `~/.zshrc`). For example: ```bash echo 'export PATH=~/bin:$PATH' >> ~/.bashrc @@ -40,11 +42,11 @@ For more detailed installation instructions, see [Avalanche-CLI Installation](/d Create Your Avalanche L1 Configuration[​](#create-your-avalanche-l1-configuration "Direct link to heading") ----------------------------------------------------------------------------------------------- -This tutorial teaches you how to create an Ethereum Virtual Machine (EVM) based Avalanche L1. To do so, you use Subnet-EVM, Avalanche's L1 fork of the EVM. It supports airdrops, custom fee tokens, configurable gas parameters, and multiple stateful precompiles. To learn more, take a look at [Subnet-EVM](https://github.com/ava-labs/subnet-evm). The goal of your first command is to create a Subnet-EVM configuration. +This tutorial teaches you how to create an Ethereum Virtual Machine (EVM) based Avalanche L1. To do so, you use Subnet-EVM, Avalanche's L1 fork of the EVM. It supports airdrops, custom fee tokens, configurable gas parameters, and multiple stateful precompiles. To learn more, take a look at [Subnet-EVM](https://github.com/ava-labs/subnet-evm). The goal of your first command is to create a Subnet-EVM configuration. -The `avalanche-cli` command suite provides a collection of tools for developing and deploying Avalanche L1s. +The `avalanche-cli` command suite provides a collection of tools for developing and deploying Avalanche L1s. -The Creation Wizard walks you through the process of creating your Avalanche L1. To get started, first pick a name for your Avalanche L1. This tutorial uses `myblockchain`, but feel free to substitute that with any name you like. Once you've picked your name, run: +The Creation Wizard walks you through the process of creating your Avalanche L1. To get started, first pick a name for your Avalanche L1. This tutorial uses `myblockchain`, but feel free to substitute that with any name you like. Once you've picked your name, run: ```bash avalanche blockchain create myblockchain @@ -106,7 +108,7 @@ To learn more about different validator management types, see [PoA vs PoS](/evm- ``` Select `I want to use defaults for a test environment`. -This will automatically setup the configuration for a test environment, including an airdrop to the EWOQ key and Avalanche ICM. +This will automatically setup the configuration for a test environment, including an airdrop to the EWOQ key and Avalanche Interchain Messaging. ### Enter Your Avalanche L1's ChainID @@ -116,7 +118,7 @@ This will automatically setup the configuration for a test environment, includin Choose a positive integer for your EVM-style ChainID. -In production environments, this ChainID needs to be unique and not shared with any other chain. You can visit [chainlist](https://chainlist.org/) to verify that your selection is unique. Because this is a development Avalanche L1, feel free to pick any number. Stay away from well-known ChainIDs such as 1 (Ethereum) or 43114 (Avalanche C-Chain) as those may cause issues with other tools. +In production environments, this ChainID needs to be unique and not shared with any other chain. You can visit [chainlist](https://chainlist.org/) to verify that your selection is unique. Because this is a development Avalanche L1, feel free to pick any number. Stay away from well-known ChainIDs such as 1 (Ethereum) or 43114 (Avalanche Contract Chain) as those may cause issues with other tools. ### Token Symbol @@ -124,7 +126,7 @@ In production environments, this ChainID needs to be unique and not shared with ✗ Token Symbol: ``` -Enter a string to name your Avalanche L1's native token. The token symbol doesn't necessarily need to be unique. Example token symbols are AVAX, JOE, and BTC. +Enter a string to name your Avalanche L1's native token. The token symbol doesn't necessarily need to be unique. Example token symbols are AVAX, JOE, and BTC. ### Wrapping Up @@ -138,4 +140,4 @@ To view the Genesis configuration, use the following command: avalanche blockchain describe myblockchain --genesis ``` -You've successfully created your first Avalanche L1 configuration. Now it's time to deploy it. +You've successfully created your first Avalanche L1 configuration. Now it's time to deploy it. From 42c9fcafea414826afdccd76dcf95cc2c9ecd287 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:58:23 +0200 Subject: [PATCH 15/27] update the academy multi-chain-architecture with glossaryterms --- .../02-custom-blockchains/01-custom-blockchains.mdx | 12 +++++++----- .../02-benefits-of-custom-blockchains.mdx | 12 +++++++----- .../03-custom-blockchains-vs-layer-2.mdx | 10 ++++++---- .../01-avalanche-starter-kit.mdx | 6 ++++-- .../01-independent-tokenomics.mdx | 8 +++++--- .../01-permissioning-validators.mdx | 6 ++++-- .../08-customizability/00-intro.mdx | 8 +++++--- content/academy/multi-chain-architecture/index.mdx | 10 ++++++---- 8 files changed, 44 insertions(+), 28 deletions(-) diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx index 32d12be9899..3ce11f7b692 100644 --- a/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx +++ b/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx @@ -6,7 +6,9 @@ authors: [usmaneth] icon: Book --- -An Avalanche L1 is a sovereign network that defines its own rules for membership and token economics. It's validated by a dynamic subset of Avalanche validators working together to achieve consensus on the blockchain's state. +import GlossaryTerm from '@/components/ui/glossary-term' + +An Avalanche L1 is a sovereign network that defines its own rules for membership and token economics. It's validated by a dynamic subset of Avalanche validators working together to achieve consensus on the blockchain's state. ## Key Concepts @@ -22,11 +24,11 @@ An Avalanche L1 is a sovereign network that defines its own rules for membership ## The Primary Network -Avalanche's three main blockchains form the Primary Network: +Avalanche's three main blockchains form the Primary Network: -- Platform Chain (P-Chain) -- Contract Chain (C-Chain) -- Exchange Chain (X-Chain) +- Platform Chain (P-Chain) +- Contract Chain (C-Chain) +- Exchange Chain (X-Chain) These blockchains are validated and secured by all Avalanche validators, which collectively form a special Avalanche L1 known as the Primary Network. diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx index a31ce2f558a..17d7af3493d 100644 --- a/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx +++ b/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx @@ -6,11 +6,13 @@ authors: [usmaneth] icon: BookOpen --- +import GlossaryTerm from '@/components/ui/glossary-term' + Custom blockchains offer a range of advantages for developers and businesses looking to create very custom & tailored solutions. ## Enhanced Compliance and Access Control -While the C-Chain operates as an open and permissionless network, custom blockchains provide more granular control over user access and permissions. This feature is particularly valuable for applications that need to meet specific regulatory requirements. +While the Contract Chain operates as an open and permissionless network, custom blockchains provide more granular control over user access and permissions. This feature is particularly valuable for applications that need to meet specific regulatory requirements. - Authorized Access: Developers can configure custom blockchains to allow only pre-approved users to deploy contracts or initiate transactions. @@ -20,12 +22,12 @@ This level of control helps ensure compliance (KYC, AML, etc) with various finan Custom blockchains offer flexibility in defining the economic model of your network. They allow for: -- Gas Token Freedom: Unlike fixed gas token systems (e.g., ETH for Ethereum), custom blockchains can use any token as their gas token. +- Gas Token Freedom: Unlike fixed gas token systems (e.g., ETH for Ethereum), custom blockchains can use any token as their gas token. - Economic Isolation: Your blockchain's economics remain unaffected by gas price fluctuations on other networks, providing stability and predictability. ## Privacy and Confidentiality -While public blockchains offer transparency, many business scenarios require controlled visibility of transaction data. Developers building custom blockchains on Avalanche can enable: +While public blockchains offer transparency, many business scenarios require controlled visibility of transaction data. Developers building custom blockchains on Avalanche can enable: - Selective Transparency: Private blockchains allow you to limit transaction visibility to authorized participants. - Data Protection: Implement transaction encryption to safeguard sensitive information. @@ -33,9 +35,9 @@ While public blockchains offer transparency, many business scenarios require con ## Virtual Machine Flexibility -The ability to choose or create custom Virtual Machines (VMs) offers unprecedented flexibility. Avalanche custom blockchains allow for developers to have: +The ability to choose or create custom Virtual Machines (VMs) offers unprecedented flexibility. Avalanche custom blockchains allow for developers to have: -- Multiple VM Support: Unlike single-VM networks like Bitcoin or Ethereum, Avalanche L1s can host multiple blockchain instances with different VMs. +- Multiple VM Support: Unlike single-VM networks like Bitcoin or Ethereum, Avalanche L1s can host multiple blockchain instances with different VMs. - Ease of Use: Leverage existing VMs like the subnetEVM or create entirely new custom VMs using our SDKs to suit your specific needs. - Network Effects: This flexible architecture creates network effects both within individual blockchains and across different Avalanche L1s and blockchains. diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx index a6039f3014b..34635dbfc4e 100644 --- a/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx +++ b/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx @@ -6,20 +6,22 @@ authors: [usmaneth] icon: BookOpen --- -Layer 2 blockchain solutions, such as rollups, are another innovation in the blockchain landscape. Layer 2s aim to enhance the scalability and performance of the Ethereum network. Rollups essentially perform computations off-chain and submit the resultant state changes to the base layer, thereby reducing the computational load on the main Ethereum chain. +import GlossaryTerm from '@/components/ui/glossary-term' + +Layer 2 blockchain solutions, such as rollups, are another innovation in the blockchain landscape. Layer 2s aim to enhance the scalability and performance of the Ethereum network. Rollups essentially perform computations off-chain and submit the resultant state changes to the base layer, thereby reducing the computational load on the main Ethereum chain. While both Avalanche Custom Blockchains and Layer 2 rollups strive to improve blockchain scalability and performance, they use different methods and each have their unique advantages and trade-offs. ## Decentralization and Security -Avalanche Custom Blockchains are part of the base layer itself. Each blockchain in Avalanche maintains its security, hence a compromise in one blockchain doesn't necessarily impact the others. On the other hand, rollups delegate security to the Ethereum mainnet. As long as the mainnet remains secure, so does the Layer 2 solution, given the rollup performs properly. However, a security breach on the mainnet can potentially affect all Layer 2 solutions. +Avalanche Custom Blockchains are part of the base layer itself. Each blockchain in Avalanche maintains its security, hence a compromise in one blockchain doesn't necessarily impact the others. On the other hand, rollups delegate security to the Ethereum mainnet. As long as the mainnet remains secure, so does the Layer 2 solution, given the rollup performs properly. However, a security breach on the mainnet can potentially affect all Layer 2 solutions. ## Interoperability and Flexibility -Avalanche's multi-chain structure offers great interoperability and flexibility, as each custom blockchain network can define its own rules and validate multiple blockchains of different virtual machines. This means Avalanche can cater to a vast array of use cases. Conversely, Layer 2 solutions are primarily designed to augment the Ethereum mainnet and might not offer the same flexibility. +Avalanche's multi-chain structure offers great interoperability and flexibility, as each custom blockchain network can define its own rules and validate multiple blockchains of different Virtual Machines. This means Avalanche can cater to a vast array of use cases. Conversely, Layer 2 solutions are primarily designed to augment the Ethereum mainnet and might not offer the same flexibility. ## Performance and Cost -Both approaches aim to offer higher transaction throughput and lower fees compared to traditional single-chain systems. Avalanche achieves this through parallel processing across its Avalanche L1s, while rollups offload computation off-chain. However, users of Layer 2 solutions might experience delays when transferring assets back to Layer 1. Furthermore, since Layer 2 systems need to checkpoint their activity to the L1, which effectively sets a price floor and couples the prices of the L1 gas token to the L2 gas token. In Avalanche, the gas tokens of an Avalanche L1 are completely independent from AVAX. +Both approaches aim to offer higher transaction throughput and lower fees compared to traditional single-chain systems. Avalanche achieves this through parallel processing across its Avalanche L1s, while rollups offload computation off-chain. However, users of Layer 2 solutions might experience delays when transferring assets back to Layer 1. Furthermore, since Layer 2 systems need to checkpoint their activity to the L1, which effectively sets a price floor and couples the prices of the L1 gas token to the L2 gas token. In Avalanche, the gas tokens of an Avalanche L1 are completely independent from AVAX. \ No newline at end of file diff --git a/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx b/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx index c3500541acf..4a2c1645585 100644 --- a/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx +++ b/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx @@ -6,14 +6,16 @@ authors: [martineckardt] icon: Book --- -To make easier your journey through this course, we have prepared a Starter Kit repo consisting of everything you will need to start developing your own custom blockchains on Avalanche. This repo will provide a self-contained environment with Avalanche-CLI, and Foundry so you can follow the course without the need of installing anything else other than launching the environment. +import GlossaryTerm from '@/components/ui/glossary-term' + +To make easier your journey through this course, we have prepared a Starter Kit repo consisting of everything you will need to start developing your own custom blockchains on Avalanche. This repo will provide a self-contained environment with Avalanche-CLI, and Foundry so you can follow the course without the need of installing anything else other than launching the environment. # What You Will Learn In this section, you will go through the following topics: - How to launch your own Codespace -- Create your own Avalanche Interchain Messaging enabled custom blockchain +- Create your own Avalanche Interchain Messaging enabled custom blockchain - Foundry configuration At the end of this section, you will have your environment ready to follow with the Cross-Chain development with Avalanche Interchain Messaging. diff --git a/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx b/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx index cef47f717a3..d685f2e07ec 100644 --- a/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx +++ b/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx @@ -6,14 +6,16 @@ authors: [usmaneth] icon: Book --- -Avalanche Custom Blockchains offer multiple ways to implement independent tokenomics. This gives developers more control and can enable new business model that would not be economically feasible on single-chain systems. +import GlossaryTerm from '@/components/ui/glossary-term' + +Avalanche Custom Blockchains offer multiple ways to implement independent tokenomics. This gives developers more control and can enable new business model that would not be economically feasible on single-chain systems. The customizations include: -- **Native Token:** Every Avalanche L1 has their own native token used for paying transaction fees. +- **Native Token:** Every Avalanche L1 has their own native token used for paying transaction fees. - **Transaction Fees:** We can configure how the transaction fees should be calculated. - **Initial Native Token Allocation:** We can specify how the inital token supply is distributed. - **Native Token Minting Rights:** We can specify if and who can mint more native tokens. -- **Staking Token:** If our Avalanche L1 allows public and permissionless validation, we can define our logic how a node can become a validator. +- **Staking Token:** If our Avalanche L1 allows public and permissionless validation, we can define our logic how a node can become a validator. You will learn about all these topics and get hands-on experience how you can configure the tokenomics of your own custom blockchain. diff --git a/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx b/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx index 9ea569547b1..4de1c69251b 100644 --- a/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx +++ b/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx @@ -6,9 +6,11 @@ authors: [usmaneth] icon: Book --- -The ability to control a blockchain's validator set has many benefits that can significantly enhance the efficiency, security, and governance of the network. It allows blockchain participants to have greater influence over the consensus process and decision-making, leading to a more robust and adaptable ecosystem. There are two ways to structure the validator set: +import GlossaryTerm from '@/components/ui/glossary-term' -- **Permissionless Validation:** Anyone can participate in the validation process and be rewarded in tokens to cover their costs for the hardware and running the validator. In Avalanche, we call Avalanche L1s that take this approach Elastic Avalanche L1s. +The ability to control a blockchain's validator set has many benefits that can significantly enhance the efficiency, security, and governance of the network. It allows blockchain participants to have greater influence over the consensus process and decision-making, leading to a more robust and adaptable ecosystem. There are two ways to structure the validator set: + +- **Permissionless Validation:** Anyone can participate in the validation process and be rewarded in tokens to cover their costs for the hardware and running the validator. In Avalanche, we call Avalanche L1s that take this approach Elastic Avalanche L1s. - **Permissioned Validation:** Only whitelisted validators can validate the Avalanche L1. A permissioned Avalanche L1 can be turned into a Elastic Avalanche L1 at any time, but not the other way round. There are many reasons why the creators might want a permissioned validator set for their Avalanche L1. diff --git a/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx b/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx index cdb5d4d0960..ea08f359dd1 100644 --- a/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx +++ b/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx @@ -6,14 +6,16 @@ authors: [ashucoder9] icon: Book --- -For some use cases, it may be necessary to use a customized VM instead of the EVM. This is the case if an application cannot be built on a regular EVM on the C-Chain, or if it would result in transaction fee costs too high to be economical for its users or creators. +import GlossaryTerm from '@/components/ui/glossary-term' -Depending on a builder's needs, Avalanche allows for different VM customizations: +For some use cases, it may be necessary to use a customized VM instead of the EVM. This is the case if an application cannot be built on a regular EVM on the C-Chain, or if it would result in transaction fee costs too high to be economical for its users or creators. + +Depending on a builder's needs, Avalanche allows for different VM customizations: ![](/course-images/avalanche-fundamentals/32.png) Customizing the EVM on the Ethereum network is difficult, requiring a wide consensus that the proposed change is mutually beneficial for all network participants. This can make customizations for unique use cases challenging, if not impossible. Additionally, Ethereum doesn't give users the option to add different chains. -In Avalanche, every Avalanche L1 has autonomy over their Virtual Machines. Their creators can customize VMs to fit their unique requirements. This is one of the biggest advantages of multi-chain systems. +In Avalanche, every Avalanche L1 has autonomy over their Virtual Machines. Their creators can customize VMs to fit their unique requirements. This is one of the biggest advantages of multi-chain systems. In this section, we will see the three way to customize Virtual Machines at a high level. In later courses, we will dive deeper and learn how to actually customize each. \ No newline at end of file diff --git a/content/academy/multi-chain-architecture/index.mdx b/content/academy/multi-chain-architecture/index.mdx index 4748862c181..faedb32bc90 100644 --- a/content/academy/multi-chain-architecture/index.mdx +++ b/content/academy/multi-chain-architecture/index.mdx @@ -6,11 +6,13 @@ authors: [usmaneth] icon: Smile --- -Are you ready to dive deeper into the fascinating world of Avalanche? This course will equip you with a comprehensive understanding of the Avalanche's Multi Blockchain architecture, along with the practical skills required to create and manage custom blockchains. +import GlossaryTerm from '@/components/ui/glossary-term' + +Are you ready to dive deeper into the fascinating world of Avalanche? This course will equip you with a comprehensive understanding of the Avalanche's Multi Blockchain architecture, along with the practical skills required to create and manage custom blockchains. Ideal for people familiar with the basics of Avalanche, this course will unlock the potential of creating custom blockchains. We will explore the various components and key concepts of the Custom Blockchain architecture, empowering you to fully leverage its benefits. -Throughout this course, you will gain hands-on experience by utilizing the Avalanche Command Line Interface (Avalanche CLI) to create your own custom blockchains and run them locally. You will explore different variations and configurations to learn the versatility and advantages of custom blockchains. Additionally, you will interact with the local instances using the Core Wallet, further enhancing your practical skills. +Throughout this course, you will gain hands-on experience by utilizing the Avalanche Command Line Interface (Avalanche CLI) to create your own custom blockchains and run them locally. You will explore different variations and configurations to learn the versatility and advantages of custom blockchains. Additionally, you will interact with the local instances using the Core Wallet, further enhancing your practical skills. Let's get started exploring the power of Avalanche Custom Blockchains. @@ -22,7 +24,7 @@ Below you can find a recording of a presentation about the Multi-Chain Architect ## Prerequisites -This course is for people who understand the Avalanche basics. If you are not familiar with Avalanche Consensus, Virtual Machines, blockchains in Avalanche, or Avalanche Custom Blockchains, we strongly recommend taking our [Avalanche Fundamentals](/academy/avalanche-fundamentals) course first. +This course is for people who understand the Avalanche basics. If you are not familiar with Avalanche Consensus, Virtual Machines, blockchains in Avalanche, or Avalanche Custom Blockchains, we strongly recommend taking our [Avalanche Fundamentals](/academy/avalanche-fundamentals) course first. ## Learning Outcomes @@ -30,5 +32,5 @@ In this course you will learn: - The benefits of Avalanche Custom Blockchains - How to use Avalanche CLI to create and run custom blockchains locally -- How to interact with Avalanche L1s using Core Wallet +- How to interact with Avalanche L1s using Core Wallet From 362596514f99fd6cb0b60def75ce78c10ed3eccf Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 13:59:02 +0200 Subject: [PATCH 16/27] update the academy courses with glossaryterms --- content/academy/avacloudapis/index.mdx | 8 +++++--- .../02-what-is-a-blockchain/04-use-cases.mdx | 6 +++--- .../01-payments-use-case.mdx | 6 +++--- .../03-payments-use-case/03-ledger.mdx | 4 ++-- content/academy/icm-chainlink/index.mdx | 20 ++++++++++--------- .../02-l1-creation/07-convert-subnet-l1.mdx | 8 +++++--- .../01-add-validator.mdx | 9 +++++---- .../academy/l1-validator-management/index.mdx | 10 ++++++---- .../01-building-programs-on-blockchain.mdx | 16 ++++++++------- content/academy/solidity-foundry/index.mdx | 10 ++++++---- 10 files changed, 55 insertions(+), 42 deletions(-) diff --git a/content/academy/avacloudapis/index.mdx b/content/academy/avacloudapis/index.mdx index 2e1406ceabf..4beefc53396 100644 --- a/content/academy/avacloudapis/index.mdx +++ b/content/academy/avacloudapis/index.mdx @@ -6,18 +6,20 @@ authors: [owenwahlgren] icon: Smile --- +import GlossaryTerm from '@/components/ui/glossary-term' + ![](/course-banner/avacloudapis.jpg) ## Why Take This Course? -[AvaCloud APIs](https://developers.avacloud.io/introduction), built by [AvaCloud](https://avacloud.io/), provides Web3 developers with multi-chain data from Avalanche’s primary network and other Avalanche L1s. With the AvaCloud API, you can easily build products that utilize real-time and historical transaction data, transfer records, native and token balances, and various types of token metadata. +[AvaCloud APIs](https://developers.avacloud.io/introduction), built by [AvaCloud](https://avacloud.io/), provides Web3 developers with multi-chain data from Avalanche's Primary Network and other Avalanche L1s. With the AvaCloud API, you can easily build products that utilize real-time and historical transaction data, transfer records, native and token balances, and various types of token metadata. ## Course Content - [AvaCloud API Overview](/academy/avacloudapis/02-overview/01-about) - [Environment Setup](/academy/avacloudapis/03-environment-setup/01-avacloud-account) - [Build an ERC-20 Token Balance App](/academy/avacloudapis/04-erc20-token-balance-app/01-overview) -- [Build a Wallet Portfolio App](/academy/avacloudapis/05-wallet-portfolio-app/01-overview) -- [Build a Basic Block Explorer](/academy/avacloudapis/06-block-explorer-app/01-overview) +- [Build a Wallet Portfolio App](/academy/avacloudapis/05-wallet-portfolio-app/01-overview) +- [Build a Basic Block Explorer](/academy/avacloudapis/06-block-explorer-app/01-overview) ## Prerequisites diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx index 082db915a01..3d86a0c129b 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx @@ -11,7 +11,7 @@ import GlossaryTerm from '@/components/ui/glossary-term' Blockchains have unique properties that make them an excellent fit for certain use cases where security, transparency, and decentralization are paramount: ### Finance -Blockchains enable secure, transparent transactions without the need for intermediaries. This is the foundation of cryptocurrency and Decentralized Finance (DeFi) platforms. The immutability of blockchain records ensures that financial transactions are tamper-proof and can be audited at any time, making it ideal for high-stakes environments where trust is critical. +Blockchains enable secure, transparent transactions without the need for intermediaries. This is the foundation of cryptocurrency and Decentralized Finance (DeFi) platforms. The immutability of blockchain records ensures that financial transactions are tamper-proof and can be audited at any time, making it ideal for high-stakes environments where trust is critical. ### Supply Chain Management Blockchain can provide an immutable record of a product's journey from origin to consumer, increasing transparency and reducing fraud. This helps ensure that every step of the supply chain is accurately tracked and verified. @@ -21,6 +21,6 @@ Blockchain's transparency and security ensure that votes are accurately counted ## Downsides -However, the same properties that make blockchains so powerful in these areas also introduce significant challenges. Blockchains are inherently less efficient than traditional databases because they require consensus among distributed nodes, which can slow down transaction speeds and increase the complexity of operations. This makes blockchain less suitable for use cases where high speed and efficiency are critical, such as real-time data processing or high-frequency trading. Additionally, the complexity of developing and maintaining blockchain systems can be a barrier, particularly for applications that don't require the levels of security and decentralization that blockchains offer. +However, the same properties that make blockchains so powerful in these areas also introduce significant challenges. Blockchains are inherently less efficient than traditional databases because they require consensus among distributed nodes, which can slow down transaction speeds and increase the complexity of operations. This makes blockchain less suitable for use cases where high speed and efficiency are critical, such as real-time data processing or high-frequency trading. Additionally, the complexity of developing and maintaining blockchain systems can be a barrier, particularly for applications that don't require the levels of security and decentralization that blockchains offer. -When deciding whether to use blockchain consider whether your use case requires the specific advantages of decentralization, transparency, and security. Blockchain is well-suited for applications where trust between parties is a major concern and where an immutable record of transactions is essential. However, if your application demands high throughput, real-time processing, or simplicity, a traditional centralized system might be more appropriate. In short, blockchain is a powerful tool for the right situations, but its use should be carefully considered against the specific needs of your application. \ No newline at end of file +When deciding whether to use blockchain consider whether your use case requires the specific advantages of decentralization, transparency, and security. Blockchain is well-suited for applications where trust between parties is a major concern and where an immutable record of transactions is essential. However, if your application demands high throughput, real-time processing, or simplicity, a traditional centralized system might be more appropriate. In short, blockchain is a powerful tool for the right situations, but its use should be carefully considered against the specific needs of your application. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx index 7dde5216096..a4ba04e61e6 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx @@ -8,7 +8,7 @@ icon: Book import GlossaryTerm from '@/components/ui/glossary-term' -In this chapter we will dive deeper in the payments use case. We will explore how blockchain technology can be used to build a decentralized payment system. We will look at the different components of a payment system, such as account balances, transactions, and user interactions. We will also discuss the benefits of using blockchain technology for payments, such as security, transparency, and decentralization. +In this chapter we will dive deeper in the payments use case. We will explore how blockchain technology can be used to build a decentralized payment system. We will look at the different components of a payment system, such as account balances, transactions, and user interactions. We will also discuss the benefits of using blockchain technology for payments, such as security, transparency, and decentralization. | Use Case | Data Structures | User Interactions | |----------------------- |------------------ |-------------------- | @@ -18,6 +18,6 @@ In this chapter we will dive deeper in the payments use case. We will explore ho | Supply Chain | Shipments | Hand Over, Deliver | | Identity Management | Certificates | Issue, Proof | -Many of the concepts we will discuss in this chapter are applicable to other use cases as well. For example, the idea of account balances and transactions is not unique to payments but can be found in other applications like Decentralized Finance (DeFi) or supply chain management. Similarly, user interactions such as transferring funds or voting can be applied to various use cases, each with its unique requirements and challenges. +Many of the concepts we will discuss in this chapter are applicable to other use cases as well. For example, the idea of account balances and transactions is not unique to payments but can be found in other applications like Decentralized Finance (DeFi) or supply chain management. Similarly, user interactions such as transferring funds or voting can be applied to various use cases, each with its unique requirements and challenges. -So while we are discussing this specific use case, try to think about how these concepts could be adapted to other scenarios. This will help you understand the broader implications of blockchain technology and how it can be used to solve a wide range of problems across different industries and domains. \ No newline at end of file +So while we are discussing this specific use case, try to think about how these concepts could be adapted to other scenarios. This will help you understand the broader implications of blockchain technology and how it can be used to solve a wide range of problems across different industries and domains. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx index 1ff2ebbc526..155f63d93dd 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx @@ -14,8 +14,8 @@ A ledger is a comprehensive record-keeping system t ## Immutability -An immutable ledger means that once a transaction is recorded, it cannot be altered or deleted. This immutability ensures that the historical record of all transactions remains intact and unchangeable, which is crucial for maintaining transparency and trust. Even if errors are made or transactions are invalid, the ledger preserves the original data, preventing tampering or unauthorized modifications. +An immutable ledger means that once a transaction is recorded, it cannot be altered or deleted. This immutability ensures that the historical record of all transactions remains intact and unchangeable, which is crucial for maintaining transparency and trust. Even if errors are made or transactions are invalid, the ledger preserves the original data, preventing tampering or unauthorized modifications. ## Append-Only -An append-only ledger operates by adding new transactions to the end of the record without altering any previous entries. This means that while the ledger grows with each new transaction, past transactions remain unchanged and preserved. Invalid transactions, which fail to execute due to issues like insufficient funds, are still recorded in the ledger to maintain a complete history. To reverse the effects of a transaction, a new transaction must be appended that counteracts the previous one, ensuring the integrity and consistency of the ledger's overall state. \ No newline at end of file +An append-only ledger operates by adding new transactions to the end of the record without altering any previous entries. This means that while the ledger grows with each new transaction, past transactions remain unchanged and preserved. Invalid transactions, which fail to execute due to issues like insufficient funds, are still recorded in the ledger to maintain a complete history. To reverse the effects of a transaction, a new transaction must be appended that counteracts the previous one, ensuring the integrity and consistency of the ledger's overall state. \ No newline at end of file diff --git a/content/academy/icm-chainlink/index.mdx b/content/academy/icm-chainlink/index.mdx index 9531d6ece64..549d5833321 100644 --- a/content/academy/icm-chainlink/index.mdx +++ b/content/academy/icm-chainlink/index.mdx @@ -6,11 +6,13 @@ authors: [martineckardt] icon: Smile --- -In this course, you will learn how to integrate your own blockchain with the Chainlink services that are deployed on C-chain. To do this, we will use Avalanche Interchain Messaging and Chainlink VRF. +import GlossaryTerm from '@/components/ui/glossary-term' + +In this course, you will learn how to integrate your own blockchain with the Chainlink services that are deployed on C-Chain. To do this, we will use Avalanche Interchain Messaging and Chainlink Verifiable Random Function (VRF). ## Why Take This Course? -As the blockchain ecosystem grows, developers require robust tools to build secure, scalable, and innovative applications. Chainlink provides a suite of decentralized services, including VRF (Verifiable Random Function), Automation, Chainlink Functions, and CCIP (Cross-Chain Interoperability Protocol), to empower developers in creating high-performance, trustless applications. These services are not integrated by default on Avalanche L1 chains. However, Avalanche’s Interchain Messaging (ICM) enables developers to consume Chainlink services, typically available on the C-Chain, directly within their own L1 environments. +As the blockchain ecosystem grows, developers require robust tools to build secure, scalable, and innovative applications. Chainlink provides a suite of decentralized services, including VRF (Verifiable Random Function), Automation, Chainlink Functions, and Cross-Chain Interoperability Protocol (CCIP), to empower developers in creating high-performance, trustless applications. These services are not integrated by default on Avalanche L1 chains. However, Avalanche's Interchain Messaging (ICM) enables developers to consume Chainlink services, typically available on the C-Chain, directly within their own L1 environments. This course equips you with the knowledge to integrate all Chainlink services into your Avalanche L1 blockchain. You will start with Chainlink VRF and progressively expand to advanced features like Automation for task scheduling, Functions for off-chain data computations, and CCIP for bridging data between Ethereum and Avalanche. We suggest you to revisit this course as we will keep on adding new content. @@ -18,7 +20,7 @@ This course equips you with the knowledge to integrate all Chainlink services in ### Introduction -Overview of Chainlink services and their role in decentralized applications. Importance of integrating these tools into Avalanche L1 chains. +Overview of Chainlink services and their role in decentralized applications. Importance of integrating these tools into Avalanche L1 chains. ### Chainlink VRF @@ -30,22 +32,22 @@ Overview of off-chain computation and API integrations. Implementing Functions f ### Chainlink Automation -Using Automation for task scheduling. Examples include automated smart contracts and dynamic pricing. +Using Automation for task scheduling. Examples include automated Smart Contracts and dynamic pricing. ### Chainlink CCIP -Bridging data and assets between Ethereum and Avalanche L1. Practical applications such as cross-chain governance and token transfers. +Bridging data and assets between Ethereum and Avalanche L1. Practical applications such as cross-chain governance and token transfers. ## Prerequisites -Avalanche Interchain Messaging (ICM): A solid understanding of Avalanche’s ICM protocol is essential. You should have completed the ICM course, which covers: +Avalanche Interchain Messaging (ICM): A solid understanding of Avalanche's ICM protocol is essential. You should have completed the ICM course, which covers: - The fundamentals of cross-chain communication in Avalanche - Message formats and flows - Security techniques for interchain messaging Blockchain and Development Knowledge -- Solidity: Familiarity with the language’s key concepts, especially those related to smart contract interactions and randomness. +- Solidity: Familiarity with the language's key concepts, especially those related to smart contract interactions and randomness. - Oracles: While we will cover the basic components of Chainlink's VRF, having a sense of oracles is desirable. If any of this is unclear, we strongly recommend taking the Avalanche Interchain Messaging course first. @@ -54,7 +56,7 @@ If any of this is unclear, we strongly recommend taking the Avalanche Interchain By the end of this course, students will: -- Understand the mechanics of Chainlink VRF and other Chainlink Services and its significance in decentralized applications. +- Understand the mechanics of Chainlink VRF and other Chainlink Services and its significance in decentralized applications. - Gain proficiency in setting up Avalanche L1 chains with Chainlink services enabled. - Integrate Chainlink VRF with Avalanche ICM for secure cross-chain randomness. - Use Chainlink functions for Off-chain data integration with on-chain logic. @@ -62,4 +64,4 @@ By the end of this course, students will: - Cross-Chain communication with ecosystems outside Avalanche trough Chainlink's CCIP - Apply best practices to ensure reliability, security, and cost-efficiency in their applications. -This course prepares developers to leverage Chainlink’s powerful suite of tools for building next-generation blockchain solutions on Avalanche L1. +This course prepares developers to leverage Chainlink's powerful suite of tools for building next-generation blockchain solutions on Avalanche L1. diff --git a/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx b/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx index 959735c8596..7eb2c5e4fd1 100644 --- a/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx +++ b/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx @@ -6,15 +6,17 @@ authors: [owenwahlgren] icon: SquareMousePointer --- +import GlossaryTerm from '@/components/ui/glossary-term' + The node you have just launched is tracking the Subnet but is not yet a validator. In fact, since the Subnet does not have any validators yet it cannot process any transactions. In this step we will do two things at once: -1. Convert the Subnet to an L1 +1. Convert the Subnet to an Avalanche L1 2. Add your node as a validator -Converting a Subnet to an L1 requires the Subnet owner issuing a `ConvertSubnetToL1Tx` transaction -on the P-Chain. This transaction establishes a new validator set for your blockchain and transforms +Converting a Subnet to an Avalanche L1 requires the Subnet owner issuing a `ConvertSubnetToL1Tx` transaction +on the Platform Chain. This transaction establishes a new validator set for your blockchain and transforms it from a Subnet into a sovereign L1 chain. The `ConvertSubnetToL1Tx` transaction is a one-time transaction that can only be executed once by the Subnet owner(s). diff --git a/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx b/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx index ca1edf18c9f..9122c16c444 100644 --- a/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx +++ b/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx @@ -8,21 +8,22 @@ icon: UserPlus import ToolboxMdxWrapper from "../../../../toolbox/src/demo/ui/ToolboxMdxWrapper.tsx" import AddValidator from "../../../../toolbox/src/demo/examples/ValidatorManager/AddValidator.tsx" +import GlossaryTerm from '@/components/ui/glossary-term' -To add a validator to your Avalanche L1, you need to call the `initiateValidatorRegistration` function on the `ValidatorManager` contract. +To add a validator to your Avalanche L1, you need to call the `initiateValidatorRegistration` function on the `ValidatorManager` contract. This function will kick off the registration process for a new validator. The process includes the following steps: 1. The L1 emits a `L1ValidatorRegistrationMessage` Warp message in the transaction logs. 2. Request an aggregated signature of the message from the L1's validators. -3. Submit the signed message to the P-Chain in a `L1ValidatorRegistration` transaction. -4. The wait for the transaction to be committed on the P-Chain. +3. Submit the signed message to the Platform Chain in a `L1ValidatorRegistration` transaction. +4. The wait for the transaction to be committed on the Platform Chain. 5. Construct a `RegisterL1ValidatorMessage` Warp message. 6. Request an aggregated signature of the `RegisterL1ValidatorMessage` Warp message from the L1's validators. 7. Submit the signed `RegisterL1ValidatorMessage` to the `ValidatorManager` contract in a `completeValidatorRegistration` transaction. -In short, the L1 does a round trip message with the P-Chain to register the validator. +In short, the L1 does a round trip message with the Platform Chain to register the validator. \ No newline at end of file diff --git a/content/academy/l1-validator-management/index.mdx b/content/academy/l1-validator-management/index.mdx index 91abe2ee35a..7c52e1bb2f2 100644 --- a/content/academy/l1-validator-management/index.mdx +++ b/content/academy/l1-validator-management/index.mdx @@ -6,9 +6,11 @@ authors: [owenwahlgren] icon: Smile --- +import GlossaryTerm from '@/components/ui/glossary-term' + ## 🏔️ L1 Validator Management -Welcome to the **L1 Validator Management** course! This course is designed to give you a deep understanding of validator management on Avalanche L1s. By the end of this course, you will have practical skills in deploying an L1 and managing the validator set in a Proof of Authority (PoA) network. +Welcome to the **L1 Validator Management** course! This course is designed to give you a deep understanding of validator management on Avalanche L1s. By the end of this course, you will have practical skills in deploying an L1 and managing the validator set in a Proof of Authority (PoA) network. ### 📚 What You'll Learn @@ -18,9 +20,9 @@ This comprehensive course will walk you through: - 🛠️ **L1 Creation and Configuration** - Setting up your chain - 📋 **Deploying the Validator Manager** - Implementing ACP99 - 👥 **Validator Management Operations** - Adding, removing, and configuring validators -- 💰 **Proof of Stake Deployment** - Deploying a Staking Manager -- 🎁 **Proof of Stake Rewards Distribution** - Implementing reward systems -- ⛓️ **Validator Manager on the C-Chain** - Advanced operations +- 💰 **Proof of Stake Deployment** - Deploying a Staking Manager +- 🎁 **Proof of Stake Rewards Distribution** - Implementing reward systems +- ⛓️ **Validator Manager on the C-Chain** - Advanced operations ### 🚀 Let's Get Started! diff --git a/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx b/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx index 346c434840f..6d0fb33ba57 100644 --- a/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx +++ b/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx @@ -6,18 +6,20 @@ authors: [Andrea Vargas, Ash] icon: Book --- -First off, thank you for enrolling in this course! We assume that you are taking this course in order to learn how to write smart contracts. This begs the question - what are smart contracts? +import GlossaryTerm from '@/components/ui/glossary-term' -From a high-level, you may have heard that smart contracts are just code that automate a process. Want to create a decentralized insurance protocol? You can build a smart contract for that. Want to create and distribute NFTs? You can also build a smart contract for that as well. So while we might understand the capabilities of a smart contract, this course will be focused on defining the actual code (and therefore, business logic) required for such intents. +First off, thank you for enrolling in this course! We assume that you are taking this course in order to learn how to write Smart Contracts. This begs the question - what are smart contracts? -## The EVM Model +From a high-level, you may have heard that smart contracts are just code that automate a process. Want to create a decentralized insurance protocol? You can build a smart contract for that. Want to create and distribute NFTs? You can also build a smart contract for that as well. So while we might understand the capabilities of a smart contract, this course will be focused on defining the actual code (and therefore, business logic) required for such intents. + +## The EVM Model In this course, we will learn Solidity, a high-level programming language that we will use to design smart contracts. Before we delve into learning Solidity, it is important to understand how our smart contracts operate in the grand scheme of things. Smart contracts are defined by the following: their behaviors and their state. Focusing first on the behaviors of a smart contract, this is simply the functions that one can call on the smart contracts. Examples of such behaviors can be found below: -- __Tokens__: behaviors include creating tokens, transferring them, getting the balances of token holders -- __Decentralized Exchange__: behaviors include swapping tokens, adding liquidity to a pool, getting the adresses of both tokens of a liquidity pools -- __DAO__: behaviors include submitting a proposal, voting on a proposal, checking if someone is a governance member +- __Tokens__: behaviors include creating tokens, transferring them, getting the balances of token holders +- __Decentralized Exchange__: behaviors include swapping tokens, adding liquidity to a pool, getting the adresses of both tokens of a liquidity pools +- __DAO__: behaviors include submitting a proposal, voting on a proposal, checking if someone is a governance member We now focus on the state of a contract. Abstractly, we can define the state of a contract as being the values and stateful data structures that are associated with said contract. Examples of the state of a smart contract are listed below: @@ -25,4 +27,4 @@ We now focus on the state of a contract. Abstractly, we can define the state of - __Decentralized Exchange__: the number of tokens of a liquidity pool, the amount of tokens a liquidity provider is entitled to - __DAO__: a list of all governance members, a list of all outstanding proposals -Understanding what a smart contract under the EVM model consists of, we are now ready to understand the relationship between Solidity and the underlying blockchain. \ No newline at end of file +Understanding what a smart contract under the EVM model consists of, we are now ready to understand the relationship between Solidity and the underlying blockchain. \ No newline at end of file diff --git a/content/academy/solidity-foundry/index.mdx b/content/academy/solidity-foundry/index.mdx index 076c87ae1d3..b8336600b09 100644 --- a/content/academy/solidity-foundry/index.mdx +++ b/content/academy/solidity-foundry/index.mdx @@ -6,11 +6,13 @@ authors: [Andrea Vargas] icon: Smile --- -In this course, you will learn how to build Solidity dApps on Avalanche. +import GlossaryTerm from '@/components/ui/glossary-term' + +In this course, you will learn how to build Solidity dApps on Avalanche. ## Why Take This Course? -A significant innovation in blockchain is the development of multi-chain systems, like Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. While a blockchain on Avalanche can be run with any VM, the most prominent choice currently is the Ethereum Virtual Machine (EVM). Users can deploy their own logic in the form of smart contracts to the EVM. +A significant innovation in blockchain is the development of multi-chain systems, like Avalanche, which provide a significant improvement in scalability, interoperability, and flexibility. While a blockchain on Avalanche can be run with any VM, the most prominent choice currently is the Ethereum Virtual Machine (EVM). Users can deploy their own logic in the form of Smart Contracts to the EVM. These smart contracts can be written in Solidity. Learning Solidity can enable you to leverage the features of blockchain for your dApp. @@ -32,7 +34,7 @@ You will learn how contracts can be standardized and how inheritance and interfa ### Blockchain / Web3 This course is meant for people with a some experience when it comes to web3. You should be familiar with these concepts: -- Wallet: What they are and how to create one +- Wallet: What they are and how to create one - dApp: What a decentralized application is and how to interact with one If any of this is unclear, we strongly recommend taking the Avalanche Fundamentals and Subnet Architecture courses first, that give a soft introduction into these topics from a user stand point. @@ -47,6 +49,6 @@ You will need a general understanding of Software Development. Therefore, we rec By the end of this course, students will: - Interact and Deploy contracts using Foundry -- Get familiar with ERC20 and ERC721 token standards +- Get familiar with ERC20 and Non-Fungible Token (ERC721) token standards - Understand important concepts such as inheritance, modifiers, and events. - Apply their knowledge by building their own smart contracts. From 78735a60ab146abc8f3865901df64a0838c23feb Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Wed, 9 Apr 2025 14:02:23 +0200 Subject: [PATCH 17/27] delete the older glossary --- .../avalanche-fundamentals/glossary.mdx | 29 ----------- .../academy/avalanche-fundamentals/meta.json | 1 - .../blockchain-fundamentals/glossary.mdx | 48 ------------------- .../academy/blockchain-fundamentals/meta.json | 1 - 4 files changed, 79 deletions(-) delete mode 100644 content/academy/avalanche-fundamentals/glossary.mdx delete mode 100644 content/academy/blockchain-fundamentals/glossary.mdx diff --git a/content/academy/avalanche-fundamentals/glossary.mdx b/content/academy/avalanche-fundamentals/glossary.mdx deleted file mode 100644 index 87a7bdb7e15..00000000000 --- a/content/academy/avalanche-fundamentals/glossary.mdx +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Avalanche Glossary -description: Key terms and concepts in the Avalanche ecosystem -updated: 2024-05-31 -authors: [ashucoder9] -icon: Book ---- -> **Note:** For general blockchain and DeFi terminology, please refer to the [Blockchain Glossary](/academy/blockchain-fundamentals/glossary). - -| Term | Abbreviation | Previous Term | Description | -|------|--------------|---------------|-------------| -| Avalanche Consensus | | | A family of consensus protocols that power the Avalanche network, known for high throughput, fast finality, and energy efficiency. The X-Chain uses the core Avalanche consensus protocol, while the P-Chain and C-Chain use the Snowman variant. [Learn more](/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro). | -| Avalanche L1 | L1 | Subnet | An independent, sovereign blockchain network on Avalanche that can have its own validator set, tokenomics, and rules. Avalanche L1s work together to form the broader Avalanche Network. [Learn more](/docs/quick-start/avalanche-l1s). | -| Avalanche Virtual Machine | AVM | | The virtual machine implementation that powers the X-Chain, handling operations on Avalanche Native Tokens. | -| Contract Chain | C-Chain | | An implementation of the Ethereum Virtual Machine (EVM) that supports the deployment and execution of smart contracts written in Solidity. Uses the Coreth Virtual Machine. [Learn more](/docs/quick-start/primary-network#c-chain). | -| Coreth | | | The virtual machine implementation that powers the C-Chain, enabling Ethereum compatibility on Avalanche. | -| Exchange Chain | X-Chain | | Responsible for operations on digital smart assets known as Avalanche Native Tokens. Uses the Avalanche Virtual Machine (AVM). [Learn more](/docs/quick-start/primary-network#x-chain). | -| Interchain Messaging | ICM | Teleporter | A protocol that enables communication between blockchains on Avalanche, allowing for secure message passing between different L1s. [Learn more](/academy/interchain-messaging). | -| Interchain Token Transfer | ICTT | | A system that allows tokens to be transferred seamlessly between different Avalanche L1s, enabling greater interoperability within the ecosystem. [Learn more](/academy/interchain-token-transfer). | -| Platform Chain | P-Chain | | Responsible for all validator and Avalanche L1-level operations, including staking, creating new blockchains, and other platform-level functions. Uses the Platform Virtual Machine. [Learn more](/docs/quick-start/primary-network#p-chain). | -| Platform Virtual Machine | | | The virtual machine implementation that powers the P-Chain, handling staking, validator, and Avalanche L1 operations. | -| Primary Network | | | A special Avalanche L1 that runs three blockchains: the P-Chain, C-Chain, and X-Chain. All validators on the Primary Network must stake at least 2,000 AVAX. [Learn more](/docs/quick-start/primary-network). | -| Snowman Consensus | | | A linear chain-optimized variant of the Avalanche consensus protocol used specifically by the P-Chain and C-Chain. Designed for smart contract chains and platform operations. [Learn more](/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus). | - -## Why Terminology Matters - -Understanding these terms is essential for effective communication within the Avalanche ecosystem. The recent terminology changes better reflect the technical architecture and capabilities of the Avalanche platform as it continues to evolve. - -As you progress through this course, you'll gain a deeper understanding of these concepts and how they fit into the broader Avalanche ecosystem. \ No newline at end of file diff --git a/content/academy/avalanche-fundamentals/meta.json b/content/academy/avalanche-fundamentals/meta.json index 6a24676482f..8d2809658b4 100644 --- a/content/academy/avalanche-fundamentals/meta.json +++ b/content/academy/avalanche-fundamentals/meta.json @@ -4,7 +4,6 @@ "root": true, "pages": [ "index", - "glossary", "---Primer on Avalanche Consensus---", "...02-avalanche-consensus-intro", "---Multi-Chain Architecture---", diff --git a/content/academy/blockchain-fundamentals/glossary.mdx b/content/academy/blockchain-fundamentals/glossary.mdx deleted file mode 100644 index 12db8950f12..00000000000 --- a/content/academy/blockchain-fundamentals/glossary.mdx +++ /dev/null @@ -1,48 +0,0 @@ ---- -title: Blockchain Glossary -description: General terms and concepts in blockchain technology and decentralized finance -updated: 2024-05-31 -authors: [ashucoder9] -icon: Book ---- - -| Term | Abbreviation | Description | -|------|--------------|-------------| -| Annual Percentage Rate | APR | The annual return you will receive on an investment, without accounting for the effects of compounding. | -| Annual Percentage Yield | APY | The annual return you will receive on an investment when returns are compounded. Unlike APR, APY includes the effects of compounding. | -| Arbitrage | | The practice of buying and selling assets between different markets to profit from price discrepancies. For example, buying a token on one exchange where it's cheaper and selling it on another where it's more expensive. | -| Automated Market Maker | AMM | A protocol that uses liquidity pools and mathematical formulas to automatically determine asset prices and enable trading without traditional order books. | -| Block | | A collection of transactions that are grouped together and added to the blockchain. Each block typically contains a reference to the previous block, creating a chain. | -| Blockchain | | A distributed ledger technology that records transactions across multiple computers in a way that ensures security, transparency, and immutability. | -| Compounding | | The process where earnings from an asset are reinvested to generate additional returns over time, creating exponential growth. | -| Consensus Mechanism | | The method by which network participants agree on the valid state of the blockchain. Examples include Proof of Work, Proof of Stake, and Avalanche Consensus. | -| Cross-Chain Interoperability Protocol | CCIP | A protocol that enables communication between different blockchains. Allows for the transfer of messages, tokens, and data across separate blockchain networks. Most commonly associated with Chainlink's cross-chain communication solution. | -| Cryptocurrency | | A digital or virtual currency that uses cryptography for security and operates independently of a central authority. | -| Decentralized Application | dApp | An application that runs on a decentralized network rather than being controlled by a single entity or authority. | -| Decentralized Autonomous Organization | DAO | An organization governed by rules encoded as smart contracts on a blockchain, without centralized leadership. Members collectively make decisions through voting mechanisms. | -| Decentralized Exchange | DEX | A peer-to-peer marketplace where users can trade cryptocurrencies directly with each other without an intermediary. These exchanges use smart contracts to execute trades. | -| Decentralized Finance | DeFi | A financial system built on blockchain technology that aims to recreate and improve upon traditional financial services without central authorities or intermediaries. | -| Gas | | The fee required to perform a transaction or execute a contract on a blockchain network. Gas is used to allocate resources of the blockchain's virtual machine. | -| Hash | | A function that converts input data to a fixed-size string of characters. Blockchain uses hash functions to ensure data integrity and security. | -| Liquidity | | The ease with which an asset can be converted to cash or traded without affecting its market price. Higher liquidity means the asset can be exchanged more easily. | -| Liquidity Pool | | A collection of tokens or assets locked in a smart contract, providing liquidity for decentralized exchanges and other DeFi applications. | -| Mining | | The process by which new transactions are verified and added to a blockchain using a Proof of Work consensus mechanism. Miners solve complex puzzles to earn rewards. | -| Multi-signature | Multisig | A security feature that requires multiple signatures (approvals) to execute a transaction. This provides enhanced security for wallets and contracts. | -| Node | | A computer that participates in a blockchain network by maintaining a copy of the blockchain, relaying information, and validating transactions. Nodes work together to ensure the network's security and functionality. | -| Non-Fungible Token | NFT | A unique digital asset that represents ownership of a specific item or piece of content on the blockchain. Unlike cryptocurrencies, NFTs are not interchangeable. | -| Private Key | | A secret code that allows access to cryptocurrency holdings. It's used to sign transactions and should never be shared. | -| Public Key | | A cryptographic code derived from a private key that serves as a public address where others can send cryptocurrency. | -| Smart Contract | | Self-executing code on a blockchain that automatically implements the terms of an agreement when predetermined conditions are met, without requiring intermediaries. | -| Stablecoin | | A type of cryptocurrency designed to minimize price volatility by pegging its value to a stable asset (like fiat currency) or using algorithmic methods to control supply. | -| Staking | | The process of actively participating in transaction validation on a proof-of-stake blockchain by locking up cryptocurrency to support network operations. | -| Token | | A digital asset built on an existing blockchain. Tokens can represent various assets or utilities within a specific ecosystem or platform. | -| Validator | | A specialized type of node that actively participates in the consensus process by validating transactions, producing blocks, and securing the network. Validators typically stake cryptocurrency as collateral to ensure honest behavior. | -| Verifiable Random Function | VRF | A cryptographic function that provides verifiable randomness. Used in blockchain protocols to generate unpredictable but verifiable random values. Important for applications requiring fair random selection like lottery systems, NFT distributions, or validator selection in some consensus mechanisms. | -| Virtual Machine | VM | A computing environment that executes code and maintains state. In blockchain, VMs define a blockchain's application logic, including state transitions, transaction rules, and smart contract execution. VMs serve as the blueprint for a blockchain's functionality. | -| Wallet | | A digital tool that allows users to store and manage their cryptocurrency assets. Wallets can be hardware devices, software applications, or services. | - -## Why Understanding Terminology Matters - -Blockchain technology introduces many new concepts and terms. Understanding this terminology is essential for effectively navigating the blockchain ecosystem, participating in projects, and communicating with others in the space. - -As you progress through this course, you'll encounter and gain a deeper understanding of these concepts and how they interconnect within the broader blockchain landscape. \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/meta.json b/content/academy/blockchain-fundamentals/meta.json index 74fa111c558..a8f20f1d596 100644 --- a/content/academy/blockchain-fundamentals/meta.json +++ b/content/academy/blockchain-fundamentals/meta.json @@ -4,7 +4,6 @@ "root": true, "pages": [ "index", - "glossary", "---What is a Blockchain?---", "...02-what-is-a-blockchain", "---Payments---", From 42668f36767e4ef881a62bed9cc24a8acc6f53b0 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 20:18:45 +0200 Subject: [PATCH 18/27] nothing, just deployment vercel --- .../01-avalanche-consensus-intro.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx index b88e11e9828..bc065227083 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx @@ -7,7 +7,7 @@ icon: Book --- import GlossaryTerm from '@/components/ui/glossary-term' - + Avalanche Consensus is a novel consensus protocol that is used in the Avalanche network. It is a leaderless, decentralized, and scalable consensus protocol that is used to achieve consensus on the state of the network. From df180c2f8454d0eeaeb5990c3d6e9a03052b6812 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 20:27:13 +0200 Subject: [PATCH 19/27] fix type glossary --- types/glossary.ts | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 types/glossary.ts diff --git a/types/glossary.ts b/types/glossary.ts new file mode 100644 index 00000000000..a9795aa1e43 --- /dev/null +++ b/types/glossary.ts @@ -0,0 +1,7 @@ +export interface GlossaryTerm { + term: string; + abbreviation?: string; + previousTerm?: string; + description: string; + learnMoreUrl?: string; +} \ No newline at end of file From 1a818a6e10ae35b9950898e254200c5c9881b826 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 20:34:18 +0200 Subject: [PATCH 20/27] fix2 type glossary --- types/glossary.ts | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/types/glossary.ts b/types/glossary.ts index a9795aa1e43..0d4995c94c9 100644 --- a/types/glossary.ts +++ b/types/glossary.ts @@ -1,7 +1,8 @@ export interface GlossaryTerm { term: string; - abbreviation?: string; - previousTerm?: string; + abbreviation?: string | null; + previousTerm?: string | null; description: string; learnMoreUrl?: string; + category: string; } \ No newline at end of file From 3671ff2a6974e00597919bb2d7638930a541dbf6 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 21:27:31 +0200 Subject: [PATCH 21/27] fix3 type glossary --- types/glossary.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/types/glossary.ts b/types/glossary.ts index 0d4995c94c9..183374aead0 100644 --- a/types/glossary.ts +++ b/types/glossary.ts @@ -3,6 +3,6 @@ export interface GlossaryTerm { abbreviation?: string | null; previousTerm?: string | null; description: string; - learnMoreUrl?: string; + learnMoreUrl?: string | null; category: string; } \ No newline at end of file From c128b5d5735cf7718758807a3d9f3901d9e302f0 Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 21:53:48 +0200 Subject: [PATCH 22/27] fix3 --- components/{ui => content-design}/glossary-term.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename components/{ui => content-design}/glossary-term.tsx (98%) diff --git a/components/ui/glossary-term.tsx b/components/content-design/glossary-term.tsx similarity index 98% rename from components/ui/glossary-term.tsx rename to components/content-design/glossary-term.tsx index 0c638b728a1..95fb41f5db6 100644 --- a/components/ui/glossary-term.tsx +++ b/components/content-design/glossary-term.tsx @@ -12,7 +12,7 @@ interface GlossaryTermProps { className?: string } -export function GlossaryTerm({ +function GlossaryTerm({ children, termKey, className = "" From 672a7e466a5e662e725f0f75b48b760fce9e55bb Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 22:00:08 +0200 Subject: [PATCH 23/27] fix4 --- content/academy/avacloudapis/index.mdx | 2 +- .../01-avalanche-consensus-intro.mdx | 2 +- .../02-avalanche-consensus-intro/02-consensus-mechanisms.mdx | 2 +- .../02-avalanche-consensus-intro/03-snowman-consensus.mdx | 2 +- .../02-avalanche-consensus-intro/04-tps-vs-ttf.mdx | 2 +- .../01-multi-chain-architecture.mdx | 2 +- .../03-multi-chain-architecture-intro/02-subnet.mdx | 2 +- .../03-multi-chain-architecture-intro/03-benefits.mdx | 2 +- .../04-creating-a-blockchain/01-creating-a-blockchain.mdx | 2 +- .../04-creating-a-blockchain/03-create-on-avacloud.mdx | 2 +- .../05-vms-and-blockchains/01-vms-and-blockchains.mdx | 2 +- .../05-vms-and-blockchains/03-blockchains.mdx | 2 +- .../06-vm-customization/00-vm-customization.mdx | 2 +- .../06-vm-customization/01-configuration.mdx | 2 +- content/academy/avalanche-fundamentals/index.mdx | 2 +- .../02-what-is-a-blockchain/01-what-is-a-blockchain.mdx | 2 +- .../02-what-is-a-blockchain/02-decentralized-computer.mdx | 2 +- .../02-what-is-a-blockchain/03-decentralized-applications.mdx | 2 +- .../02-what-is-a-blockchain/04-use-cases.mdx | 2 +- .../03-payments-use-case/01-payments-use-case.mdx | 2 +- .../03-payments-use-case/02-account-balances-transfers.mdx | 2 +- .../blockchain-fundamentals/03-payments-use-case/03-ledger.mdx | 2 +- .../blockchain-fundamentals/04-signatures/01-signatures.mdx | 2 +- .../04-signatures/xx-signature-schemes.mdx | 2 +- .../01-tx-ordering-through-consensus.mdx | 2 +- .../02-longest-chain-consensus.mdx | 2 +- .../04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx | 2 +- .../05-sybil-protection/01-sybil-protection.mdx | 2 +- .../05-sybil-protection/02-proof-of-work.mdx | 2 +- .../05-sybil-protection/03-proof-of-stake.mdx | 2 +- .../06-smart-contracts/01-smart-contracts.mdx | 2 +- content/academy/blockchain-fundamentals/index.mdx | 2 +- content/academy/blockchain-fundamentals/xx-decentralization.mdx | 2 +- .../blockchain-fundamentals/xx-regulation/01-regulation.mdx | 2 +- content/academy/blockchain-fundamentals/xx-tokens.mdx | 2 +- .../customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx | 2 +- .../customizing-evm/06-precompiles/01-what-are-precompiles.mdx | 2 +- .../customizing-evm/06-precompiles/02-why-precompiles.mdx | 2 +- .../08-calculator-precompile/02-generating-precompile.mdx | 2 +- .../10-stateful-counter-precompile/03-implement-set-counter.mdx | 2 +- content/academy/customizing-evm/index.mdx | 2 +- content/academy/icm-chainlink/index.mdx | 2 +- .../01-interopability-between-blockchains.mdx | 2 +- .../02-interoperability/03-multi-chain-networks.mdx | 2 +- .../14-access-chainlink-vrf-services/01-introduction.mdx | 2 +- content/academy/interchain-messaging/index.mdx | 2 +- .../academy/interchain-token-transfer/03-tokens/01-tokens.mdx | 2 +- .../interchain-token-transfer/03-tokens/02-native-tokens.mdx | 2 +- .../interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx | 2 +- .../06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx | 2 +- .../06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx | 2 +- content/academy/interchain-token-transfer/index.mdx | 2 +- content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx | 2 +- .../l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx | 2 +- .../l1-tokenomics/05-transaction-fees/01-introduction.mdx | 2 +- .../05-transaction-fees/02-transaction-fee-configuration.mdx | 2 +- .../02-l1-creation/07-convert-subnet-l1.mdx | 2 +- .../04-validator-management/01-add-validator.mdx | 2 +- content/academy/l1-validator-management/index.mdx | 2 +- .../02-custom-blockchains/01-custom-blockchains.mdx | 2 +- .../02-custom-blockchains/02-benefits-of-custom-blockchains.mdx | 2 +- .../02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx | 2 +- .../03-avalanche-starter-kit/01-avalanche-starter-kit.mdx | 2 +- .../04-independent-tokenomics/01-independent-tokenomics.mdx | 2 +- .../07-permissioning-validators/01-permissioning-validators.mdx | 2 +- .../multi-chain-architecture/08-customizability/00-intro.mdx | 2 +- content/academy/multi-chain-architecture/index.mdx | 2 +- .../03-smart-contracts/01-building-programs-on-blockchain.mdx | 2 +- content/academy/solidity-foundry/index.mdx | 2 +- .../common/avalanche-starter-kit/create-default-blockchain.mdx | 2 +- content/common/cryptography/multi-signature-schemes.mdx | 2 +- content/common/cryptography/signature-schemes.mdx | 2 +- content/common/evm-precompiles/precompiles.mdx | 2 +- .../common/multi-chain-architecture/etna-upgrade-motivation.mdx | 2 +- content/common/multi-chain-architecture/transaction-fees.mdx | 2 +- content/common/primary-network/p-chain.mdx | 2 +- content/docs/quick-start/avalanche-l1s.mdx | 2 +- content/docs/quick-start/primary-network.mdx | 2 +- content/docs/tooling/create-avalanche-l1.mdx | 2 +- content/guides/etna-changes.mdx | 2 +- content/guides/l1-validator-fee.mdx | 2 +- content/guides/subnet-vs-l1-validators.mdx | 2 +- content/guides/use-privy-on-l1.mdx | 2 +- content/guides/what-is-a-blockchain.mdx | 2 +- 84 files changed, 84 insertions(+), 84 deletions(-) diff --git a/content/academy/avacloudapis/index.mdx b/content/academy/avacloudapis/index.mdx index 4beefc53396..688a52829f6 100644 --- a/content/academy/avacloudapis/index.mdx +++ b/content/academy/avacloudapis/index.mdx @@ -6,7 +6,7 @@ authors: [owenwahlgren] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ![](/course-banner/avacloudapis.jpg) ## Why Take This Course? diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx index bc065227083..4744bf97dbe 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx index 4c94a0ce900..1debd41d42a 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Consensus plays a crucial role in [blockchain networks](/guides/what-is-a-blockchain) by resolving conflicts and ensuring that all validators agree on the current state of the distributed ledger. The main objective of a Consensus Mechanism is to create a single version of truth that is universally accepted by network participants. diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx index f1f5b9e34a4..2f2fc66858f 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Protocols in the Avalanche Consensus family operate through repeated sub-sampled voting. When a validator is determining whether a Block should be accepted, it asks a small, random subset of validators on their preferences. Based on the responses the validator gets, it might change its own preference. diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx index 7247b5949d8..148267b296b 100644 --- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx +++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' To measure blockchain performance we can use two metrics: diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx index 687f69a0e04..c5a7ce5b7fb 100644 --- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx +++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Multi-chain systems are a significant innovation, which provide greater scalability, customizability, and independence. At the core of multi-chain systems is the ability to run multiple blockchains simultaneously. Each blockchain is optimized for specialized use cases, thereby boosting the network's overall performance. diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx index cef03306662..43dc1ebdd68 100644 --- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx +++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' An Avalanche L1 is a network with its own set of rules regarding membership, token economics, and execution layer. It is composed of a Subset of Avalanche validators collaborating to achieve consensus on the state of one or more blockchains. Validators can be members of numerous Avalanche L1s. diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx index 4289fc1c477..1e9b8929a84 100644 --- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx +++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Avalanche L1s are autonomous. Their creators can define their execution logic, set their own fees, manage their state, handle their networking, and ensure their security. They operate independently from other Avalanche L1s and the Primary Network, effectively enabling the greater Avalanche network to scale while delivering the benefits of lower latency, higher transactions per second (TPS), and lower transaction costs. diff --git a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx index ecda9b375d4..9a37f3fc905 100644 --- a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx +++ b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Now that we've gone over what an Avalanche L1 is and what the benefits of creating an Avalanche L1 on Avalanche are, you are probably eager to test out the functionality of Avalanche L1s by creating one yourself! diff --git a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx index 9360fea7766..6f0f3cf827f 100644 --- a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx +++ b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx @@ -7,7 +7,7 @@ icon: Terminal --- import { Step, Steps } from 'fumadocs-ui/components/steps'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this section, we will get our first taste of deploying an Avalanche L1. diff --git a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx index 3c89ca53220..a505551fc8a 100644 --- a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx +++ b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx index 1734c2f85f1..5ea872f67ad 100644 --- a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx +++ b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Let's look at how VMs work in blockchain. Each validator operates an instance of our hypothetical soda dispenser. So, they have their own instance of a machine running on their server. They do this so they do not have to trust a single party with the operation of a soda dispenser, and to make it easy for everyone to verify the outcome of operations. diff --git a/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx b/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx index ea2798b4bf7..2bd42ea53f7 100644 --- a/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx +++ b/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx b/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx index ce40e2fae49..448d782b08e 100644 --- a/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx +++ b/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' When building a VM, it is possible to define certain parameters that can change the behavior of the VM. In our soda dispenser analogy these may be the products and prices offered by the dispenser. We might want to have two dispenser blockchains that offer different products and prices. If the VM is built in a way that it has parameters for the products and prices, it can be easily reused for different use items. diff --git a/content/academy/avalanche-fundamentals/index.mdx b/content/academy/avalanche-fundamentals/index.mdx index 598cf86c7fa..4ac8b13b15e 100644 --- a/content/academy/avalanche-fundamentals/index.mdx +++ b/content/academy/avalanche-fundamentals/index.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Welcome to the Avalanche Fundamentals, an online course introducing you to the exciting world of the Avalanche technology! This course will provide you with a comprehensive understanding of the basic concepts making Avalanche unique. diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx index b96a6211929..ec5500ad259 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Blockchains introduce a lot of new concepts. In this chapter we will approach the concept from a high level and see how it compares with other kinds of computers we are used to: diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx index 88d4a196fd1..688af61c0d6 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' We interact with various types of computers every day, each designed to serve specific functions based on its unique characteristics. Smartphones, for example, are portable and convenient, offering powerful computing capabilities in a compact form. They are ideal for tasks that require mobility, such as communication, navigation, and media consumption. However, their small screen size and limited processing power compared to larger computers make them less suitable for tasks that require intensive computing power or extensive multitasking. PCs, on the other hand, provide more robust processing power and versatility. They are well-suited for tasks like video editing, gaming, or software development, where performance and the ability to use larger screens and peripherals like a mouse and keyboard are crucial. Yet, they lack the portability of smartphones and often require more space and power to operate. diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx index bc4355a988f..cefed1aeca9 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Programs and apps are software applications designed to run on different types of computers, such as smartphones, PCs, and web servers. On smartphones, apps are typically designed for specific tasks like messaging, gaming, or social media, optimized for touch interfaces and mobile connectivity. PCs run more complex programs, such as word processors, video editors, or development tools, which take advantage of larger screens, more powerful hardware, and the ability to handle multitasking. Web servers, on the other hand, run server-side applications that power websites, process data, and handle multiple user requests simultaneously. These programs often provide the backend services that apps on smartphones and PCs rely on to function. diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx index 3d86a0c129b..8b9cbf083ee 100644 --- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx +++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Blockchains have unique properties that make them an excellent fit for certain use cases where security, transparency, and decentralization are paramount: diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx index a4ba04e61e6..c509c8900f4 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this chapter we will dive deeper in the payments use case. We will explore how blockchain technology can be used to build a decentralized payment system. We will look at the different components of a payment system, such as account balances, transactions, and user interactions. We will also discuss the benefits of using blockchain technology for payments, such as security, transparency, and decentralization. diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx index 59d639b16b1..22983140ee3 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Account Balances diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx index 155f63d93dd..c9dac51853a 100644 --- a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx +++ b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' A ledger is a comprehensive record-keeping system that documents all transactions. It maintains a detailed and chronological list of transactions, capturing every transfers across accounts. This ensures that every action is accurately tracked and traceable, providing a clear and complete view of the system's activity. diff --git a/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx b/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx index 09ed08fb1b2..9e4340cca77 100644 --- a/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx +++ b/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx @@ -6,6 +6,6 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Coming soon \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx b/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx index 0be66ce5374..71b76446509 100644 --- a/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx +++ b/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Notebook --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' While transactions on ledgers in the analogue world were often authorized by hand-written signatures, that is not going to work for the adoption in blockchain. To utilize the concept of a ledger in the modern age, we leverage cryptography instead. diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx index 635a13efb9d..18e31a203ac 100644 --- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx +++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx @@ -6,4 +6,4 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx index 9fcbc16517d..9c7f0266f06 100644 --- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx +++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx @@ -6,4 +6,4 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx index 6029cd91003..d259eabccf5 100644 --- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx +++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Notebook --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Creation diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx index 58a3f52959c..268d06886b8 100644 --- a/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx +++ b/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx @@ -6,5 +6,5 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx index bd2d034e970..3e43c43983f 100644 --- a/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx +++ b/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx @@ -6,4 +6,4 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' \ No newline at end of file +import GlossaryTerm from '@/components/content-design/glossary-term' \ No newline at end of file diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx index b050dfe46e0..d8058453965 100644 --- a/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx +++ b/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' - Carrots and Sticks diff --git a/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx b/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx index 909bdfc9ade..c9d0349da6f 100644 --- a/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx +++ b/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx @@ -6,4 +6,4 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/blockchain-fundamentals/index.mdx b/content/academy/blockchain-fundamentals/index.mdx index 1ad2dae869d..1bad6bf97c0 100644 --- a/content/academy/blockchain-fundamentals/index.mdx +++ b/content/academy/blockchain-fundamentals/index.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Welcome to the Blockchain Fundamentals, an online course introducing you to blockchain! This course will provide you with a comprehensive understanding of the basic concepts of blockchains. diff --git a/content/academy/blockchain-fundamentals/xx-decentralization.mdx b/content/academy/blockchain-fundamentals/xx-decentralization.mdx index fb3b378dcc9..56db4b262ba 100644 --- a/content/academy/blockchain-fundamentals/xx-decentralization.mdx +++ b/content/academy/blockchain-fundamentals/xx-decentralization.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Moving from a centralized Entity to a Collective of Validators diff --git a/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx b/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx index c8ae80be25d..f10537c4954 100644 --- a/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx +++ b/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx @@ -6,4 +6,4 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/blockchain-fundamentals/xx-tokens.mdx b/content/academy/blockchain-fundamentals/xx-tokens.mdx index f35a06a0b3c..e25d8d823e5 100644 --- a/content/academy/blockchain-fundamentals/xx-tokens.mdx +++ b/content/academy/blockchain-fundamentals/xx-tokens.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Notebook --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Tokens are a concept that existed in societies for a long time. diff --git a/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx b/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx index 7083a607a70..441f6948d5c 100644 --- a/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx +++ b/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9, owenwahlgren] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' The **Ethereum Virtual Machine (EVM)** is a fundamental component of Ethereum's infrastructure, responsible for executing Smart Contracts across the network. The origins of the EVM can be traced back to the creation of the Ethereum blockchain itself, proposed in a whitepaper by **Vitalik Buterin** in late 2013. diff --git a/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx b/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx index f90cec7f228..6e8384f4b51 100644 --- a/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx +++ b/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx @@ -5,7 +5,7 @@ updated: 2024-05-31 authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Precompiled contracts allow the execution of code written in the low-level programming language Go from the EVM, which is significantly faster and more efficient than Solidity. diff --git a/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx b/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx index 7323ecbf3f5..ca3dca980b5 100644 --- a/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx +++ b/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx @@ -5,7 +5,7 @@ updated: 2024-05-31 authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Adding precompiles to the EVM offers several significant advantages, which we will outline in this chapter. diff --git a/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx b/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx index d1c83b6556e..661f0d8553b 100644 --- a/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx +++ b/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx @@ -5,7 +5,7 @@ updated: 2024-05-31 authors: [ashucoder9] icon: Terminal --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this step, we will again utilize the precompile generation script to generate all the Go files based on the ABI for your calculator. diff --git a/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx b/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx index e7f6b225044..fdf97a17fb1 100644 --- a/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx +++ b/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx @@ -5,7 +5,7 @@ updated: 2024-05-31 authors: [ashucoder9] icon: Terminal --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Having seen how strings are stored in `StringStore`, its time for us to store integers with Counter. The thought process for this section can be defined as follows: diff --git a/content/academy/customizing-evm/index.mdx b/content/academy/customizing-evm/index.mdx index 38ad7059620..e1ff7662be1 100644 --- a/content/academy/customizing-evm/index.mdx +++ b/content/academy/customizing-evm/index.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9, owenwahlgren] icon: Smile --- import { Step, Steps } from 'fumadocs-ui/components/steps'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Why take this Course? diff --git a/content/academy/icm-chainlink/index.mdx b/content/academy/icm-chainlink/index.mdx index 549d5833321..92b0d8fedde 100644 --- a/content/academy/icm-chainlink/index.mdx +++ b/content/academy/icm-chainlink/index.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this course, you will learn how to integrate your own blockchain with the Chainlink services that are deployed on C-Chain. To do this, we will use Avalanche Interchain Messaging and Chainlink Verifiable Random Function (VRF). diff --git a/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx b/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx index 872950c3749..44be86bc398 100644 --- a/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx +++ b/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx @@ -5,7 +5,7 @@ updated: 2024-05-31 authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' diff --git a/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx b/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx index 6e9c7c5a148..478cd8aa998 100644 --- a/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx +++ b/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx @@ -5,7 +5,7 @@ updated: 2024-05-31 authors: [martineckardt] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ![](/common-images/multi-chain-architecture/subnets.png) diff --git a/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx b/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx index 833239b1e5e..42772c014cf 100644 --- a/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx +++ b/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx @@ -6,7 +6,7 @@ authors: [0xstt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' As decentralized applications (dApps) expand across multiple blockchains, some Layer 1 (L1) networks lack direct support from essential services like **Chainlink VRF (Verifiable Random Functions)**. This presents a significant challenge for developers who rely on verifiable randomness for use cases such as gaming, lotteries, NFT minting, and other decentralized functions that require unbiased, unpredictable random numbers. diff --git a/content/academy/interchain-messaging/index.mdx b/content/academy/interchain-messaging/index.mdx index e543a8ca920..f356a649434 100644 --- a/content/academy/interchain-messaging/index.mdx +++ b/content/academy/interchain-messaging/index.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this course, you will learn how to build cross-L1 Solidity dApps with Interchain Messaging and Avalanche Warp Messaging. diff --git a/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx index f059f58f1be..87445654514 100644 --- a/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx +++ b/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## What You Will Learn diff --git a/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx index 5c4484306ac..6f59e0bbcfc 100644 --- a/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx +++ b/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' A native token in a blockchain running the EVM refers to the primary digital currency or cryptocurrency native to the EVM blockchain. Every EVM layer 1 chain has it's own native token: diff --git a/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx index 6079a4eb4c2..79f24e9dd81 100644 --- a/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx +++ b/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' There is only a single native token to a chain. However, to allow to represent a wide range of assets on EVM-chains, the ERC-20 token standard was developed. "ERC" stands for Ethereum Request for Comment, and "20" is the proposal identifier. diff --git a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx index 988afe5386e..f2c32ed5d25 100644 --- a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx +++ b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx @@ -8,7 +8,7 @@ icon: Book import { Step, Steps } from 'fumadocs-ui/components/steps'; import Link from 'next/link'; import { buttonVariants } from '@/components/ui/button.tsx' -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Transfer an ERC-20 Token → Avalanche L1 as an ERC-20 Token diff --git a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx index 3515b0ecaf4..56c323e060e 100644 --- a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx +++ b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx @@ -7,7 +7,7 @@ icon: Terminal --- import { Step, Steps } from 'fumadocs-ui/components/steps'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' To ensure the wrapped token is bridged into the destination chain (in this case, C-Chain) you'll need to deploy a _remote_ contract that implements the `IERC20Bridge` interface, as well as inheriting the properties of `TeleporterTokenRemote`. In order for the bridged tokens to have all the normal functionality of a locally deployed ERC20 token, this remote contract must also inherit the properties of a standard `ERC20` contract. diff --git a/content/academy/interchain-token-transfer/index.mdx b/content/academy/interchain-token-transfer/index.mdx index 5b5ebab6214..7ca85a2ab95 100644 --- a/content/academy/interchain-token-transfer/index.mdx +++ b/content/academy/interchain-token-transfer/index.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this course, you will learn how to transfer assets across multiple Avalanche blockchains with Avalanche Interchain Token Transfer ICTT. diff --git a/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx b/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx index c6bd17c3e1f..8cec73c400f 100644 --- a/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx +++ b/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx @@ -5,7 +5,7 @@ updated: 2024-09-03 authors: [0xstt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In many networks, such as Ethereum, the same token is used for both Staking and paying for Gas. However, in the Avalanche network, staking tokens and gas tokens can be separated, as they fulfill different purposes within the blockchain ecosystem. diff --git a/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx b/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx index bfdd796d33e..08fd55eed75 100644 --- a/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx +++ b/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx @@ -6,7 +6,7 @@ authors: [0xstt] icon: Book --- import { Steps, Step } from 'fumadocs-ui/components/steps'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' The contracts in the [`validator-manager`](https://github.com/ava-labs/teleporter/tree/validator-manager/contracts/validator-manager) branch define the Validator Manager used to manage Subnet-only Validators, as defined in ACP-77. `ValidatorManager.sol` is the top-level abstract contract that provides the basic functionality. The other contracts are related as follows: diff --git a/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx b/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx index 4b515bd6180..a3b36068d28 100644 --- a/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx +++ b/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx @@ -6,7 +6,7 @@ authors: [0xstt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ### Background When creating an Avalanche L1 we cannot only configure our custom native token, but also how the transaction fees (also known as gas fees) are determined. This allows Avalanche L1s to define the desired or maximal throughput of the blockchain differently. diff --git a/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx b/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx index 2b10ec516ed..b8da2c0cc25 100644 --- a/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx +++ b/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx @@ -6,7 +6,7 @@ authors: [0xstt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Configuration Format diff --git a/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx b/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx index 7eb2c5e4fd1..7260526a7f1 100644 --- a/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx +++ b/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx @@ -6,7 +6,7 @@ authors: [owenwahlgren] icon: SquareMousePointer --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' The node you have just launched is tracking the Subnet but is not yet a validator. In fact, since the Subnet does not have any validators yet it cannot process any transactions. In this step we will do two diff --git a/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx b/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx index 9122c16c444..89715ed3bf4 100644 --- a/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx +++ b/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx @@ -8,7 +8,7 @@ icon: UserPlus import ToolboxMdxWrapper from "../../../../toolbox/src/demo/ui/ToolboxMdxWrapper.tsx" import AddValidator from "../../../../toolbox/src/demo/examples/ValidatorManager/AddValidator.tsx" -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' To add a validator to your Avalanche L1, you need to call the `initiateValidatorRegistration` function on the `ValidatorManager` contract. diff --git a/content/academy/l1-validator-management/index.mdx b/content/academy/l1-validator-management/index.mdx index 7c52e1bb2f2..e7c62caa1cd 100644 --- a/content/academy/l1-validator-management/index.mdx +++ b/content/academy/l1-validator-management/index.mdx @@ -6,7 +6,7 @@ authors: [owenwahlgren] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## 🏔️ L1 Validator Management diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx index 3ce11f7b692..2fc614b2a7a 100644 --- a/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx +++ b/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx @@ -6,7 +6,7 @@ authors: [usmaneth] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' An Avalanche L1 is a sovereign network that defines its own rules for membership and token economics. It's validated by a dynamic subset of Avalanche validators working together to achieve consensus on the blockchain's state. diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx index 17d7af3493d..bde1d5c20b7 100644 --- a/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx +++ b/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx @@ -6,7 +6,7 @@ authors: [usmaneth] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Custom blockchains offer a range of advantages for developers and businesses looking to create very custom & tailored solutions. diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx index 34635dbfc4e..78cc9c2f195 100644 --- a/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx +++ b/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx @@ -6,7 +6,7 @@ authors: [usmaneth] icon: BookOpen --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Layer 2 blockchain solutions, such as rollups, are another innovation in the blockchain landscape. Layer 2s aim to enhance the scalability and performance of the Ethereum network. Rollups essentially perform computations off-chain and submit the resultant state changes to the base layer, thereby reducing the computational load on the main Ethereum chain. diff --git a/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx b/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx index 4a2c1645585..eb5830f07f8 100644 --- a/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx +++ b/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx @@ -6,7 +6,7 @@ authors: [martineckardt] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' To make easier your journey through this course, we have prepared a Starter Kit repo consisting of everything you will need to start developing your own custom blockchains on Avalanche. This repo will provide a self-contained environment with Avalanche-CLI, and Foundry so you can follow the course without the need of installing anything else other than launching the environment. diff --git a/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx b/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx index d685f2e07ec..f2e5ca36868 100644 --- a/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx +++ b/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx @@ -6,7 +6,7 @@ authors: [usmaneth] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Avalanche Custom Blockchains offer multiple ways to implement independent tokenomics. This gives developers more control and can enable new business model that would not be economically feasible on single-chain systems. diff --git a/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx b/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx index 4de1c69251b..a4cdfc3fdce 100644 --- a/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx +++ b/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx @@ -6,7 +6,7 @@ authors: [usmaneth] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' The ability to control a blockchain's validator set has many benefits that can significantly enhance the efficiency, security, and governance of the network. It allows blockchain participants to have greater influence over the consensus process and decision-making, leading to a more robust and adaptable ecosystem. There are two ways to structure the validator set: diff --git a/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx b/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx index ea08f359dd1..b73c9de3b98 100644 --- a/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx +++ b/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx @@ -6,7 +6,7 @@ authors: [ashucoder9] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' For some use cases, it may be necessary to use a customized VM instead of the EVM. This is the case if an application cannot be built on a regular EVM on the C-Chain, or if it would result in transaction fee costs too high to be economical for its users or creators. diff --git a/content/academy/multi-chain-architecture/index.mdx b/content/academy/multi-chain-architecture/index.mdx index faedb32bc90..2f138992629 100644 --- a/content/academy/multi-chain-architecture/index.mdx +++ b/content/academy/multi-chain-architecture/index.mdx @@ -6,7 +6,7 @@ authors: [usmaneth] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Are you ready to dive deeper into the fascinating world of Avalanche? This course will equip you with a comprehensive understanding of the Avalanche's Multi Blockchain architecture, along with the practical skills required to create and manage custom blockchains. diff --git a/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx b/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx index 6d0fb33ba57..56a5118f888 100644 --- a/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx +++ b/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx @@ -6,7 +6,7 @@ authors: [Andrea Vargas, Ash] icon: Book --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' First off, thank you for enrolling in this course! We assume that you are taking this course in order to learn how to write Smart Contracts. This begs the question - what are smart contracts? diff --git a/content/academy/solidity-foundry/index.mdx b/content/academy/solidity-foundry/index.mdx index b8336600b09..ff7766280f9 100644 --- a/content/academy/solidity-foundry/index.mdx +++ b/content/academy/solidity-foundry/index.mdx @@ -6,7 +6,7 @@ authors: [Andrea Vargas] icon: Smile --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this course, you will learn how to build Solidity dApps on Avalanche. diff --git a/content/common/avalanche-starter-kit/create-default-blockchain.mdx b/content/common/avalanche-starter-kit/create-default-blockchain.mdx index d476cd778bc..ec96aaae3f9 100644 --- a/content/common/avalanche-starter-kit/create-default-blockchain.mdx +++ b/content/common/avalanche-starter-kit/create-default-blockchain.mdx @@ -1,5 +1,5 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' > In the following commands, make sure to substitute the name of your Avalanche L1 for `` (including the `<>`). You can choose whatever name you want, but I recommend using `myblockchain` as the name to avoid the need for some manual configuration. diff --git a/content/common/cryptography/multi-signature-schemes.mdx b/content/common/cryptography/multi-signature-schemes.mdx index 506a193f904..3cb020624c7 100644 --- a/content/common/cryptography/multi-signature-schemes.mdx +++ b/content/common/cryptography/multi-signature-schemes.mdx @@ -1,4 +1,4 @@ -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Multi-signature schemes, also known as Multi-signature, are cryptographic methods enabling multiple parties to collectively authorize a specific action or operation, typically by requiring a predefined number of authorized participants to provide their digital signatures. In a multi-signature scheme, each authorized party possesses their own Private Key, and to validate the action. A specified subset of these parties must produce their unique signatures. diff --git a/content/common/cryptography/signature-schemes.mdx b/content/common/cryptography/signature-schemes.mdx index 8ffa4f11b0d..7cc99abc77c 100644 --- a/content/common/cryptography/signature-schemes.mdx +++ b/content/common/cryptography/signature-schemes.mdx @@ -1,6 +1,6 @@ import { buttonVariants } from '@/components/ui/button'; import { cn } from '@/utils/cn'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Signature schemes are cryptographic schemes, that allow us to sign some piece of data, and someone else can verify our signature. Think of signature schemes as a very modern version of signing for example a contract, which does not rely on your unique hand movement, but on math. There are many different signature schemes. They vary in efficiency and security. diff --git a/content/common/evm-precompiles/precompiles.mdx b/content/common/evm-precompiles/precompiles.mdx index 6e1383deac2..ec87510d0b8 100644 --- a/content/common/evm-precompiles/precompiles.mdx +++ b/content/common/evm-precompiles/precompiles.mdx @@ -1,4 +1,4 @@ -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Precompiled contracts are a way to execute code written in the low-level coding language Go from the EVM. Go is much faster and more efficient than Solidity. diff --git a/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx b/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx index a2dc4acc24f..1a74f48514f 100644 --- a/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx +++ b/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx @@ -1,5 +1,5 @@ import YouTube from '@/components/content-design/youtube'; -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' The Etna Upgrade will be the largest network upgrade of Avalanche to date. This upgrade will introduce a new concept called Layer 1 blockchains (L1s), which will replace the current Subnet model. In this article we will discuss the current limitations of Subnets, and how the changes suggested in ACP-77 ([ACP-77 Proposal](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md)) will address these limitations in the Etna Upgrade. diff --git a/content/common/multi-chain-architecture/transaction-fees.mdx b/content/common/multi-chain-architecture/transaction-fees.mdx index b1d9df6bb4d..d1ae7af14d6 100644 --- a/content/common/multi-chain-architecture/transaction-fees.mdx +++ b/content/common/multi-chain-architecture/transaction-fees.mdx @@ -1,4 +1,4 @@ -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' NFT collectors, Decentralized Finance traders, and Blockchain gamers have independently spent significant sums to execute their transactions. These unrelated activities converge on the blockchain, competing for the finite capacity of the next blockspace. In an effort to avoid delays or being outpaced by others, participants can be compelled to pay substantial fees to secure prompt transaction processing. diff --git a/content/common/primary-network/p-chain.mdx b/content/common/primary-network/p-chain.mdx index b4e5211e4fe..31902d9789d 100644 --- a/content/common/primary-network/p-chain.mdx +++ b/content/common/primary-network/p-chain.mdx @@ -1,4 +1,4 @@ -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In the Avalanche Network, the Platform Chain of the Primary Network is responsible for all Validator and Avalanche L1-level operations. The P-Chain supports the creation of new blockchains and Avalanche L1s, the addition of validators to Avalanche L1s, Staking operations, and other platform-level operations. diff --git a/content/docs/quick-start/avalanche-l1s.mdx b/content/docs/quick-start/avalanche-l1s.mdx index 7a75693c52a..f60bebd2743 100644 --- a/content/docs/quick-start/avalanche-l1s.mdx +++ b/content/docs/quick-start/avalanche-l1s.mdx @@ -3,7 +3,7 @@ title: Avalanche L1s description: Explore the multi-chain architecture of Avalanche ecosystem. --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' An Avalanche L1 is a sovereign network which defines its own rules regarding its membership and token economics. It is composed of a dynamic subset of Avalanche validators working together to achieve consensus on the state of one or more blockchains. Each blockchain is validated by exactly one Avalanche L1, while an Avalanche L1 can validate many blockchains. diff --git a/content/docs/quick-start/primary-network.mdx b/content/docs/quick-start/primary-network.mdx index b748f5a91b1..04265e694fa 100644 --- a/content/docs/quick-start/primary-network.mdx +++ b/content/docs/quick-start/primary-network.mdx @@ -3,7 +3,7 @@ title: Primary Network description: Learn about the Avalanche Primary Network and its three blockchains. --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' Avalanche is a heterogeneous network of blockchains. As opposed to homogeneous networks, where all applications reside in the same chain, heterogeneous networks allow separate chains to be created for different applications. diff --git a/content/docs/tooling/create-avalanche-l1.mdx b/content/docs/tooling/create-avalanche-l1.mdx index 703d47d7ac0..962da54620e 100644 --- a/content/docs/tooling/create-avalanche-l1.mdx +++ b/content/docs/tooling/create-avalanche-l1.mdx @@ -3,7 +3,7 @@ title: Create Avalanche L1 description: This page demonstrates how to create an Avalanche L1 using Avalanche-CLI. --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' This tutorial walks you through the process of using Avalanche-CLI to create an Avalanche L1, deploy it to a local network, and connect to it with Core wallet. diff --git a/content/guides/etna-changes.mdx b/content/guides/etna-changes.mdx index a0505f5fb89..4cf8d378278 100644 --- a/content/guides/etna-changes.mdx +++ b/content/guides/etna-changes.mdx @@ -6,7 +6,7 @@ authors: [meagfitzgerald] topics: [Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1] comments: true --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' This guide outlines the operational impact on existing network participants expected from the activation of the AvalancheGo "Etna Upgrade" upgrade. diff --git a/content/guides/l1-validator-fee.mdx b/content/guides/l1-validator-fee.mdx index be4b12537bc..fd8c2381955 100644 --- a/content/guides/l1-validator-fee.mdx +++ b/content/guides/l1-validator-fee.mdx @@ -6,7 +6,7 @@ authors: [meagfitzgerald] topics: [ Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1, L1 Validators, Continuous L1 Validation Fee] comments: true --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## What are L1 Validators? diff --git a/content/guides/subnet-vs-l1-validators.mdx b/content/guides/subnet-vs-l1-validators.mdx index a1b88da2b9d..c02e808b636 100644 --- a/content/guides/subnet-vs-l1-validators.mdx +++ b/content/guides/subnet-vs-l1-validators.mdx @@ -6,7 +6,7 @@ authors: [meagfitzgerald] topics: [Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1, L1 Validators, Subnet Validators] comments: true --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' The Etna Upgrade introduced L1s to the Avalanche network, providing an enhanced sovereign network design to the original Subnet model. diff --git a/content/guides/use-privy-on-l1.mdx b/content/guides/use-privy-on-l1.mdx index e411c8393e2..10438cd2c5a 100644 --- a/content/guides/use-privy-on-l1.mdx +++ b/content/guides/use-privy-on-l1.mdx @@ -6,7 +6,7 @@ authors: [satatocom] topics: [Avalanche L1, Avalanche Starter Kit, Magic Link, Social Login, Embedded Wallets] --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' In this guide, you will learn how to use Privy to easily onboard your users and create transactions without the need for any Web3 wallet. diff --git a/content/guides/what-is-a-blockchain.mdx b/content/guides/what-is-a-blockchain.mdx index 2cf123c31cc..71c9c307c56 100644 --- a/content/guides/what-is-a-blockchain.mdx +++ b/content/guides/what-is-a-blockchain.mdx @@ -6,7 +6,7 @@ authors: [martin_eckardt] topics: [Blockchain Basics] --- -import GlossaryTerm from '@/components/ui/glossary-term' +import GlossaryTerm from '@/components/content-design/glossary-term' ## Introduction to Different Types of Computers Computers are integral to our daily lives, and they come in various forms, each designed to serve specific purposes. Here's a quick overview: From 9c326e678827e87d2bd8c45c3b3bb6fc80ed2a6e Mon Sep 17 00:00:00 2001 From: federiconardelli7 Date: Mon, 28 Apr 2025 22:17:27 +0200 Subject: [PATCH 24/27] fix5 --- app/academy/[...slug]/page.tsx | 3 ++- app/docs/[...slug]/page.tsx | 2 ++ app/guides/[...slug]/page.tsx | 3 ++- 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/app/academy/[...slug]/page.tsx b/app/academy/[...slug]/page.tsx index c266ea9e6e4..d2496dd8f18 100644 --- a/app/academy/[...slug]/page.tsx +++ b/app/academy/[...slug]/page.tsx @@ -26,6 +26,7 @@ import { Heading } from 'fumadocs-ui/components/heading'; import Quiz from '@/components/quizzes/quiz'; import YouTube from "@/components/content-design/youtube"; import Gallery from "@/components/content-design/gallery"; +import GlossaryTerm from "@/components/content-design/glossary-term"; import { CodeBlock, type CodeBlockProps, @@ -79,7 +80,7 @@ export default async function Page(props: { h4: (props) => , h5: (props) => , h6: (props) => , - Cards, Card, Callout, Accordion, Accordions, AutoTypeTable, Gallery, Mermaid, Quiz, Popup, PopupContent, PopupTrigger, Step, Steps, Tab, Tabs, TypeTable, YouTube, + Cards, Card, Callout, Accordion, Accordions, AutoTypeTable, Gallery, GlossaryTerm, Mermaid, Quiz, Popup, PopupContent, PopupTrigger, Step, Steps, Tab, Tabs, TypeTable, YouTube, pre: ({ title, className, icon, allowCopy, ...props }: CodeBlockProps) => ( 
diff --git a/app/docs/[...slug]/page.tsx b/app/docs/[...slug]/page.tsx
index a48207441c0..57dfdbe654f 100644
--- a/app/docs/[...slug]/page.tsx
+++ b/app/docs/[...slug]/page.tsx
@@ -25,6 +25,7 @@ import { AutoTypeTable } from '@/components/content-design/type-table';
 import { BackToTop } from '@/components/ui/back-to-top';
 import { File, Folder, Files } from 'fumadocs-ui/components/files';
 import Mermaid from "@/components/content-design/mermaid";
+import GlossaryTerm from "@/components/content-design/glossary-term";
 import type { MDXComponents } from 'mdx/types';
 import YouTube from '@/components/content-design/youtube';
 import { Feedback } from '@/components/ui/feedback';
@@ -74,6 +75,7 @@ export default async function Page(props: {
             Step,
             Steps,
             YouTube,
+            GlossaryTerm,
             Mermaid,
             TypeTable,
             AutoTypeTable,
diff --git a/app/guides/[...slug]/page.tsx b/app/guides/[...slug]/page.tsx
index bb726b79f28..dda7585df24 100644
--- a/app/guides/[...slug]/page.tsx
+++ b/app/guides/[...slug]/page.tsx
@@ -16,6 +16,7 @@ import { AutoTypeTable } from '@/components/content-design/type-table';
 import { Heading } from 'fumadocs-ui/components/heading';
 import YouTube from "@/components/content-design/youtube";
 import Gallery from "@/components/content-design/gallery";
+import GlossaryTerm from "@/components/content-design/glossary-term";
 import { cn } from "@/utils/cn";
 import {
   CodeBlock,
@@ -73,7 +74,7 @@ export default async function Page(props: {
                 h4: (props) => ,
                 h5: (props) => ,
                 h6: (props) => ,
-                BadgeCheck, Cards, Card, Callout, Accordion, Accordions, AutoTypeTable, Gallery, Mermaid, Popup, PopupContent, PopupTrigger, Step, Steps, Tab, Tabs, TypeTable, YouTube, 
+                BadgeCheck, Cards, Card, Callout, Accordion, Accordions, AutoTypeTable, Gallery, GlossaryTerm, Mermaid, Popup, PopupContent, PopupTrigger, Step, Steps, Tab, Tabs, TypeTable, YouTube, 
                 pre: ({ title, className, icon, allowCopy, ...props }: CodeBlockProps) => (
                     
                     

From 239928acebbf0679eb90ff93e9aa4daee804f69d Mon Sep 17 00:00:00 2001
From: federiconardelli7 
Date: Mon, 28 Apr 2025 22:59:33 +0200
Subject: [PATCH 25/27] fix6

---
 mdx-components.tsx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/mdx-components.tsx b/mdx-components.tsx
index 0f7e7466cc5..6202b79de26 100644
--- a/mdx-components.tsx
+++ b/mdx-components.tsx
@@ -16,6 +16,7 @@ import "fumadocs-twoslash/twoslash.css";
 import { Popup, PopupContent, PopupTrigger } from "fumadocs-twoslash/ui";
 import YouTube from "@/components/content-design/youtube";
 import Gallery from "@/components/content-design/gallery";
+import GlossaryTerm from "@/components/content-design/glossary-term";
 import { cn } from "@/utils/cn";
 import { BadgeCheck } from "lucide-react";
 import dynamic from "next/dynamic";
@@ -49,6 +50,7 @@ export function useMDXComponents(components: MDXComponents): MDXComponents {
     YouTube,
     Gallery,
     Mermaid,
+    GlossaryTerm,
     InstallTabs: ({
       items,
       children,

From 847e1dfebd0adc51b9b33e84dfba8be47da249c7 Mon Sep 17 00:00:00 2001
From: federiconardelli7 
Date: Mon, 28 Apr 2025 23:14:50 +0200
Subject: [PATCH 26/27] fix7

---
 content/academy/avacloudapis/index.mdx                          | 2 +-
 .../01-avalanche-consensus-intro.mdx                            | 2 +-
 .../02-avalanche-consensus-intro/02-consensus-mechanisms.mdx    | 2 +-
 .../02-avalanche-consensus-intro/03-snowman-consensus.mdx       | 2 +-
 .../02-avalanche-consensus-intro/04-tps-vs-ttf.mdx              | 2 +-
 .../01-multi-chain-architecture.mdx                             | 2 +-
 .../03-multi-chain-architecture-intro/02-subnet.mdx             | 2 +-
 .../03-multi-chain-architecture-intro/03-benefits.mdx           | 2 +-
 .../04-creating-a-blockchain/01-creating-a-blockchain.mdx       | 2 +-
 .../04-creating-a-blockchain/03-create-on-avacloud.mdx          | 2 +-
 .../05-vms-and-blockchains/01-vms-and-blockchains.mdx           | 2 +-
 .../05-vms-and-blockchains/03-blockchains.mdx                   | 2 +-
 .../06-vm-customization/00-vm-customization.mdx                 | 2 +-
 .../06-vm-customization/01-configuration.mdx                    | 2 +-
 content/academy/avalanche-fundamentals/index.mdx                | 2 +-
 .../02-what-is-a-blockchain/01-what-is-a-blockchain.mdx         | 2 +-
 .../02-what-is-a-blockchain/02-decentralized-computer.mdx       | 2 +-
 .../02-what-is-a-blockchain/03-decentralized-applications.mdx   | 2 +-
 .../02-what-is-a-blockchain/04-use-cases.mdx                    | 2 +-
 .../03-payments-use-case/01-payments-use-case.mdx               | 2 +-
 .../03-payments-use-case/02-account-balances-transfers.mdx      | 2 +-
 .../blockchain-fundamentals/03-payments-use-case/03-ledger.mdx  | 2 +-
 .../blockchain-fundamentals/04-signatures/01-signatures.mdx     | 2 +-
 .../04-signatures/xx-signature-schemes.mdx                      | 2 +-
 .../01-tx-ordering-through-consensus.mdx                        | 2 +-
 .../02-longest-chain-consensus.mdx                              | 2 +-
 .../04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx        | 2 +-
 .../05-sybil-protection/01-sybil-protection.mdx                 | 2 +-
 .../05-sybil-protection/02-proof-of-work.mdx                    | 2 +-
 .../05-sybil-protection/03-proof-of-stake.mdx                   | 2 +-
 .../06-smart-contracts/01-smart-contracts.mdx                   | 2 +-
 content/academy/blockchain-fundamentals/index.mdx               | 2 +-
 content/academy/blockchain-fundamentals/xx-decentralization.mdx | 2 +-
 .../blockchain-fundamentals/xx-regulation/01-regulation.mdx     | 2 +-
 content/academy/blockchain-fundamentals/xx-tokens.mdx           | 2 +-
 .../customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx        | 2 +-
 .../customizing-evm/06-precompiles/01-what-are-precompiles.mdx  | 2 +-
 .../customizing-evm/06-precompiles/02-why-precompiles.mdx       | 2 +-
 .../08-calculator-precompile/02-generating-precompile.mdx       | 2 +-
 .../10-stateful-counter-precompile/03-implement-set-counter.mdx | 2 +-
 content/academy/customizing-evm/index.mdx                       | 2 +-
 content/academy/icm-chainlink/index.mdx                         | 2 +-
 .../01-interopability-between-blockchains.mdx                   | 2 +-
 .../02-interoperability/03-multi-chain-networks.mdx             | 2 +-
 .../14-access-chainlink-vrf-services/01-introduction.mdx        | 2 +-
 content/academy/interchain-messaging/index.mdx                  | 2 +-
 .../academy/interchain-token-transfer/03-tokens/01-tokens.mdx   | 2 +-
 .../interchain-token-transfer/03-tokens/02-native-tokens.mdx    | 2 +-
 .../interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx    | 2 +-
 .../06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx   | 2 +-
 .../06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx             | 2 +-
 content/academy/interchain-token-transfer/index.mdx             | 2 +-
 content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx  | 2 +-
 .../l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx  | 2 +-
 .../l1-tokenomics/05-transaction-fees/01-introduction.mdx       | 2 +-
 .../05-transaction-fees/02-transaction-fee-configuration.mdx    | 2 +-
 .../02-l1-creation/07-convert-subnet-l1.mdx                     | 2 +-
 .../04-validator-management/01-add-validator.mdx                | 2 +-
 content/academy/l1-validator-management/index.mdx               | 2 +-
 .../02-custom-blockchains/01-custom-blockchains.mdx             | 2 +-
 .../02-custom-blockchains/02-benefits-of-custom-blockchains.mdx | 2 +-
 .../02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx  | 2 +-
 .../03-avalanche-starter-kit/01-avalanche-starter-kit.mdx       | 2 +-
 .../04-independent-tokenomics/01-independent-tokenomics.mdx     | 2 +-
 .../07-permissioning-validators/01-permissioning-validators.mdx | 2 +-
 .../multi-chain-architecture/08-customizability/00-intro.mdx    | 2 +-
 content/academy/multi-chain-architecture/index.mdx              | 2 +-
 .../03-smart-contracts/01-building-programs-on-blockchain.mdx   | 2 +-
 content/academy/solidity-foundry/index.mdx                      | 2 +-
 .../common/avalanche-starter-kit/create-default-blockchain.mdx  | 2 +-
 content/common/cryptography/multi-signature-schemes.mdx         | 2 +-
 content/common/cryptography/signature-schemes.mdx               | 2 +-
 content/common/evm-precompiles/precompiles.mdx                  | 2 +-
 .../common/multi-chain-architecture/etna-upgrade-motivation.mdx | 2 +-
 content/common/multi-chain-architecture/transaction-fees.mdx    | 2 +-
 content/common/primary-network/p-chain.mdx                      | 2 +-
 content/docs/quick-start/avalanche-l1s.mdx                      | 2 +-
 content/docs/quick-start/primary-network.mdx                    | 2 +-
 content/docs/tooling/create-avalanche-l1.mdx                    | 2 +-
 content/guides/etna-changes.mdx                                 | 2 +-
 content/guides/l1-validator-fee.mdx                             | 2 +-
 content/guides/subnet-vs-l1-validators.mdx                      | 2 +-
 content/guides/use-privy-on-l1.mdx                              | 2 +-
 content/guides/what-is-a-blockchain.mdx                         | 2 +-
 84 files changed, 84 insertions(+), 84 deletions(-)

diff --git a/content/academy/avacloudapis/index.mdx b/content/academy/avacloudapis/index.mdx
index 688a52829f6..58d77867ff1 100644
--- a/content/academy/avacloudapis/index.mdx
+++ b/content/academy/avacloudapis/index.mdx
@@ -6,7 +6,7 @@ authors: [owenwahlgren]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ![](/course-banner/avacloudapis.jpg)
 ## Why Take This Course?
diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx
index 4744bf97dbe..5ee10f607b1 100644
--- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx
+++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/01-avalanche-consensus-intro.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
  
 
 
diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx
index 1debd41d42a..db9aa22dcd9 100644
--- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx
+++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/02-consensus-mechanisms.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Consensus plays a crucial role in [blockchain networks](/guides/what-is-a-blockchain) by resolving conflicts and ensuring that all validators agree on the current state of the distributed ledger. The main objective of a Consensus Mechanism is to create a single version of truth that is universally accepted by network participants.
 
diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx
index 2f2fc66858f..077fd0cd666 100644
--- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx
+++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/03-snowman-consensus.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Protocols in the Avalanche Consensus family operate through repeated sub-sampled voting. When a validator is determining whether a Block should be accepted, it asks a small, random subset of validators on their preferences. Based on the responses the validator gets, it might change its own preference.
 
diff --git a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx
index 148267b296b..a983d616324 100644
--- a/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx
+++ b/content/academy/avalanche-fundamentals/02-avalanche-consensus-intro/04-tps-vs-ttf.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 To measure blockchain performance we can use two metrics:
 
diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx
index c5a7ce5b7fb..86b79e27845 100644
--- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx
+++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/01-multi-chain-architecture.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Multi-chain systems are a significant innovation, which provide greater scalability, customizability, and independence. At the core of multi-chain systems is the ability to run multiple blockchains simultaneously. Each blockchain is optimized for specialized use cases, thereby boosting the network's overall performance.
 
diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx
index 43dc1ebdd68..bbc0187359f 100644
--- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx
+++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/02-subnet.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 An Avalanche L1 is a network with its own set of rules regarding membership, token economics, and execution layer. It is composed of a Subset of Avalanche validators collaborating to achieve consensus on the state of one or more blockchains. Validators can be members of numerous Avalanche L1s.
 
diff --git a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx
index 1e9b8929a84..f9a0bcaf450 100644
--- a/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx
+++ b/content/academy/avalanche-fundamentals/03-multi-chain-architecture-intro/03-benefits.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Avalanche L1s are autonomous. Their creators can define their execution logic, set their own fees, manage their state, handle their networking, and ensure their security. They operate independently from other Avalanche L1s and the Primary Network, effectively enabling the greater Avalanche network to scale while delivering the benefits of lower latency, higher transactions per second (TPS), and lower transaction costs.
 
diff --git a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx
index 9a37f3fc905..f6f220cd6ac 100644
--- a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx
+++ b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/01-creating-a-blockchain.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Now that we've gone over what an Avalanche L1 is and what the benefits of creating an Avalanche L1 on Avalanche are, you are probably eager to test out the functionality of Avalanche L1s by creating one yourself!
 
diff --git a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx
index 6f0f3cf827f..ef9542eec8e 100644
--- a/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx
+++ b/content/academy/avalanche-fundamentals/04-creating-a-blockchain/03-create-on-avacloud.mdx
@@ -7,7 +7,7 @@ icon: Terminal
 ---
 
 import { Step, Steps } from 'fumadocs-ui/components/steps';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this section, we will get our first taste of deploying an Avalanche L1. 
 
diff --git a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx
index a505551fc8a..3935f670c55 100644
--- a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx
+++ b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/01-vms-and-blockchains.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 
 
diff --git a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx
index 5ea872f67ad..20cbd04e657 100644
--- a/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx
+++ b/content/academy/avalanche-fundamentals/05-vms-and-blockchains/03-blockchains.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Let's look at how VMs work in blockchain. Each validator operates an instance of our hypothetical soda dispenser. So, they have their own instance of a machine running on their server. They do this so they do not have to trust a single party with the operation of a soda dispenser,  and to make it easy for everyone to verify the outcome of operations.
 
diff --git a/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx b/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx
index 2bd42ea53f7..441be33643b 100644
--- a/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx
+++ b/content/academy/avalanche-fundamentals/06-vm-customization/00-vm-customization.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 
 
diff --git a/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx b/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx
index 448d782b08e..72553181b74 100644
--- a/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx
+++ b/content/academy/avalanche-fundamentals/06-vm-customization/01-configuration.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 When building a VM, it is possible to define certain parameters that can change the behavior of the VM. In our soda dispenser analogy these may be the products and prices offered by the dispenser. We might want to have two dispenser blockchains that offer different products and prices. If the VM is built in a way that it has parameters for the products and prices, it can be easily reused for different use items.
 
diff --git a/content/academy/avalanche-fundamentals/index.mdx b/content/academy/avalanche-fundamentals/index.mdx
index 4ac8b13b15e..c86b35425e3 100644
--- a/content/academy/avalanche-fundamentals/index.mdx
+++ b/content/academy/avalanche-fundamentals/index.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Welcome to the Avalanche Fundamentals, an online course introducing you to the exciting world of the Avalanche technology! This course will provide you with a comprehensive understanding of the basic concepts making Avalanche unique.
 
diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx
index ec5500ad259..5960ebe0fd8 100644
--- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx
+++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/01-what-is-a-blockchain.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Blockchains introduce a lot of new concepts. In this chapter we will approach the concept from a high level and see how it compares with other kinds of computers we are used to:
 
diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx
index 688af61c0d6..941c8bd39aa 100644
--- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx
+++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/02-decentralized-computer.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 We interact with various types of computers every day, each designed to serve specific functions based on its unique characteristics. Smartphones, for example, are portable and convenient, offering powerful computing capabilities in a compact form. They are ideal for tasks that require mobility, such as communication, navigation, and media consumption. However, their small screen size and limited processing power compared to larger computers make them less suitable for tasks that require intensive computing power or extensive multitasking. PCs, on the other hand, provide more robust processing power and versatility. They are well-suited for tasks like video editing, gaming, or software development, where performance and the ability to use larger screens and peripherals like a mouse and keyboard are crucial. Yet, they lack the portability of smartphones and often require more space and power to operate.
 
diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx
index cefed1aeca9..f8f11f4c72d 100644
--- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx
+++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/03-decentralized-applications.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Programs and apps are software applications designed to run on different types of computers, such as smartphones, PCs, and web servers. On smartphones, apps are typically designed for specific tasks like messaging, gaming, or social media, optimized for touch interfaces and mobile connectivity. PCs run more complex programs, such as word processors, video editors, or development tools, which take advantage of larger screens, more powerful hardware, and the ability to handle multitasking. Web servers, on the other hand, run server-side applications that power websites, process data, and handle multiple user requests simultaneously. These programs often provide the backend services that apps on smartphones and PCs rely on to function.
 
diff --git a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx
index 8b9cbf083ee..33b47f274be 100644
--- a/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx
+++ b/content/academy/blockchain-fundamentals/02-what-is-a-blockchain/04-use-cases.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Blockchains have unique properties that make them an excellent fit for certain use cases where security, transparency, and decentralization are paramount:
 
diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx
index c509c8900f4..48c79cc7c0c 100644
--- a/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx
+++ b/content/academy/blockchain-fundamentals/03-payments-use-case/01-payments-use-case.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this chapter we will dive deeper in the payments use case. We will explore how blockchain technology can be used to build a decentralized payment system. We will look at the different components of a payment system, such as account balances, transactions, and user interactions. We will also discuss the benefits of using blockchain technology for payments, such as security, transparency, and decentralization.
 
diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx
index 22983140ee3..b63b4df2a77 100644
--- a/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx
+++ b/content/academy/blockchain-fundamentals/03-payments-use-case/02-account-balances-transfers.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Account Balances
 
diff --git a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx
index c9dac51853a..084bd71c5dc 100644
--- a/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx
+++ b/content/academy/blockchain-fundamentals/03-payments-use-case/03-ledger.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 A ledger is a comprehensive record-keeping system that documents all transactions. It maintains a detailed and chronological list of transactions, capturing every transfers across accounts. This ensures that every action is accurately tracked and traceable, providing a clear and complete view of the system's activity.
 
diff --git a/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx b/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx
index 9e4340cca77..8c1bbff9ab2 100644
--- a/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx
+++ b/content/academy/blockchain-fundamentals/04-signatures/01-signatures.mdx
@@ -6,6 +6,6 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Coming soon
\ No newline at end of file
diff --git a/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx b/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx
index 71b76446509..4407f1f8ea8 100644
--- a/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx
+++ b/content/academy/blockchain-fundamentals/04-signatures/xx-signature-schemes.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Notebook
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 While transactions on ledgers in the analogue world were often authorized by hand-written signatures, that is not going to work for the adoption in blockchain. To utilize the concept of a ledger in the modern age, we leverage cryptography instead. 
 
diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx
index 18e31a203ac..53920d37c31 100644
--- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx
+++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/01-tx-ordering-through-consensus.mdx
@@ -6,4 +6,4 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx
index 9c7f0266f06..34eb93313b4 100644
--- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx
+++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/02-longest-chain-consensus.mdx
@@ -6,4 +6,4 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
diff --git a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx
index d259eabccf5..28fc1161c77 100644
--- a/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx
+++ b/content/academy/blockchain-fundamentals/04-tx-ordering-through-consensus/xx-tx-lifecycle.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Notebook
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Creation
 
diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx
index 268d06886b8..b445f2cb494 100644
--- a/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx
+++ b/content/academy/blockchain-fundamentals/05-sybil-protection/01-sybil-protection.mdx
@@ -6,5 +6,5 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx
index 3e43c43983f..667bfb9d7ec 100644
--- a/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx
+++ b/content/academy/blockchain-fundamentals/05-sybil-protection/02-proof-of-work.mdx
@@ -6,4 +6,4 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
\ No newline at end of file
+import GlossaryTerm from '@/components/content-design/glossary-term';
\ No newline at end of file
diff --git a/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx b/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx
index d8058453965..8b0730f32a2 100644
--- a/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx
+++ b/content/academy/blockchain-fundamentals/05-sybil-protection/03-proof-of-stake.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 - Carrots and Sticks
 
diff --git a/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx b/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx
index c9d0349da6f..ada101fa868 100644
--- a/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx
+++ b/content/academy/blockchain-fundamentals/06-smart-contracts/01-smart-contracts.mdx
@@ -6,4 +6,4 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
diff --git a/content/academy/blockchain-fundamentals/index.mdx b/content/academy/blockchain-fundamentals/index.mdx
index 1bad6bf97c0..1b345e7110b 100644
--- a/content/academy/blockchain-fundamentals/index.mdx
+++ b/content/academy/blockchain-fundamentals/index.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Welcome to the Blockchain Fundamentals, an online course introducing you to blockchain! This course will provide you with a comprehensive understanding of the basic concepts of blockchains.
 
diff --git a/content/academy/blockchain-fundamentals/xx-decentralization.mdx b/content/academy/blockchain-fundamentals/xx-decentralization.mdx
index 56db4b262ba..7b2e5225140 100644
--- a/content/academy/blockchain-fundamentals/xx-decentralization.mdx
+++ b/content/academy/blockchain-fundamentals/xx-decentralization.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Moving from a centralized Entity to a Collective of Validators
 
diff --git a/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx b/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx
index f10537c4954..44b96931904 100644
--- a/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx
+++ b/content/academy/blockchain-fundamentals/xx-regulation/01-regulation.mdx
@@ -6,4 +6,4 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
diff --git a/content/academy/blockchain-fundamentals/xx-tokens.mdx b/content/academy/blockchain-fundamentals/xx-tokens.mdx
index e25d8d823e5..670135ab4f3 100644
--- a/content/academy/blockchain-fundamentals/xx-tokens.mdx
+++ b/content/academy/blockchain-fundamentals/xx-tokens.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Notebook
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Tokens are a concept that existed in societies for a long time. 
 
diff --git a/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx b/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx
index 441f6948d5c..155c8390851 100644
--- a/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx
+++ b/content/academy/customizing-evm/02-intro-to-evm/01-origin-of-evm.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9, owenwahlgren]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 The **Ethereum Virtual Machine (EVM)** is a fundamental component of Ethereum's infrastructure, responsible for executing Smart Contracts across the network. The origins of the EVM can be traced back to the creation of the Ethereum blockchain itself, proposed in a whitepaper by **Vitalik Buterin** in late 2013.
 
diff --git a/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx b/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx
index 6e8384f4b51..cde117e8219 100644
--- a/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx
+++ b/content/academy/customizing-evm/06-precompiles/01-what-are-precompiles.mdx
@@ -5,7 +5,7 @@ updated: 2024-05-31
 authors: [ashucoder9]
 icon: BookOpen
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Precompiled contracts allow the execution of code written in the low-level programming language Go from the EVM, which is significantly faster and more efficient than Solidity.
 
diff --git a/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx b/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx
index ca3dca980b5..0dd998e5a79 100644
--- a/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx
+++ b/content/academy/customizing-evm/06-precompiles/02-why-precompiles.mdx
@@ -5,7 +5,7 @@ updated: 2024-05-31
 authors: [ashucoder9]
 icon: BookOpen
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Adding precompiles to the EVM offers several significant advantages, which we will outline in this chapter.
 
diff --git a/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx b/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx
index 661f0d8553b..a63ff6ce2e2 100644
--- a/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx
+++ b/content/academy/customizing-evm/08-calculator-precompile/02-generating-precompile.mdx
@@ -5,7 +5,7 @@ updated: 2024-05-31
 authors: [ashucoder9]
 icon: Terminal
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this step, we will again utilize the precompile generation script to generate all the Go files based on the ABI for your calculator.
 
diff --git a/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx b/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx
index fdf97a17fb1..5023c8e7ccf 100644
--- a/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx
+++ b/content/academy/customizing-evm/10-stateful-counter-precompile/03-implement-set-counter.mdx
@@ -5,7 +5,7 @@ updated: 2024-05-31
 authors: [ashucoder9]
 icon: Terminal
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Having seen how strings are stored in `StringStore`, its time for us to store integers with Counter. The thought process for this section can be defined as follows:
 
diff --git a/content/academy/customizing-evm/index.mdx b/content/academy/customizing-evm/index.mdx
index e1ff7662be1..83b72f29d87 100644
--- a/content/academy/customizing-evm/index.mdx
+++ b/content/academy/customizing-evm/index.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9, owenwahlgren]
 icon: Smile
 ---
 import { Step, Steps } from 'fumadocs-ui/components/steps';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Why take this Course?
 
diff --git a/content/academy/icm-chainlink/index.mdx b/content/academy/icm-chainlink/index.mdx
index 92b0d8fedde..5e2ce0b93b9 100644
--- a/content/academy/icm-chainlink/index.mdx
+++ b/content/academy/icm-chainlink/index.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this course, you will learn how to integrate your own blockchain with the Chainlink services that are deployed on C-Chain. To do this, we will use Avalanche Interchain Messaging and Chainlink Verifiable Random Function (VRF).
 
diff --git a/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx b/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx
index 44be86bc398..f94563deeab 100644
--- a/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx
+++ b/content/academy/interchain-messaging/02-interoperability/01-interopability-between-blockchains.mdx
@@ -5,7 +5,7 @@ updated: 2024-05-31
 authors: [martineckardt]
 icon: Book
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 
 
diff --git a/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx b/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx
index 478cd8aa998..78722ede3bc 100644
--- a/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx
+++ b/content/academy/interchain-messaging/02-interoperability/03-multi-chain-networks.mdx
@@ -5,7 +5,7 @@ updated: 2024-05-31
 authors: [martineckardt]
 icon: BookOpen
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ![](/common-images/multi-chain-architecture/subnets.png)
 
diff --git a/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx b/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx
index 42772c014cf..e2d804e2339 100644
--- a/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx
+++ b/content/academy/interchain-messaging/14-access-chainlink-vrf-services/01-introduction.mdx
@@ -6,7 +6,7 @@ authors: [0xstt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 As decentralized applications (dApps) expand across multiple blockchains, some Layer 1 (L1) networks lack direct support from essential services like **Chainlink VRF (Verifiable Random Functions)**. This presents a significant challenge for developers who rely on verifiable randomness for use cases such as gaming, lotteries, NFT minting, and other decentralized functions that require unbiased, unpredictable random numbers.
 
diff --git a/content/academy/interchain-messaging/index.mdx b/content/academy/interchain-messaging/index.mdx
index f356a649434..12a5f74e509 100644
--- a/content/academy/interchain-messaging/index.mdx
+++ b/content/academy/interchain-messaging/index.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this course, you will learn how to build cross-L1 Solidity dApps with Interchain Messaging and Avalanche Warp Messaging.
 
diff --git a/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx
index 87445654514..d65b7c46e73 100644
--- a/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx
+++ b/content/academy/interchain-token-transfer/03-tokens/01-tokens.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## What You Will Learn
 
diff --git a/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx
index 6f59e0bbcfc..11331079c53 100644
--- a/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx
+++ b/content/academy/interchain-token-transfer/03-tokens/02-native-tokens.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 A native token in a blockchain running the EVM refers to the primary digital currency or cryptocurrency native to the EVM blockchain. Every EVM layer 1 chain has it's own native token:
 
diff --git a/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx b/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx
index 79f24e9dd81..16282663ab9 100644
--- a/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx
+++ b/content/academy/interchain-token-transfer/03-tokens/07-erc-20-tokens.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 There is only a single native token to a chain. However, to allow to represent a wide range of assets on EVM-chains, the ERC-20 token standard was developed. "ERC" stands for Ethereum Request for Comment, and "20" is the proposal identifier.
 
diff --git a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx
index f2c32ed5d25..20e20b556f8 100644
--- a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx
+++ b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/01-erc-20-to-erc-20-bridge.mdx
@@ -8,7 +8,7 @@ icon: Book
 import { Step, Steps } from 'fumadocs-ui/components/steps';
 import Link from 'next/link';
 import { buttonVariants } from '@/components/ui/button.tsx'
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Transfer an ERC-20 Token → Avalanche L1 as an ERC-20 Token
 
diff --git a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx
index 56c323e060e..a1f2e6a4a8b 100644
--- a/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx
+++ b/content/academy/interchain-token-transfer/06-erc-20-to-erc-20-bridge/04-deploy-remote.mdx
@@ -7,7 +7,7 @@ icon: Terminal
 ---
 
 import { Step, Steps } from 'fumadocs-ui/components/steps';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 To ensure the wrapped token is bridged into the destination chain (in this case, C-Chain) you'll need to deploy a _remote_ contract that implements the `IERC20Bridge` interface, as well as inheriting the properties of `TeleporterTokenRemote`. In order for the bridged tokens to have all the normal functionality of a locally deployed ERC20 token, this remote contract must also inherit the properties of a standard `ERC20` contract.
 
diff --git a/content/academy/interchain-token-transfer/index.mdx b/content/academy/interchain-token-transfer/index.mdx
index 7ca85a2ab95..90abd088a66 100644
--- a/content/academy/interchain-token-transfer/index.mdx
+++ b/content/academy/interchain-token-transfer/index.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this course, you will learn how to transfer assets across multiple Avalanche blockchains with Avalanche Interchain Token Transfer ICTT.
 
diff --git a/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx b/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx
index 8cec73c400f..fa5b85ff83b 100644
--- a/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx
+++ b/content/academy/l1-tokenomics/04-staking/01-staking-tokens.mdx
@@ -5,7 +5,7 @@ updated: 2024-09-03
 authors: [0xstt]
 icon: Book
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In many networks, such as Ethereum, the same token is used for both Staking and paying for Gas. However, in the Avalanche network, staking tokens and gas tokens can be separated, as they fulfill different purposes within the blockchain ecosystem.
 
diff --git a/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx b/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx
index 08fd55eed75..60272d4dd15 100644
--- a/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx
+++ b/content/academy/l1-tokenomics/04-staking/03-staking-contract-post-etna.mdx
@@ -6,7 +6,7 @@ authors: [0xstt]
 icon: Book
 ---
 import { Steps, Step } from 'fumadocs-ui/components/steps';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 The contracts in the [`validator-manager`](https://github.com/ava-labs/teleporter/tree/validator-manager/contracts/validator-manager) branch define the Validator Manager used to manage Subnet-only Validators, as defined in ACP-77. `ValidatorManager.sol` is the top-level abstract contract that provides the basic functionality. The other contracts are related as follows:
 
diff --git a/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx b/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx
index a3b36068d28..71336372345 100644
--- a/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx
+++ b/content/academy/l1-tokenomics/05-transaction-fees/01-introduction.mdx
@@ -6,7 +6,7 @@ authors: [0xstt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ### Background
 When creating an Avalanche L1 we cannot only configure our custom native token, but also how the transaction fees (also known as gas fees) are determined. This allows Avalanche L1s to define the desired or maximal throughput of the blockchain differently.
diff --git a/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx b/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx
index b8da2c0cc25..6a0540f8fbb 100644
--- a/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx
+++ b/content/academy/l1-tokenomics/05-transaction-fees/02-transaction-fee-configuration.mdx
@@ -6,7 +6,7 @@ authors: [0xstt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Configuration Format
 
diff --git a/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx b/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx
index 7260526a7f1..596edbb6e6b 100644
--- a/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx
+++ b/content/academy/l1-validator-management/02-l1-creation/07-convert-subnet-l1.mdx
@@ -6,7 +6,7 @@ authors: [owenwahlgren]
 icon: SquareMousePointer
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 The node you have just launched is tracking the Subnet but is not yet a validator. In fact, since the Subnet
 does not have any validators yet it cannot process any transactions. In this step we will do two
diff --git a/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx b/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx
index 89715ed3bf4..096edd7c741 100644
--- a/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx
+++ b/content/academy/l1-validator-management/04-validator-management/01-add-validator.mdx
@@ -8,7 +8,7 @@ icon: UserPlus
 
 import ToolboxMdxWrapper from "../../../../toolbox/src/demo/ui/ToolboxMdxWrapper.tsx"
 import AddValidator from "../../../../toolbox/src/demo/examples/ValidatorManager/AddValidator.tsx"
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 To add a validator to your Avalanche L1, you need to call the `initiateValidatorRegistration` function on the `ValidatorManager` contract.
 
diff --git a/content/academy/l1-validator-management/index.mdx b/content/academy/l1-validator-management/index.mdx
index e7c62caa1cd..991241d04be 100644
--- a/content/academy/l1-validator-management/index.mdx
+++ b/content/academy/l1-validator-management/index.mdx
@@ -6,7 +6,7 @@ authors: [owenwahlgren]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## 🏔️ L1 Validator Management
 
diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx
index 2fc614b2a7a..ec3ea9805f2 100644
--- a/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx
+++ b/content/academy/multi-chain-architecture/02-custom-blockchains/01-custom-blockchains.mdx
@@ -6,7 +6,7 @@ authors: [usmaneth]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 An Avalanche L1 is a sovereign network that defines its own rules for membership and token economics. It's validated by a dynamic subset of Avalanche validators working together to achieve consensus on the blockchain's state.
 
diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx
index bde1d5c20b7..e5093642447 100644
--- a/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx
+++ b/content/academy/multi-chain-architecture/02-custom-blockchains/02-benefits-of-custom-blockchains.mdx
@@ -6,7 +6,7 @@ authors: [usmaneth]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Custom blockchains offer a range of advantages for developers and businesses looking to create very custom & tailored solutions. 
 
diff --git a/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx b/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx
index 78cc9c2f195..40e40b220fd 100644
--- a/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx
+++ b/content/academy/multi-chain-architecture/02-custom-blockchains/03-custom-blockchains-vs-layer-2.mdx
@@ -6,7 +6,7 @@ authors: [usmaneth]
 icon: BookOpen
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Layer 2 blockchain solutions, such as rollups, are another innovation in the blockchain landscape. Layer 2s aim to enhance the scalability and performance of the Ethereum network. Rollups essentially perform computations off-chain and submit the resultant state changes to the base layer, thereby reducing the computational load on the main Ethereum chain.
 
diff --git a/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx b/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx
index eb5830f07f8..4eb5a9922e2 100644
--- a/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx
+++ b/content/academy/multi-chain-architecture/03-avalanche-starter-kit/01-avalanche-starter-kit.mdx
@@ -6,7 +6,7 @@ authors: [martineckardt]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 To make easier your journey through this course, we have prepared a Starter Kit repo consisting of everything you will need to start developing your own custom blockchains on Avalanche. This repo will provide a self-contained environment with Avalanche-CLI, and Foundry so you can follow the course without the need of installing anything else other than launching the environment.
 
diff --git a/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx b/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx
index f2e5ca36868..e388d1acc11 100644
--- a/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx
+++ b/content/academy/multi-chain-architecture/04-independent-tokenomics/01-independent-tokenomics.mdx
@@ -6,7 +6,7 @@ authors: [usmaneth]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Avalanche Custom Blockchains offer multiple ways to implement independent tokenomics. This gives developers more control and can enable new business model that would not be economically feasible on single-chain systems.
 
diff --git a/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx b/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx
index a4cdfc3fdce..5df3f274a2d 100644
--- a/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx
+++ b/content/academy/multi-chain-architecture/07-permissioning-validators/01-permissioning-validators.mdx
@@ -6,7 +6,7 @@ authors: [usmaneth]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 The ability to control a blockchain's validator set has many benefits that can significantly enhance the efficiency, security, and governance of the network. It allows blockchain participants to have greater influence over the consensus process and decision-making, leading to a more robust and adaptable ecosystem. There are two ways to structure the validator set:
 
diff --git a/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx b/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx
index b73c9de3b98..3c61aef5c55 100644
--- a/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx
+++ b/content/academy/multi-chain-architecture/08-customizability/00-intro.mdx
@@ -6,7 +6,7 @@ authors: [ashucoder9]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 For some use cases, it may be necessary to use a customized VM instead of the EVM. This is the case if an application cannot be built on a regular EVM on the C-Chain, or if it would result in transaction fee costs too high to be economical for its users or creators.
 
diff --git a/content/academy/multi-chain-architecture/index.mdx b/content/academy/multi-chain-architecture/index.mdx
index 2f138992629..72d9679a768 100644
--- a/content/academy/multi-chain-architecture/index.mdx
+++ b/content/academy/multi-chain-architecture/index.mdx
@@ -6,7 +6,7 @@ authors: [usmaneth]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Are you ready to dive deeper into the fascinating world of Avalanche? This course will equip you with a comprehensive understanding of the Avalanche's Multi Blockchain architecture, along with the practical skills required to create and manage custom blockchains.
 
diff --git a/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx b/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx
index 56a5118f888..f670aa06c97 100644
--- a/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx
+++ b/content/academy/solidity-foundry/03-smart-contracts/01-building-programs-on-blockchain.mdx
@@ -6,7 +6,7 @@ authors: [Andrea Vargas, Ash]
 icon: Book
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 First off, thank you for enrolling in this course! We assume that you are taking this course in order to learn how to write Smart Contracts. This begs the question - what are smart contracts?
 
diff --git a/content/academy/solidity-foundry/index.mdx b/content/academy/solidity-foundry/index.mdx
index ff7766280f9..9c77076a766 100644
--- a/content/academy/solidity-foundry/index.mdx
+++ b/content/academy/solidity-foundry/index.mdx
@@ -6,7 +6,7 @@ authors: [Andrea Vargas]
 icon: Smile
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this course, you will learn how to build Solidity dApps on Avalanche.
 
diff --git a/content/common/avalanche-starter-kit/create-default-blockchain.mdx b/content/common/avalanche-starter-kit/create-default-blockchain.mdx
index ec96aaae3f9..c5e0a79d3a9 100644
--- a/content/common/avalanche-starter-kit/create-default-blockchain.mdx
+++ b/content/common/avalanche-starter-kit/create-default-blockchain.mdx
@@ -1,5 +1,5 @@
 import { Step, Steps } from 'fumadocs-ui/components/steps';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 > In the following commands, make sure to substitute the name of your Avalanche L1 for `` (including the `<>`). You can choose whatever name you want, but I recommend using `myblockchain` as the name to avoid the need for some manual configuration.
 
diff --git a/content/common/cryptography/multi-signature-schemes.mdx b/content/common/cryptography/multi-signature-schemes.mdx
index 3cb020624c7..36a3fc09bfa 100644
--- a/content/common/cryptography/multi-signature-schemes.mdx
+++ b/content/common/cryptography/multi-signature-schemes.mdx
@@ -1,4 +1,4 @@
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Multi-signature schemes, also known as Multi-signature, are cryptographic methods enabling multiple parties to collectively authorize a specific action or operation, typically by requiring a predefined number of authorized participants to provide their digital signatures. In a multi-signature scheme, each authorized party possesses their own Private Key, and to validate the action. A specified subset of these parties must produce their unique signatures.
 
diff --git a/content/common/cryptography/signature-schemes.mdx b/content/common/cryptography/signature-schemes.mdx
index 7cc99abc77c..6d8661a1555 100644
--- a/content/common/cryptography/signature-schemes.mdx
+++ b/content/common/cryptography/signature-schemes.mdx
@@ -1,6 +1,6 @@
 import { buttonVariants } from '@/components/ui/button';
 import { cn } from '@/utils/cn';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Signature schemes are cryptographic schemes, that allow us to sign some piece of data, and someone else can verify our signature. Think of signature schemes as a very modern version of signing for example a contract, which does not rely on your unique hand movement, but on math. There are many different signature schemes. They vary in efficiency and security. 
 
diff --git a/content/common/evm-precompiles/precompiles.mdx b/content/common/evm-precompiles/precompiles.mdx
index ec87510d0b8..f4cfa771dbf 100644
--- a/content/common/evm-precompiles/precompiles.mdx
+++ b/content/common/evm-precompiles/precompiles.mdx
@@ -1,4 +1,4 @@
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Precompiled contracts are a way to execute code written in the low-level coding language Go from the EVM. Go is much faster and more efficient than Solidity.
 
diff --git a/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx b/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx
index 1a74f48514f..c35db5d23f9 100644
--- a/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx
+++ b/content/common/multi-chain-architecture/etna-upgrade-motivation.mdx
@@ -1,5 +1,5 @@
 import YouTube from '@/components/content-design/youtube';
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 The Etna Upgrade will be the largest network upgrade of Avalanche to date. This upgrade will introduce a new concept called Layer 1 blockchains (L1s), which will replace the current Subnet model. In this article we will discuss the current limitations of Subnets, and how the changes suggested in ACP-77 ([ACP-77 Proposal](https://github.com/avalanche-foundation/ACPs/blob/main/ACPs/77-reinventing-subnets/README.md)) will address these limitations in the Etna Upgrade.
 
diff --git a/content/common/multi-chain-architecture/transaction-fees.mdx b/content/common/multi-chain-architecture/transaction-fees.mdx
index d1ae7af14d6..d5cb325a1e7 100644
--- a/content/common/multi-chain-architecture/transaction-fees.mdx
+++ b/content/common/multi-chain-architecture/transaction-fees.mdx
@@ -1,4 +1,4 @@
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 NFT collectors, Decentralized Finance traders, and Blockchain gamers have independently spent significant sums to execute their transactions. These unrelated activities converge on the blockchain, competing for the finite capacity of the next blockspace. In an effort to avoid delays or being outpaced by others, participants can be compelled to pay substantial fees to secure prompt transaction processing.
 
diff --git a/content/common/primary-network/p-chain.mdx b/content/common/primary-network/p-chain.mdx
index 31902d9789d..a3db546e81c 100644
--- a/content/common/primary-network/p-chain.mdx
+++ b/content/common/primary-network/p-chain.mdx
@@ -1,4 +1,4 @@
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In the Avalanche Network, the Platform Chain of the Primary Network is responsible for all Validator and Avalanche L1-level operations. The P-Chain supports the creation of new blockchains and Avalanche L1s, the addition of validators to Avalanche L1s, Staking operations, and other platform-level operations. 
 
diff --git a/content/docs/quick-start/avalanche-l1s.mdx b/content/docs/quick-start/avalanche-l1s.mdx
index f60bebd2743..4a4e0f9b246 100644
--- a/content/docs/quick-start/avalanche-l1s.mdx
+++ b/content/docs/quick-start/avalanche-l1s.mdx
@@ -3,7 +3,7 @@ title: Avalanche L1s
 description: Explore the multi-chain architecture of Avalanche ecosystem.
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 An Avalanche L1 is a sovereign network which defines its own rules regarding its membership and token economics. It is composed of a dynamic subset of Avalanche validators working together to achieve consensus on the state of one or more blockchains. Each blockchain is validated by exactly one Avalanche L1, while an Avalanche L1 can validate many blockchains.
 
diff --git a/content/docs/quick-start/primary-network.mdx b/content/docs/quick-start/primary-network.mdx
index 04265e694fa..0badf52dbf6 100644
--- a/content/docs/quick-start/primary-network.mdx
+++ b/content/docs/quick-start/primary-network.mdx
@@ -3,7 +3,7 @@ title: Primary Network
 description: Learn about the Avalanche Primary Network and its three blockchains.
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 Avalanche is a heterogeneous network of blockchains. As opposed to homogeneous networks, where all applications reside in the same chain, heterogeneous networks allow separate chains to be created for different applications.
 
diff --git a/content/docs/tooling/create-avalanche-l1.mdx b/content/docs/tooling/create-avalanche-l1.mdx
index 962da54620e..5565adb63e9 100644
--- a/content/docs/tooling/create-avalanche-l1.mdx
+++ b/content/docs/tooling/create-avalanche-l1.mdx
@@ -3,7 +3,7 @@ title: Create Avalanche L1
 description: This page demonstrates how to create an Avalanche L1 using Avalanche-CLI.
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 This tutorial walks you through the process of using Avalanche-CLI to create an Avalanche L1, deploy it to a local network, and connect to it with Core wallet.
 
diff --git a/content/guides/etna-changes.mdx b/content/guides/etna-changes.mdx
index 4cf8d378278..fe852b51373 100644
--- a/content/guides/etna-changes.mdx
+++ b/content/guides/etna-changes.mdx
@@ -6,7 +6,7 @@ authors: [meagfitzgerald]
 topics: [Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1]
 comments: true
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 This guide outlines the operational impact on existing network participants expected from the activation of the AvalancheGo "Etna Upgrade" upgrade.
 
diff --git a/content/guides/l1-validator-fee.mdx b/content/guides/l1-validator-fee.mdx
index fd8c2381955..6156dc9d140 100644
--- a/content/guides/l1-validator-fee.mdx
+++ b/content/guides/l1-validator-fee.mdx
@@ -6,7 +6,7 @@ authors: [meagfitzgerald]
 topics: [ Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1, L1 Validators, Continuous L1 Validation Fee]
 comments: true
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## What are L1 Validators?
 
diff --git a/content/guides/subnet-vs-l1-validators.mdx b/content/guides/subnet-vs-l1-validators.mdx
index c02e808b636..0a7ce109f19 100644
--- a/content/guides/subnet-vs-l1-validators.mdx
+++ b/content/guides/subnet-vs-l1-validators.mdx
@@ -6,7 +6,7 @@ authors: [meagfitzgerald]
 topics: [Avalanche Network Upgrade, Etna Upgrade, Validators, Layer 1, L1, L1 Validators, Subnet Validators]
 comments: true
 ---
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 The Etna Upgrade introduced L1s to the Avalanche network, providing an enhanced sovereign network design to the original Subnet model. 
 
diff --git a/content/guides/use-privy-on-l1.mdx b/content/guides/use-privy-on-l1.mdx
index 10438cd2c5a..843bb78b259 100644
--- a/content/guides/use-privy-on-l1.mdx
+++ b/content/guides/use-privy-on-l1.mdx
@@ -6,7 +6,7 @@ authors: [satatocom]
 topics: [Avalanche L1, Avalanche Starter Kit, Magic Link, Social Login, Embedded Wallets]
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 In this guide, you will learn how to use Privy to easily onboard your users and create transactions without the need for any Web3 wallet.
 
diff --git a/content/guides/what-is-a-blockchain.mdx b/content/guides/what-is-a-blockchain.mdx
index 71c9c307c56..b56d6bab638 100644
--- a/content/guides/what-is-a-blockchain.mdx
+++ b/content/guides/what-is-a-blockchain.mdx
@@ -6,7 +6,7 @@ authors: [martin_eckardt]
 topics: [Blockchain Basics]
 ---
 
-import GlossaryTerm from '@/components/content-design/glossary-term'
+import GlossaryTerm from '@/components/content-design/glossary-term';
 
 ## Introduction to Different Types of Computers
 Computers are integral to our daily lives, and they come in various forms, each designed to serve specific purposes. Here's a quick overview:

From 6f79f82ead3f381cc2b95b7ed98cc75f8f830cb4 Mon Sep 17 00:00:00 2001
From: federiconardelli7 
Date: Mon, 28 Apr 2025 23:35:55 +0200
Subject: [PATCH 27/27] fix9

---
 components/content-design/glossary-term.tsx | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/components/content-design/glossary-term.tsx b/components/content-design/glossary-term.tsx
index 95fb41f5db6..158cc92f401 100644
--- a/components/content-design/glossary-term.tsx
+++ b/components/content-design/glossary-term.tsx
@@ -12,7 +12,7 @@ interface GlossaryTermProps {
   className?: string
 }
 
-function GlossaryTerm({ 
+export default function GlossaryTerm({ 
   children, 
   termKey, 
   className = "" 
@@ -72,6 +72,4 @@ function GlossaryTerm({
       
     
   )
-}
-
-export default GlossaryTerm 
\ No newline at end of file
+}
\ No newline at end of file