♾️
OneFinity Docs
πŸŽ“ LearnπŸ›  BuildπŸ’Ύ Testnet πŸ‘” ProtocolπŸ”„ Bridge
  • Welcome to OneFinity
  • OneFinity
    • What is OneFinity
    • OneFinity approach
    • What is a Sovereign Shard?
  • Technology
    • Basic concepts
      • Nodes and Wallets
      • Epoch and Rounds
      • Secure Proof of Stake
      • Glossary
    • Sovereign Shard
    • WASM Virtual Machine
    • Ethereum Virtual Machine (EVM)
    • ESDT vs ERC-20
    • Run a OneFinity node
      • System Requirements
      • Configuration
      • Installation
      • Updates
      • Management
      • Nodes
        • Rating
        • Redundancy Setup
        • Configuration files
        • Operation modes
        • Node Databases
        • Import Database
        • Node CLI
      • Staking
      • Unstaking
      • Jail/Unjail
      • Staking Smart Contract
      • Keys
        • Validator Keys
        • Wallet Keys
        • Multikey nodes
  • Validators
    • Overview
    • Git repo
    • Binaries
    • Go
    • General setup
    • How to generate a Validator pem
    • Node start
    • Interact with the blockchain
    • Unjail
  • OneFinity Protocol
    • Overview
    • Governance
    • Protocol Rewards
      • Validators
      • Delegators
      • Staking Agencies
    • ONE Token
    • OG Validators: NFT Staking
  • Technical documentation
    • Overview
    • Integration of the Ethereum Virtual Machine (EVM)
    • Integration of the Ethereum Remote Procedure Call (RPC)
    • Interoperability between Ethereum and MultiversX ecosystems
    • Tools and SDKs for developers
    • Environments
  • Bridges
  • Ecosystem
  • Grants
  • FAQs
  • Social Media
  • Roadmap & Tokenomics
  • Team
Powered by GitBook
On this page
  • Account and Wallet Management
  • Node Operator Overview
  • Node and Validator Dynamics
  1. Technology
  2. Basic concepts

Nodes and Wallets

Account and Wallet Management

Users manage account keys through wallets, applications designed for secure key storage, though advanced users may operate without them. Accounts in the OneFinity Network are identified by a 32-byte public key, doubling as the account address in Bech32 format.

Node Operator Overview

A node operator controls one or more nodes within the OneFinity Network, placing a significant ONE token stake as collateral for each node. This stake, which locks during the operation, signifies commitment to node reliability and efficiency. These staked nodes elevate to validator status, becoming pivotal in consensus activities and eligible for rewards. Unstaked, nodes function as observers, passive yet crucial network entities. The current requirements for those wishing to run a node on OneFinity is 3000 $ONE as staked collateral, along with 1 OneFinity Validator NFT per node.

Node and Validator Dynamics

Nodes are devices executing user requests on the OneFinity Network, with the active ones categorized as eligible validators. These validators engage in consensus processes, block addition, and network state maintenance, identified by a unique 96-byte BLS public key. Accounts, formed by pairs of keys (one public, one secret), transact by submitting signed instructions to the network, each holding a ONE token balance and an associative storage space.

PreviousBasic conceptsNextEpoch and Rounds

Last updated 1 year ago