White paper drafted under the European Markets in Crypto-Assets Regulation (EU) 2023/1114 for FFG 76KSM9451

The crypto-asset AlloX (ALLOX) referred to in this white paper is a crypto-asset other than EMT and ART and will be issued on the Ethereum, Base and BNB Smart Chain networks, according to the DTI FFG shown in Section F.14, as of 2026-08-31. The maximum supply of the crypto-asset is 1,000,000,000 tokens.

AlloX is a capital allocation platform that enables users to select market narratives, such as gaming, artificial intelligence, real-world assets, decentralised finance infrastructure, Layer 1 and Layer 2 networks, and decentralised science, and to obtain exposure through diversified baskets of crypto-assets associated with the selected narrative. The platform uses market data and model-based analysis to determine basket composition and weighting across different risk tiers. Portfolio construction, swaps, staking, rebalancing and routing may be executed on-chain through the platform, while allocation and rebalancing activity may be incorporated into subsequent portfolio construction and risk modelling.

The ALLOX crypto-asset is intended to provide platform-related functionality, including participation in governance, access to fee discounts and access to certain premium features within the AlloX platform.

The crypto-asset does not grant any legally enforceable or contractual rights or obligations to its holders or purchasers. Any functionalities accessible through the underlying technology are purely technical or operational in nature and do not confer rights comparable to ownership, profit participation, governance, or similar entitlements known from traditional financial instruments.

As defined in Article 3(9) of Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on Markets in Crypto-Assets – amending Regulations (EU) No 1093/2010 and (EU) No 1095/2010 and Directives 2013/36/EU and (EU) 2019/1937 – a utility token is “a type of crypto-asset that is only intended to provide access to a good or a service supplied by its issuer”. This crypto-asset does not qualify as a utility token, as its intended use goes beyond providing access to a good or a service supplied solely by the issuer.

AlloX Ltd is seeking admission to trading on the Payward Global Solutions LTD (“Kraken”) platform in the European Union in accordance with Article 5 of Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on Markets in Crypto-Assets, and amending Regulations (EU) No 1093/2010 and (EU) No 1095/2010 and Directives 2013/36/EU and (EU) 2019/1937. The admission to trading is not accompanied by a public offer of the crypto-asset.

AlloX Ltd operates AlloX (allox.ai), an AI-powered capital allocation platform that transforms crypto market narratives (e.g. AI, DeFi, Gaming, RWA, SocialFi, DePIN) into diversified, risk-managed, automatically rebalanced on-chain portfolios. The Company is non-custodial and aggregates swap execution across BNB Chain, Ethereum and Base.

AlloX Ltd was incorporated on 20 August 2026 and has no trading or financial history since registration. Initial capitalisation consists of 1 ordinary share of US$1.00 par value, issued to the sole shareholder at incorporation; no revenue, assets, or liabilities have yet been recorded for the entity.

AlloX is a capital allocation platform that enables users to select market narratives, such as gaming, artificial intelligence, real-world assets, decentralised finance infrastructure, Layer 1 and Layer 2 networks, and decentralised science, and to obtain exposure through diversified baskets of crypto-assets associated with the selected narrative. The platform uses market data and model-based analysis to determine basket composition and weighting across different risk tiers. Portfolio construction, swaps, staking, rebalancing and routing may be executed on-chain through the platform, while allocation and rebalancing activity may be incorporated into subsequent portfolio construction and risk modelling.

The project does not involve the granting of ownership, profit-participation rights, or legal claims against the project entity or its contributors. The long-term evolution of the AlloX system, including the scope of available features, the decentralisation roadmap and the operational continuity of the infrastructure, may vary based on technical, economic, and regulatory considerations. All future developments remain subject to change.

This section provides an overview of the historical developments related to the ALLOX crypto-asset and a description of planned or anticipated project milestones. All forward-looking elements are subject to significant uncertainty. They do not constitute commitments, assurances, or guarantees, and may be modified, delayed, or discontinued at any time. The implementation of past milestones cannot be assumed to continue in the future, and future changes may have adverse effects for token holders.

Past milestones:

- Platform Launch (23 February 2026): The AlloX platform was launched publicly with support for BNB Chain, Base, Ethereum and Solana.

- bStocks Launch (15 April 2026): AlloX launched its first on-chain revenue-generating product, providing access to 68 tokenised US stocks and exchange-traded funds that can be traded on a 24/7 basis through the Binance Web3 API.

- Security Audit (2026): A security audit of the project was completed by CertiK, resulting in a Grade A assessment and placement within the top 10% of projects audited by CertiK.

- Binance Wallet Listing and Booster Campaign (2026): AlloX was listed on Binance Wallet and participated in an Exclusive campaign under Binance's Booster format.

- Strategic Investment (2026): AlloX received a strategic investment from Zerra Ventures, a Turkey-based venture investor.

Future milestones:

- ALLOX Token Generation Event (Q3 2026): The Token Generation Event for the ALLOX crypto-asset is targeted for the third quarter of 2026. The planned event is intended to expand distribution of the crypto-asset beyond wallets. The associated staking mechanics, including lock-up arrangements, reward calculations and unstaking terms, remain under development and have not yet been finalised.

- White-Label Basket Engine (Future): AlloX plans to develop a white-label basket engine intended for integration with Sui, Aptos and other emerging Layer 1 and Layer 2 ecosystems.

- API Licensing (Future): AlloX plans to make its application programming interfaces available for licensing to wallets and protocols, enabling third-party services to integrate AlloX functionality into their existing user interfaces and workflows.

Note: All future milestones are subject to significant uncertainty, including but not limited to technical feasibility, regulatory developments, market adoption, and community governance decisions. The project may modify, delay, or discontinue any of these initiatives at any time. Past implementation or performance outcomes do not constitute an indication of future results, and any such changes may materially affect the characteristics, availability, or perceived value of the ALLOX crypto-asset for its holders.

In May 2026, Zerra Ventures made a strategic investment of USD 2.5 million in AlloX. The investment is intended to support the continued development of the AlloX platform, including product development, ecosystem expansion, and the project's longer-term positioning within the digital-asset market.

This white paper relates solely to the admission of the token to trading and does not constitute an offer of crypto-assets to the public.

The purpose of seeking admission to trading is to enable the crypto-asset to be listed on a regulated platform in accordance with the applicable provisions of Regulation (EU) 2023/1114 and Commission Implementing Regulation (EU) 2024/2984. The white paper has been drawn up to comply with the transparency requirements applicable to trading venues.

Holder restrictions are subject to the rules applicable to the crypto-asset service provider, as well as any additional restrictions that provider may impose.

