Transférez vos cryptos chez Coinhouse et recevez jusqu’à 10 000 €*
logo

Rapport de durabilité

La nouvelle règle du jeu pour une finance responsable.

image

Depuis 2024, la réglementation européenne exige que chaque entreprise financière publie des indicateurs de durabilité qui offrent une vision transparente de l'impact environnemental de ses activités.

En quelques mots, ces indicateurs prouvent qu'une entreprise agit concrètement pour la planète.

Explorez ci-dessous les indicateurs de durabilité des crypto-actifs sélectionnés par notre plateforme.

image
Rechercher un rapport
magnifying glass
usdc
USDCUSDC (USDC)
Informations générales
Nom de l'entité déclarante :Coinhouse SAS
Identifiant juridique de l'entité (LEI) :969500E5GFHK2RKF8251
Nom du crypto-actif :USDC
Mécanisme de consensus :

USDC is present on the following networks: Algorand, Aptos Coin, Arbitrum, Arc, Avalanche, Base, Celo, Cronos, Ethereum, Flow, Hedera Hbar, Hyperliquid, Injective, Linea, Monad, Near Protocol, Okt Chain, Optimism, Pharos, Plasma, Plume, Polygon, Ripple, Sei, Solana, Sonic, Starknet, Statemint, Stellar, Sui, Tron, Worldchain, Xdc Network, Zksync.
Algorand uses Pure Proof-of-Stake (PPoS). In each round, verifiable random functions select a block proposer and voting committees in proportion to participating online stake. Committee votes certify the proposed block and determine the next ledger state.
Aptos uses a stake-weighted Byzantine fault-tolerant consensus protocol. A validator leader proposes an ordered block of transactions, validators vote on the proposal and execution result, and a supermajority of voting power is required before the block is committed.
Arbitrum One is an optimistic Layer-2 rollup that settles on Ethereum. A sequencer orders transactions. ArbOS and the state transition function execute them and determine the resulting Layer-2 state. A batch poster publishes compressed transaction data to Ethereum. Validators submit state assertions to Ethereum and may challenge conflicting assertions under the BoLD dispute protocol. An assertion is confirmed after the applicable challenge period if no successful challenge remains.
Arc uses Malachite, an implementation of Tendermint Byzantine fault-tolerant consensus, with a permissioned Proof-of-Authority validator set. Validators exchange pre-votes and pre-commits in consensus rounds, and a block is committed when more than two-thirds of validator voting power agrees.
The Avalanche C-Chain uses Snowman consensus with stake-weighted validators. Validators repeatedly sample subsets of other validators and update their preference until a block reaches the protocol confidence threshold. Accepted blocks form the C-Chain’s linear history.
Base is an OP Stack optimistic rollup. A sequencer orders and executes Layer-2 transactions, while transaction data and state commitments are submitted to Ethereum for settlement. Invalid state claims can be challenged through the OP Stack fault-proof process.
Celo is an Ethereum Layer-2 rollup built on the OP Stack. A sequencer orders and executes transactions to form Layer-2 blocks, EigenDA provides data availability, and transaction outputs are submitted to Ethereum for settlement.
Cronos EVM uses a permissioned Proof-of-Authority validator set with CometBFT-style Byzantine fault-tolerant block agreement. Authorized validators propose and sign blocks. CRO stake delegation on Cronos POS does not determine the Cronos EVM validator set.
Ethereum uses proof of stake through Gasper, which combines the LMD-GHOST fork-choice rule with Casper FFG finality. Validators stake ETH, propose blocks in assigned slots and attest to block validity. Weighted attestations determine the canonical chain and justify and finalize checkpoints. Defined consensus faults can result in slashing.
Flow uses proof of stake with HotStuff-based Byzantine-fault-tolerant consensus and separate node roles. Consensus nodes propose and vote on blocks, while collection, execution and verification nodes perform transaction intake, computation and result checking. Quorum certificates and epoch procedures coordinate finalization and validator-set changes.
Hedera uses a stake-weighted hashgraph consensus algorithm with asynchronous Byzantine fault tolerance. Nodes exchange transactions and event histories through gossip about gossip. Each node derives virtual votes from the shared event history to determine consensus order and timestamps. The resulting consensus is final once the protocol threshold is reached.
Hyperliquid is a Layer-1 blockchain using HyperBFT, a stake-weighted Byzantine fault-tolerant consensus protocol inspired by HotStuff. Validators propose and vote on blocks, and the resulting consensus order is shared by HyperCore and HyperEVM. HyperCore and HyperEVM are execution environments of the same chain rather than separate consensus networks.
Injective uses CometBFT proof-of-stake consensus. Validators propose and vote on blocks, while voting power is determined by self-delegated and delegated INJ. A block is committed when the required validator voting power approves it.
Linea is a zero-knowledge rollup that settles state on Ethereum. Its Maru consensus client uses QBFT to order and finalize Layer-2 blocks, while Linea execution clients execute the transactions. Batches are proven with zero-knowledge proofs and reach Ethereum settlement after the proof and associated data are accepted by the Layer-1 contracts.
Monad uses MonadBFT with Proof of Stake. A stake-weighted leader proposes a block in each round, validators evaluate the proposal, and votes representing more than two thirds of stake form quorum certificates that advance the block toward finality. Delegation is supported.
NEAR uses Proof of Stake with sharded block production. Validators are assigned block-production and chunk-validation duties according to staked and delegated NEAR. Validators attest to shard data, and the protocol combines validated chunks into the canonical chain under its block-finality rules.
OKTChain was an EVM-compatible Layer 1 network built with the Cosmos SDK and Tendermint. It used delegated Proof of Stake, under which OKT holders delegated tokens to validators that proposed and voted on blocks. OKX discontinued maintenance and support, and the network’s announced operating period ended on 1 January 2026.
OP Mainnet is an optimistic Layer 2 rollup settled on Ethereum. Its sequencer orders transactions and produces Layer 2 blocks, then transaction batches are published to Ethereum. A transaction reaches finality when the Ethereum block containing its batch is finalized, while fault proofs are used to challenge invalid withdrawal claims.
Pharos is an EVM-compatible Layer 1 network using an asynchronous Byzantine fault-tolerant consensus protocol. Validators propose, validate, and commit transactions through the network’s adaptive consensus process. Special Processing Networks may use separate validator sets for their assigned execution functions.
Plasma Chain uses PlasmaBFT, a consensus protocol based on Fast HotStuff with pipelined execution. Validators are selected through a simplified Proof-of-Stake mechanism and participate in block production and finalization. Misbehavior does not lead to full slashing of stake but results in reduced rewards.
Plume is an Arbitrum Orbit rollup using the Nitro stack. A sequencer orders and executes transactions, while rollup nodes derive the state and validators can challenge invalid state assertions through the Arbitrum dispute process. The network uses Celestia-based data availability and settles its rollup contracts on Ethereum.
Polygon PoS is an EVM-compatible sidechain with its own Proof-of-Stake validator set. Under the Rio architecture, validators elect a block producer for a span, Bor executes transactions and produces blocks, and Heimdall coordinates validator attestations and checkpoint submission to Ethereum.
The XRP Ledger uses the XRP Ledger Consensus Protocol. Each server selects a Unique Node List of validators whose proposals it evaluates. Validators iteratively agree on transaction ordering and results, and a ledger version is validated when the required threshold of trusted validators supports it.
Sei uses a stake-weighted validator set with Autobahn Byzantine fault-tolerant consensus. Validators maintain individual proposal lanes, exchange certified transaction batches, and vote on ordered block cuts. Quorum certificates record the validator agreement used to finalize ordering before application execution completes.
Solana uses stake-weighted Proof of Stake with Tower BFT. A scheduled leader orders transactions and produces block entries using Proof of History as a cryptographic clock, while validators replay the entries and submit stake-weighted votes. Confirmed votes and lockout rules determine finality.
Sonic utilizes a Proof-of-Stake (PoS) consensus mechanism integrated with a Directed Acyclic Graph (DAG) architecture to enhance scalability and efficiency. Validators are required to stake the network’s native $S tokens, with a minimum of 500,000 $S tokens needed to operate a validator node. This substantial staking requirement ensures that validators have a significant investment in the network’s integrity.
Starknet is a validity rollup. Sequencers order and execute Layer 2 transactions, and provers generate STARK proofs for batches of state transitions. Ethereum contracts verify the proofs and record the resulting Starknet state commitments, while transaction data required for state reconstruction is published to Ethereum.
Statemint was renamed Polkadot Asset Hub. It is a Polkadot system parachain whose collators assemble candidate blocks and submit them to Polkadot relay-chain validators. Relay-chain validators verify parachain state transitions, and Polkadot consensus provides finality for accepted Asset Hub blocks.
Stellar uses the Stellar Consensus Protocol, a federated Byzantine agreement system. Each validator defines quorum slices representing the sets of validators whose agreement it accepts. Transactions are included when overlapping quorums nominate and confirm the same ledger value through the protocol’s ballot process.
Sui uses Delegated Proof of Stake with the Mysticeti Byzantine fault-tolerant consensus protocol. Validator voting power is determined by delegated SUI stake. Validators exchange and certify transaction data through a directed acyclic graph, while Mysticeti orders consensus transactions and commits them after the required stake-weighted support is reached.
TRON uses Delegated Proof of Stake. TRX stakers allocate TRON Power to elect 27 Super Representatives, which produce blocks in a scheduled rotation. A block becomes solidified after at least 19 distinct active Super Representatives have produced a block at that height or above. The active set is recalculated from votes at scheduled maintenance updates.
World Chain does not operate a consensus mechanism or validator set of its own. Transactions are ordered and blocks are produced by a single sequencer, which is not open to third parties. Settlement and finality come from the proof-of-stake consensus of Ethereum, to which the transaction data and state commitments are posted. As an optimistic rollup, World Chain treats state commitments as valid unless they are challenged during a challenge period. At present, only designated parties may submit state commitments and challenge them. If the sequencer does not include a transaction, users can submit it through Ethereum, subject to a delay. Accordingly, the security of World Chain depends on Ethereum for settlement and finality, while transaction ordering depends on the sequencer.
XDC Network uses XDPoS 2.0, a delegated Proof-of-Stake mechanism. Staked masternodes take turns proposing blocks, and validator quorum signatures confirm them under the protocol’s Byzantine fault-tolerant finality rules. Full nodes independently verify transactions, blocks and the resulting ledger state.
ZKsync Era is an Ethereum Layer 2 zero-knowledge rollup. A sequencer orders and executes transactions and groups them into batches. The prover generates validity proofs for the batches, and a verifier contract on Ethereum checks the proofs and finalizes the corresponding state transitions.

