Skip to content

Commit 82f4bf1

Browse files
authored
Merge pull request #3359 from ava-labs/native-token-staking-manager
`Permissionless L1s`: Native Token Staking Manager
2 parents 994dbca + b1c6ed5 commit 82f4bf1

File tree

13 files changed

+405
-153
lines changed

13 files changed

+405
-153
lines changed

content/academy/avalanche-l1/permissioned-l1s/XX-poa-manager-deployment/03-deploy-poa-manager.mdx

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,11 @@ icon: Terminal
99
import ToolboxMdxWrapper from "@/components/toolbox/academy/wrapper/ToolboxMdxWrapper.tsx"
1010
import DeployPoAManager from "@/components/toolbox/console/permissioned-l1s/multisig-setup/DeployPoAManager.tsx"
1111

12+
### PoAValidatorManager
13+
14+
Proof-of-Authority Validator management is provided via `PoAValidatorManager`, which restricts modification of the Validator set to an owner address. After deploying `PoAValidatorManager.sol` and a proxy, the `initialize` function takes the owner address, in addition to standard `ValidatorManagerSettings`.
15+
16+
1217
## Overview
1318

1419
The Proof of Authority (PoA) Manager is a simplified validator management contract that provides an easier interface for managing validators on your L1. It acts as a wrapper around the core Validator Manager contract, offering streamlined operations for PoA-based L1s.

content/academy/avalanche-l1/permissionless-l1s/03-transformation-requirements/01-introduction.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Native Token Staking Blockchain
2+
title: Introduction
33
description: Precompile contracts necessary for a Permissionless L1 implementation
44
updated: 2025-03-13
55
authors: [nicolasarnedo]
@@ -12,6 +12,8 @@ Now that we've covered how Proof of Stake serves as a Sybil protection mechanism
1212

1313
In the previous section on [staking token selection](/academy/permissionless-l1s/proof-of-stake/staking-token), we learned that the staking token can either be the native token or a separate ERC20 token. **For this course, we will focus on building a permissionless L1 where the native token is also the staking token**—the most common and straightforward implementation that creates unified token economics.
1414

15+
*Optionally*, or in case you lost access to your previous chain, you can quickly [setup a Permissioned L1](/academy/permissionless-l1s/04-speedrun-base-l1) at the end of this chapter and will transform it the next chapter.
16+
1517
### 1. Opening Validator Management (From Permissioned L1s)
1618

1719
In the [Permissioned L1s course](/academy/permissioned-l1s), we learned about the [Validator Manager Contract](/academy/permissioned-l1s/proof-of-authority/validator-manager-contract)—specifically how PoA restricts validator control to a single owner address. The contract hierarchy showed us:
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"title": "Permissioned L1 Setup",
3+
"icon": "Settings",
4+
"pages": [
5+
"01-create-l1-speedrun",
6+
"02-permissioned-l1-speedrun"
7+
]
8+
}

content/academy/avalanche-l1/permissionless-l1s/05-staking-manager-contract/03-staking-contract-post-etna.mdx

Lines changed: 0 additions & 151 deletions
This file was deleted.

0 commit comments

Comments
 (0)