Beam

BEAM

BEAM

BEAM is the native cryptographic token that powers the Beam ecosystem. As an ERC-20 token, BEAM serves as the fundamental infrastructure layer that enables transactions on the Beam Network. The Beam ecosystem creates an environment where developers, creators, and users collaborate to build innovative digital experiences across multiple sectors such as gaming, artificial intelligence, NFTs, RWAs.

EVERY CLAIM IS SOURCE-LINKED · “—” MEANS NOT VERIFIED, NOT ZERO · METHODOLOGY · REVISIONS

[OVERVIEW]

Mission

Build a technology ecosystem around the Beam EVM network, developer tooling and applications. The SDK remains gaming-focused, while the current ecosystem site extends its remit to AI, compute, DeFi and consumer applications. This is the onbeam.com BEAM ecosystem, not the unrelated Mimblewimble privacy cryptocurrency.Sourcesdocs.onbeam.com · Sdkonbeam.com · Ecosystemdocs.onbeam.com · Token

Team

Beam Interface is the Cayman Islands company identified in the site's April 10, 2025 terms. The network, protocol governance and ecosystem contributors should not be conflated with this interface operator. The node documentation also identifies Beam Foundation as proposing validator incentives; founder identities and a complete organizational funding history were not verified here.Sourcesonbeam.com · Termsdocs.onbeam.com · Requirements

[TECHNOLOGY]

CONSENSUS_MECHANISM
Proof of Stake
BLOCKCHAIN_TYPE
EVM-compatible Avalanche Layer 1
SMART_CONTRACT_SUPPORT
✓ YES

Scalability & architecture

[TOKENOMICS]

EMISSION_SCHEDULE

Official distribution documentation explicitly says the schedule has changed because of burns and longer lockups, and that additional information remains forthcoming. A current allocation table, complete vesting schedule and annualized issuance rate are therefore not supplied. Burns reduce supply, but do not alone establish circulating float or future selling pressure.Sourcesdocs.onbeam.com · Distributiondocs.onbeam.com · Burning

TOKEN_UTILITY

BEAM pays gas on Beam, supports governance and ecosystem payments, and is staked with Node Tokens for validation or delegation. The Ethereum ERC-20 contract is 0x62D0A8458eD7719FDAF978fe5929C6D342B0bFcE; the official repository distinguishes native BEAM, wrapped WBEAM and LayerZero bridge representations. BEAM is not a dollar-pegged or reserve-backed claim.Sourcesdocs.onbeam.com · Tokendocs.onbeam.com · NodesGitHub · BuildOnBeam/beam-subnet

[CHART]

TradingView • BINANCE:BEAMUSDT

[MARKET_DATA]

PRICE_USD
$0.00344549
Market Cap
$173.40M
Fully Diluted Valuation
$198.11M
24h Volume
$9.54M
24h Change
+4.65%
All-Time High
$0.04416304(Mar 10, 2024)
All-Time Low
$0.00121358(Jun 25, 2026)

Last updated: Nov 22, 2026, 12:00 AM UTC

[ECONOMICS]

Trading pairs

PairExchangeSource
USDC/WBEAMBeam SwapSource ↗
USDT/WBEAMBeam SwapSource ↗
Official deployment registry lists the pair at 0xe510c67dd0A54D06f04fd5af9094fe64Ed605EaB. Deployment evidence does not establish current reserves, TVL or executable liquidity.SourceGitHub · BuildOnBeam/beam-subnet
Official deployment registry lists the pair at 0x7063F3446223Bc4f5c37B0F9d1e12547F0358e90. No live order size, depth or slippage measurement is asserted.SourceGitHub · BuildOnBeam/beam-subnet

On-Chain Metrics

[ECOSYSTEM]

Integrations

LayerZeroCross-chain messaging and bridging

Official bridge documentation identifies LayerZero as the infrastructure for moving tokens to and from Beam.Sourcedocs.onbeam.com · Bridge

Unity, Unreal and Web SDKsDeveloper tooling

