A suspicious digital-asset transaction can move beyond an institution’s control in minutes. An investigator may have a victim report, wallet address, or active case. A financial institution may see a withdrawal, conversion, or transfer that appears connected to unlawful activity. Yet the information needed to understand the risk may sit in different organizations and reach the decision-maker too late.
Section 10305 of the updated CLARITY Act addresses one part of that timing problem.
The July 22 text analyzed in this article remains proposed legislation. The Senate did not pass H.R. 3633 before its August state work period. A cloture motion on whether to advance to consideration is scheduled to ripen on September 15, 2026, but that is a procedural step, not final passage, and Section 10305 could still change.
The proposal would protect certain digital-asset service providers and payment stablecoin issuers from federal and state private causes of action when they voluntarily place a qualifying temporary hold on a transaction in good faith and comply with the section’s conditions. A hold could be based on the provider’s reasonable belief that activity relates to a violation or attempted violation of state or federal law, or on a qualified written request from an authorized state or federal law-enforcement official.
The proposal is significant because it would create a protected window for review and coordination. It would not, by itself, supply the intelligence needed to use that window well.
Short answer: Section 10305 would allow specified providers to delay a digital-asset transaction, conversion, or withdrawal for a reasonable period of up to 30 calendar days, with a possible extension of up to 150 additional days pursuant to a qualified written request. Providers acting voluntarily, in good faith, and in compliance with the section would receive protection from federal and state private causes of action. The provision would not automatically seize, permanently freeze, or recover assets.
What would Section 10305 do?
Section 10305 is titled “Temporary Hold for Certain Digital Asset Transactions.”
It defines a temporary hold as a restriction applied by a covered person that delays the execution of a digital-asset transaction, conversion, or withdrawal for a reasonable period. The initial period could not exceed 30 calendar days. It could be extended for up to 150 additional calendar days pursuant to a qualified written request.
The section’s covered persons would include:
- Permitted payment stablecoin issuers
- Certain foreign payment stablecoin issuers registered with the Office of the Comptroller of the Currency
- Digital asset service providers, as defined by the GENIUS Act
The proposal would protect a covered person from federal or state private causes of action for voluntarily implementing a temporary hold when the person acts in good faith and complies with the section.
That wording is narrower than a general statement that providers would have immunity.
The proposal does not eliminate all legal, regulatory, contractual, or operational risk. It creates a specific protection from private lawsuits under federal or state law when the statutory conditions are satisfied.
When could a covered provider receive the proposed protection?
The text describes two primary bases for a temporary hold.
First, a covered provider could implement a hold based on a reasonable belief that the transaction, conversion, or withdrawal relates to a violation or attempted violation of state or federal law.
Second, the provider could act after receiving a qualified written request from a covered agency.
A covered agency would be a state or federal law-enforcement agency, including the Treasury Department. A qualified written request would have to:
- Come from an authorized official of a covered agency.
- Identify a specific wallet, address, account, or transaction reasonably suspected of being linked to illicit activity.
- Request action involving that specified target, including delaying a transaction, conversion, or withdrawal.
- Include a designated agency contact.
Specificity matters. The proposal does not describe a general request to watch “suspicious crypto activity.” It contemplates a written communication tied to an identifiable wallet, address, account, or transaction and a named point of contact.
That structure makes intelligence quality central to the process. Law enforcement must be able to identify the relevant target and communicate the request through an authorized official. The institution must be able to authenticate the request, locate the activity, assess the applicable facts, and document its response.
A temporary hold is not the same as a freeze, seizure, or recovery
The language used in digital-asset investigations can blur several legally distinct actions.
| Action | General function in the Section 10305 context |
| Temporary hold | Delays execution of a transaction, conversion, or withdrawal for a limited period |
| Freeze or block | Prevents assets from being transferred under an applicable legal or sanctions authority |
| Seizure | Government takes control of property through lawful process |
| Recovery | Assets are ultimately returned or otherwise restored through the applicable legal and operational process |
Section 10305 would not convert a voluntary temporary hold into a seizure.
The section separately states that a permitted payment stablecoin issuer must comply with a valid federal writ, process, order, rule, decree, command, or other requirement from a court of competent jurisdiction that requires payment stablecoins to be frozen or prevented from transfer, identifies the relevant stablecoins or accounts with reasonable particularity, and is subject to review or appeal as provided by law.
It also includes rules of construction. The section would not compel a covered person to freeze, seize, or block digital assets when that action is not otherwise required under existing law. It would not alter government enforcement authority, suspicious-activity reporting requirements, or lawful seizure and freeze authorities.
The practical distinction is straightforward:
A temporary hold may preserve time. Additional legal authority and investigative work may be required to preserve the assets beyond that period, seize them, or return them to a victim.
What conditions would apply to a temporary hold?
The proposed protection would depend on more than the provider’s initial suspicion.
Good faith and a qualifying basis
The provider would need to act in good faith and either have a reasonable belief that the activity relates to a violation or attempted violation of law or have received a qualified written request.
Customer notification
The provider generally would need to make reasonable efforts to notify the affected customer.
The text also recognizes circumstances in which notification may not be appropriate. A provider could reasonably determine that notice would impede actual or potential law-enforcement efforts, or a qualified written request could ask the provider not to attempt notification.
Government notification
When the provider has not acted after receiving a qualified written request, it would need to notify an appropriate state or federal law-enforcement agency or the Federal Trade Commission as soon as reasonably practicable.
Documentation
The provider would need to retain documentation of the basis for the temporary hold for three years. It would also need to make that documentation available upon request to a covered agency or the Federal Trade Commission.
These conditions show that Section 10305 is not merely about allowing a system to stop a transaction after a risk alert. It is about creating a defensible decision process involving reasonable grounds, communication, escalation, and records.
A practical scenario
Consider a financial institution that detects a proposed withdrawal to a digital-asset address associated with suspected fraud.
Its transaction-monitoring and blockchain analytics systems identify unusual activity. At approximately the same time, a local detective receives a complaint from a victim who was induced to transfer funds as part of an investment scam. Another agency may already have a case involving the same wallet cluster.
Several things must happen for that information to become useful.
- The institution must identify the specific transaction, address, or account.
- Its investigators must evaluate the signal and determine whether there is a reasonable basis for concern.
- The detective must preserve transaction details and communicate through an authorized, verifiable channel.
- The institution must be able to authenticate any written request and reach the designated agency contact.
- Investigators should determine whether related cases or agencies exist.
- The institution must apply its legal, compliance, customer-notification, escalation, and documentation procedures.
- Law enforcement may need to obtain additional legal process before the temporary window closes.
If the victim report reaches the institution after the assets have moved, the intelligence may still support tracing and investigation. It may no longer support immediate intervention at that provider.
If the information arrives quickly but cannot be verified, the institution may lose time determining whether the source and claim are legitimate.
If several agencies are investigating the same network without knowing it, separate requests may create confusion, duplication, or incomplete context.
The practical objective is not simply “share more.” It is to connect verified information to the right organization soon enough to support an authorized and documented action.
Where Deconflict fits
Deconflict serves law enforcement and financial institutions by helping them connect verified investigative context across organizational boundaries.
For law enforcement, access is free. Investigators can use the platform to improve crypto case deconfliction and identify potential overlap before duplicating work or approaching an institution with incomplete context.
For financial institutions, Deconflict provides institutional capabilities designed to support Verified Intelligence and coordination with authorized partners.
Deconflict should not be confused with the authority described in Section 10305. The platform does not independently determine that a transaction violates the law, direct an institution to place a hold, replace an institution’s transaction-monitoring or compliance systems, or substitute for legal process.
The connection is more fundamental:
Section 10305 would create a potential window for action. Deconflict helps law enforcement and financial institutions improve the quality, verification, and coordination of the intelligence that may need to move through that window.