The token is intended to be listed on the trading platform operated by Payward Global Solutions LTD ("Kraken"). Access to this platform depends on regional availability and user eligibility under Kraken’s terms and conditions. Investors should consult Kraken’s official documentation to determine whether they meet the requirements for account creation and token trading.

The costs involved in accessing the trading platform depend on the specific fee structure and terms of the respective crypto-asset service provider. These may include trading fees, deposit or withdrawal charges, and network-related gas fees. Investors are advised to consult the applicable fee schedule of the chosen platform before engaging in trading activities.

Not applicable, as this white paper is written to seek admission to trading, not for the initial offer to the public.

MiCA-compliant Crypto Asset Service Providers shall have strong measures in place in order to manage conflicts of interest. Due to the broad audience this white-paper addresses, potential investors should always check the conflicts of Interest policy of their respective counterparty.

Not applicable, as this white paper is written to seek admission to trading, not for the initial offer to the public.

Not applicable, as this white paper is written to seek admission to trading, not for the initial offer to the public.

The ALLOX crypto-asset is intended to function as a technical and economic component within the AlloX platform. Its planned uses include participation in governance concerning narrative categories, risk parameters and platform upgrades, access to discounts on trading, portfolio creation and transaction fees, and access to premium platform features, including advanced AI functionalities, priority allocations and selected campaigns.

Beyond the functions described above, ALLOX is not intended to confer any ownership, profit participation, repayment, redemption or other legally enforceable economic entitlement on its holders. In particular, holding ALLOX does not itself entitle the holder to any fixed quantity of AI services, portfolio allocations, returns, revenues or other assets, nor does it confer corporate governance rights in relation to AlloX or any related entity.

The functionalities described in this section are technical and platform-related in nature and depend on their implementation and the continued operation and development of the AlloX platform. Their availability may be affected by platform changes, technical design decisions, system stability, operational conditions and other factors outside the control of token holders.

Future milestones:

- ALLOX Token Generation Event (Q3 2026): The Token Generation Event for the ALLOX crypto-asset is targeted for the third quarter of 2026. The planned event is intended to expand distribution of the crypto-asset beyond wallets. The associated staking mechanics, including lock-up arrangements, reward calculations and unstaking terms, remain under development and have not yet been finalised.

- White-Label Basket Engine (Future): AlloX plans to develop a white-label basket engine intended for integration with Sui, Aptos and other emerging Layer 1 and Layer 2 ecosystems.

- API Licensing (Future): AlloX plans to make its application programming interfaces available for licensing to wallets and protocols, enabling third-party services to integrate AlloX functionality into their existing user interfaces and workflows.

Note: All future milestones are subject to significant uncertainty, including but not limited to technical feasibility, regulatory developments, market adoption, and community governance decisions. The project may modify, delay, or discontinue any of these initiatives at any time. Past implementation or performance outcomes do not constitute an indication of future results, and any such changes may materially affect the characteristics, availability, or perceived value of the ALLOX crypto-asset for its holders.

The crypto-asset referred to herein is a crypto-asset other than an EMT or ART and will be available on the Ethereum, Base and BNB Smart Chain networks. The crypto-asset will fungible up to 18 digits after the decimal point. The crypto-asset constitutes a digital representation recorded on distributed-ledger technology and does not confer ownership, governance, profit participation, or any other legally enforceable rights. Any functionalities associated with the token are limited to potential technical features within the relevant platform environment. These functionalities do not represent contractual entitlements and may depend on future development decisions, technical design choices, and operational conditions. The crypto-asset does not embody intrinsic economic value; instead, its value, if any, is determined exclusively by market dynamics such as supply, demand, and liquidity in secondary markets.

No further services are currently planned.

The crypto-asset does not grant any legally enforceable or contractual rights or obligations to its holders or purchasers. Any functionalities accessible through the underlying technology are of a purely technical or operational nature and do not constitute rights comparable to ownership, profit participation, governance, or similar entitlements known from traditional financial instruments. Accordingly, holders do not acquire any legally enforceable claim against the issuer of the crypto-asset or any third party.

As the crypto-asset does not confer any legally enforceable rights or obligations, there are no applicable procedures or conditions for their exercise. Any interaction or functionality that may be available within the project’s technical infrastructure – such as participation mechanisms or protocol-level features – serves operational purposes only and does not create, evidence, or constitute any contractual or statutory entitlement.

As the crypto-asset does not confer any legally enforceable rights or obligations, there are no conditions or mechanisms for modifying such rights or obligations. Adjustments to the technical protocol, smart contract logic, or related systems may occur in the ordinary course of development or maintenance. Such changes do not alter the legal position of holders, as no contractual rights exist and no rights arise under applicable law or regulation. Holders should not interpret technical updates or governance-related changes as amendments to legally binding entitlements.

No future public offers of crypto-assets are currently planned by the issuer.

The crypto-assets themselves are not subject to any technical or contractual transfer restrictions and are generally freely transferable. However, crypto-asset service providers may impose restrictions on buyers or sellers in accordance with applicable laws, internal policies or contractual terms agreed with their clients.

Not applicable.

Applicable law likely depends on the location of any particular transaction with the token.

Competent court likely depends on the location of any particular transaction with the token.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The following applies to Ethereum:

The crypto-asset operates on a defined set of protocols and technical standards that are intended to ensure its security, decentralisation, and functionality. Key items are set out below.

1. Network protocols

Ethereum operates as a decentralised, peer-to-peer network. Nodes communicate using the DevP2P networking stack, with RLPx as the encrypted transport layer for peer-to-peer messages.

Transaction ordering and finality are secured through a Proof-of-Stake (PoS) consensus mechanism. Validators on the Beacon Chain propose blocks, attest to them, and finalise them through Casper FFG operating on top of the LMD-GHOST fork-choice rule. Smart contract execution is performed by the Ethereum Virtual Machine (EVM), which interprets EVM bytecode within the gas limits set by the protocol and by the transaction sender.

2. Transaction and address standards

Ethereum addresses are 20-byte identifiers, derived as the last 20 bytes of the Keccak-256 hash of the uncompressed elliptic-curve public key (excluding the 0x04 prefix). They are commonly represented as 40-character hexadecimal strings with a 0x prefix and an optional EIP-55 mixed-case checksum.

The protocol currently supports the following transaction types:

- Type 0: legacy transactions (pre-EIP-1559).

- Type 1: access-list transactions (EIP-2930).

- Type 2: dynamic-fee transactions with base-fee burning (EIP-1559).

- Type 3: blob-carrying transactions (EIP-4844), introduced with the Dencun upgrade on 2024-03-13.

