ava-labs · navillanueva · Jun 18, 2025 · Jun 20, 2025 · Jun 20, 2025
@@ -11,7 +11,7 @@ This how-to guide focuses on taking an already created permissioned Avalanche L1
 
 ## Prerequisites
 
-- [Avalanche-CLI installed](/docs/tooling/guides/get-avalanche-cli)
+- [Avalanche-CLI installed](/docs/tooling/get-avalanche-cli)
 - You have deployed a permissioned Avalanche L1 on [local](/docs/avalanche-l1s/deploy-a-avalanche-l1/local-network), on [Fuji](/docs/avalanche-l1s/deploy-a-avalanche-l1/fuji-testnet) or on [Mainnet](/docs/avalanche-l1s/deploy-a-avalanche-l1/avalanche-mainnet)
 
 Getting Started[](#getting-started "Direct link to heading")

@@ -59,8 +59,8 @@ The AllowList interface is implemented by multiple precompiles in the Subnet-EVM
 
 Several precompiles in Subnet-EVM use the AllowList interface:
 
-- [Native Minter](/docs/virtual-machines/default-precompiles/nativeminter)
+- [Native Minter](/docs/avalanche-l1s/evm-configuration/tokenomics#native-minter)
 - [Fee Manager](/docs/virtual-machines/default-precompiles/feemanager)
 - [Reward Manager](/docs/virtual-machines/default-precompiles/rewardmanager)
 - [Contract Deployer Allow List](/docs/virtual-machines/default-precompiles/deployerallowlist)
-- [Transaction Allow List](/docs/virtual-machines/default-precompiles/transactionallowlist)
+- [Transaction Allow List](/docs/avalanche-l1s/evm-configuration/permissions#transaction-allowlist)
@@ -10,7 +10,7 @@ The Subnet-EVM provides two powerful precompiles for managing permissions on you
 - **Contract Deployer Allowlist**: Control which addresses can deploy smart contracts
 - **Transaction Allowlist**: Control which addresses can submit transactions
 
-Both precompiles use the [AllowList interface](/docs/avalanche-l1s/allowlist) to manage permissions with a consistent role-based system.
+Both precompiles use the [AllowList interface](/docs/avalanche-l1s/evm-configuration/allowlist) to manage permissions with a consistent role-based system.
 
 ## Contract Deployer Allowlist
 
@@ -64,12 +64,12 @@ By enabling this feature, you can define which addresses are allowed to submit t
 
 ## Permissions Management
 
-Both precompiles use the [AllowList interface](/docs/avalanche-l1s/allowlist) to manage permissions. This provides a consistent way to:
+Both precompiles use the [AllowList interface](/docs/avalanche-l1s/evm-configuration/allowlist) to manage permissions. This provides a consistent way to:
 - Assign and revoke permissions
 - Manage admin and manager roles
 - Control who can deploy contracts or submit transactions
 
-For detailed information about the role-based permission system and available functions, see the [AllowList interface documentation](/docs/avalanche-l1s/allowlist).
+For detailed information about the role-based permission system and available functions, see the [AllowList interface documentation](/docs/avalanche-l1s/evm-configuration/allowlist).
 
 ## Implementation
 

@@ -9,7 +9,7 @@ The tokenomics of your Avalanche L1 blockchain is a crucial aspect that determin
 
 - Initial token allocation in genesis
 - Dynamic token minting through the Native Minter precompile
-- Fee burning or redistribution mechanisms (via [Transaction Fees & Gas](/docs/avalanche-l1s/default-precompiles/transaction-fees))
+- Fee burning or redistribution mechanisms (via [Transaction Fees & Gas](/docs/avalanche-l1s/evm-configuration/transaction-fees))
 
 ## Initial Token Supply
 
@@ -90,7 +90,7 @@ interface INativeMinter {
 }
 ```
 
-The Native Minter precompile uses the [AllowList interface](/docs/avalanche-l1s/allowlist) to restrict access to its functionality with the following roles.
+The Native Minter precompile uses the [AllowList interface](/docs/avalanche-l1s/evm-configuration/allowlist) to restrict access to its functionality with the following roles.
 
 ## Tokenomics Best Practices
 

@@ -10,7 +10,7 @@ The Subnet-EVM provides two powerful precompiles for managing transaction fees a
 - **Fee Manager**: Configure dynamic fee parameters and gas costs
 - **Reward Manager**: Control how transaction fees are distributed or burned
 
-Both precompiles use the [AllowList interface](/docs/avalanche-l1s/allowlist) to restrict access to their functionality.
+Both precompiles use the [AllowList interface](/docs/avalanche-l1s/evm-configuration/allowlist) to restrict access to their functionality.
 
 ## Fee Manager
 
@@ -62,7 +62,7 @@ The Fee Manager allows configuration of the following parameters:
 
 ### Access Control and Additional Features
 
-The FeeManager precompile uses the [AllowList interface](/docs/avalanche-l1s/allowlist) to restrict access to its functionality.
+The FeeManager precompile uses the [AllowList interface](/docs/avalanche-l1s/evm-configuration/allowlist) to restrict access to its functionality.
 
 In addition to the AllowList interface, the FeeManager adds the following capabilities:
 

@@ -38,9 +38,9 @@ Subnet-EVM Native Precompiles will start emitting events with the Durango networ
 
 ### Custom Events[](#custom-events "Direct link to heading")
 
-Events above are already introduced and handled in Subnet-EVM native precompiles. If you have a custom precompile, you can start emitting your custom events using Durango activation. In order to do this you can define your custom event in your solidity interface and regenerate the go bindings using `precompilegen` tool, for more information see [here](/docs/virtual-machines/evm-customization/generating-your-precompile).
+Events above are already introduced and handled in Subnet-EVM native precompiles. If you have a custom precompile, you can start emitting your custom events using Durango activation. In order to do this you can define your custom event in your solidity interface and regenerate the go bindings using `precompilegen` tool, for more information see [here](/docs/virtual-machines/custom-precompiles/create-precompile).
 
-Generally you will generate an `event.go` file in addition to your existing precompile files. You need to implement how to emit your events and your events' gas costs, as in [hello world example](/docs/virtual-machines/evm-customization/defining-precompile#event-file). In this guide we will use the hello world example to demonstrate how to emit custom events. The event that will be introduced is:
+Generally you will generate an `event.go` file in addition to your existing precompile files. You need to implement how to emit your events and your events' gas costs, as in [hello world example](/docs/virtual-machines/custom-precompiles/defining-precompile#event-file). In this guide we will use the hello world example to demonstrate how to emit custom events. The event that will be introduced is:
 
 ```go
 event GreetingChanged(address indexed sender, string oldGreeting, string newGreeting)

@@ -10,7 +10,7 @@ Note that currently only [Subnet-EVM](https://github.com/ava-labs/subnet-evm) an
 
 ## Prerequisites
 
-- [Avalanche-CLI installed](/docs/tooling/guides/get-avalanche-cli)
+- [Avalanche-CLI installed](/docs/tooling/get-avalanche-cli)
 
 ## Create Avalanche L1 Configurations
 

@@ -35,7 +35,7 @@ source ~/.bashrc
 
 Once you add it to your path, you should be able to call the program anywhere with just: `avalanche`
 
-For more detailed installation instructions, see [Avalanche-CLI Installation](/docs/tooling/guides/get-avalanche-cli).
+For more detailed installation instructions, see [Avalanche-CLI Installation](/docs/tooling/get-avalanche-cli).
 
 Create Your Avalanche L1 Configuration[](#create-your-avalanche-l1-configuration "Direct link to heading")
 -----------------------------------------------------------------------------------------------
@@ -93,7 +93,7 @@ This key is used to manage (add/remove) the validator set.
 Do not use EWOQ key in a testnet or production setup. The EWOQ private key is publicly exposed.
 </Callout>
 
-To learn more about different validator management types, see [PoA vs PoS](/evm-l1s/validator-manager/poa-vs-pos).
+To learn more about different validator management types, see [PoA vs PoS](/docs/avalanche-l1s/validator-manager/poa-vs-pos).
 
 ### Choose Blockchain Configuration
 

@@ -7,7 +7,7 @@ This how-to guide focuses on taking an already created Avalanche L1 configuratio
 
 ## Prerequisites
 
-- [Avalanche-CLI installed](/docs/tooling/guides/get-avalanche-cli)
+- [Avalanche-CLI installed](/docs/tooling/get-avalanche-cli)
 - You have [created an Avalanche L1 configuration](/docs/tooling/create-avalanche-l1#create-your-avalanche-l1-configuration)
 
 Deploying Avalanche L1s Locally[](#deploying-avalanche-l1s-locally "Direct link to heading")

@@ -35,7 +35,7 @@ This chain implements the Ethereum Virtual Machine and supports Solidity smart c
 Avalanche-CLI[](#avalanche-cli "Direct link to heading")
 ---------------------------------------------------------
 
-If not yet installed, install `Avalanche-CLI` following the tutorial at [Avalanche-CLI installation](/docs/tooling/guides/get-avalanche-cli)
+If not yet installed, install `Avalanche-CLI` following the tutorial at [Avalanche-CLI installation](/docs/tooling/get-avalanche-cli)
 
 ### Private Key[](#private-key "Direct link to heading")
 

@@ -18,7 +18,7 @@ This how-to guide focuses on transferring funds between ledger accounts.
 
 ## Prerequisites
 
-- [`Avalanche-CLI`](/docs/tooling/guides/get-avalanche-cli) installed
+- [`Avalanche-CLI`](/docs/tooling/get-avalanche-cli) installed
 - Multiple Ledger devices [configured for Avalanche](/docs/avalanche-l1s/deploy-a-avalanche-l1/avalanche-mainnet#setting-up-your-ledger)
 
 Example: Sending All Funds From One Ledger to Another[](#example-sending-all-funds-from-one-ledger-to-another "Direct link to heading")

@@ -5,7 +5,7 @@ description: Learn how to execute a native transfer on the C or P-Chain using th
 
 # Prerequisites
 
-- Install the [Avalanche CLI](/docs/tooling/guides/get-avalanche-cli).
+- Install the [Avalanche CLI](/docs/tooling/get-avalanche-cli).
 - Use the CLI to [create a key](/docs/tooling/avalanche-cli#key-create).
 - Fund the key with AVAX. You can use the [faucet](https://test.core.app/tools/testnet-faucet/?subnet=c&token=c) with coupon code `devrel-avax-0112` to get testnet AVAX. 
 - *Optionally*, you can [export](/docs/tooling/avalanche-cli#key-export) your private key for use in scripting or other tools. 

@@ -13,7 +13,7 @@ The document [Upgrade an Avalanche L1](/docs/avalanche-l1s/upgrade/consideration
 It's very important that you have read and understood the previously linked document. Failing to do so can potentially grind your network to a halt.
 </Callout>
 
-This tutorial assumes that you have already [installed](/docs/tooling/guides/get-avalanche-cli) Avalanche-CLI. It assumes you have already created and deployed an Avalanche L1 called `testblockchain`.
+This tutorial assumes that you have already [installed](/docs/tooling/get-avalanche-cli) Avalanche-CLI. It assumes you have already created and deployed an Avalanche L1 called `testblockchain`.
 
 Generate the Upgrade File[](#generate-the-upgrade-file "Direct link to heading")
 ---------------------------------------------------------------------------------

@@ -6,7 +6,7 @@ description: "Sherry is the publishing layer that turns any interaction — from
 logo: /images/sherry.png
 developer: Sherry Labs
 website: https://sherry.social
-documentation: https://docs.sherry.social
+documentation: https://docs.sherry.social/docs/intro
 ---
 
 ## Overview
@@ -67,13 +67,13 @@ To begin building with Sherry:
 
 ## Documentation
 
-For comprehensive guides and technical documentation, visit [Sherry Documentation](https://docs.sherry.social). Key resources include:
+For comprehensive guides and technical documentation, visit [Sherry Documentation](https://docs.sherry.social/docs/intro). Key resources include:
 
 - **[SDK Introduction](https://docs.sherry.social/docs/intro)**: Getting started with the Sherry SDK
-- **[Action Types](https://docs.sherry.social/docs/sdk/action-types/blockchain-actions)**: Learn about different interaction types
-- **[Parameters Guide](https://docs.sherry.social/docs/sdk/parameters)**: Configure user inputs and validation
-- **[Chain Support](https://docs.sherry.social/docs/sdk/chains)**: Multi-chain deployment guide
-- **[Guides](https://docs.sherry.social/docs/sdk/examples)**: Guides and code samples for common use cases
+- **[Action Types](https://docs.sherry.social/docs/api/action-types)**: Learn about different interaction types
+- **[Parameters Guide](https://docs.sherry.social/docs/api-reference/parameters/)**: Configure user inputs and validation
+- **[Chain Support](https://docs.sherry.social/docs/core-concepts/chains)**: Multi-chain deployment guide
+- **[Guides](https://docs.sherry.social/docs/getting-started/examples)**: Guides and code samples for common use cases
 
 ## Use Cases
 

@@ -64,6 +64,11 @@ const config = {
         destination: '/docs/avalanche-l1s/evm-configuration/tokenomics#native-minter',
         permanent: true,
       },
+      {
+        source: '/docs/virtual-machines/default-precompiles/nativeminter',
+        destination: '/docs/avalanche-l1s/evm-configuration/tokenomics#native-minter',
+        permanent: true,
+      },
       {
         source: '/docs/virtual-machines/default-precompiles/feemanager',
         destination: '/docs/avalanche-l1s/evm-configuration/transaction-fees#fee-manager',
@@ -79,6 +84,11 @@ const config = {
         destination: '/docs/avalanche-l1s/evm-configuration/warpmessenger',
         permanent: true,
       },
+      {
+        source: '/docs/avalanche-l1s/default-precompiles/transaction-fees',
+        destination: '/docs/avalanche-l1s/evm-configuration/transaction-fees',
+        permanent: true,
+      },
       {
         source: '/academy/interchain-messaging/10-running-a-relayer/01-running-a-relayer',
         destination: '/academy/interchain-messaging/10-running-a-relayer/01-relayer-introduction',
@@ -128,6 +138,30 @@ const config = {
         source: '/docs/api-reference/standards/guides/txn-fees#c-chain-fees',
         destination: '/docs/api-reference/guides/txn-fees#c-chain-fees',
         permanent: true,
+      }, {
+        source: '/docs/tooling/guides/get-avalanche-cli',
+        destination: '/docs/tooling/get-avalanche-cli',
+        permanent: true,
+      }, {
+        source: '/evm-l1s/validator-manager/poa-vs-pos',
+        destination: 'docs/avalanche-l1s/validator-manager/poa-vs-pos',
+        permanent: true,
+      }, {
+        source: '/docs/avalanche-l1s/allowlist',
+        destination: '/docs/avalanche-l1s/evm-configuration/allowlist',
+        permanent: true,
+      }, {
+        source: '/docs/virtual-machines/evm-customization/generating-your-precompile',
+        destination: '/docs/virtual-machines/custom-precompiles/create-precompile',
+        permanent: true,
+      }, {
+        source: '/docs/virtual-machines/evm-customization/defining-precompile#event-file',
+        destination: '/docs/virtual-machines/custom-precompiles/defining-precompile#event-file',
+        permanent: true,
+      }, {
+        source: '/docs/virtual-machines/evm-customization/testing-your-precompile',
+        destination: '/docs/virtual-machines/custom-precompiles/test-precompile',
+        permanent: true,
       },
     ];
   },