Mécanismes d’incitation et frais applicables :

USDC is present on the following networks: Algorand, Aptos Coin, Arbitrum, Arc, Avalanche, Base, Celo, Cronos, Ethereum, Flow, Hedera Hbar, Hyperliquid, Injective, Linea, Monad, Near Protocol, Okt Chain, Optimism, Pharos, Plasma, Plume, Polygon, Ripple, Sei, Solana, Sonic, Starknet, Statemint, Stellar, Sui, Tron, Worldchain, Xdc Network, Zksync.
Eligible online consensus accounts that propose blocks can receive ALGO-denominated payouts comprising a protocol-defined share of transaction fees and, where available, a bonus from the FeeSink. Transactions incur fees in ALGO under protocol parameters, and accounts that do not meet participation requirements may be suspended from reward eligibility.
Validators and their stakers receive APT-denominated staking rewards based on stake and validator performance, with operator commissions applied where configured. Transactions pay execution, I/O and storage fees in APT. Execution fees are burned, and storage fees may be refunded when the associated state storage is deleted.
Arbitrum One transactions incur fees in ETH. The total fee consists of a Layer-2 execution component and a parent-chain data component reflecting the cost of publishing compressed transaction data to Ethereum. The amount depends on the computational resources used, the size and compressibility of the transaction data, the Layer-2 gas price and the applicable Ethereum data-posting costs. Validators that submit or challenge state assertions under BoLD must provide protocol-defined bonds. Bonds are returned or forfeited according to the applicable protocol rules and the outcome of a dispute. Withdrawals through the canonical bridge become executable after the relevant Layer-2 state has been confirmed and the applicable challenge period has elapsed.
Transactions on the currently available Arc Testnet incur gas fees denominated in USDC. The fee model comprises a protocol base fee and an optional priority fee, and collected fees are paid to validators under the current Testnet configuration.
Primary Network validators and delegators can receive AVAX staking rewards after satisfying protocol participation requirements. The protocol does not ordinarily slash bonded principal. Failure to meet validation requirements can result in loss of reward eligibility. C-Chain transactions incur AVAX gas fees, which are burned rather than paid to validators.
Base has no native protocol token. Transaction fees are paid in ETH and comprise a Layer-2 execution fee and a Layer-1 fee reflecting the cost of publishing transaction data to Ethereum. Both components vary with the applicable network conditions.
Transactions incur gas fees based on gas used and network fee parameters, payable in CELO or supported ERC-20 fee currencies. Separately, eligible community RPC providers and holders who lock CELO and vote for elected provider groups can receive protocol-defined epoch rewards.
Cronos EVM transactions and smart-contract operations incur gas fees paid in CRO. Block production is performed by authorized validators rather than through an open delegation mechanism. CRO holders seeking protocol staking rewards use the separate Cronos POS chain.
Validators receive newly issued ETH for block proposals, attestations and other consensus duties and may receive priority fees and execution-layer value associated with proposed blocks. Each transaction pays gas in ETH. The EIP-1559 base fee is burned and an optional priority fee is paid to the block proposer. Missed duties reduce rewards, while defined misconduct can cause slashing.
Node operators and delegators receive FLOW staking rewards funded by newly issued tokens and transaction fees, subject to role requirements, commission and slashing rules. Transactions pay FLOW-denominated fees based on execution effort and storage or account-related resource use under current protocol parameters.
Users pay HBAR transaction charges comprising applicable node, network and service fees. Fee schedules are expressed in USD-equivalent terms and converted to HBAR at the current exchange rate used by the network. Eligible node operators and accounts staked to participating nodes can receive HBAR rewards under council-defined parameters. Native staking does not require HBAR to be locked.
Validators and delegators can receive HYPE staking rewards under the protocol’s staking rules. HyperCore trading activity incurs maker and taker fees according to the applicable fee schedule, with additional rules for selected products and builder fees. HyperEVM transactions separately incur HYPE-denominated gas fees. These charges are distinct from trading funding payments and liquidation outcomes.
Validators and delegators receive staking rewards from protocol issuance and network fees after validator commission. Network transactions require gas fees that are generally paid in INJ. Separately, a share of fees generated by exchange applications enters an auction, and the INJ paid by the winning bidder is burned.
Users pay Linea gas fees exclusively in ETH. After Layer-1 and other protocol costs are deducted, the dual-burn mechanism allocates twenty percent of net fee revenue to burning ETH and uses the remaining eighty percent to burn LINEA. LINEA is used for ecosystem incentives rather than gas payments or validator staking.
MON may be staked or delegated to validators as part of Proof-of-Stake participation. Users pay transaction fees in MON. The fee uses an EIP-1559-compatible base fee and priority fee, and Monad charges the transaction’s stated gas limit rather than the gas actually consumed.
Validators and delegators receive protocol staking rewards in NEAR. Users pay gas fees in NEAR for transactions and contract execution. A protocol-defined portion of eligible contract-execution fees may be assigned to the contract account, while the remaining fee is burned. Accounts and contracts must also maintain NEAR balances for occupied storage.
While OKTChain operated, validators and delegators received rewards under its delegated Proof-of-Stake rules, and users paid transaction and smart-contract execution fees in OKT. OKX ended OKT trading and converted eligible exchange-held OKT to OKB as part of the chain’s decommissioning. These historical incentives and fees no longer describe an active supported network.
Users pay OP Mainnet transaction fees in ETH. The total fee includes the Layer 2 execution fee, the cost of publishing transaction data to Ethereum, and an operator fee after the relevant network upgrade. Fee components are routed to protocol fee vaults, and OP Mainnet does not provide public validator or delegation rewards for Layer 2 consensus.
PROS is used for transaction fees and staking on Pharos. Validators may receive protocol rewards for participating in base-layer consensus, while native restaking can assign stake and rewards to Special Processing Networks. Slashing or reduced rewards may apply under the rules of the relevant validator role.
Validators stake XPL and receive protocol rewards for signing and finalizing blocks. Their reward share may be reduced for missed or incorrect participation. Users generally pay gas in XPL, while qualifying USDT transfers may be sponsored by the protocol and presented to the user without a transaction fee.
Transactions incur gas fees in PLUME. The total fee reflects execution on Plume and costs associated with data availability and settlement to Ethereum. PLUME can be delegated through Plume’s staking program, with validator and delegator rewards determined by the applicable staking rules. The token is also used for governance and separately administered ecosystem incentives.
Validators stake POL and receive protocol rewards and transaction-fee allocations. Delegators may receive a share of a validator’s rewards after commission. Users pay POL gas for transfers and smart-contract execution, and the Rio fee rules allocate block-related fees between the elected producer and the validator set.
The XRP Ledger does not pay protocol rewards to validators and does not use mining or staking. Each transaction specifies an XRP fee that is permanently destroyed rather than paid to a validator. The minimum fee can change through validator voting and rises temporarily under load. Separate XRP reserve requirements apply to accounts and ledger objects but are not transaction fees.
Validators and delegators receive SEI staking rewards after validator commission and may be subject to slashing under the network rules. Users pay transaction and smart-contract execution fees in SEI based on gas used and the applicable fee parameters. Governance participation is separate from transaction-validation compensation.
Validators and delegators receive inflation-funded staking rewards after validator commission. Each transaction pays a base fee in SOL and may include a prioritization fee. Half of the base fee is burned and half is paid to the validator, while the prioritization fee is paid to the validator. Accounts may also require a refundable rent-exempt reserve.
Sonic’s economic model is designed to incentivize active participation from both validators and developers. Validators earn rewards through a combination of block rewards and transaction fees. The block reward system employs a dynamic Annual Percentage Rate (APR) mechanism.
Users pay fees for Layer 2 computation, data, and settlement-related costs in supported fee tokens, including ETH and STRK. Sequencers collect transaction fees according to the protocol rules. Eligible validators and delegators may receive STRK staking rewards subject to participation requirements and commission arrangements.
Polkadot validators receive DOT staking rewards under Polkadot relay-chain rules. Polkadot Asset Hub collators do not receive inflation-funded era rewards and may receive a portion of transaction fees. Users pay fees in DOT or an eligible supported asset, and some asset-management operations require deposits or reserves.
Stellar does not issue protocol block rewards and validators do not receive transaction fees. Each transaction pays a fee in XLM based on its operations and the submitted fee bid, with surge pricing applying when demand exceeds ledger capacity. Accounts and ledger entries may also require minimum XLM reserves.
Validators and delegators receive SUI staking rewards from protocol subsidies and the network fee model, subject to validator commission and performance. Users pay SUI gas covering computation and storage. Storage charges are paid into the storage fund, and a storage rebate may be returned when the corresponding on-chain data is deleted.
Successful blocks create a production reward for the producing Super Representative and a voter-reward pool shared among the highest-ranked representatives according to votes. Each representative sets a brokerage rate that determines the retained share and the share claimable by voters. Transactions consume Bandwidth, while smart-contract execution also consumes Energy. These resources can be obtained by staking or delegation. If available resources are insufficient, TRX is burned at parameterized rates. TRON has no priority fee and no protocol slashing.
Transaction fees on World Chain are paid in ETH. World Chain does not issue a separate network token and does not operate a staking or validator-reward mechanism. Each transaction fee has two components: an execution fee, made up of a base fee that adjusts with demand for block space and an optional priority fee, and a data fee covering the cost of publishing the transaction data to Ethereum. Unlike on Ethereum, the base fee is not burned. All fees are collected in fee contracts on World Chain and are available to the network operator. Fee parameters are set at protocol level, published by the project and subject to change.
Masternodes receive XDC rewards based on participation in block production and signing. XDC holders may stake or delegate under the network’s rules, and eligible participants receive the associated reward allocation. Transactions pay EVM-style gas in XDC, calculated from the gas used and the applicable gas price.
Users pay transaction fees, normally in ETH, covering Layer 2 execution, proof and batch overhead and the cost of publishing state-change data to Ethereum. The network operator charges these fees and pays the related Layer 1 costs. Native account abstraction also permits paymasters to sponsor gas or accept supported ERC-20 tokens from users. ZKsync Era does not publish a protocol validator reward schedule.

