Skip to main content

3 posts tagged with "enterprise technology"

Enterprise technology solutions

View all tags

Rain: Transforming Stablecoin Infrastructure with a $1.95 Billion Valuation

· 9 min read
Dora Noda
Software Engineer

A 17x valuation increase in 10 months. Three funding rounds in under a year. $3 billion in annualized transactions. When Rain announced its $250 million Series C at a $1.95 billion valuation on January 9, 2026, it didn't just become another crypto unicorn—it validated a thesis that the biggest opportunity in stablecoins isn't speculation but infrastructure.

While the crypto world obsesses over token prices and airdrop mechanics, Rain quietly built the pipes through which stablecoins actually flow into the real economy. The result is a company that processes more volume than most DeFi protocols combined, with partners including Western Union, Nuvei, and over 200 enterprises globally.

DePIN's Enterprise Pivot: From Token Speculation to $166M ARR Reality

· 13 min read
Dora Noda
Software Engineer

When the World Economic Forum projects a sector will grow from $19 billion to $3.5 trillion by 2028, you should pay attention. When that same sector generates $166 million in annual recurring revenue from real enterprise customers—not token emissions—it's time to stop dismissing it as crypto hype.

Decentralized Physical Infrastructure Networks (DePIN) have quietly undergone a fundamental transformation. While speculators chase memecoins, a handful of DePIN projects are building billion-dollar businesses by delivering what centralized cloud providers cannot: 60-80% cost savings with production-grade reliability. The shift from tokenomics theater to enterprise infrastructure is rewriting blockchain's value proposition—and traditional cloud giants are taking notice.

The $3.5 Trillion Opportunity Hidden in Plain Sight

The numbers tell a story that most crypto investors have missed. The DePIN ecosystem expanded from $5.2 billion in market cap (September 2024) to $19.2 billion by September 2025—a 269% surge that barely made headlines in an industry obsessed with layer-1 narratives. Nearly 250 tracked projects now span six verticals: compute, storage, wireless, energy, sensors, and bandwidth.

But market cap is a distraction. The real story is revenue density. DePIN projects now generate an estimated $72 million in annual on-chain revenue across the sector, trading at 10-25x revenue multiples—a dramatic compression from the 1,000x+ valuations of the 2021 cycle. This isn't just valuation discipline; it's evidence of fundamental business model maturation.

The World Economic Forum's $3.5 trillion projection for 2028 isn't based on token price dreams. It reflects the convergence of three massive infrastructure shifts:

  1. AI compute demand explosion: Machine learning workloads are projected to consume 24% of U.S. electricity by 2030, creating insatiable demand for distributed GPU networks.
  2. 5G/6G buildout economics: Telecom operators need to deploy edge infrastructure at 10x the density of 4G networks, but at lower capital expenditure per site.
  3. Cloud cost rebellion: Enterprises are finally questioning why AWS, Azure, and Google Cloud impose 30-70% markups on commodity compute and storage.

DePIN isn't replacing centralized infrastructure tomorrow. But when Aethir delivers 1.5 billion compute hours to 150+ enterprise clients, and Helium signs partnerships with T-Mobile, AT&T, and Telefónica, the "experimental technology" narrative collapses.

From Airdrops to Annual Recurring Revenue

The DePIN sector's transformation is best understood through the lens of actual businesses generating eight-figure revenue, not token inflation schemes masquerading as economic activity.

Aethir: The GPU Powerhouse

Aethir isn't just the largest DePIN revenue generator—it's rewriting the economics of cloud computing. $166 million ARR by Q3 2025, derived from 150+ paying enterprise customers across AI training, inference, gaming, and Web3 infrastructure. This isn't theoretical throughput; it's billing from customers like AI model training operations, gaming studios, and AI agent platforms that require guaranteed compute availability.

The scale is staggering: 440,000+ GPU containers deployed across 94 countries, delivering over 1.5 billion compute hours. For context, that's more revenue than Filecoin (135x larger by market cap), Render (455x), and Bittensor (14x) combined—measured by revenue-to-market-cap efficiency.

