Deprecated: Optional parameter $content declared before required parameter $post is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/functions.php on line 840

Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 553

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 594

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 534

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 543

Warning: Private methods cannot be final as they are never overridden by other classes in /home/blogcert/public_html/wp-includes/class-wp-session-tokens.php on line 69

Deprecated: Optional parameter $object_id declared before required parameter $taxonomy is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/nav-menu.php on line 1060

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 934

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 954

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 966

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 977

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: Optional parameter $block_name declared before required parameter $block_content is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/blocks.php on line 405

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 386

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 378

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 372

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 390

Warning: The magic method OCDI\OneClickDemoImport::__wakeup() must have public visibility in /home/blogcert/public_html/wp-content/plugins/one-click-demo-import/inc/OneClickDemoImport.php on line 128

Deprecated: Optional parameter $type declared before required parameter $wrapper is implicitly treated as a required parameter in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/class-fs-logger.php on line 145

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/wp-db.php on line 3008

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378
{"id":3797,"date":"2021-11-24T04:59:21","date_gmt":"2021-11-24T04:59:21","guid":{"rendered":"https:\/\/blog.certifiedfinancialguardian.com\/?p=3797"},"modified":"2021-11-24T05:18:57","modified_gmt":"2021-11-24T05:18:57","slug":"should-you-invest-in-mutual-funds-betting-on-blockchain-technology-and-cryptos","status":"publish","type":"post","link":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/2021\/11\/24\/should-you-invest-in-mutual-funds-betting-on-blockchain-technology-and-cryptos\/","title":{"rendered":"Should You Invest in Mutual Funds Betting on Blockchain Technology and Cryptos?"},"content":{"rendered":"\n

Greed and fear are the two psychological factors that drive the capital markets and affect individual and institutional investors alike. Even professional money managers such as mutual funds sometimes find it difficult to resist the FOMO (Fear of Missing Out) trait.<\/p>\n\n\n\n

The emergence of next-generation technologies and digital adoption of businesses are the two most popular investment themes attracting investors globally at present. Blockchain technology<\/strong>, for instance, has introduced many investors to the world of cryptocurrencies<\/a><\/strong>.<\/p>\n\n\n\n

As per investopedia.com<\/a>, crypto in cryptocurrencies refers to complicated cryptography that allows the creation and processing of digital currencies and their transactions across decentralized systems. Thus, cryptocurrencies are also referred to as virtual or digital money in form of coins or tokens.<\/p>\n\n\n\n

Bitcoins, Binance Coin, Ethereum, Tether, Cardano, and Solana, are some of the most popular cryptocurrencies (as per CoinMarketCap) that exist today, and many of them have delivered mindboggling returns in a very short period of time. This has enticed a lot of investors, including mutual funds.<\/p>\n\n\n\n

Recently, Invesco (India) Mutual Fund announced the launch of its new fund — Invesco CoinShares Global Blockchain ETF Fund of Fund — after a nod from the capital market regulator, SEBI. The permission was given despite no regulations in India for cryptocurrencies. But soon enough, Invesco Mutual Fund put this fund launch on a hold or backburner owing to regulatory concerns. In its media representations, Invesco Mutual Fund<\/a> has cited potential legislative changes in India pertaining to crypto-assets and likely uncertainty thereof as the primary reason.<\/p>\n\n\n\n

Invesco (India) Mutual Fund was planning to launch Invesco India-Invesco CoinShares Global Blockchain ETF Fund of Fund (FoF) on November 24, 2021. The investment objective of the scheme was to generate returns by investing predominantly in units of Invesco CoinShares Global Blockchain UCITS ETF, an overseas Exchange Traded Fund — referred to as the underlying fund — that seeks to achieve the performance of the CoinShares Blockchain Global Equity Index (the Reference Index) less fees, expenses and transaction costs.<\/p>\n\n\n\n

Invesco CoinShares Global Blockchain UCITS ETF, incepted in March 2019 has Assets Under Management (AUM) worth USD 983.18 million as of November 19, 2021, and invests across industries and geographies. The top-5 regions it invests in are the U.S., U.K., developed part of Europe, Asia, and Japan.<\/p>\n\n\n\n

Although the underlying fund hasn’t been betting actively on cryptocurrencies, it has significant exposure to listed crypto infrastructure companies. For example, the fund’s core holdings are Coinbase Global Inc., Bitfarms Ltd., Monex Group Inc., GMO Internet Inc., Hive Blockchain Technologies Ltd. Taiwan Semiconductor amongst others, many of which are in the technology sector, communication services, and financial services whose business operations provide infrastructure to crypto-economy. Their fate is closely tied to that of cryptocurrencies.<\/p>\n\n\n\n

You would be surprised to know, Coinbase has over 7.3 crore users spread across more than 100 countries. Coinbase allows users to invest, spend, store, and earn cryptocurrencies. Whereas Hive is a crypto mining company that mines Bitcoin and Ethereum.<\/p>\n\n\n\n

Technocrats believe blockchain technology<\/a> is still in its nascent stages of development and can find applications in diverse industries right from agriculture to internet advertising. Since data blocks are sequential and stored in every computer on the network, it’s impossible to remotely alter data once recorded. Thus, blockchain eliminates the need for third-party validation. Blockchain technology allows decentralized recording keeping of transactions across the network. When properly implemented, the blockchain enhances transparency, traceability and security of data. Moreover, it offers cost savings and delivers efficiency.<\/p>\n\n\n\n

Having said that, it raises concerns when fund house such as Invesco does not adopt a very diligent approach when launching a high-risk thematic fund. Broadly speaking, investing in Invesco India – Invesco CoinShares Global Blockchain ETF Fund of Fund should have assessed if enough regulations exist and then may be considered launch. Currently, such schemes are riskier than any technology sector fund.<\/p>\n\n\n\n

The RBI<\/a> has been warning against risks involved in crypto assets for a long time now. The central bank after internal deliberations has made serious concerns about macroeconomic, monetary, and financial stability with cryptocurrencies. Besides, the alleged role of cryptocurrencies in money laundering<\/a> and terror funding has been a topic of discussion for quite a while now.<\/p>\n\n\n\n

Is it that the fund houses only recognize the seriousness of the situation when they see the government moving to regulate crypto assets? Currently, only the U.K., Ukraine, Singapore, Indonesia, and Canada are among the few countries that have regulated cryptocurrencies. The countries that have proposed to regulate cryptocurrencies are the United States of America (USA), Brazil, and India to name a few. On the other hand, countries like China, Algeria, and Bangladesh, have banned cryptocurrencies.<\/p>\n\n\n\n

It is true that blockchain technology is much bigger than the cryptocurrency ecosystem and cryptocurrencies are just one part of it. But it is equally true that if cryptocurrencies nosedive someday for any reason, including regulatory changes across geographies, the popularity of blockchain technology might take a severe beating.<\/p>\n\n\n\n

It is unfortunate that instead of cautioning investors against following such market fads, some mutual fund houses are capitalising on the excitement for cryptocurrencies; striking while the iron is hot.<\/p>\n\n\n\n

I would like to caution you, the investors, not to get carried away by the marketing literature of mutual funds betting heavily on the crypto ecosystem, cryptocurrencies and blockchain technology. You would do better staying away from such schemes. If looking at the extraordinary returns or jaw-dropping rallies of certain cryptocurrencies is encouraging you to invest your hard-earned money, it is an imprudent approach. All that shines and goes up quickly isn’t gold and holds the propensity to descend as well. Investing in cryptocurrencies and mutual funds investing in blockchain technology is a very high-risk proposition.<\/p>\n\n\n\n

At PersonalFN, we have been time and again continually cautioning you to stay away from the sector and thematic funds<\/a>. They carry too much risk and the returns do not always commensurate with the kind of risk taken.<\/p>\n\n\n\n

You need not take unwarranted risks or invest in fancy themes to outperform markets. Instead, what you require to do is devise a sensible and time-tested investment strategy. The Core & Satellite Investment strategy is followed by some of the most successful investors.<\/p>\n\n\n\n

The term ‘Core’ applies to the more stable, long-term holdings of the portfolio, while the term ‘Satellite’ applies to the strategic portion that would help boost the overall returns of the portfolio, across market conditions.<\/p>\n\n\n\n

When you construct a portfolio of equity mutual fund schemes with strategy, the ‘Core’ holding should comprise around 65-70% of your equity mutual fund portfolio and consist of a Large-cap Fund<\/a>, Flexi-cap Fund<\/a>, and Value Fund<\/a>\/Contra Fund. Whereas, the ‘Satellite’ holdings of the portfolio can be around 30-35% comprising of a Mid-cap Fund<\/a> and an Aggressive Hybrid Fund<\/a>.<\/p>\n\n\n\n

By wisely structuring and timely reviewing the Core and Satellite portions and the holdings therein, you would be able to add stability to the portfolio while strategically boosting your portfolio returns at the same time.<\/p>\n\n\n\n

While you add equity mutual fund schemes to your investment portfolio based on the Core & Satellite strategy, here are a few fundamental rules to follow:<\/strong><\/p>\n\n\n\n