Contact
Digital Currency Authority serves as a reference resource covering the regulatory, operational, and technical dimensions of digital currency in the United States. This page outlines how inquiries are handled, what kinds of questions fall within the scope of this resource, and what external channels exist for matters requiring licensed professional or regulatory agency attention. Understanding which type of inquiry belongs where is essential — the digital currency sector is governed by overlapping federal frameworks administered by agencies including the Financial Crimes Enforcement Network (FinCEN), the Commodity Futures Trading Commission (CFTC), the Securities and Exchange Commission (SEC), and the Internal Revenue Service (IRS), and no single reference site substitutes for guidance from those bodies.
Response expectations
Inquiries submitted through this site are reviewed against a defined scope. Digital Currency Authority publishes reference-grade informational content — it does not provide legal advice, tax counsel, investment recommendations, or regulatory compliance opinions. Responses to editorial questions, factual corrections, or content clarifications are typically addressed within 5 business days of receipt.
The following breakdown defines how different inquiry types are categorized:
- Editorial and factual corrections — Reports of outdated regulatory citations, broken links, or inaccurate data points. These receive priority handling and are routed to the content review process.
- Content scope requests — Suggestions for topics not yet covered in the reference library, such as gaps identified in areas like state-level digital currency laws or digital currency estate planning. These are logged and evaluated against the editorial roadmap.
- Licensing and partnership inquiries — Requests related to syndication, citation permissions, or institutional reference use. These are handled separately from editorial matters.
- Regulatory or legal questions — Inquiries seeking compliance opinions, tax positions, or legal interpretations are outside the scope of this resource and are redirected to the appropriate agencies or licensed professionals.
Responses are not guaranteed for inquiries that fall outside these 4 defined categories, including general investment questions or requests for portfolio advice.
Additional contact options
For matters that require authoritative regulatory guidance rather than reference information, the following named federal agencies and their public contact channels are the appropriate destinations:
- IRS Digital Assets guidance — The IRS publishes formal guidance on tax treatment of digital currency at IRS Notice 2014-21 and subsequent updates. The IRS taxpayer assistance line handles reporting and filing questions.
- FinCEN compliance questions — Money services businesses and virtual currency exchangers subject to the Bank Secrecy Act (31 U.S.C. § 5311 et seq.) can reach FinCEN through fincen.gov/contact.
- SEC investor inquiries — Questions about whether a digital asset qualifies as a security or about registered exchanges can be directed to the SEC's public inquiry line at sec.gov/contact-information.
- CFTC commodity and derivatives questions — The CFTC regulates digital asset derivatives and certain spot markets; public inquiries are handled at cftc.gov/Contact.
- State money transmission regulators — Licensing obligations for digital currency businesses vary by state. The Conference of State Bank Supervisors (CSBS) maintains the NMLS system and provides a provider network of state regulators.
For consumer complaints about fraud, scams, or exchange failures — topics covered in reference form at digital-currency-scams-and-fraud and hacks-and-exchange-failures — the Consumer Financial Protection Bureau (CFPB) and the FTC at ReportFraud.ftc.gov accept formal complaints.
How to reach this office
Editorial correspondence is accepted through the contact form embedded on this page. When submitting a factual correction or content gap request, including the specific page URL and the relevant regulatory source or public document that supports the correction reduces review time. Anonymous submissions are accepted, though they cannot receive a reply.
For citation or licensing requests, a brief description of the intended use and the publishing context should accompany the inquiry. Academic and government reference uses are evaluated under different criteria than commercial syndication.
Response times follow this structure:
| Inquiry Type | Expected Response Window |
|---|---|
| Factual correction with source citation | 3 business days |
| Content scope suggestion | 5 business days |
| Licensing or syndication request | 7 business days |
| Out-of-scope regulatory question | Redirect only, no timeline |
No inquiry should be treated as establishing a professional relationship, retainer, or advisory engagement. This site operates as a reference publisher, not a licensed financial, legal, or compliance services provider.
Service area covered
Digital Currency Authority covers digital currency topics as they apply within United States jurisdictional frameworks. The primary regulatory scope encompasses federal law — including the Bank Secrecy Act, IRS reporting obligations under 26 U.S.C. § 6045, and SEC/CFTC oversight authorities — alongside the money transmission licensing regimes of all 50 states and the District of Columbia.
Reference content on this site does not extend to jurisdiction-specific compliance advice for non-US regulatory environments, though comparative context is occasionally included where it illuminates US frameworks. For example, the EU's Markets in Crypto-Assets (MiCA) regulation appears in reference discussions where it contrasts structurally with the fragmented US regulatory approach.
Content covering cross-border transactions — including cross-border payments and digital currency — addresses the US regulatory obligations of US-based parties rather than foreign compliance requirements. Inquiries relating exclusively to non-US regulatory questions are outside the editorial scope of this resource and are not assigned to the standard response queue.
Report a Data Error or Correction
Found incorrect information, an outdated fact, or a broken link? Use the form below.