Aethir's enterprise strategy reveals why DePIN can win against centralized clouds: 70% cost reduction versus AWS while maintaining SLA guarantees that would make traditional infrastructure providers jealous. By aggregating idle GPUs from data centers, gaming cafes, and enterprise hardware, Aethir creates a supply-side marketplace that undercuts hyperscalers on price while matching them on performance.

Q1 2026 targets are even more ambitious: doubling the global compute footprint to capture accelerating AI infrastructure demand. Partnerships with Filecoin Foundation (for perpetual storage integration) and major cloud gaming platforms position Aethir as the first DePIN project to achieve true enterprise stickiness—recurring contracts, not one-time protocol interactions.

Grass: The Data Scraping Network

While Aethir monetizes compute, Grass proves DePIN's flexibility across infrastructure categories. $33 million ARR from a fundamentally different value proposition: decentralized web scraping and data collection for AI training pipelines.

Grass turned consumer bandwidth into a tradeable commodity. Users install a lightweight client that routes AI training data requests through their residential IP addresses, solving the "anti-bot detection" problem that plagues centralized scraping services. AI companies pay premium rates to access clean, geographically diverse training data without triggering rate limits or CAPTCHA walls.

The economics work because Grass captures margin that would otherwise flow to proxy service providers (Bright Data, Smartproxy) while offering better coverage. For users, it's passive income from unutilized bandwidth. For AI labs, it's reliable access to web-scale data at 50-60% cost savings.

Bittensor: Decentralized Intelligence Markets

Bittensor's approach differs fundamentally from infrastructure-as-a-service models. Instead of selling compute or bandwidth, it monetizes AI model outputs through a marketplace of specialized "subnets"—each focused on specific machine learning tasks like image generation, text completion, or predictive analytics.

By September 2025, over 128 active subnets collectively generate approximately $20 million in annual revenue, with the leading inference-as-a-service subnet projected to hit $10.4 million individually. Developers access Bittensor-powered models through OpenAI-compatible APIs, abstracting away the decentralized infrastructure while delivering cost-competitive inference.

Institutional validation arrived with Grayscale's Bittensor Trust (GTAO) in December 2025, followed by public companies like xTAO and TAO Synergies accumulating over 70,000 TAO tokens (~$26 million). Custody providers including BitGo, Copper, and Crypto.com integrated Bittensor through Yuma's validator, signaling that DePIN is no longer too "exotic" for traditional finance infrastructure.

Render Network: From 3D Rendering to Enterprise AI

Render's trajectory shows how DePIN projects evolve beyond initial use cases. Originally focused on distributed 3D rendering for artists and studios, Render pivoted toward AI compute as demand shifted.

July 2025 metrics: 1.49 million frames rendered, $207,900 in USDC fees burned—with 35% of all-time frames rendered in 2025 alone, demonstrating accelerating adoption. Q4 2025 brought enterprise GPU onboarding through RNP-021, integrating NVIDIA H200 and AMD MI300X chips to serve AI inference and training workloads alongside rendering tasks.

Render's economic model burns fee revenue (207,900 USDC in a single month), creating deflationary tokenomics that contrast sharply with inflationary DePIN projects. As enterprise GPU onboarding scales, Render positions itself as the premium-tier option: higher performance, audited hardware, curated supply—targeting enterprises that need guaranteed compute SLAs, not hobbyist node operators.

Helium: Telecom's Decentralized Disruption

Helium's wireless networks prove DePIN can infiltrate trillion-dollar incumbent industries. Partnerships with T-Mobile, AT&T, and Telefónica aren't pilot programs—they're production deployments where Helium's decentralized hotspots augment macro cell coverage in hard-to-reach areas.

