N |
Field |
Content |
General information |
S.1 |
CASP Name |
BB TRADE ESTONIA OÜ |
S.2 |
Relevant legal entity identifier |
984500L05A5D0E66Q610 |
S.3 |
Blockchain network name |
EOS.IO |
S.4 |
Name of the crypto-asset |
EOS |
S.5 |
Consensus Mechanism |
Delegated Proof of Stake (DPoS) |
S.6 |
Incentive Mechanisms and Applicable Fees |
EOS.IO operates on a Delegated Proof of Stake (DPoS) consensus mechanism. In this system, EOS token holders vote for a limited number of Block Producers (BPs) (typically 21 active BPs) who are responsible for producing blocks, validating transactions, and maintaining the network. Incentives: Block Producers (BPs): Earn rewards in EOS for successfully producing blocks and securing the network. Their election is based on the votes they receive from token holders, incentivizing them to provide reliable service and potentially share rewards. Voters/Token Holders: EOS token holders contribute to network security by staking their EOS to vote for BPs. While there is no direct staking reward from the protocol for voters, a portion of the Block Producers' earnings may be shared with their voters. This encourages active participation in network governance and decentralization. Resource Model (CPU, NET, RAM): EOS traditionally uses a unique resource model where users stake EOS to gain access to network resources (CPU for computation, NET for bandwidth, RAM for storage), rather than paying per-transaction gas fees. This model aims to make basic transactions free for users who have staked sufficient EOS. Fees: For users who don't want to stake or need more resources, they can rent or purchase CPU/NET resources. The DPoS mechanism is designed for extremely high transaction throughput (thousands of transactions per second) and low operational costs, making it highly energy-efficient compared to Proof of Work. |
S.7 |
Beginning of the period to which the disclosure relates |
2024-01-01 |
S.8 |
End of the period to which the disclosure relates |
2024-12-31 |
Mandatory key indicator on energy consumption |
S.9 |
Energy consumption |
~344,281.08 kWh per calendar year |
S.10 |
Energy consumption sources and methodologies |
The energy consumption of the EOS network primarily stems from the electricity used by its Block Producer nodes and supporting full nodes that maintain the blockchain. As a DPoS network, it entirely avoids energy-intensive mining. Methodologies for estimation typically involve: Hardware power draw: Analyzing the typical power consumption of robust server hardware required by Block Producers. Node count and uptime: Scaling this hardware consumption by the known number of active Block Producers (21) and their continuous operational uptime. The design of DPoS inherently minimizes computational energy requirements by relying on elected block producers rather than a global competition. |
Supplementary key indicators on energy and GHG emissions |
S.11 |
Renewable energy consumption |
n/a |
S.12 |
Energy intensity |
~0.000003 kWh per transaction |
S.13 |
Scope 1 DLT GHG emissions – Controlled |
~0 t CO2eq per calendar year |
S.14 |
Scope 2 DLT GHG emissions – Purchased |
~85.5 t CO2eq per calendar year |
S.15 |
GHG intensity |
~0.00001 kg CO2eq per transaction |
S.16 |
Key energy sources and methodologies |
The energy sources for EOS's Block Producers reflect the diverse electricity grid mixes of their global distribution. These include a combination of conventional sources (e.g., natural gas, coal) and renewable/sustainable sources (e.g., hydro, solar, wind, nuclear), depending on the geographic location of the Block Producer operators. Methodologies for assessing this would involve: Geographic identification: Attempting to identify the physical locations of active Block Producer nodes. Grid mix data correlation: Integrating this location information with publicly available datasets on national/regional electricity generation mixes and their associated carbon intensity factors (e.g., from IEA, Ember, regional energy authorities). The limited and known set of active Block Producers makes this estimation more feasible than for highly decentralized PoW networks. |
S.17 |
Key GHG sources and methodologies |
The predominant source of Greenhouse Gas (GHG) emissions for EOS.IO is Scope 2 (indirect emissions from purchased electricity). Methodologies for estimating these emissions involve: Energy consumption * Emission Factor: Multiplying the estimated total electricity consumption of the EOS network (S.8) by the carbon intensity (grams of CO2 equivalent per kWh) of the electricity mix used by its Block Producers. Focus on operational emissions: Calculations primarily focus on the operational energy usage of the DPoS Block Producers, which constitute the main energy-consuming component of the chain. Emissions from hardware manufacturing (Scope 3) are typically outside the scope of such operational reports. |