- Type 4: set-code transactions (EIP-7702), introduced with the Pectra upgrade on 2025-05-07, allow externally owned accounts (EOAs) to authorise delegated code execution during transactions, without permanently converting the account into a smart contract. This enables features such as transaction batching, sponsored gas payments and delegated signing.

3. Blockchain data structure and block standards

The Ethereum state consists of accounts (externally owned accounts and smart contracts) together with their associated storage and code, organised in Modified Merkle Patricia Tries to allow efficient verification.

Each block contains:

- a block header, comprising the parent hash, state root, transactions root, receipts root, timestamp, gas limit, gas used, and the proposer's signature, among other fields;

- the ordered list of transactions, including smart-contract executions and value transfers; and

- blob commitments, where applicable, referring to data published to the data availability layer under EIP-4844.

Block size is not fixed in bytes. It is constrained by a per-block gas limit, which is adjustable within protocol-defined bounds and currently targets approximately 60 million gas following EIP-7935 (Fusaka, activated on 2025-12-03). EIP-7825 (Fusaka) also introduces a per-transaction gas cap of 16,777,216 gas to improve block composability and resilience against denial-of-service patterns.

The data availability layer used by Layer 2 rollups, introduced through EIP-4844, was further developed by EIP-7691 (Pectra, 2025-05-07), which raised the maximum number of blob commitments per block, and by EIP-7594 (Fusaka, 2025-12-03), which introduced Peer Data Availability Sampling (PeerDAS). PeerDAS enables nodes to verify that blob data has been published by sampling small portions of it, rather than downloading every blob in full. Following PeerDAS, Ethereum uses Blob Parameter Only (BPO) forks, introduced by EIP-7892, to adjust blob targets and maxima between major upgrades.

4. Upgrade and improvement standards

Ethereum protocol upgrades are coordinated through the Ethereum Improvement Proposal (EIP) process. EIPs are published openly, reviewed by core developers and the wider community, and bundled into named hard-fork upgrades. The most recent network upgrades are the Pectra upgrade (2025-05-07) and the Fusaka upgrade (2025-12-03). The next named upgrade currently under preparation by the Ethereum core developers is referred to as Glamsterdam.

The following applies to Base:

Base is an Ethereum Layer-2 rollup introduced by Coinbase and launched in 2023 using Optimism’s OP Stack. On 2026-02-18, Base announced a migration towards a unified, Base-operated technology stack. Base does not operate a separate decentralised consensus mechanism comparable to a Layer-1 blockchain. Transactions are currently ordered by a centralised sequencer, while transaction data and state commitments are posted to Ethereum, whose Proof-of-Stake consensus secures the underlying data availability and settlement layer. Since the Azul upgrade in May 2026, Base uses a multi-proof system in which state commitments may be verified by trusted execution environment (TEE) proofs or permissionless zero-knowledge (ZK) proofs, with the ZK path able to override an invalid TEE-backed proposal. If the sequencer becomes unavailable, users may submit transactions through Ethereum Layer-1 for inclusion, subject to the protocol’s applicable delay mechanisms.

The following applies to BNB Smart Chain (BSC):

BSC is a Layer-1 blockchain that utilises a Proof-of-Staked-Authority (PoSA) consensus mechanism. This mechanism combines elements of Proof-of-Authority (PoA) and Delegated-Proof-of-Stake (DPoS) and is intended to secure the network and validate transactions. In PoSA, validators are selected based on their stake and authority, with the goal of providing fast transaction times and low fees while maintaining network security through staking.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The following applies to Ethereum:

1. Decentralised Ledger: The Ethereum blockchain acts as the decentralised ledger and execution environment for ETH transactions and smart-contract operations, including ERC-20 token transfers, maintaining an append-only record of transfers and account balances to support transparency and verifiable settlement.

2. Account Model: Ethereum uses two account types: externally owned accounts (EOAs), which are controlled through private keys, and contract accounts, which are controlled through deployed smart contract code. Following the Pectra upgrade on 2025-05-07, EOAs can additionally authorise delegated code execution through EIP-7702 transactions without permanently converting the account into smart contracts.

3. Private Key Management: Users must securely store the private keys and recovery material associated with their wallets. Loss or compromise of a private key may result in irreversible loss of access to the associated ETH or ERC-20 token balance.

4. Cryptographic Integrity: Ethereum uses ECDSA over the secp256k1 elliptic curve for key generation and digital signatures on the execution layer. Keccak-256 hashing is used for transaction hashing, state hashing and address derivation. Ethereum addresses are derived from the last 20 bytes of the Keccak-256 hash of the public key. On the consensus layer, BLS (Boneh-Lynn-Shacham) signatures are used to aggregate validator attestations under the Proof-of-Stake consensus mechanism.

The following applies to Base:

1. Base-compatible wallets: The tokens are supported by wallets compatible with the Ethereum Virtual Machine (EVM), including MetaMask, Coinbase Wallet and Trust Wallet. These wallets interact with Base in the same manner as with other EVM-compatible networks through standard Web3 interfaces.

2. Distributed ledger: Base operates as a Layer-2 network on Ethereum and maintains its own distributed ledger for recording token transactions. Transaction batches and corresponding state commitments are periodically posted to Ethereum Layer 1, allowing the Layer-2 state to be anchored to Ethereum and verified through the network’s security mechanisms.

3. Token standards: Base supports crypto-assets implemented using the ERC-20 token standard. As an EVM-compatible network, Base supports the same token interface standards commonly used on Ethereum. Since 8 July 2026, Base additionally supports B20, a native token standard implemented at protocol level that retains the ERC-20 interface, so B20 tokens remain interoperable with wallets and other infrastructure supporting ERC-20.

4. Scalability and transaction efficiency: As a Layer-2 rollup, Base executes transactions off-chain and periodically posts transaction data and state commitments to Ethereum. This reduces the volume of data processed directly on the Ethereum mainnet and typically results in lower transaction fees than settling the same transactions on Ethereum directly.

The following applies to BNB Smart Chain (BSC):

1. BSC-compatible wallets

Tokens on BSC are supported by wallets compatible with the Ethereum Virtual Machine (EVM), such as MetaMask. These wallets can be configured to connect to the BSC network and are designed to interact with BSC using standard Web3 interfaces.

2. Decentralised Ledger

BSC maintains its own decentralised ledger for recording token transactions. This ledger is intended to ensure transparency and security, providing a verifiable record of all activities on the network.

3. BEP-20 token standard

BSC supports tokens implemented under the BEP-20 standard, which is tailored for the BSC ecosystem. This standard is designed to facilitate the creation and management of tokens on the network.

4. Scalability and transaction efficiency