The economics are compelling for telecom operators: Helium's community-deployed hotspots cost a fraction of traditional cell tower buildouts, solving the "last-mile coverage" problem without capital-intensive infrastructure investments. For hotspot operators, it's recurring revenue from real data usage, not token speculation.

Messari's Q3 2025 State of Helium report highlights sustained network growth and data transfer volume, with the blockchain-in-telecom sector projected to grow from $1.07 billion (2024) to $7.25 billion by 2030. Helium is capturing meaningful market share in a segment that traditionally resisted disruption.

The 60-80% Cost Advantage: Economics That Force Adoption

DePIN's value proposition isn't ideological decentralization—it's brutal cost efficiency. When Fluence Network claims 60-80% savings versus centralized clouds, they're comparing apples to apples: equivalent compute capacity, SLA guarantees, and availability zones.

The cost advantage stems from structural differences:

  1. Elimination of platform margin: AWS, Azure, and Google Cloud impose 30-70% markups on underlying infrastructure costs. DePIN protocols replace these markups with algorithmic matching and transparent fee structures.

  2. Utilization of stranded capacity: Centralized clouds must provision for peak demand, leaving capacity idle during off-hours. DePIN aggregates globally distributed resources that operate at higher average utilization rates.

  3. Geographic arbitrage: DePIN networks tap into regions with lower energy costs and underutilized hardware, routing workloads dynamically to optimize price-performance ratios.

  4. Open market competition: Fluence's protocol, for example, fosters competition among independent compute providers, driving prices down without requiring multi-year reserved instance commitments.

Traditional cloud providers offer comparable discounts—AWS Reserved Instances save up to 72%, Azure Reserved VM Instances hit 72%, Azure Hybrid Benefit reaches 85%—but these require 1-3 year commitments with upfront payment. DePIN delivers similar savings on-demand, with spot pricing that adjusts in real-time.

For enterprises managing variable workloads (AI model experimentation, rendering farms, scientific computing), the flexibility is game-changing. Launch 10,000 GPUs for a weekend, pay spot rates 70% below AWS, and shut down infrastructure Monday morning—no capacity planning, no wasted reserved capacity.

Institutional Capital Follows Real Revenue

The shift from retail speculation to institutional allocation is quantifiable. DePIN startups raised approximately $1 billion in 2025, with $744 million invested across 165+ projects between January 2024 and July 2025 (plus 89+ undisclosed deals). This isn't dumb money chasing airdrops—it's calculated deployment from infrastructure-focused VCs.

Two funds signal institutional seriousness:

  • Borderless Capital's $100M DePIN Fund III (September 2024): Backed by peaq, Solana Foundation, Jump Crypto, and IoTeX, targeting projects with demonstrated product-market fit and revenue traction.

  • Entrée Capital's $300M Fund (December 2025): Explicitly focused on AI agents and DePIN infrastructure at pre-seed through Series A, betting on the convergence of autonomous systems and decentralized infrastructure.

Importantly, these aren't crypto-native funds hedging into infrastructure—they're traditional infrastructure investors recognizing that DePIN offers superior risk-adjusted returns compared to centralized cloud competitors. When you can fund a project trading at 15x revenue (Aethir) versus hyperscalers at 10x revenue but with monopolistic moats, the DePIN asymmetry becomes obvious.

Newer DePIN projects are also learning from 2021's tokenomics mistakes. Protocols launched in the past 12 months achieved average fully diluted valuations of $760 million—nearly double the valuations of projects launched two years ago—because they've avoided the emission death spirals that plagued early networks. Tighter token supply, revenue-based unlocks, and burn mechanisms create sustainable economics that attract long-term capital.

From Speculation to Infrastructure: What Changes Now

January 2026 marked a turning point: DePIN sector revenue hit $150 million in a single month, driven by enterprise demand for computing power, mapping data, and wireless bandwidth. This wasn't a token price pump—it was billed usage from customers solving real problems.

The implications cascade across the crypto ecosystem:

