Author: 137Las
I. RWA is hot, but why haven't most projects seen real growth?
Over the past two years, RWA has become one of the most certain narratives in the crypto industry, with traditional financial institutions such as BlackRock, Franklin Templeton, Apollo, and WisdomTree continuously driving assets like funds, government bonds, credit, and commodities onto the blockchain. The market widely expects RWA to bring the massive asset scale of traditional finance into the crypto ecosystem. However, when examining user growth and on-chain activity, many RWA projects have not fully lived up to this narrative, as they address the question of “whether assets can be tokenized” but fail to truly solve the issue of “whether anyone will actually use these tokenized assets.”
This is precisely the core tension in Phase One of RWA: although assets have been moved on-chain, they typically exist only as static tokens, leaving users with few subsequent financial use cases after purchase. DeFi protocols struggle to build lending, trading, yield aggregation, or derivative strategies around these assets, resulting in many RWA products achieving tokenization in name only without entering crypto’s most critical network of composability. Messari’s research on Plume also highlights that the current issue with many RWAs is not a lack of assets themselves, but rather that these assets often remain fragmented, illiquid, high-barrier, and devoid of native crypto use cases—making it difficult to generate true network effects.
Plume’s entry point is precisely redefining RWA from “asset issuance” to “asset financialization.” In Plume’s narrative, RWA is not merely about packaging real-world assets into tokens and storing them in users’ wallets for redemption; instead, it’s about integrating these assets into an on-chain financial system where they can be traded, lent, staked, combined, and reallocated. In other words, Plume is not building a display case for assets—it’s attempting to construct a DeFi operating system designed for real-world assets.
II. Plume's First Principle: Serve Crypto-Native Users First, Not Institutions
The intuitive path for many RWA projects is to first serve institutions, since the source of real-world assets lies with institutions; after institutions issue assets, they distribute products to users through compliant channels. This approach works in traditional finance, but in the crypto world, it faces a clear problem: if the asset fails to address the genuine needs of crypto-native users, even the strongest institutional brand will struggle to achieve on-chain growth.
Plume’s reverse approach is that the successful model for RWA should not focus solely on traditional financial assets themselves, but should instead revisit the growth history of stablecoins. Stablecoins became the most successful RWA not because they initially captivated institutions with a grand narrative of “tokenizing real-world assets,” but because they precisely addressed the most urgent needs of crypto users: a stable unit of account for trading, a foundational settlement asset for DeFi, low-friction USD liquidity for cross-border transfers, and an on-chain hedging tool. In other words, the growth of stablecoins did not begin with institutional supply, but with native crypto demand.
Plume’s inspiration from this is evident. Rather than positioning itself as a permissioned platform for institutional asset issuance, it emphasizes RWAfi—Real World Asset Finance—which goes beyond mere RWA tokenization to enable real-world assets with financial utility on-chain. Messari’s characterization of Plume is similar: Plume is a dedicated blockchain and ecosystem for crypto-native users, with a core focus on ensuring that tokenized assets are accessible, usable, and integrable within DeFi environments from day one.
Behind this lies a clear growth philosophy: institutional assets themselves are not growth—user demand is; asset size is not growth—asset utilization is; compliance entry points are not growth—financial scenarios that enable repeated user interaction are. Therefore, Plume’s early strategy was not simply about “how many assets to onboard,” but rather about reimagining RWA around the yields, liquidity, leverage, and composability that Crypto Native users already understand, so that users perceive not “I bought a traditional financial product,” but “I gained a new on-chain yield and asset allocation tool.”
Three: The True Starting Point of Growth—Not TVL, But Product Design
Plume’s product design can be understood as a three-layer structure: the asset entry layer, the yield utilization layer, and the user access layer. These correspond to Arc, Nest, and Portal, respectively, which together form Plume’s growth foundation.
Arc functions more like Plume’s asset issuance and tokenization engine, addressing how assets are brought on-chain, how they are compliantly encapsulated, and how they are transformed into financial objects callable by on-chain applications. For RWA projects, asset issuance is certainly important, but Plume’s focus goes beyond issuance itself—through Arc, it standardizes assets so they can seamlessly enter subsequent on-chain financial use cases.
Nest is Plume’s most critical growth product today, as it enables the conversion of “static assets” into “yield-generating assets.” Plume’s official blog has repeatedly positioned Nest as an RWA yield infrastructure—for example, EtherFi’s collaboration with Plume leverages the Nest Vault infrastructure to provide users with a tokenized RWA yield entry point backed by Superstate USCC. The key significance of this product design lies in its ability to repackage RWA into familiar on-chain yield products, eliminating the need for users to understand complex traditional asset structures.
If the traditional RWA product user journey is “purchase asset—wait for returns—redeem and exit,” Plume aims to enable a new journey: “purchase asset—receive yield token—enter DeFi—generate ongoing liquidity and compositional returns.” This means users no longer hold just a tokenized real-world asset, but an on-chain financial component that can be further utilized in lending markets, yield markets, and liquidity markets. For growth, this design is critical, as it transforms a one-time asset purchase into continuous on-chain interaction.
Portal solves the problem of user onboarding. Plume officially describes Portal as the gateway to RWAfi, enabling users to discover dApps, protocols, institutional-grade yield opportunities, and various RWA assets. Although it may appear to be merely a frontend entry point, it is critically important for growth, as one of the biggest challenges with RWA is high user comprehension costs, fragmented access points, and complex product structures—without a unified entry point, users struggle to move from “knowing about Plume” to “actually using Plume.”
Therefore, Plume’s growth is not driven by a single product breakout, but by a product structure that reduces user cognitive costs and connects asset issuance, yield generation, and on-chain interactions into a closed loop. Its true goal is not to make users “see RWA,” but to make them “use RWA as easily as they use DeFi.”
Four: The Growth Flywheel: Why Is Plume Accelerating?
Plume’s growth flywheel can be summarized as: institutional assets enter, assets are transformed into composable yield products via Nest, users join the ecosystem due to the yields, users and capital bring liquidity, liquidity attracts more DeFi protocols and institutional assets, ultimately creating a positive feedback loop between asset supply and user demand.
The first layer is institutional asset inflow. Plume has secured funding support from institutions such as Brevan Howard Digital, Haun Ventures, Galaxy Ventures, Lightspeed Faction, Superscrypt, HashKey, and Laser Digital. Its $20 million Series A round, completed in December 2024, demonstrates shared interest from traditional finance and crypto capital in its RWAfi direction. Such institutional backing not only provides capital but, more importantly, helps Plume access institutional assets, compliance resources, and financial industry networks.
The second layer transforms assets into DeFi Lego blocks. Plume’s core isn’t merely showcasing institutional assets—it’s enabling those assets to integrate into Nest, lending protocols, yield strategies, cross-chain infrastructure, and wallet gateways, turning RWA from an “investment product” into a “financial primitive.” If this step succeeds, Plume’s asset volume will no longer be limited to static TVL but will evolve into multi-dimensional on-chain activities such as trading, lending, staking, and portfolio composition.
The third layer is user growth. BeInCrypto cited data from RWA.xyz stating that Plume holds a very large market share in the number of RWA holders and once surpassed Ethereum to become the network with the most RWA holders. However, its total asset value remains relatively limited, indicating that Plume initially built its user-side advantage through low barriers to entry, high distribution, and high user engagement, rather than prioritizing large-scale institutional asset accumulation. From a growth perspective, this is significant because it means Plume’s strength lies not just in “having assets,” but in “having a large number of users willing to participate in RWAfi.”
The fourth layer is liquidity growth. As the user base expands, protocols become more willing to integrate with Plume, since they require users and capital; similarly, institutions become more inclined to deploy assets on Plume, as they seek distribution and liquidity. Plume’s official website also emphasizes its goal of transforming assets into globally accessible, crypto-native financial instruments, highlighting key metrics such as asset pipelines, ecosystem partners, and TVL.
The fifth layer involves greater institutional participation. When a network already has users, protocols, liquidity, and yield opportunities, institutions are no longer motivated simply to "get on-chain," but rather to "access new distribution markets." This is the most critical aspect of Plume’s growth flywheel: it aims to encourage institutions to go on-chain not for narrative purposes, but to reach genuine on-chain demand.
Five: Ecosystem Growth — Plume is building a network rather than chasing TVL
Many public blockchains emphasize TVL in their early growth stages, but Plume’s growth model is more aligned with ecosystem network building, as the value of RWAfi is not determined by individual assets alone, but rather by the collective contributions of asset issuers, yield protocols, lending protocols, wallets, cross-chain protocols, data services, and compliance services. RWA.xyz’s introduction to Plume also highlights it as a full-stack L1 and ecosystem designed for RWAfi, featuring an EVM-compatible environment and over 180 projects building on its network.
The key to this ecosystem growth is that Plume doesn’t just add partner logos—it aims to ensure every type of partnership enhances asset utilization. Asset issuers provide the underlying assets, Nest packages them into yield-bearing products, DeFi protocols enable lending, trading, and liquidity scenarios, wallets and Portal lower user entry barriers, and cross-chain protocols expand asset distribution. While this multi-sided network is harder to build than single-point growth, once established, it creates a more durable moat.
For example, when Plume launched its $25 million RWAfi ecosystem fund in 2025, official communications highlighted that over 180 projects had already been built on its network, emphasizing that Plume provides a composable, EVM-compatible environment for accessing and managing diverse real-world assets. This demonstrates that Plume’s understanding of the ecosystem is not “I issue assets, others buy them,” but rather “I provide assets and infrastructure, and ecosystem projects build financial applications around these assets.”
From a growth perspective, this ecosystem strategy is more complex than simply chasing TVL, but it better aligns with the long-term logic of RWAfi, because the ultimate goal of RWA is not to top asset size rankings, but to enable assets to be integrated into the widest range of use cases, repeatedly utilized by the most users, and ultimately become a core part of on-chain finance.
Six: Community Growth: Why the Testnet Is More Important Than Mainnet Launch?
Another often-underestimated aspect of Plume’s growth is that it cultivated an early user base through its testnet, points, tasks, community events, and ecosystem incentives before mainnet launch—enabling it to complete user education and behavioral training prior to mainnet, rather than starting from scratch afterward.
For RWA projects, community growth is particularly challenging because RWA lacks the inherent viral properties of memes, GameFi, or NFTs; it is more akin to a financial product, with a higher barrier to understanding and weaker emotional appeal, leading users to engage more rationally. Therefore, Plume must transform the abstract RWAfi narrative into tangible on-chain actions for users through points, tasks, yield experiences, and ecosystem activities—such as connecting wallets, participating in testnets, experiencing the Portal, entering Vaults, and interacting with ecosystem protocols.
The essence of this approach is not simply inflating data, but training users to develop the mindset that "RWA can be used just like DeFi." For a new blockchain, the greatest fear at mainnet launch is not the lack of assets, but the absence of user activity. Through sustained operations during the testnet phase, Plume has transformed a portion of users from observers into participants, and then from participants into potential liquidity providers—laying the foundation for early mainnet growth.
Of course, there is also the risk that points and airdrop expectations may attract short-term speculative users; however, from a growth strategy perspective, Plume has at least grasped a key insight: the mass adoption of RWA cannot rely solely on institutional backing—it must transform complex financial products into on-chain experiences that users are willing to try, through actionable, tangible, and repeatable user tasks.
Seven: Differences Between Plume and Ondo
Plume is often compared to Ondo, but their positioning is fundamentally different. Ondo functions more like an asset issuance and asset management platform, with its core strength lying in tokenizing products such as U.S. Treasuries and yield-generating dollar assets, while building market recognition through branding, compliance, and distribution capabilities. In contrast, Plume is more akin to a dedicated blockchain and financial operating system built around RWAfi, aiming not merely to issue one type of asset, but to provide a comprehensive environment for issuing, distributing, yield-generating, and integrating DeFi for a wide range of real-world assets.
Therefore, Ondo’s approach is more about bringing high-quality assets on-chain, while Plume’s approach is more about creating financial markets on-chain for a variety of real-world assets. This does not mean the two are necessarily zero-sum competitors; rather, they may represent two different layers within the RWA space: Ondo leans more toward asset-side branding, while Plume focuses more on asset-side infrastructure and use cases.
This distinction means their growth metrics differ as well. When evaluating Ondo, the market focuses more on assets under management, product yields, compliance structures, and issuance capabilities; when evaluating Plume, in addition to assets under management, it’s essential to assess user count, number of protocols, asset composability, on-chain interaction frequency, and depth of ecosystem partnerships. In simple terms, Ondo is more like selling assets, while Plume is more like building a market.
Eight: The Greatest Challenge Ahead
Although Plume's growth logic is clear, it still faces three core challenges.
First is the challenge of asset quality. The most common issue in the RWA space is packaging growth through asset volume, but risks, liquidity, transparency, and user demand vary significantly across different asset types—government bonds, private credit, commodities, accounts receivable, GPU revenue rights, and real estate equity cannot be meaningfully compared under a single growth metric. For Plume to build long-term trust, it must demonstrate that the assets it introduces are not only numerous but also of sufficiently high underlying quality, with clear risk disclosures and transparent sources of yield.
Second is the challenge of user retention. Plume’s early user growth inevitably included points, airdrops, and incentives; what truly determines long-term value is whether users continue to use Nest, Portal, and ecosystem protocols after incentives decline. If users only come for short-term rewards, growth will drop off once incentives end. But if users stay for the yields, asset allocation, and DeFi composability, Plume’s user base will transform from campaign-driven traffic into genuine financial liquidity.
Third is the challenge of balancing compliance with openness. RWA inherently requires compliance, KYC, asset custody, legal structures, and cross-border regulatory support, yet the crypto world champions openness, composability, and permissionless innovation. Plume’s challenge lies in making institutions feel secure issuing assets, while also ensuring DeFi developers and everyday users perceive the platform as sufficiently open. Over-compliance may erode crypto-native vitality; excessive openness, however, could increase regulatory and asset risks.
Conclusion
If you view Plume merely as an RWA Layer 1, you’re underestimating its ambition. Plume is truly building an on-chain financial operating system for real-world assets, whose core mission isn’t simply to move assets on-chain, but to give them new life on-chain—enabling them to be used, combined, traded, borrowed, yield-generating, and ultimately integrated into the DeFi ecosystem.
This is also the key difference between Plume and many RWA projects. Many projects still focus on the tokenization narrative, emphasizing asset on-chainization, institutional backing, and market size; whereas Plume places greater emphasis on financialization—how assets generate ongoing financial activity once on-chain. The former addresses “where the assets are,” while the latter addresses “how the assets flow.”
Therefore, Plume’s growth cannot be explained by a single metric—it stems from a compounding flywheel driven by asset supply, user demand, ecosystem protocols, yield products, community operations, and institutional partnerships. If this flywheel continues to turn, Plume’s moat will not be defined by any single asset, partner, or funding round, but rather by a multi-sided network built around RWAfi.
Ultimately, the winner in the RWA赛道 may not be determined by who puts assets on-chain first, but by who can truly turn real-world assets into usable financial primitives in the crypto world. Plume is currently betting on this very direction.