BSC is designed to handle high volumes of transactions with low fees. It leverages its PoSA consensus mechanism to achieve fast transaction times and efficient network performance, making it suitable for applications requiring high throughput.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The following applies to Ethereum:

Ethereum uses a Proof-of-Stake (PoS) consensus mechanism introduced with The Merge on 2022-09-15, which replaced the previous Proof-of-Work consensus model. The PoS mechanism is implemented through Gasper, combining Casper-FFG for finality with the LMD-GHOST fork-choice rule for chain selection. Validators participate in consensus by staking ETH through the Beacon Chain. Validators are pseudo-randomly selected to propose new blocks, while other validators attest to the validity of proposed blocks. The network operates using 12-second slots grouped into epochs of 32 slots. Under normal network conditions, finality is typically achieved after two epochs, approximately 12.8 minutes, through Casper-FFG. The LMD-GHOST fork-choice rule determines the canonical chain based on the accumulated weight of validator attestations. Validators that engage in certain malicious behaviour, such as equivocation or contradictory attestations, may be subject to slashing penalties, while offline validators may incur inactivity penalties. Subsequent network upgrades, including Dencun (2024-03-13), Pectra (2025-05-07) and Fusaka (2025-12-03), introduced protocol changes affecting Ethereum’s consensus mechanism and Layer 2 functionality.

The following applies to Base:

Base does not operate a decentralised validator set comparable to a Layer-1 blockchain. Transaction ordering is currently performed by a single sequencer, while transaction data and state commitments are posted to Ethereum and ultimately benefit from Ethereum’s Proof-of-Stake consensus. Following the Azul upgrade, Base uses a multi-proof system for Layer-2 checkpoints associated with withdrawals to Ethereum: TEE proofs support the normal path, while permissionless zero-knowledge proofs provide an independent verification and challenge path. The sequencer remains a central component of transaction ordering.

The following applies to BNB Smart Chain (BSC):

BSC uses a hybrid consensus mechanism called Proof-of-Staked-Authority (PoSA), which combines elements of Delegated-Proof-of-Stake (DPoS) and Proof-of-Authority (PoA). This method is intended to support fast block times and low fees while maintaining a level of decentralisation and security.

Core components

1. Validators (Cabinet and Candidates): Validators are responsible for producing blocks, validating transactions, and maintaining network security. The validator set consists of up to 45 validators, including 21 “Cabinet” validators and 24 “Candidate” validators, selected based on bonded stake. A subset of validators is selected per epoch to participate in block production.

2. Delegators: Token holders may delegate BNB to validators to support their selection. Delegators share in the rewards generated by validators, providing an economic incentive to participate in staking.

3. Candidates: Validator candidates are nodes that have staked BNB but are not part of the primary validator subset for a given epoch. They may be selected into the active set based on staking rank and can participate in block production with lower probability.

Consensus process

4. Validator selection: Validators are ranked based on the amount of bonded BNB and are updated periodically (approximately every 24 hours). The highest-ranked validators form the active validator set, with Cabinet validators having a higher probability of participating in block production.

5. Block production: Validators take turns producing blocks in a PoA-like manner. For each epoch, a subset of validators is selected to produce and validate blocks sequentially, ensuring high throughput and low latency.

6. Transaction finality: BSC achieves short block times (approximately 0.45 seconds) and fast finality. With Fast Finality enabled, blocks are typically finalised within approximately one second, subject to validator participation.

7. Staking: Validators must stake BNB as collateral and may be subject to slashing in cases of misbehaviour, including double-signing, malicious voting, or prolonged downtime.

8. Delegation and rewards: Validators and delegators are rewarded through transaction fees collected in each block. Validators may share rewards with delegators to attract stake.

9. Transaction fees: BSC does not rely on inflationary block rewards; instead, validators are compensated primarily through transaction fees paid in BNB, aligning incentives with network usage.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The following applies to Ethereum:

Ethereum’s Proof-of-Stake (PoS) mechanism secures the network through validator incentives and protocol-defined penalties. Validators are required to stake ETH in order to participate in block proposal and attestation activities. A minimum of 32 ETH is required to activate a validator. Following the Pectra upgrade on 2025-05-07, EIP-7251 increased the maximum effective balance per validator from 32 ETH to 2,048 ETH. Validators may receive protocol-defined rewards for proposing blocks, attesting to valid blocks and participating in sync committees. Rewards consist of newly issued ETH and transaction-related fees. Transaction fees on Ethereum follow the mechanism introduced by EIP-1559, under which each transaction includes a base fee that is burned at the protocol level and an optional priority fee paid to the validator proposing the relevant block. Validators that engage in certain malicious behaviour, including equivocation or contradictory attestations, may be subject to slashing penalties. Validators that fail to participate correctly in consensus activities may also incur inactivity penalties. These mechanisms are intended to support validator participation and the economic security of the Ethereum network.

The following applies to Base:

Base uses ETH for transaction fees and does not issue a separate Base network token or operate a staking or validator-reward mechanism. Fees comprise a charge for Layer-2 execution and a component reflecting the cost of posting transaction data to Ethereum. The checkpoint-verification system also uses proposal bonds, which may reward a successful challenge to an invalid checkpoint proposal.

The following applies to BNB Smart Chain (BSC):

BSC uses the Proof-of-Staked-Authority (PoSA) consensus mechanism to support network security and incentivise participation from validators and delegators.

Incentive mechanisms

1. Validators: Validators must self-delegate BNB in order to participate in the validator system. Validator selection is staking-based, and validators that rank highly enough enter the active set and participate in block production and transaction validation. Validators are rewarded from transaction fees collected on the network. When a block is produced, most of the block fee is allocated to the validator that proposed the block. A portion is retained as validator commission, while the remainder is allocated for distribution through the validator credit structure.

2. Delegators: BNB holders may delegate BNB to validators. This increases the validator’s total stake and may improve its position in the validator ranking. Delegators share in the rewards earned by the validator they support, after deduction of the validator’s commission.

3. Candidates: BSC distinguishes between Cabinet, Candidate and Inactive validators. The current model provides that the top 21 validators form the Cabinet, while the validators ranked from 22 to 45 are Candidates. Candidate validators have a smaller chance of producing blocks, but they remain part of the broader validator structure and support network resilience. Validator roles are updated every 24 hours based on the latest staking information.

4. Economic Security: Validators may be penalised for misconduct or poor performance. Slashable events include double signing, malicious fast-finality voting and unavailability. Depending on the violation, consequences may include removal from the validator set, loss of staking rewards and slashing of part of the validator’s self-delegated BNB. The staking model therefore creates an economic incentive for validators and delegators to support reliable validator performance.