For developers: DePIN infrastructure finally offers production-grade alternatives to AWS. Aethir's 440,000 GPUs can train LLMs, Filecoin can store petabytes of data with cryptographic verification, Helium can deliver IoT connectivity without AT&T contracts. The blockchain stack is complete.

For enterprises: Cost optimization is no longer a choice between performance and price. DePIN delivers both, with transparent pricing, no vendor lock-in, and geographic flexibility that centralized clouds can't match. CFOs will notice.

For investors: Revenue multiples are compressing toward tech sector norms (10-25x), creating entry points that were impossible during 2021's speculative mania. Aethir at 15x revenue is cheaper than most SaaS companies, with faster growth rates.

For tokenomics: Projects that generate real revenue can burn tokens (Render), distribute protocol fees (Bittensor), or fund ecosystem growth (Helium) without relying on inflationary emissions. Sustainable economic loops replace Ponzi reflexivity.

The World Economic Forum's $3.5 trillion projection suddenly seems conservative. If DePIN captures just 10% of cloud infrastructure spending by 2028 (~$60 billion annually at current cloud growth rates), and projects trade at 15x revenue, you're looking at $900 billion in sector market cap—46x from today's $19.2 billion base.

What BlockEden.xyz Builders Should Know

The DePIN revolution isn't happening in isolation—it's creating infrastructure dependencies that Web3 developers will increasingly rely on. When you're building on Sui, Aptos, or Ethereum, your dApp's off-chain compute requirements (AI inference, data indexing, IPFS storage) will increasingly route through DePIN providers instead of AWS.

Why it matters: Cost efficiency. If your dApp serves AI-generated content (NFT creation, game assets, trading signals), running inference through Bittensor or Aethir could cut your AWS bill by 70%. For projects operating on tight margins, that's the difference between sustainability and burn rate death.

BlockEden.xyz provides enterprise-grade API infrastructure for Sui, Aptos, Ethereum, and 15+ blockchain networks. As DePIN protocols mature into production-ready infrastructure, our multichain approach ensures developers can integrate decentralized compute, storage, and bandwidth alongside reliable RPC access. Explore our API marketplace to build on foundations designed to last.

The Enterprise Pivot Is Already Complete

DePIN isn't coming—it's here. When Aethir generates $166 million ARR from 150 enterprise customers, when Helium partners with T-Mobile and AT&T, when Bittensor serves AI inference through OpenAI-compatible APIs, the "experimental technology" label no longer applies.

The sector has crossed the chasm from crypto-native adoption to enterprise validation. Institutional capital is no longer funding potential—it's funding proven revenue models with cost structures that centralized competitors can't match.

For blockchain infrastructure, the implications are profound. DePIN proves that decentralization isn't just an ideological preference—it's a competitive advantage. When you can deliver 70% cost savings with SLA guarantees, you don't need to convince enterprises about the philosophy of Web3. You just need to show them the invoice.

The $3.5 trillion opportunity isn't a prediction. It's math. And the projects building real businesses—not token casinos—are positioning themselves to capture it.


Sources:

Chain Abstraction Is How Enterprises Will Finally Use Web3 (Without Thinking About Chains)

· 8 min read
Dora Noda
Software Engineer

TL;DR

Cross-chain abstraction turns a maze of chains, bridges, and wallets into a single, coherent platform experience for both developers and end users. The ecosystem has quietly matured: intent standards, account abstraction, native stablecoin mobility, and network-level initiatives like the OP Superchain and Polygon's AggLayer make a "many chains, one experience" future realistic in 2025. For enterprises, the win is pragmatic: simpler integrations, enforceable risk controls, deterministic operations, and compliance-ready auditability—without betting the farm on any single chain.


The Problem Enterprises Actually Have (and Why Bridges Alone Didn’t Fix It)

Most enterprise teams don’t want to “pick a chain.” They want outcomes: settle a payment, issue an asset, clear a trade, or update a record—reliably, auditably, and at a predictable cost. The trouble is that production Web3 today is irredeemably multichain. Hundreds of rollups, appchains, and L2s have launched over the past 18 months alone, each with its own fees, finality times, tooling, and trust assumptions.

