Market Cap: $2.8588T -5.21%
Volume(24h): $157.21B 50.24%
Fear & Greed Index:

38 - Fear

  • Market Cap: $2.8588T -5.21%
  • Volume(24h): $157.21B 50.24%
  • Fear & Greed Index:
  • Market Cap: $2.8588T -5.21%
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
Top Cryptospedia

Select Language

Select Language

Select Currency

Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos

How to monitor institutional ETH ETF holdings? (13F filings)

U.S. 13F filings don’t capture ETH ETF holdings—these are excluded as non-equity securities—forcing analysts to rely on issuer dashboards, DTCC flow data, on-chain analytics, and N-PORT reports for institutional exposure insights.

Jan 06, 2026 at 09:20 am

Understanding 13F Filings in the Context of ETH ETFs

1. The U.S. Securities and Exchange Commission mandates that institutional investment managers with over $100 million in assets under management file Form 13F quarterly.

2. While traditional 13F reports cover equity holdings, they do not include direct exposure to spot Ethereum or ETH ETF shares, as these ETFs are classified as exchange-traded funds and fall outside the scope of standard equity reporting.

3. Managers holding ETH ETFs may report them under “other securities” or omit them entirely if the fund is structured as a commodity trust or registered under the Investment Company Act of 1940 differently than typical equity ETFs.

4. Some institutions disclose ETH ETF positions via voluntary supplements or through separate regulatory filings such as N-PORT for registered investment companies, though access remains limited to SEC-registered entities and select data vendors.

Alternative Data Sources Beyond 13F

1. ETF issuer transparency dashboards—Grayscale, BlackRock (iShares Ethereum Trust), and Bitwise publish daily holdings, total AUM, and share count updates on their official websites.

2. On-chain analytics platforms like Nansen and Arkham Intelligence track wallet addresses linked to known institutional custodians, revealing inflows and outflows tied to ETH ETF creation/redemption activity.

3. Depository Trust & Clearing Corporation (DTCC) provides daily ETF creation and redemption reports, which reflect authorized participants’ activity—these are publicly accessible and serve as a proxy for institutional demand pressure.

4. Bloomberg Terminal and FactSet offer ETF ownership breakdowns by institution when available, sourced from shareholder registry data or proprietary surveys—not derived from 13F but often more timely and precise for crypto-native products.

Decoding Authorized Participant Activity

1. Institutions rarely hold ETH ETF shares long-term; instead, they act as intermediaries facilitating arbitrage between the ETF’s market price and its net asset value (NAV).

2. High-frequency creation/redemption volumes—especially during volatility spikes—signal institutional positioning shifts, even without explicit disclosure of beneficial ownership.

3. Authorized participants like Citadel Securities, Jane Street, and Virtu Financial dominate ETH ETF flow, and their public commentary or regulatory disclosures sometimes reference exposure levels or hedging strategies involving ETH futures or staking derivatives.

4. SEC filings such as Form D or ADV Part 1A occasionally list cryptocurrency-related ETFs under “securities held” if the adviser manages dedicated crypto strategies, though coverage remains inconsistent across firms.

Regulatory Classification Challenges

1. The SEC treats spot ETH ETFs differently depending on their structure: some are organized as trusts under Delaware law, others as series of an investment company, affecting whether holdings appear in public databases at all.

2. Unlike equities, ETH ETF shares lack CUSIP numbers tied to standardized ownership registries, making aggregation across custodians difficult without direct access to transfer agent records.

3. No central repository exists for real-time institutional ETH ETF ownership, forcing analysts to triangulate signals from custody reports, options open interest, and basis trade behavior across CME and Deribit.

4. Filing delays compound uncertainty—13F submissions occur 45 days after quarter-end, while ETH ETF flows can reverse direction multiple times within that window due to macro-driven volatility.

Frequently Asked Questions

Q1. Can hedge funds report ETH ETF holdings on Schedule 13G?A1. No. Schedule 13G applies only to passive investors holding >5% of a Section 12 registered equity security. ETH ETFs are not classified as equities for this purpose, and most do not meet the registration criteria required for 13G eligibility.

Q2. Do mutual funds disclose ETH ETF exposure in their semiannual reports?A2. Yes—if a mutual fund holds ETH ETF shares, it must list them in its Statement of Investments filed on Form N-PORT. These reports are publicly available via the SEC’s EDGAR database approximately 60 days after period-end.

Q3. Why don’t broker-dealer prime brokerage reports show ETH ETF positions?A3. Prime brokers typically treat ETH ETFs as listed securities subject to internal risk systems rather than client-level position reporting. Disclosure obligations focus on margin, concentration, and counterparty exposure—not granular fund-level holdings.

Q4. Are there jurisdictional differences in ETH ETF disclosure standards?A4. Yes. EU-based ETFs governed by UCITS regulations publish full portfolio holdings weekly, including underlying ETH reserves and custodial arrangements. U.S.-listed products maintain far less frequent and less detailed transparency protocols.

Disclaimer:info@kdj.com

The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!

If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.

Related knowledge

See all articles

User not found or password invalid

Your input is correct