Fees on BSC

5. Transaction fees: Transaction fees on BSC are paid in BNB and are intended to compensate validators for maintaining the network. BSC is designed as a comparatively low-fee network, and smart-contract transactions and transfers require gas fees in BNB.

6. Validator rewards: BSC does not rely on a separate protocol-level block reward. Instead, staking rewards are derived from transaction fees. Most of the block fee is allocated to the proposing validator, then split between validator commission and delegator-linked reward distribution.

7. System-level fee allocation: Part of transaction-fee revenue is collected through the System Reward Contract and used for designated system purposes, including fast-finality rewards.

8. Smart contract fees: Deploying and interacting with smart contracts on BSC requires payment of gas fees in BNB. These fees depend on the computational resources required and form part of the network’s overall fee and validator-incentive model.

Not applicable, as the DLT is not operated by the issuer, the offeror, the person seeking admission to trading, or any third party acting on their behalf.

The AlloX application underwent an external security assessment conducted by CertiK, with the final report published on 11 April 2026. The assessment covered the frontend and backend application repositories and included dynamic testing, manual review and testnet deployment.

The assessment identified 13 findings, including no critical findings, two high-severity findings and three medium-severity findings. Both high-severity and all three medium-severity findings were reported as resolved. Of the seven low-severity findings, five were resolved and two were acknowledged, while the single informational finding was resolved.

Users should note that security assessments provide a limited evaluation of specific components at a particular point in time and do not eliminate the risk of future vulnerabilities, implementation errors or security incidents.

1. Regulatory and Compliance

Regulatory frameworks applicable to crypto-asset services in the European Union and in third countries are evolving. Supervisory authorities may introduce, interpret, or enforce rules that affect (i) the eligibility of this crypto-asset for admission to trading, (ii) the conditions under which a crypto-asset service provider may offer trading, custody, or transfer services for it, or (iii) the persons or jurisdictions to which such services may be provided. As a result, the crypto-asset service provider admitting this crypto-asset to trading may be required to suspend, restrict, or terminate trading or withdrawals for regulatory reasons, even if the crypto-asset itself continues to function on its underlying network.

2. Trading venue and connection risk

Trading in the crypto-asset depends on the uninterrupted operation of the trading venues on which it is listed and, where applicable, on its technical connections to external liquidity sources or venues. Interruptions such as system downtime, maintenance, faulty integrations, API changes, or failures at an external venue can temporarily prevent order placement, execution, deposits, or withdrawals, even when the underlying blockchain is functioning. In addition, trading platforms in emerging markets may operate under differing governance, compliance, and oversight standards, which can increase the risk of operational failures or disorderly market conditions.

3. Market formation and liquidity conditions

The price and tradability of the crypto-asset depend on actual trading activity on the venues to which the service provider is connected, whether centralised exchanges (CEXs) or decentralised exchanges (DEXs). Trading volumes may at times be low, order books thin, or liquidity concentrated on a single venue. In such conditions, buy or sell orders may not be executed in full or may be executed only at a less favourable price, resulting in slippage.

Volatility: The market price of the crypto-asset may fluctuate significantly over short periods, including for reasons that are not linked to changes in the underlying project or protocol. Periods of limited liquidity, shifts in overall market sentiment, or trading on only a small number of CEXs or DEXs can amplify these movements and lead to higher slippage when orders are executed. As a result, investors may be unable to sell the crypto-asset at or close to a previously observed price, even where no negative project-specific event has occurred.

4. Counterparty and service provider dependence

The admission of the crypto-asset to trading may rely on several external parties, such as connected centralised or decentralised trading venues, liquidity providers, brokers, custodians, or technical integrators. If any of these counterparties fail to perform, suspend their services, or apply internal restrictions, the trading, deposit, or withdrawal of the crypto-asset on the listing crypto-asset service provider can be interrupted or halted.

Quality of counterparties: Trading venues and service providers in certain jurisdictions may operate under regulatory or supervisory standards that are lower or differently enforced than those applicable in the European Union. In such environments, deficiencies in governance, risk management, or compliance may remain undetected, which increases the probability of abrupt service interruptions, investigations, or forced wind-downs.

Delisting and service suspension: The crypto-asset’s availability may depend on the internal listing decisions of these counterparties. A delisting or suspension on a key connected venue can materially reduce liquidity or make trading temporarily impossible on the admitting service provider, even if the underlying crypto-asset continues to function.

Insolvency of counterparties: If a counterparty involved in holding, routing, or settling the crypto-asset becomes insolvent, enters restructuring, or is otherwise subject to resolution measures, assets held or processed by that counterparty may be frozen, become temporarily unavailable, or be recoverable only in part or not at all, which can result in losses for clients whose positions were maintained through that counterparty. This risk applies in particular where client assets are held on an omnibus basis or where segregation is not fully recognised in the counterparty’s jurisdiction.

5. Operational and information risks

Due to the irrevocability of blockchain transactions, incorrect transaction approvals or the use of wrong networks or addresses will typically make the transferred funds irrecoverable. Because trading may also rely on technical connections to other venues or service providers, downtime or faulty code in these connections can temporarily block trading, deposits, or withdrawals even when the underlying blockchain is functioning. In addition, different groups of market participants may have unequal access to technical, governance, or project-related information, which can lead to information asymmetry and place less informed investors at a disadvantage when making trading decisions.

6. Market access and liquidity concentration risk

If the crypto-asset is only available on a limited number of trading platforms or through a single market-making entity, this may result in reduced liquidity, greater price volatility, or periods of inaccessibility for retail holders.

1. Insolvency of the issuer

As with any commercial entity, the issuer may face insolvency risks. These may result from insufficient funding, low market interest, mismanagement, or external shocks (e.g. pandemics, armed conflicts). In such a case, ongoing development, support, and governance of the project may cease, potentially affecting the viability and tradability of the crypto-asset.

2. Legal and regulatory risks

The issuer operates in a dynamic and evolving regulatory environment. Failure to comply with applicable laws or regulations in relevant jurisdictions may result in enforcement actions, penalties, or restrictions on the project’s operations. These may negatively impact the crypto-asset’s availability, market acceptance, or legal status.

3. Operational risks

The issuer may fail to implement adequate internal controls, risk management, or governance processes. This can result in operational disruptions, financial losses, delays in updating the white paper, or reputational damage.

4. Governance and decision-making

The issuer’s management body is responsible for key strategic, operational, and disclosure decisions. Ineffective governance, delays in decision-making, or lack of resources may compromise the stability of the project and its compliance with MiCA requirements. High concentration of decision-making authority or changes in ownership/control can amplify these risks.