Traditional cross-chain approaches solved transport—moving tokens or messages from A to B—but not the experience. Teams are still forced to manage wallets per network, provision gas per chain, pick a bridge per route, and shoulder security differences they can’t easily quantify. That friction is the real adoption tax.

Cross-chain abstraction removes that tax by hiding chain selection and transport behind declarative APIs, intent-driven user experiences, and unified identity and gas. In other words, users and applications express what they want; the platform determines how and where it happens, safely. Chain abstraction makes blockchain technology invisible to end users while preserving its core benefits.

Why 2025 is Different: The Building Blocks Finally Clicked

The vision of a seamless multi-chain world isn't new, but the foundational technology is finally ready for production. Several key components have matured and converged, making robust chain abstraction possible.

  • Network-Level Unification: Projects are now building frameworks to make separate chains feel like a single, unified network. The OP Superchain aims to standardize OP-Stack L2s with shared tooling and communication layers. Polygon's AggLayer aggregates many ZK-secured chains with "pessimistic proofs" for chain-level accounting, preventing one chain’s issues from contaminating others. Meanwhile, IBC v2 is expanding standardized interoperability beyond the Cosmos ecosystem, pushing toward "IBC everywhere."

  • Mature Interop Rails: The middleware for cross-chain communication is now battle-tested and widely available. Chainlink CCIP offers enterprise-grade token and data transfer across a growing number of chains. LayerZero v2 provides omnichain messaging and standardized OFT tokens with a unified supply. Axelar delivers General Message Passing (GMP) for complex contract calls across ecosystems, connecting EVM and Cosmos chains. Platforms like Hyperlane enable permissionless deployments, allowing new chains to join the network without gatekeepers, while Wormhole offers a generalized messaging layer used across more than 40 chains.

  • Intent & Account Abstraction: The user experience has been transformed by two critical standards. ERC-7683 standardizes cross-chain intents, allowing apps to declare goals and let a shared solver network execute them efficiently across chains. Concurrently, EIP-4337 smart accounts, combined with Paymasters, enable gas abstraction. This allows an application to sponsor transaction fees or let users pay in stablecoins, which is essential for any flow that might touch multiple networks.

  • Native Stablecoin Mobility: Circle’s Cross-Chain Transfer Protocol (CCTP) moves native USDC across chains via a secure burn-and-mint process, reducing wrapped-asset risk and unifying liquidity. The latest version, CCTP v2, further cuts latency and simplifies developer workflows, making stablecoin settlement a seamless part of the abstracted experience.

What “Cross-Chain Abstraction” Looks Like in an Enterprise Stack

Think of it as a layered capability you can add to existing systems. The goal is to have a single endpoint to express an intent and a single policy plane to govern how it executes across any number of chains.

  1. Unified Identity & Policy: At the top layer are smart accounts (EIP-4337) with role-based access controls, social recovery, and modern custody options like passkeys or MPC. This is governed by a central policy engine that defines who can do what, where, using allow- and deny-lists for specific chains, assets, and bridges.

  2. Gas & Fee Abstraction: Paymasters remove the "I need native gas on chain X" headache. Users or services can pay fees in stablecoins, or the application can sponsor them entirely, subject to predefined policies and budgets.

  3. Intent-Driven Execution: Users express outcomes, not transactions. For example, "swap USDC for wETH and deliver it to our supplier's wallet on chain Y before 5 p.m." The ERC-7683 standard defines the format for these orders, allowing shared solver networks to compete to execute them safely and cheaply.

  4. Programmable Settlement & Messaging: Under the hood, the system uses a consistent API to select the right rail for each route. It might use CCIP for a token transfer where enterprise support is key, Axelar GMP for a cross-ecosystem contract call, or IBC where native light-client security fits the risk model.

  5. Observability & Compliance by Default: The entire workflow is traceable, from the initial intent to the final settlement. This produces clear audit trails and allows data to be exported to existing SIEMs. Risk frameworks can be programmed to enforce allowlists or trigger emergency brakes, for instance, by pausing routes if a bridge’s security posture degrades.

