ORCLB, issued by BTech Holdings Limited, is a tokenized certificate over shares offering economic exposure to a U.S.-listed equity, made available through Binance's bStocks product. [S1]

Each ORCLB token tracks the live price of Oracle Corporation common stock (ORCL), listed on the New York Stock Exchange, and is backed 1:1 by a corresponding underlying share held with a regulated custodian. [S1] The issuer processes corporate actions such as stock splits and dividend-related adjustments automatically, so holders maintain continuous exposure without manual steps. [S1] Holders can convert between the underlying equity and ORCLB at a 1:1 ratio with zero conversion fees, other than during corporate actions or platform maintenance. [S1]

ORCLB is issued by BTech Holdings Limited, a Binance group affiliate, under an Approved Prospectus in the Abu Dhabi Global Market (ADGM), UAE, following approval from the Financial Services Regulatory Authority (FSRA). [S1] As a Certificate representing certain Financial Instruments under paragraph 92, Schedule 1 of the Financial Services and Markets Regulations, ORCLB is not a share of Oracle Corporation and does not carry ownership or voting rights in the company. [S1] Access is limited to eligible non-U.S. users on a secondary-market basis, with conversion to and from the underlying equity executed through broker-dealer Nest Trading Limited. [S1]

ORCLB is issued as a BEP-20 token on BNB Chain (BNB Smart Chain), compatible with BNB Chain wallets and onchain applications. [S1] Minting and redemption operate under the issuer's bStocks Minting and Redemption Product Terms, preserving the 1:1 conversion ratio with the underlying equity while supporting self-custody for holders. [S1]

<Sources
  retrievedAt="2026-07-28"
  items={[
    { id: "S1", url: "https://www.adgm.com/financial-services-regulatory-authority/listing-authority/official-list-of-securities" },
  ]}
/>


# Asset transfer volume methodology

## 1. Overview

Asset transfer volume is defined as the total value of assets transferred onchain. Since transaction fees are paid by users for each transfer, a correlation is typically observed between this metric and the customer demand that exists to use an asset for transacting purposes. Daily transfer volumes are aggregated across all supported blockchains, normalized by decimal precision, and converted into USD. To ensure an accurate representation of economic activity, transactions involving non-circulating treasury or premint addresses are subtracted where applicable.

## 2. Data sources

- **EVM chain events**: ERC-20 token transfers, covering EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, Optimism, Tron, Starknet, zkSync Era, and others)
- **Solana instructions**: SPL token transfers, mints, and burns
- **Aptos events**: Token withdraw events
- **Near events**: Token transfer events
- **Polkadot Asset Hub events**: `Transferred` events from the `assets` pallet
- **Cardano UTXO transactions**: Token deposits, withdrawals, and mint/burn events
- **Stellar operations**: Classic token withdrawals and Soroban SEP-41 token transfers
- **Sui transactions**: Token withdrawals and `TreasuryCap` supply changes
- **Algorand transactions**: Asset transfer transactions
- **Injective events**: Token transfer, mint, and burn events
- **Stacks transactions**: Token transfer events
- **Asset metadata**: Token contract addresses and decimal precision
- **External data**: End-of-day price feeds and fiat exchange rates

## 3. Step-by-step calculation

### Component A: Raw transfer volume extraction

- **Purpose**: Extract raw token transfer quantities from onchain events and transactions
- **Logic**: On EVM-compatible chains, token transfer quantities are extracted from ERC-20 `Transfer` events. On Solana, quantities are extracted from SPL token transfers, mints, and burns. On Aptos, Near, Algorand, Injective, and Stacks, transfer volumes are parsed from native token transfer and withdrawal events. On Polkadot Asset Hub, volumes are extracted from `Transferred` events emitted by the `assets` pallet. On Cardano, UTXO withdrawals and mint events are aggregated to capture all token movements. On Stellar, classic token withdrawals and Soroban SEP-41 transfer, mint, and burn events are parsed. On Sui, token withdrawals are combined with mint events derived from `TreasuryCap` supply changes.
- **Key fields**: `timestamp` (the day of the transfer) `token_address` (the contract or asset identifier) `amount` (the raw transfer quantity)

### Component B: Premint and preburn correction

- **Purpose**: Exclude non-circulating token movements to isolate genuine economic transfer volume
- **Logic**: For supported chains, raw transfer volumes are corrected by subtracting premints and preburns. Premints are defined as tokens minted directly into designated project treasury or premint addresses, while preburns are represented by tokens burned directly from these non-circulating addresses. On EVM-compatible chains, Solana, Injective, Stacks, and Stellar Soroban, these flows are identified by filtering transfers where the sender or recipient matches a known treasury address. On Algorand, transfers between asset configuration addresses and treasury addresses are subtracted. On Cardano, deposits to and withdrawals from treasury addresses during mint or burn transactions are netted out.
- **Key fields**: `amount` (the corrected transfer quantity) `token_address` (the contract or asset identifier) `timestamp` (the day of the transfer)

### Component C: Decimal normalization and zero-filling

- **Purpose**: Normalize token quantities to human-readable units and ensure continuous daily time series
- **Logic**: Raw token quantities are normalized by the decimal precision retrieved from the asset metadata. For days with no recorded transfer activity, the time series is filled with zero values to maintain a continuous daily record for each asset.
- **Key fields**: `amount` (the normalized transfer quantity) `decimals` (the decimal precision of the token)

### Component D: USD conversion and final aggregation

- **Purpose**: Convert normalized transfer volumes to USD and aggregate across all chains
- **Logic**: Normalized daily transfer volumes are multiplied by the end-of-day price feeds sourced from market data providers. For assets pegged to fiat currencies other than USD, daily exchange rates are applied using Chainlink FX price feeds to determine the USD-equivalent value. The final daily asset transfer volume is calculated by summing the USD-denominated transfer volumes across all active chains for each asset.
- **Key fields**: `price_usd` (the end-of-day market price of the asset in USD) `amount_usd` (the final transfer volume in USD)

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Asset transfer volume

Tokenized stocks

twitter

website

terms

Real-world asset (RWA) issuers

Binance bStocks

Oracle (bStocks Tokenized Stock) (ORCLb) is a token tracking ORCL shares, backed by dedicated collateral, issued by Binance bStocks through Btech Holdings Ltd, and distributed through Binance with Alpaca as broker.

The underlying security is listed in the information technology sector in North America.

Each token tracks one underlying share, entitles holders to dividends, which are distributed as additional tokens, carries no voting rights, and carries an annual fee of 0%.

The collateral assets are held by Alpaca Securities LLC in segregated accounts within a bankruptcy-remote structure and Crowe Mak LLP as auditor.

Retail investors and institutions AE can mint and redeem directly with Binance bStocks in USDC after completing KYC.

Residents of the United States and jurisdictions under applicable sanctions cannot mint or redeem with Binance bStocks.

Btech Holdings Ltd is incorporated in the United Arab Emirates, is regulated in Abu Dhabi's ADGM, and is supervised by the Financial Services Regulatory Authority.

Holder terms are governed by the law of the United Arab Emirates.

ORCLb has been issued on BNB Chain as an ERC-20 token since July 2026.

Oracle (bStocks Tokenized Stock)ORCLb