xBETH Asset Review
Summary
LlamaRisk supports onboarding xBETH to the Aave V3 X Layer instance. xBETH is a centrally administered, yield-bearing wrapper of OKX’s internal BETH, with rewards accruing via a monotonic exchangeRate (non-rebasing) updated on a 24-hour cadence. Minting and burning are permissioned and mediated by OKX backend accounting and MPC-controlled roles, so redemption is operationally routed through OKX rather than permissionless on-chain unwrapping.
As of 17 Feb 2026, xBETH supply is ~3,165 xBETH (about $6.33m), fully issued on X Layer, and highly concentrated, with a single OKX deposit address holding ~94.9%. On-chain secondary liquidity is single-venue and shallow: Uniswap is the only meaningful DEX source, with the xETH/xBETH pool at roughly $659k TVL and LP ownership dominated by one provider; a 25 xBETH → USDT0 swap shows -7.7% price impact.
The underlying BETH is listed on OKX via BETH/ETH and BETH/USDT. BETH/USDT has higher 24h turnover but limited ±2% depth, while BETH/ETH has materially deeper visible depth. For pricing the asset on Aave, xBETH can be valued as exchangeRate × Chainlink ETH/USD. Residual risks are primarily operational: validator performance depends on OKX’s stack (Prysm), slashing coverage is an off-chain OKX commitment, and redemption timelines are OKX-controlled and may extend from ~13 days to several weeks.
Full Asset Evaluation
1. Asset Fundamental Characteristics
1.1 Asset
xBETH is an on-chain ERC-20 representation of OKX’s internal BETH (staked ETH within OKX validator infrastructure) designed to carry staking yield without rebasing: user balances remain constant while an exchange rate increases over time.
1.2 Architecture
BETH is the sole underlying asset for xBETH, which is managed internally by OKX. The proportional share of xBETH is determined by the exchange rate.
Key components that enable xBETH include:
- BETH: an internal CEX LST that represents delegated ETH to OKX validators.
- Mint & Burn Controller: MPC that controls xBETH minting and burning operations.
- ExchangeRateUpdater: contract validates and constrains exchange rate updates
- Admin: MPC that manages updates and controls transfer restrictions/blacklisting.
- TimelockController: Manages sensitive admin functions
- Authorized Receiver: Dedicated address that receives newly minted xBETH.
- ProxyAdmin: Can modify contract parameters or implement xBETH upgrade.
Mint & Burn Process
xBETH is minted when a user deposits their BETH to the X Layer. Underlying BETH is minted when users stake ETH via OKX validators, receiving the same amount of BETH at the current exchange rate.
Source: OKX, February 17, 2026
xBETH is burned when a user deposits xBETH back to OKX for redemption: the xBETH is transferred to OKX’s designated receiver on X Layer and burned by the Burner role, and the user is credited with the corresponding amount of BETH on OKX’s internal ledger.
Source: OKX, February 17, 2026
Validators
Validator operations for xBETH are run by OKX-managed validators under a three-pool segregation model (Global, EEA, US): users in the US and EEA participate only in their respective regional pools, while the Global pool serves users from the Bahamas, Seychelles, Singapore, Australia, Turkey, Brazil, and the UAE. The OKX Ethereum validator stack currently uses the Prysm client.
OKX is currently developing a user interface to allow users to track their validator sets and staking/unstaking events. It is expected to be made available in February.
Rewards
Underlying BETH rewards come from standard Ethereum validator income: consensus rewards for proposing/attesting, plus execution-layer income from transaction tips and MEV when a validator proposes a block. OKX reports an estimated BETH yield of ~2.6% APY, and xBETH reflects this yield via exchange-rate updates once per day.
Slashing
Token holders remain indirectly exposed to slashing risk. If OKX validators are penalized or slashed, the underlying staked ETH backing BETH can decrease.
The OKX operator has not been slashed to date. The current validator set is rated moderate based on RAVER scoring, indicating generally solid performance with some variability. RAVER reports approximately 643k ETH of active stake across ~20k active validators. This differs from OKX’s self-reported figure of ~446k ETH on its dashboard; the variance is most likely driven by differences in scope and attribution methodology. Further clarification has been requested from the X Layer team.
Source: Rated.network, February 17, 2026
OKX claims it will absorb any slashing-related losses instead of passing them on to xBETH holders; this is an off-chain assurance, and its effectiveness ultimately depends on OKX’s operational execution and creditworthiness.
Consensus Client
OKX runs Prysm for its consensus stack, which aligns its validator performance and operational risk profile with the Prysm client line. The practical implication is that any client-specific defect or incident affecting Prysm would have both network-level relevance (given its share) and direct exposure for OKX; conversely, the fragmented long tail of other clients supports broader diversity but does not remove the concentration pocket around the top implementations.
Source: clientdiversity.org, February 17, 2026
Unstaking
Unstaking is handled through OKX’s redemption process and may involve a waiting period. OKX documentation indicates that BETH→ETH redemption can take approximately 13 days to several weeks, depending on processing conditions, and the minimum redemption amount is 0.001 BETH.
Fees
Based on the OKX team response, there are no additional fees other than the validator fee and the service fee, both of which are deducted before calculating the conversion rate. For xBETH, the OKX validator charges a 0% commission, and the exchange charges a 5% service fee.
Withdrawals
The X Layer team indicated that xBETH deposits and withdrawals are now live, following the planned activation.
Reserves
Source: OKX, February 17, 2026
xBETH backing is sourced from OKX’s broader ETH staking reserve. Based on the provided staking-address inventory, the reserve is distributed across 11,022 validator deposit addresses totaling 446,277.296 ETH staked, while xBETH supply on X Layer is only ~3,165 xBETH as of 17 Feb 2026, implying the X Layer representation is a small slice of the overall staked base.
The X Layer team also indicated that a Chainlink Proof of Reserves integration is planned after Aave goes live. The following withdrawal addresses are intended to serve as the PoR reference set:
ETH Staking (Global)
• 0xa27cef8af2b6575903b676e5644657fae96f491f
• 0xe839a3e9efb32c6a56ab7128e51056585275506c
• 0xd5f8c864f21824daf3a4b22d9c33693642ed7634
ETH Staking (EEA)
• 0x560cfcb78aecac04104dc5097f7530832cc3e7e2
• 0x05e851e9196fa1fc55f92ddd07ee83a978db35d0
• 0x9b4495fcc3c99b3cb73a3722320ff1858c81c2f0
ETH Staking (US)
• 0x366a88f8de3b8036aeb24e4f6512aeff2c5cc76a
• 0x4ccda666c69cd35be70aabd8931d824b2cfa3d2d
• 0x4cbc9e809b3b9182efd319793fd2f9e29ce35975
1.3 Tokenomics
As of 17 Feb 2026, total xBETH supply is approximately 3,165 xBETH (about $6.33m), with the full amount issued on X Layer. This reflects an early-stage footprint on the network, with circulating supply still small relative to the broader OKX staking base.
1.3.1 Token Holder Concentration
Source: xBETH token holders, February 17, 2026
xBETH holdings are currently extremely concentrated, with one single address holding ~95% of the supply:
- OKX (Deposit): 3,003.1064 xBETH (94.89%)
- Uniswap V3: 161.2279 xBETH (5.09%)
- EOA: 0.3292 xBETH (0.01%)
2. Market Risk
2.1 Liquidity
Source: Uniswap, February 17, 2026
A swap transaction of 25 xBETH into USDT0 returns about 46.0k USDT0, with the interface flagging a high price impact of -7.73%. Additional liquidity has been committed to support onboarding, with $1M for the xBETH / xETH pool.
2.1.1 Liquidity Venue Concentration
As shown in section 1.3.1, Uniswap represents the sole venue for xBETH liquidity. As of February 17th, the xETH/xBETH pool TVL is $659K.
2.1.2 DEX LP Concentration
Source: Debank, February 17, 2026
Given the asset’s recent deployment, liquidity is primarily supplied by the X Layer team, resulting in a single LP source for both pools.
2.2 Volatility
None at this stage, given the token’s recent deployment.
2.3 Exchanges
Source: CoinGecko, February 17, 2026
The underlying BETH is currently listed on multiple exchanges. Among reputable CEXs, BETH is listed on OKX, and the spot market is primarily concentrated in two pairs: BETH/ETH and BETH/USDT.
At the time of observation, BETH/USDT is the higher-turnover venue, with $879k in 24h volume and a shallow top-of-book depth of roughly $32k within +2% and $59k within -2%.
BETH/ETH shows $648k in 24h volume and materially deeper visible liquidity: approximately $9.59m within +2% and $27.29m within -2%.
2.4 Growth
None at this stage, given the token’s recent deployment. As shown in section 2.3, the OKX exchange represents a large base for potential growth for xBETH on X Layer.
3. Technological Risk
3.1 Smart Contract Risk
xBETH is covered within the broader xAsset audit scope: OKX’s security team audited the xAsset codebase internally, Zellic and MixBytes audited it externally, so xBETH is covered to the extent it uses that audited xAsset implementation.
- OKX internal audit (10 Dec 2025): 2 findings, including a low issue where the exchange-rate update rate limit could be bypassed, allowing two updates in the same block after inactivity.
- Zellic external audit (23 Dec 2025): 4 findings, no critical/high; one medium issue was a denylisted address still being able to use
transferFromvia existing allowances (fixed). Two low issues:setReceivercould set a denylisted receiver (minting can be blocked), andexchangeRate()could return 0 before the first oracle update (fixed). - MixBytes’ external audit (22 Jan 2026): reported no critical/high/medium issues and identified 8 low-severity findings (7 acknowledged, 1 fixed). Key low items include: (i)
configureCaller()may reset a caller’s allowance without replenishment; (ii) role/ownership hardening gaps (unrestrictedrenounceRole/renounceOwnership).
3.2 Bug Bounty Program
xBETH smart contracts are covered under a live OKG bug bounty program hosted on HackerOne with a max bounty of $1M.
3.3 Price Feed Risk
The xBETH price is calculated as 1 xBETH = exchangeRate * 1 ETH. A Chainlink ETH/USD price feed used with the internal exchange rate, along with a CAPO adapter, could be used to price xBETH.
3.4 Dependency Risk
Staking is executed by OKX-managed validators, so reward realization and principal safety depend on OKX’s validator performance and its ability to manage tail events such as slashing. In addition, the exchange-rate mechanism introduces an operational dependency: while the rate is designed to update on a regular cadence, there is a manual component to exchange-rate updates, creating governance/operations risk around timing, accuracy, and incident handling.
Redemption introduces liquidity and processing dependency. Converting exposure back to ETH is mediated by OKX’s redemption workflow, so redemption timeliness depends on OKX’s liquidity buffers and its ability to process withdrawals under Ethereum’s protocol-level exit/withdrawal throughput constraints.
4. Counterparty Risk
4.1 Governance and Regulatory Risk
To the extent other X Layer assets are governed by the same dedicated wrapped-token user agreement that applies across all wrapped 1:1 assets, they should be treated as operating within the same core legal architecture as xETH. On that premise, the legal analysis prepared for xETH is directionally applicable to such X Layer assets, particularly the findings regarding (i) the assets’ legal construct, (ii) the eligibility and access model, and (iii) the authorisation and regulatory perimeter status of the operating entity.
4.2 Access Control Risk
4.2.1 Contract Modification Options
A Role-Based Access Control system is utilized. The roles and their associated capabilities are outlined below:
MINTER_ROLE: Can mint and burn tokens, assigned to MPC 1.
DENY_LISTER_ROLE: Can pause/unpause transfers and manage the deny list, assigned to MPC 2.
DEFAULT_ADMIN_ROLE: Has admin privileges over Timelock, ProxyAdmin, and xBETH, assigned to MPC 2.
ExchangeRateUpdater Owner: manages callers, determines the parameters (rate changes and intervals of change), and can transfer ownership. Assigned to MPC 2:
ExchangeRateUpdater Caller: can make allowance-based updates, limited by contract parameters assigned to MPC 1
TimelockController Roles manage sensitive admin functions through a timelock delay mechanism. assigned to MPC 2:
- PROPOSER_ROLE: initiates transactions to the queue.
- EXECUTOR_ROLE: executes transactions after a delay.
- CANCELLER_ROLE: can cancel pending operations.
Sensitive functions exposed by each role include
MINTER_ROLE:
- mint and burn xBETH
transferMinterrelinquishes the role to a new account
DENY_LISTER_ROLE:
- pause and unpause all token transfers
setReceiverdetermines where the newly minted tokens are sentaddToDenyListandremoveFromDenyListcontrol a permissioned Deny list that blocks addresses from sending/receiving tokenstransferDenyListerrelinquishes the role to a new account
DEFAULT_ADMIN_ROLE:
- All Deny List Role functions
grantRoleassigns roles to addressesrevokeRoleremoves roles assigned to addresses
PROPOSER_ROLE:
scheduleschedules a single transaction (target address, value, and data).scheduleBatchschedules multiple transactions to be executed in sequence.
EXECUTOR_ROLE:
executetriggers the actual call to the target contract once the delay has ended.executeBatchtriggers a group of function calls.
CANCELLER_ROLE:
canceldeletes a pending operation before it is executed.
ExchangeRateUpdater Caller:
updateExchangeRatechanges the value of the exchange rate and, in turn, the token’s value. Changes are limited by the allowance rate limit.
ExchangeRateUpdater Owner
transferOwnershipallows the owner to add a new caller or increase the rate limit allowance
These roles highlight the highly centralized controls that roles have over key contracts, i.e, minting, transferring, pausing, and determining where newly minted xBETH are sent.
4.2.2 Timelock Duration and Function
TimelockController enforces a 3-day delay for upgrades and role changes.
4.2.3 Multisig Threshold / Signer identity
MPCs are controlled internally by OKX; no external parties are involved in the management of control systems. Admin actions require internal review and senior management approval.
Note: This assessment follows the LLR-Aave Framework, a comprehensive methodology for asset onboarding and parameterization in Aave V3. This framework is continuously updated and available here.
Price feed Recommendation
The xBETH price is calculated as 1 xBETH = exchangeRate * 1 ETH. A Chainlink ETH/USD price feed together with the internal exchange rate, alongside a CAPO adapter would be used to price xBETH.
Disclaimer
This review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.
The information provided should not be construed as legal, financial, tax, or professional advice.