5. Reputational risks

The issuer’s reputation may be harmed by internal failures, external accusations, or association with illicit activity. Negative publicity can reduce trust in the issuer and impact the perceived legitimacy or value of the crypto-asset.

6. Counterparty dependence

The issuer may depend on third-party providers for certain core functions, such as technology development, marketing, legal advice, or infrastructure. If these partners discontinue their services, change ownership, or underperform, the issuer’s ability to operate the project or maintain investor communication may be impaired. This could disrupt project continuity or undermine market confidence, ultimately affecting the crypto-asset’s value.

1. Valuation risk

The crypto-asset does not represent a claim, nor is it backed by physical assets or legal entitlements. Its market value is driven solely by supply and demand dynamics and may fluctuate significantly. In the absence of fundamental value anchors, such assets can lose their entire market value within a very short time. Historical market behaviour has shown that some types of crypto-assets have become worthless. Investors should be aware that this crypto-asset may lose all of its value.

2. Market volatility risk

Crypto-asset prices can fluctuate sharply due to changes in market sentiment, macroeconomic conditions, regulatory developments, or technology trends. Such volatility may result in rapid and significant losses. Holders should be prepared for the possibility of losing the full amount invested.

3. Liquidity and price-determination risk

Low trading volumes, fragmented trading across venues, or the absence of active market makers can restrict the ability to buy or sell the crypto-asset. In such situations, it is not guaranteed that an observable market price will exist at all times. Spreads may widen materially, and orders may only be executable under unfavourable conditions, which can make liquidation costly or temporarily impossible.

4. Crypto-asset security risk

Loss or theft of private keys, unauthorised access to wallets, or failures of custodial or exchange service providers can result in the irreversible loss of assets. Because blockchain transactions are final, recovery of funds after a compromise is generally impossible.

5. Fraud and scam risk

The pseudonymous and irreversible nature of blockchain transactions can attract fraudulent schemes. Typical forms include fake or unauthorised crypto-assets imitating established ones, phishing attempts, deceptive airdrops, or social-engineering attacks. Investors should exercise caution and verify the authenticity of counterparties and information sources.

6. Legal and regulatory reclassification risk

Legislative or regulatory changes in the European Union or in the Member State where the crypto-asset is admitted to trading may alter its legal classification, permitted uses, or tradability. In third countries, the crypto-asset may be treated as a financial instrument or security, which can restrict its offering, trading, or custody.

7. Absence of investor protection

The crypto-asset is not covered by investor-compensation or deposit-guarantee schemes. In the event of loss, fraud, or insolvency of a service provider, holders may have no access to recourse mechanisms typically available in regulated financial markets.

8. Counterparty risk

Reliance on third-party exchanges, custodians, or intermediaries exposes holders to operational failures, insolvency, or fraud of these parties. Investors should conduct due diligence on service providers, as their failure may lead to the partial or total loss of held assets.

9. Reputational risk

Public confidence in crypto-assets generally can be affected by events in the wider market, including security incidents at third parties and adverse media coverage of the sector. A decline in confidence, whether or not connected to the token or its issuer, may reduce demand for the token and affect its market price.

10. Community and sentiment risk

Because the crypto-asset’s perceived relevance and expected future use depend largely on community engagement and the prevailing sentiment, a loss of public interest, negative coverage or reduced activity of key contributors can materially reduce market demand.

11. Macroeconomic and interest-rate risk

Fluctuations in interest rates, exchange rates, general market conditions, or overall market volatility can influence investor sentiment towards digital assets and affect the crypto-asset’s market value.

12. Taxation risk

Tax treatment varies across jurisdictions. Holders are individually responsible for complying with all applicable tax laws, including the reporting and payment of taxes arising from the acquisition, holding, or disposal of the crypto-asset.

13. Anti-money-laundering and counter-terrorist financing risk

Wallet addresses or transactions connected to the crypto-asset may be linked to sanctioned or illicit activity. Regulatory responses to such findings may include transfer restrictions, reporting obligations, or the freezing of assets on certain venues.

14. Market-abuse risk

Due to limited oversight and transparency, crypto-assets may be vulnerable to market-abuse practices such as spoofing, pump-and-dump schemes, or insider trading. Such activities can distort prices and expose holders to sudden losses.

15. Legal ownership and jurisdictional risk

Depending on the applicable law, holders of the crypto-asset may not have enforceable ownership rights or effective legal remedies in cases of disputes, fraud, or service failure. In certain jurisdictions, access to exchanges or interfaces may be restricted by regulatory measures, even if on-chain transfer remains technically possible.

16. Circulating supply and token unlock risk

A significant part of the total supply is allocated to the team, ecosystem and reserve pools and is released over time in accordance with the applicable tokenomics and vesting schedule. Increases in the circulating supply upon scheduled unlocks may affect liquidity conditions and the market price of the token. Holders of large allocations may also dispose of tokens once released, which can affect market conditions at the time of release.

As this white paper relates to admission to trading of the crypto-asset, the risk description below reflects general implementation risks typically associated with crypto-asset projects and relevant for the crypto-asset service provider.

Delays, failures, or changes in the implementation of the project as outlined in its public roadmap or technical documentation may negatively impact the perceived credibility or usability of the crypto-asset. This includes risks related to project governance, resource allocation, technical delivery, and team continuity.

Key-person risk: The project may rely on a limited number of individuals for development, maintenance, or strategic direction. The departure, incapacity, or misalignment of these individuals may delay or derail the implementation.

Timeline and milestone risk: Project milestones may not be met as announced. Delays in feature releases, protocol upgrades, or external integrations can undermine market confidence and affect the adoption, use, or value of the crypto-asset.

Delivery risk: Even if implemented on time, certain functionalities or integrations may not perform as intended or may be scaled back during execution, limiting the crypto-asset’s practical utility.

As this white paper relates to admission to trading of the crypto-asset, the following risks concern the underlying distributed ledger technology (DLT), its supporting infrastructure, and related technical dependencies. Failures or vulnerabilities in these systems may affect the availability, integrity, or transferability of the crypto-asset.

1. Blockchain dependency risk

The functionality of the crypto-asset depends on the continuous and stable operation of the blockchain(s) on which it is issued. Network congestion, outages, or protocol errors may temporarily or permanently disrupt on-chain transactions. Extended downtime or degradation in network performance can affect trading, settlement, or the usability of the crypto-asset.

2. Smart contract vulnerability risk

The smart contract that defines the crypto-asset’s parameters or governs its transfers may contain coding errors or security vulnerabilities. Exploitation of such weaknesses can result in unintended token minting, permanent loss of funds, or disruption of token functionality. Even after external audits, undetected vulnerabilities may persist due to the immutable nature of deployed code.