Début de la période de déclaration :2025-11-14
Fin de la période de déclaration :2026-11-14
Environnement (E)
Consommation d’énergie totale :520608.85322 (kWh/an)
Sources et méthodologies de calcul de la consommation d’énergie :

The energy consumption of this asset is aggregated across multiple components:
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. 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 energy consumption of a token, the energy consumption of the network(s) algorand, aptos_coin, arbitrum, arc, avalanche, base, celo, cronos, ethereum, flow, hedera_hbar, hyperliquid, injective, linea, monad, near_protocol, okt_chain, optimism, pharos, plasma, plume, polygon, ripple, sei, solana, sonic, starknet, statemint, stellar, sui, tron, worldchain, xdc_network, zksync is calculated first. 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 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.

Part de consommation d’énergie renouvelable :37.653452428 %
Intensité énergétique :0.00000 (kWh/transaction)
Émissions GES Scope 1 (contrôlées par la DLT) :0.00000 (tCO₂e)
Émissions GES Scope 2 (achetées par la DLT) :175.56645 (tCO₂e)
Intensité des émissions de GES :0.00000
Gouvernance (G)
Sources et méthodologies principales pour l’énergie :

To determine the proportion of renewable energy usage, the locations of the nodes are to be determined using public information sites, open-source crawlers and crawlers developed in-house. If no information is available on the geographic distribution of the nodes, reference networks are used which are comparable in terms of their incentivization structure and consensus mechanism. This geo-information is merged with public information from Our World in Data, see citation. The intensity is calculated as the marginal energy cost wrt. one more 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]. Ember, “Yearly Electricity Data Europe”; Ember, “Yearly Electricity Data”; Energy Institute, “Statistical Review of World Energy” [original data]. Retrieved from https://ourworldindata.org/grapher/share-electricity-renewables.

Sources et méthodologies principales pour les émissions de GES :

To determine the GHG Emissions, the locations of the nodes are to be determined using public information sites, open-source crawlers and crawlers developed in-house. If no information is available on the geographic distribution of the nodes, reference networks are used which are comparable in terms of their incentivization structure and consensus mechanism. This geo-information is merged with public information from Our World in Data, see citation. The intensity is calculated as the marginal emission wrt. one more 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]. Ember, “Yearly Electricity Data Europe”; Ember, “Yearly Electricity Data”; Energy Institute, “Statistical Review of World Energy” [original data]. Retrieved from https://ourworldindata.org/grapher/carbon-intensity-electricity Licenced under CC BY 4.0.

Date dernière mise à jour du rapport ESG : 15/11/2026 3:00:27 am