The SDK provides platform clients, APIs, account abstraction, sessions and policies for game integrations.Sourcedocs.onbeam.com · Sdk

dApps

SphereNFT marketplace

Marketplace for NFT trading and developer-integrated asset markets using Seaport.Sourcedocs.onbeam.com · Sphere

Beam SwapDecentralized exchange

Uniswap V2-style AMM with liquidity pools; liquidity providers bear impermanent-loss and contract risks.Sourcedocs.onbeam.com · Amm

Beam BridgeBridge

Interface for LayerZero-powered transfers to and from Beam.Sourcedocs.onbeam.com · Bridge

[UNIQUE_VALUE_PROPOSITION]

Core value proposition

Combines an EVM chain with game-engine SDKs, wallet onboarding, session-based authorization and asset-market tooling so developers can integrate blockchain features without implementing each component separately.Sourcedocs.onbeam.com · Sdk

Key differentiators

1

Self-custodial Player Service and custodial Automation Service address different end-user and backend workflows.Sourcedocs.onbeam.com · Sdk

2

Validation combines fungible BEAM stake with ERC-721 Node Tokens, rather than relying on BEAM balance alone.Sourcedocs.onbeam.com · Nodes

3

A native NFT marketplace, AMM and bridge complement chain-level functionality.Sourcesdocs.onbeam.com · Spheredocs.onbeam.com · Ammdocs.onbeam.com · Bridge

Competitive edge

The defensible proposition is integrated developer tooling and distribution across ecosystem applications. No independently verified superiority in active users, fees or transaction throughput is claimed.Sourcesdocs.onbeam.com · Sdkonbeam.com · Ecosystem

Target audience

Game studios, application developers, players and asset traders, with a broader ecosystem mandate covering AI, compute, DeFi and consumer products.Sourcesdocs.onbeam.com · Sdkonbeam.com · Ecosystem

[COMPARATIVE]

Competitive positioning

Compared with using a generic EVM chain alone, Beam offers a purpose-built application stack covering wallets, game clients, sessions and marketplaces. Compared with a standalone game token, BEAM also pays network gas and supports validation and governance. These are architectural distinctions, not proof of superior adoption.Sourcesdocs.onbeam.com · Sdkdocs.onbeam.com · Token

Strengths

Weaknesses

[ROADMAP]

Roadmap

Horizon · HorizonCOMPLETED

  • Current node documentation describes the permissionless PoS transition as completed, with validator/delegator participation and Node Token requirements. An exact activation date was not verified here.Sourcedocs.onbeam.com · Nodes

Validator incentive intentions · Validator incentive intentionsPLANNED

  • The requirements page describes an intended approximately $750,000 AVAX subsidy and intended participation in an Avalanche proposal to reduce validator costs. Disbursement and implementation status were not verified.Sourcedocs.onbeam.com · Requirements

Risk factors

Outlook

The constructive case is that useful SDK integrations and applications create sustained demand for gas, payments and validation. The adverse case is that broad ecosystem ambitions do not translate into recurring on-chain use while token liquidity, unlock transparency and bridge risks remain material. This is conditional analysis, not a valuation forecast; no dated future delivery calendar was established.Sourcesdocs.onbeam.com · Sdkonbeam.com · Ecosystemdocs.onbeam.com · Distribution

[GOVERNANCE]

Governance model

BEAM governance covers mutable protocol features and checks on DAO-adjacent entities whose governing documents recognize approved votes. Other votes can be non-binding sentiment signals; not every ecosystem activity requires a vote.Sourcedocs.onbeam.com · Governance

Voting mechanism

The published constitution gives eligible balances equal voting weight unless the applicable contracts specify otherwise, using holdings before creation of a vote. It requires at least two days of voting, a quorum equal to 1% of circulating supply measured at the preceding quarter-end reference block, and a simple majority exceeding 50%, subject to applicable smart-contract rules. DAO-adjacent entities must prohibit their own participation in BIP votes through their governing documents.SourceBeam Governance Constitution (Stamped).pdf

Proposal process