3. Wallet and key-management risk

The custody of crypto-assets relies on secure private key management. Loss, theft, or compromise of private keys results in irreversible loss of access. Custodians, trading venues, or wallet providers may be targeted by cyberattacks. Compatibility issues between wallet software and changes to the blockchain protocol (e.g. network upgrades) can further limit user access or the ability to transfer the crypto-asset.

Outdated or vulnerable wallet software:

Users relying on outdated, unaudited, or unsupported wallet software may face compatibility issues, security vulnerabilities, or failures when interacting with the blockchain. Failure to update wallet software in line with protocol developments can result in transaction errors, loss of access, or exposure to known exploits.

4. Network security risks

Attack risks: Blockchains may be subject to denial-of-service (DoS) attacks, 51% attacks, or other exploits targeting the consensus mechanism. These can delay transactions, compromise finality, or disrupt the accurate recording of transfers.

Centralisation concerns: Despite claims of decentralisation, a relatively small number of validators or a high concentration of stake may increase the risk of collusion, censorship, or coordinated network downtime, which can affect the resilience and operational reliability of the crypto-asset.

5. Bridge and interoperability risk

Where the token is transferred between distributed ledgers using third-party bridging protocols, those protocols are operated independently of the issuer. A technical failure or exploit affecting such a protocol may result in the loss of tokens held or transferred through it, or in discrepancies between the token representations on the ledgers concerned.

6. Forking and protocol-upgrade risk

Network upgrades or disagreements among node operators or validators can result in blockchain “forks”, where the blockchain splits into two or more incompatible versions that continue separately from a shared past. This may lead to duplicate token representations or incompatibilities between exchanges and wallets. Until consensus stabilises, trading or transfers may be disrupted or misaligned. Such situations may be difficult for retail holders to navigate, particularly when trading platforms or wallets display inconsistent token information.

7. Economic-layer and abstraction risk

Mechanisms such as gas relayers, wrapped tokens, or synthetic representations may alter the transaction economics of the underlying token. Changes in transaction costs, token demand, or utility may reduce its usage and weaken both its economic function and perceived value within its ecosystem.

8. Spam and network-efficiency risk

The token is recorded on a public distributed ledger shared with other applications. Periods of high transaction volume on that ledger may slow confirmation times and increase transaction fees. This can affect the cost and speed of transferring the token and the performance of applications that rely on it.

9. Front-end and access-interface risk

If users rely on centralised web interfaces or hosted wallets to interact with the blockchain, service outages, malicious compromises, or domain expiries affecting these interfaces may block access to the crypto-asset, even while the blockchain itself remains fully functional. Dependence on single web portals introduces a critical point of failure outside the DLT layer.

The following measures are in place or have been adopted to mitigate the risks described in this white paper:

1. Security assessment: The AlloX application underwent an external security assessment conducted by CertiK covering its frontend and backend application repositories. Identified security-related findings were reviewed and, according to the assessment report, the high- and medium-severity findings were resolved, while certain low-severity findings were acknowledged.

2. Non-custodial architecture. The AlloX platform is non-custodial. Users retain control of their own assets and of the private keys controlling them at all times, and the platform does not hold, transfer or dispose of user assets on its own account. Interactions are executed directly from the user's own wallet. As a result, user assets are not exposed to the insolvency of, or to a custody failure at, the platform operator.

3. Key and access management. Access to production systems and to privileged keys is restricted to authorised personnel, subject to multi-factor authentication and role-based access controls, and is reviewed periodically.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The following applies to Ethereum:

Ethereum uses a Proof-of-Stake (PoS) consensus mechanism introduced with The Merge on 2022-09-15, which replaced the previous Proof-of-Work consensus model. The PoS mechanism is implemented through Gasper, combining Casper-FFG for finality with the LMD-GHOST fork-choice rule for chain selection. Validators participate in consensus by staking ETH through the Beacon Chain. Validators are pseudo-randomly selected to propose new blocks, while other validators attest to the validity of proposed blocks. The network operates using 12-second slots grouped into epochs of 32 slots. Under normal network conditions, finality is typically achieved after two epochs, approximately 12.8 minutes, through Casper-FFG. The LMD-GHOST fork-choice rule determines the canonical chain based on the accumulated weight of validator attestations. Validators that engage in certain malicious behaviour, such as equivocation or contradictory attestations, may be subject to slashing penalties, while offline validators may incur inactivity penalties. Subsequent network upgrades, including Dencun (2024-03-13), Pectra (2025-05-07) and Fusaka (2025-12-03), introduced protocol changes affecting Ethereum’s consensus mechanism and Layer 2 functionality.

The following applies to Base:

Base does not operate a decentralised validator set comparable to a Layer-1 blockchain. Transaction ordering is currently performed by a single sequencer, while transaction data and state commitments are posted to Ethereum and ultimately benefit from Ethereum’s Proof-of-Stake consensus. Following the Azul upgrade, Base uses a multi-proof system for Layer-2 checkpoints associated with withdrawals to Ethereum: TEE proofs support the normal path, while permissionless zero-knowledge proofs provide an independent verification and challenge path. The sequencer remains a central component of transaction ordering.

The following applies to BNB Smart Chain (BSC):

BSC uses a hybrid consensus mechanism called Proof-of-Staked-Authority (PoSA), which combines elements of Delegated-Proof-of-Stake (DPoS) and Proof-of-Authority (PoA). This method is intended to support fast block times and low fees while maintaining a level of decentralisation and security.

Core components

1. Validators (Cabinet and Candidates): Validators are responsible for producing blocks, validating transactions, and maintaining network security. The validator set consists of up to 45 validators, including 21 “Cabinet” validators and 24 “Candidate” validators, selected based on bonded stake. A subset of validators is selected per epoch to participate in block production.

2. Delegators: Token holders may delegate BNB to validators to support their selection. Delegators share in the rewards generated by validators, providing an economic incentive to participate in staking.

3. Candidates: Validator candidates are nodes that have staked BNB but are not part of the primary validator subset for a given epoch. They may be selected into the active set based on staking rank and can participate in block production with lower probability.

Consensus process

4. Validator selection: Validators are ranked based on the amount of bonded BNB and are updated periodically (approximately every 24 hours). The highest-ranked validators form the active validator set, with Cabinet validators having a higher probability of participating in block production.

5. Block production: Validators take turns producing blocks in a PoA-like manner. For each epoch, a subset of validators is selected to produce and validate blocks sequentially, ensuring high throughput and low latency.

