A claim that an institution has adopted a crypto product or signed on as a client is verifiable only at one step: the named entity's own regulatory filing. For US public companies and many foreign issuers, that filing must be submitted electronically to the SEC's EDGAR (Electronic Data Gathering, Analysis, and Retrieval) system, and anyone can access and download that information for free or query it through EDGAR public searches. This article sets out a repeatable way to test an adoption claim against that record rather than against the press release making the claim.

Step 1: Pin the claimant to a filing issuer

An adoption claim usually names a brand, a parent, or a fund. Those are not always the same legal entity. Start by asking whether the named party is itself a registrant. All companies, foreign and domestic, are required to file registration statements, periodic reports, and other forms electronically through the SEC's EDGAR system, so if the named entity is a registrant, there should be a filing history to search.

If the name in the announcement does not match a registrant, the claim may rest on a subsidiary, an affiliate, or an entity outside the filing perimeter. That gap is itself a finding: an adoption claim about a non-registrant has no EDGAR trail, and the evidence must come from somewhere else.

Step 2: Search before you script

For a single claim, EDGAR public searches are sufficient. Anyone can query the system through its public searches, and that is the appropriate route when you are checking one announcement against one company.

Scripted access is a different activity with published obligations. To ensure everyone has equitable access, the SEC asks users to use efficient scripting, download only what is needed, and moderate requests to minimize server load. The SEC also reserves the right to limit request rates to preserve fair access for all users, and it points users to its Internet Security Policy for the current rate request limit. It does not allow botnets or automated tools to crawl the site, and requests identified as part of a botnet or an automated tool outside the acceptable policy will be managed to ensure fair access for all users.

If you do build a scripted check, the published guidance asks you to declare your user agent in request headers, with a sample format of a company name plus an administrative contact email on the company domain. The SEC states plainly that it does not offer technical support for developing or debugging scripted processes. For a newsroom verifying a single adoption claim, public searches avoid this layer entirely.

Step 3: Read the filing, not the summary

An adoption claim typically asserts one of three things: that a named institution is a client, that it holds a product, or that it has entered an agreement. Each maps to different filing language, and a filing may disclose one without the other.

  • A client claim requires a named counterparty in the filing. A general statement about demand or institutional interest does not name one.
  • A holding claim requires the entity to appear in the relevant ownership or holdings disclosure, not merely to be discussed in a press release.
  • An agreement claim requires the agreement to be described or filed. Announcement language about a signed deal is not the same as a filed agreement.

Record the exact wording. A filing that describes a pilot, an evaluation, or an intent is not the same as one that describes completed adoption, and the difference usually survives in the text.

Step 4: Check the timing against the index

Filing timing explains why a claim sometimes cannot be checked on the day it appears. EDGAR accepts new filer applications, new filings, and changes to filer data each business day, Monday through Friday, from 6:00 a.m. Indexes incorporating the current business day's filings are updated nightly starting about 10:00 p.m., ET, usually completing within a few hours.

Late submissions move the check to the next day. Some filing submissions that begin after 5:30 p.m. for Ownership forms 3, 4, and 5 will be disseminated the next business day, showing up in the following business day's index. An announcement published in the evening may therefore have no visible filing trail until the next index update, and that absence is a timing fact rather than proof the claim is false.

A worked example of the check

Hypothetical: a crypto firm announces on a Tuesday morning that a named bank has adopted its product, and the supporting language is a single sentence about institutional demand. The verification path is: confirm whether the bank is a registrant with an EDGAR filing history; search its recent periodic reports for the named product; if nothing appears, check whether the announcement was timed after a 5:30 p.m. submission cutoff on the prior business day; and if the product is named only in the press release, classify the claim as unsupported by filing evidence rather than as false.

That classification matters for readers. Three outcomes should be kept separate: a filing confirms the claim; a filing exists but does not confirm it; and no filing has yet appeared because of index timing. Only the first is confirmation.

Older and paper records

For historical checks, paper copies of filing documents prior to 1994 may be available by filing a Freedom of Information Act request. The SEC directs users to a separate page on accessing or requesting records not accessible via its website. Adoption claims about older arrangements may therefore have no electronic trail at all.

What the source does not say

The source describes EDGAR access and filing mechanics. It does not establish that any particular institutional adoption claim is true or false, does not list which entities are registrants, and does not describe how crypto products appear in disclosure language.

It also does not publish a specific numeric request-rate limit in the text reviewed; it points to a separate security policy for the current figure. Nothing in it indicates that a missing filing proves a claim was fabricated, and nothing in it validates any product, token, or price, so no price implication should be drawn from a filing's presence or absence.

Sources