Proposals are discussed on the governance forum for at least two days; material revisions restart that period. A proposal should specify the requested outcome, justification and budget. Token gating may be introduced through approved governance rather than inferred as a fixed threshold. Materially similar rejected proposals generally cannot return within six months.SourceBeam Governance Constitution (Stamped).pdf

[SECURITY]

Security practices

  • Validators stake at least one ERC-721 Node Token and 20,000 BEAM and pay the continuous Avalanche P-Chain fee. These requirements are economic participation constraints, not a direct measurement of validator independence or stake concentration.Sourcedocs.onbeam.com · Requirements
  • The SDK distinguishes self-custodial Player Service from custodial Automation Service. Their key-control and operational risks differ; the entire Beam application stack should not be described as uniformly self-custodial.Sourcedocs.onbeam.com · Sdk
  • Bridging uses LayerZero and adds cross-chain contract and messaging dependencies. The guide explicitly warns users to verify addresses, destinations and fees.Sourcedocs.onbeam.com · Bridge
  • Sphere uses Seaport and its documentation refers to upstream audits. That statement is not a verified Beam-specific audit report or certification of all Sphere integrations.Sourcedocs.onbeam.com · Sphere

[REGULATORY]

Regulatory classification

The constitution calls BEAM a utility token. This is a governance-document description, not a jurisdiction-wide regulator determination or investment-product license.SourceBeam Governance Constitution (Stamped).pdf

Compliance status

The interface terms prohibit sanctioned persons and users in comprehensively sanctioned jurisdictions. They state that Beam Interface is not an exchange, broker or virtual/crypto-asset service provider. These are the operator's statements, not independently verified regulatory approvals.Sourceonbeam.com · Terms

[COMMUNITY]

[GITHUB_REPOSITORIES]

beam-subnetPRIMARY

Official L1 connection settings, token/pool deployment addresses and node configuration instructions.SourceGitHub · BuildOnBeam/beam-subnet

beam-docs

Documentation source repository linked from Beam's developer site.Sourcedocs.onbeam.com · Chain

governance

Public repository hosting the Beam Governance Constitution.Sourcedocs.onbeam.com · Constitution

[SOCIAL_MEDIA]

[COMMUNITY_PLATFORMS]

[TECHNICAL_DETAILS]

Network Information

Chain ID
4337

RPC Endpoints

Beam Mainnet
https://build.onbeam.com/rpc
Public
Beam Testnet
https://build.onbeam.com/rpc/testnet
Public

Node requirements

Minimum Hardware
Eight AWS-vCPU-equivalent cores, 16 GiB RAM, Ubuntu 22.04+ or macOS 13+.Sourcedocs.onbeam.com · Requirements
Network Requirements
Sustained 5 Mbps upload/download and inbound TCP port 9651.Sourcedocs.onbeam.com · Requirements
Storage Requirements
1 TiB storage is the published minimum; the page's approximately 50 GB chain-state estimate is not a live disk measurement.Sourcedocs.onbeam.com · Requirements

Technical specifications

Chain Design
Beam is an EVM-compatible Avalanche L1. The official connection repository identifies mainnet chain ID 4337 and testnet 13337 and publishes the RPC and explorer links listed here; endpoint availability was not load-tested.SourceGitHub · BuildOnBeam/beam-subnet
Consensus Detail
Current node documentation describes Horizon as a completed transition to permissionless PoS. Minimum validator requirements are one Node Token plus 20,000 BEAM, with maxima of 1,000 Node Tokens and 200 million BEAM per node.Sourcesdocs.onbeam.com · Nodesdocs.onbeam.com · Requirements
Token Representations
Ethereum BEAM is 0x62D0A8458eD7719FDAF978fe5929C6D342B0bFcE. Beam-native WBEAM is 0xD51BFa777609213A653a2CD067c9A0132a2D316A and LayerZero BEAM is 0xF5759Ef6D0E0003cFdF80aD3c9a628fc8736c821. These identifiers distinguish assets, not interchangeable deposit instructions for every venue.SourceGitHub · BuildOnBeam/beam-subnet