Flare Network koers

OKcoin Europe LTD

54930069NLWEIGLHXU42

Flare

The Flare Blockchain uses a unique consensus mechanism known as Avalanche Consensus combined with a Federated Byzantine Agreement (FBA) model to provide scalability, security, and decentralization. Flare aims to enable interoperability between blockchains by connecting smart contract platforms to non-Turing complete networks like Bitcoin, and this consensus mechanism plays a crucial role in the network's overall operation. Key Features of Flare's Consensus Mechanism: 1. Avalanche Consensus: Scalable and Fast: The Avalanche consensus is designed for high throughput and low latency. It uses a gossip protocol for communication between nodes, which helps achieve consensus faster than traditional consensus mechanisms like Proof-of-Work (PoW) or Proof-of-Stake (PoS). Nodes quickly confirm transaction validity by repeatedly querying other nodes, increasing network speed. Decentralized and Secure: This consensus mechanism doesn't require heavy computational power like PoW, making it more energy-efficient while maintaining robust security. 2. Federated Byzantine Agreement (FBA): Federated Nodes: FBA ensures that nodes within the Flare network reach a consensus without needing to rely on a central authority. The network uses a set of trusted "federated" nodes that help maintain consensus, allowing nodes outside the federated set to participate without requiring full trust. Leaderless Consensus: FBA allows for a leaderless and decentralized structure, where each node can validate transactions independently, enhancing both security and decentralization. 3. Interoperability: Flare's consensus mechanism is designed to allow cross-chain communication, particularly bridging the gap between Turing-complete smart contract platforms like Ethereum and non-Turing-complete chains like Bitcoin. This makes it possible to bring data and value from non-smart contract chains into the smart contract ecosystem.

Flare Network employs a multifaceted incentive mechanism to promote active participation and ensure the network's security and efficiency. Incentive Mechanisms: 1. FTSO Delegation Rewards: Flare Time Series Oracle (FTSO) data providers offer price feeds to the network. Users can delegate their FLR tokens to these providers, earning a share of the rewards based on the accuracy of the data provided. 2. FlareDrops: A portion of FLR tokens is distributed monthly to WFLR holders through FlareDrops. This incentivizes users to hold and utilize WFLR tokens within the ecosystem. 3. rFLR Rewards: Reward FLR (rFLR) tokens are distributed monthly to enhance liquidity in Flare's DeFi ecosystem. Users can earn rFLR by participating in various DeFi activities, such as lending or borrowing assets. 4. FLR Protocol Emissions: Selected decentralized applications (dApps) launching on Flare receive FLR emissions to incentivize user participation and liquidity provision. Applicable Fees: 1. Transaction Fees: Users pay FLR tokens to execute transactions on the network, compensating validators for processing and confirming transactions. 2. Staking Fees: When delegating FLR tokens to FTSO data providers or participating in staking activities, users may incur fees associated with these services.

2024-04-20

2025-04-20

170820.00000 (kWh/a)

For the calculation of energy consumptions, the so called “bottom-up” approach is being used. The nodes are considered to be the central factor for the energy consumption of the network. These assumptions are made on the basis of empirical findings through the use of public information sites, open-source crawlers and crawlers developed in-house. The main determinants for estimating the hardware used within the network are the requirements for operating the client software. The energy consumption of the hardware devices was measured in certified test laboratories. When calculating the energy consumption, we used - if available - the Functionally Fungible Group Digital Token Identifier (FFG DTI) to determine all implementations of the asset of question in scope and we update the mappings regulary, based on data of the Digital Token Identifier Foundation.