Analyst: Bitcoin ETF size is expected to surpass gold ETFs, highlighting its investment value

BlockBeatNews
BTC0,11%

BlockBeats message, April 4, Bloomberg ETF analyst James Seyffart said that as market demand continues to expand, the future assets under management (AUM) of Bitcoin spot ETFs are expected to surpass those of gold ETFs.

Seyffart noted that Bitcoin’s use in investment portfolios is more diverse: it can be seen as “digital gold” and a store of value, and it also has attributes such as diversified asset allocation, liquidity trading, and growth-oriented risk assets, while gold’s investment logic is relatively singular.

In terms of fund flows, US gold ETFs have recently seen a clear outflow, with net outflows of about $2.92 billion in March; over the same period, Bitcoin spot ETFs achieved net inflows of about $1.32 billion, indicating that investor preferences are shifting.

Although fund flows have diverged, the recent price trends of Bitcoin and gold have moved in tandem. Over the past 30 days, the price of Bitcoin has fallen by about 8.07%, while the price of gold has fallen by about 8.25%.
Market views hold that as investors’ demand for digital-asset allocation increases, Bitcoin ETFs are gradually shifting from “alternative assets” to mainstream allocation tools, and their long-term scale growth potential is being re-evaluated.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments