Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/u814201603/domains/kriptobulten.online/public_html/wp-includes/functions.php on line 6121
VanEck, Ethereum vadeli işlemler ETF’sini kapatma kararı aldı! - Kripto Bülten

VanEck, Ethereum vadeli işlemler ETF’sini kapatma kararı aldı!

0

VanEck, Ethereum vadeli işlemlerine dayalı borsa yatırım fonu olan “VanEck Ethereum Strategy ETF”yi kapatma ve tasfiye etme kararı aldı, bu süreç 16 Eylül 2024 tarihinde tamamlanacak ve hissedarlar nakit dağıtımı alacaklar.

vaneck etf delist edildi

VanEck, bugün yaptığı açıklamada, Ethereum vadeli işlemlerine dayalı borsa yatırım fonu (ETF) olan “VanEck Ethereum Strategy ETF“yi (EFUT) kapatmayı ve tasfiye etmeyi planladığını duyurdu.

VanEck ETF Trust Yönetim Kurulu, 5 Eylül 2024 tarihinde aldığı kararla aşağıda belirtilen fonun tasfiyesi ve feshi konusunda onay verdi:

ETF Adı: VanEck Ethereum Strategy ETF
Ticker: EFUT
Borsa: CBOE

VanEck, ETF‘lerinin performansı, likidite durumu, yönetilen varlık miktarı ve yatırımcı ilgisi gibi çeşitli faktörleri sürekli olarak değerlendiriyor. Bu değerlendirmeler sonucunda, söz konusu fonun likidasyonu kararı alındı.

Fonun Tasfiye Süreci:

  • Yatırımcılar, 16 Eylül 2024 tarihine kadar borsada işlemlerini gerçekleştirebilecekler. Bu tarihten sonra fon hisseleri borsada işlem görmeyecek ve listeden kaldırılacak.
  • Hisselerini tasfiye tarihine kadar elinde bulunduran yatırımcılar, net varlık değerine eşit bir nakit dağıtımı alacaklar. Bu ödeme, yatırımcıların aracı kurumlarındaki nakit hesaplarına 23 Eylül 2024 tarihinde aktarılması planlanıyor.
  • Yatırımcılar, bu likidasyon kapsamında elde ettikleri gelir üzerinden sermaye kazancı ya da zararı beyan etmek zorunda kalacaklar.
  • Fon, 16 Eylül 2024 tarihinden itibaren yeni yatırımcılar için yeni fon yaratma taleplerini kabul etmeyecek.

Ek olarak, fonu elinde bulunduran hissedarlar, tasfiye öncesinde fon tarafından dağıtılmamış olan son net gelir ve sermaye kazançlarını alabilirler.

Vergi Durumu:

Fon tarafından yapılan dağıtımların nihai vergi durumu, yıl sonunda yatırımcılara gönderilecek vergi raporlarıyla birlikte sağlanacak. Bu raporlar, dağıtımın sermaye geri dönüşü olarak değerlendirilip değerlendirilmeyeceğini ve yatırımcının hisse maliyetini nasıl etkileyeceğini gösterecek.

VanEck‘in bu stratejik hamlesi, Ethereum vadeli işlemler ETF pazarındaki ilginin ve performansın bir yansıması olarak değerlendiriliyor.

Kaynak: VanEck

Leave a Reply