Zearn Docs
  • Zearn Overview
    • Overview
    • Administration
    • Achitecture
    • Roadmap
  • How Zearn Works
    • Zearn Stake Tutorial
    • Fees
    • Guides
    • Contracts
    • Integrating stZETA
    • Audits
    • Deployed Contracts
  • ZEARN.FUN OVERVIEW
    • Overview
    • MemeCoin Explanation
    • Zearn.fun Tutorials
    • Fees
  • Resources
    • Media Kit
    • FAQ
    • Bug Bounty
    • Meet Our Team
    • Opportunities
    • Social Media
    • Privacy Policy
    • Terms of Use
Powered by GitBook
On this page
  • Node Operators
  • How to join as an Operator
  • Protocol levers
  • A note on upgradeability
  • NodeOperatorsRegistry
  1. How Zearn Works

Guides

Node Operators

A key component of the Zearn protocol is the node operators. These operators run the ZetaChain PoS validators and are registered in the Zearn node operator registry contract. Their job is to manage a secure and stable setup for running the ZetaChain validator infrastructure, all to benefit the protocol. As professional staking providers, they are trusted to safeguard the funds of protocol users and guarantee the accuracy of validator operations.

Note:

  • You can obtain the ZetaChain Mainnet NodeOperatorRegistry Proxy address from here.

  • The ZetaChain Testnet NodeOperatorRegistry Proxy address is available from here.

  • The ZetaChain Mainnet StakingNFT Contract Address Proxy address can be sourced here.

  • You can retrieve the ZetaChain Testnet StakingNFT Contract Address Proxy address from here.

How to join as an Operator

Zearn DAO is solely responsible for adding new validators to the Node Operator Registry. Once the snapshot proposal, which includes the suggested group of node operators, is approved, Zearn DAO will proceed to list the new validators. No additional steps are necessary.

Protocol levers

The protocol offers a range of settings that the DAO can control. Each modification requires the caller to have specific permissions. After the DAO's deployment, all permissions are owned by its Voting app, which can also manage them. This implies that, at first, only the DAO voting can alter the levers. Other entities can only gain the same permission through a successful vote. Below is a list of all the existing levers, grouped by their respective contracts.

A note on upgradeability

The DAO voting process can upgrade the following contracts:

  • stZETA

  • NodeOperatorsRegistry

NodeOperatorsRegistry

Coming soon

PreviousFeesNextContracts

Last updated 1 year ago

Aragon's kernel and base contracts enable upgradeability. To upgrade an app, you're going to need the dao.APP_MANAGER_ROLE permission from Aragon. Every upgradeable contract uses the for maintaining a consistent storage structure throughout upgrades.

Unstructured Storage pattern