A Reference Architecture

From the top down, a chain-abstracted system is composed of clear layers:

  • Experience Layer: Application surfaces that collect user intents and completely hide chain details, paired with SSO-style smart account wallet flows.
  • Control Plane: A policy engine for managing permissions, quotas, and budgets. This plane integrates with KMS/HSM systems and maintains allowlists for chains, assets, and bridges. It also ingests risk feeds to circuit-break vulnerable routes automatically.
  • Execution Layer: An intent router that selects the best interop rail (CCIP, LayerZero, Axelar, etc.) based on policy, price, and latency requirements. A Paymaster handles fees, drawing from a treasury of pooled gas and stablecoin budgets.
  • Settlement & State: Canonical on-chain contracts for core functions like custody and issuance. A unified indexer tracks cross-chain events and proofs, exporting data to a warehouse or SIEM for analysis and compliance.

Build vs. Buy: How to Evaluate Providers of Chain Abstraction

When selecting a partner to provide chain abstraction capabilities, enterprises should ask several key questions:

  • Security & Trust Model: What are the underlying verification assumptions? Does the system rely on oracles, guardian sets, light clients, or validator networks? What can be slashed or vetoed?
  • Coverage & Neutrality: Which chains and assets are supported today? How quickly can new ones be added? Is the process permissionless or gated by the provider?
  • Standards Alignment: Does the platform support key standards like ERC-7683, EIP-4337, OFT, IBC, and CCIP?
  • Operations: What are the provider’s SLAs? How transparent are they about incidents? Do they offer replayable proofs, deterministic retries, and structured audit logs?
  • Governance & Portability: Can you switch interop rails per route without rewriting your application? Vendor-neutral abstractions are critical for long-term flexibility.
  • Compliance: What controls are available for data retention and residency? What is their SOC2/ISO posture? Can you bring your own KMS/HSM?

A Pragmatic 90-Day Enterprise Rollout

  • Days 0–15: Baseline & Policy: Inventory all chains, assets, bridges, and wallets currently in use. Define an initial allowlist and establish circuit-break rules based on a clear risk framework.
  • Days 16–45: Prototype: Convert a single user journey, such as a cross-chain payout, to use an intent-based flow with account abstraction and a paymaster. Measure the impact on user drop-off, latency, and support load.
  • Days 46–75: Expand Rails: Add a second interoperability rail to the system and route transactions dynamically based on policy. Integrate CCTP for native USDC mobility if stablecoins are part of the workflow.
  • Days 76–90: Harden: Wire the platform’s observability data to your SIEM, run chaos tests on route failures, and document all operating procedures, including emergency pause protocols.

Common Pitfalls (and How to Avoid Them)

  • Routing by "Gas Price Only": Latency, finality, and security assumptions matter as much as fees. Price alone is not a complete risk model.
  • Ignoring Gas: If your experience touches multiple chains, gas abstraction isn't optional—it's table stakes for a usable product.
  • Treating Bridges as Interchangeable: They aren’t. Their security assumptions differ significantly. Codify allowlists and implement circuit breakers to manage this risk.
  • Wrapped-Asset Sprawl: Whenever possible, prefer native asset mobility (like USDC via CCTP) to minimize liquidity fragmentation and reduce counterparty risk.

The Enterprise Upside

When chain abstraction is done well, blockchain stops being a collection of idiosyncratic networks and becomes an execution fabric your teams can program against. It offers policies, SLAs, and audit trails that match the standards you already operate under. Thanks to mature intent standards, account abstraction, robust interop rails, and native stablecoin transport, you can finally deliver Web3 outcomes without forcing users—or your own developers—to care about which chain did the work.