6. Transaction finality: BSC achieves short block times (approximately 0.45 seconds) and fast finality. With Fast Finality enabled, blocks are typically finalised within approximately one second, subject to validator participation.

7. Staking: Validators must stake BNB as collateral and may be subject to slashing in cases of misbehaviour, including double-signing, malicious voting, or prolonged downtime.

8. Delegation and rewards: Validators and delegators are rewarded through transaction fees collected in each block. Validators may share rewards with delegators to attract stake.

9. Transaction fees: BSC does not rely on inflationary block rewards; instead, validators are compensated primarily through transaction fees paid in BNB, aligning incentives with network usage.

The crypto-asset in scope will be implemented on the DLT network Ethereum, Base and BNB Smart Chain as a token, following the standards described below.

The following applies to Ethereum:

Ethereum’s Proof-of-Stake (PoS) mechanism secures the network through validator incentives and protocol-defined penalties. Validators are required to stake ETH in order to participate in block proposal and attestation activities. A minimum of 32 ETH is required to activate a validator. Following the Pectra upgrade on 2025-05-07, EIP-7251 increased the maximum effective balance per validator from 32 ETH to 2,048 ETH. Validators may receive protocol-defined rewards for proposing blocks, attesting to valid blocks and participating in sync committees. Rewards consist of newly issued ETH and transaction-related fees. Transaction fees on Ethereum follow the mechanism introduced by EIP-1559, under which each transaction includes a base fee that is burned at the protocol level and an optional priority fee paid to the validator proposing the relevant block. Validators that engage in certain malicious behaviour, including equivocation or contradictory attestations, may be subject to slashing penalties. Validators that fail to participate correctly in consensus activities may also incur inactivity penalties. These mechanisms are intended to support validator participation and the economic security of the Ethereum network.

The following applies to Base:

Base uses ETH for transaction fees and does not issue a separate Base network token or operate a staking or validator-reward mechanism. Fees comprise a charge for Layer-2 execution and a component reflecting the cost of posting transaction data to Ethereum. The checkpoint-verification system also uses proposal bonds, which may reward a successful challenge to an invalid checkpoint proposal.

The following applies to BNB Smart Chain (BSC):

BSC uses the Proof-of-Staked-Authority (PoSA) consensus mechanism to support network security and incentivise participation from validators and delegators.

Incentive mechanisms

1. Validators: Validators must self-delegate BNB in order to participate in the validator system. Validator selection is staking-based, and validators that rank highly enough enter the active set and participate in block production and transaction validation. Validators are rewarded from transaction fees collected on the network. When a block is produced, most of the block fee is allocated to the validator that proposed the block. A portion is retained as validator commission, while the remainder is allocated for distribution through the validator credit structure.

2. Delegators: BNB holders may delegate BNB to validators. This increases the validator’s total stake and may improve its position in the validator ranking. Delegators share in the rewards earned by the validator they support, after deduction of the validator’s commission.

3. Candidates: BSC distinguishes between Cabinet, Candidate and Inactive validators. The current model provides that the top 21 validators form the Cabinet, while the validators ranked from 22 to 45 are Candidates. Candidate validators have a smaller chance of producing blocks, but they remain part of the broader validator structure and support network resilience. Validator roles are updated every 24 hours based on the latest staking information.

4. Economic Security: Validators may be penalised for misconduct or poor performance. Slashable events include double signing, malicious fast-finality voting and unavailability. Depending on the violation, consequences may include removal from the validator set, loss of staking rewards and slashing of part of the validator’s self-delegated BNB. The staking model therefore creates an economic incentive for validators and delegators to support reliable validator performance.

Fees on BSC

5. Transaction fees: Transaction fees on BSC are paid in BNB and are intended to compensate validators for maintaining the network. BSC is designed as a comparatively low-fee network, and smart-contract transactions and transfers require gas fees in BNB.

6. Validator rewards: BSC does not rely on a separate protocol-level block reward. Instead, staking rewards are derived from transaction fees. Most of the block fee is allocated to the proposing validator, then split between validator commission and delegator-linked reward distribution.

7. System-level fee allocation: Part of transaction-fee revenue is collected through the System Reward Contract and used for designated system purposes, including fast-finality rewards.

8. Smart contract fees: Deploying and interacting with smart contracts on BSC requires payment of gas fees in BNB. These fees depend on the computational resources required and form part of the network’s overall fee and validator-incentive model.

The energy consumption of this asset is aggregated across multiple components: For the energy consumption of the token, a fraction of the energy consumption of the network is attributed to the token, which is determined based on the expected activity of the crypto-asset within the network. When calculating the energy consumption, the Functionally Fungible Group Digital Token Identifier (FFG DTI) is used - if available - to determine all implementations of the asset in scope. The mappings are updated regularly, based on data of the Digital Token Identifier Foundation. The information regarding the hardware used and the number of participants in the network is based on assumptions that are verified with best effort using empirical data. In general, participants are assumed to be largely economically rational. As a precautionary principle, we make assumptions on the conservative side when in doubt, i.e. making higher estimates for the adverse impacts.

To determine the proportion of renewable energy usage, the locations of the nodes are determined using public information sites, open-source and in-house-developed crawlers. Where no information is available on the geographic distribution of nodes, comparable reference networks are used, taking into account similarities in incentivisation structure and consensus mechanism. This geographic information is then combined with publicly available data from Our World in Data. The resulting intensity is calculated as the marginal energy consumption with respect to one additional transaction.

Ember (2025); Energy Institute, Statistical Review of World Energy (2024), with major processing by Our World in Data. “Share of electricity generated by renewables - Ember and Energy Institute” [dataset]. Underlying sources: Ember, “Yearly Electricity Data Europe”; Ember, “Yearly Electricity Data”; Energy Institute, “Statistical Review of World Energy”. Retrieved from: https://ourworldindata.org/grapher/share-electricity-renewables

To determine GHG emissions, the locations of the nodes are determined using public information sites, open-source crawlers, and crawlers developed in-house. Where no information is available on the geographic distribution of nodes, comparable reference networks are used, taking into account similarities in incentivisation structure and consensus mechanism. This geographic information is then combined with publicly available data from Our World in Data. The resulting intensity is calculated as the marginal emission intensity with respect to one additional transaction.

Ember (2025); Energy Institute, Statistical Review of World Energy (2024), with major processing by Our World in Data. “Carbon intensity of electricity generation – Ember and Energy Institute” [dataset]. Underlying sources: Ember, “Yearly Electricity Data Europe”; Ember, “Yearly Electricity Data”; Energy Institute, “Statistical Review of World Energy”. Retrieved from: https://ourworldindata.org/grapher/carbon-intensity-electricity. Licensed under CC BY 4.0.