U.S. government confirms it did not sell Bitcoin seized from Samourai Wallet

ambcryptoОпубликовано 2026-01-16Обновлено 2026-01-16

Введение

The U.S. government has not sold the Bitcoin seized from Samourai Wallet, according to a confirmation from the Department of Justice (DOJ). The statement refutes earlier claims that the assets were liquidated, which would have violated Executive Order 14233 requiring forfeited Bitcoin to be retained. The DOJ clarified that the Bitcoin remains on the government’s balance sheet as part of a Strategic Bitcoin Reserve. On-chain data from Arkham supports this, showing no significant outflows from known U.S. government wallets. The confusion stemmed from historical precedent where seized Bitcoin was auctioned, but current policy under the executive order mandates holding such assets. The U.S. government continues to hold over 328,000 BTC, valued at more than $31 billion.

The U.S. government has confirmed that it did not sell Bitcoin seized from Samourai Wallet. The confirmation addresses earlier claims that the assets had been liquidated in violation of federal policy governing forfeited digital assets.

U.S. DOJ clarification addresses liquidation claims

Patrick Witt, Executive Director of the President’s Council of Advisors for Digital Assets, said the Department of Justice [DOJ] has confirmed that the seized Bitcoin “have not been liquidated and will not be liquidated”.

He added that the assets will remain on the U.S. government’s balance sheet as part of the Strategic Bitcoin Reserve.

The clarification follows reports earlier this month suggesting that prosecutors in the Southern District of New York [SDNY] had sold Bitcoin forfeited by developers associated with Samourai Wallet.

The alleged sale potentially contradicts Executive Order 14233, which mandates that forfeited Bitcoin be retained rather than sold.

According to Witt, the DOJ confirmed that the forfeited digital assets remain in the U.S. government’s possession and comply with the executive order. The statement directly counters claims that the Bitcoin had already been liquidated following the Samourai plea agreement.

The DOJ has not publicly detailed operational handling of the assets beyond confirming they remain on the government’s balance sheet.

However, the confirmation removes uncertainty around whether the seizure resulted in market sales or contributed to recent Bitcoin price movements.

On-chain data aligns with U.S. government statement

Independent blockchain data from Arkham supports the U.S. DOJ’s position. Publicly tracked wallets associated with U.S. government holdings show no material reduction in Bitcoin balances consistent with a sale linked to the Samourai case.

As of mid-January, on-chain analytics indicate the U.S. government continues to hold more than 328,000 BTC, valued at over $31 billion, alongside smaller balances of ether and stablecoins. No abnormal outflows tied to the Samourai forfeiture have been observed.

Why the confusion emerged

Historically, the U.S. government has sold seized Bitcoin through public auctions, particularly in earlier cases such as Silk Road.

That precedent shaped market expectations and led to the assumption that newly forfeited Bitcoin would also be liquidated.

However, Executive Order 14233 represents a policy shift, requiring certain seized Bitcoin to be retained as a strategic asset rather than sold.

The Samourai case appears to fall under this updated framework, marking a departure from earlier forfeiture practices.

For now, the DOJ’s confirmation closes the question of whether Samourai-related Bitcoin entered the market.


Final Thoughts

  • The DOJ’s confirmation resolves claims that Samourai Wallet–related Bitcoin had been liquidated, reinforcing that the assets remain held under current federal policy.
  • The episode highlights how legacy expectations around seized Bitcoin sales continue to clash with the U.S. government’s evolving approach.

Связанные с этим вопросы

QWhat did the U.S. government confirm regarding the Bitcoin seized from Samourai Wallet?

AThe U.S. government confirmed that it did not sell the Bitcoin seized from Samourai Wallet and that the assets will remain on the government's balance sheet as part of the Strategic Bitcoin Reserve.

QWhich executive order mandates that forfeited Bitcoin be retained rather than sold?

AExecutive Order 14233 mandates that forfeited Bitcoin be retained rather than sold.

QHow much Bitcoin does the U.S. government currently hold according to on-chain analytics as of mid-January?

AAs of mid-January, the U.S. government holds more than 328,000 BTC, valued at over $31 billion.

QWhy did confusion emerge about the liquidation of the seized Bitcoin from Samourai Wallet?

AConfusion emerged because historically the U.S. government sold seized Bitcoin through public auctions, which shaped market expectations, but Executive Order 14233 represents a policy shift requiring certain Bitcoin to be retained as a strategic asset.

QWhat role did on-chain data from Arkham play in this situation?

AIndependent blockchain data from Arkham supported the U.S. DOJ's position by showing no material reduction in Bitcoin balances in publicly tracked wallets associated with U.S. government holdings, consistent with no sale linked to the Samourai case.

Похожее

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

A researcher discovered a critical "infinite mint" vulnerability in the Zcash cryptocurrency's Orchard protocol using Claude Opus 4.8, leading to a swift fix but also a 50% market drop, erasing billions in value. This incident highlights a new era where powerful, accessible AI models are dramatically lowering the barrier to finding software vulnerabilities. Previously, the security community feared specialized models like Claude Mythos Preview, capable of finding decades-old zero-day exploits. The Zcash case, however, involved a publicly available, general-purpose model. This shift makes advanced security auditing—and attack capabilities—accessible to far more people, not just experts. The mass democratization of vulnerability discovery brings a dual challenge: a flood of low-quality, AI-generated false reports that overwhelm maintainers, and the real, rapid uncovering of deep, dangerous bugs. Open-source projects, often understaffed and unfunded, are particularly vulnerable to this "attention DDoS." The article cites examples like curl shutting down its bug bounty program due to the unsustainable workload. Our perceived digital safety has often been luck, relying on the high cost and effort required to find deeply hidden flaws in complex systems, as seen with historical vulnerabilities like Heartbleed or Baron Samedit. AI changes this cost structure, effectively "mass-producing flashlights" to illuminate every corner of our codebase. While large companies operate extensive security chains involving external white-hat hackers and massive defensive operations, the global cybersecurity workforce faces a severe shortage, especially of experienced personnel capable of analyzing complex threats and coordinating fixes. The core dilemma emerges: AI makes *finding* bugs cheap and scalable, but *fixing* them remains a slow, expensive, and human-intensive process. The article concludes that AI won't destroy the internet but acts as a bright light, revealing that our digital existence is not inherently secure but is precariously maintained by ongoing human effort. The true cost in the AI era may not be discovery, but whether there will be enough people left willing and able to do the hard work of repair.

marsbit5 мин. назад

Claude Opus 4.8 Finds a $4.5 Billion Bug: The AI Era is Mass-Producing Hackers

marsbit5 мин. назад

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

"Codex Goal Mode: How to Make AI Work Continuously Toward a Specific Goal" OpenAI's Codex "goal mode" (/goal) transforms the AI from a reactive code assistant into a proactive execution agent capable of working autonomously for hours or even days to achieve a defined objective. To maximize its effectiveness, follow these key principles: 1. **Define Clear, Verifiable Exit Criteria:** The goal prompt should be a concise, measurable success condition, not a lengthy specification. Use quantifiable metrics like "reduce build time by 30%" or "achieve 100% test parity." 2. **Provide Initial Guidance and Tools:** Direct Codex toward likely problem areas and specify available tools (e.g., browsers, testing environments) to prevent it from exploring unproductive paths. 3. **Enable Progress Measurement:** Equip Codex with ways to track advancement, such as creating comparison tools for visual tasks or evaluation sets, ensuring it can gauge its own progress. 4. **Use a Realistic Execution Environment:** For tasks like performance optimization, provide access to environments that closely mimic production (e.g., similar configs, databases) to yield valid results. 5. **Be Cautious with Visual Goals:** Avoid vague "pixel-perfect" instructions. Instead, supplement visual references with functional checklists or design system specifications to prevent Codex from obsessing over minor details. 6. **Implement Progress Tracking:** For long-running tasks, have Codex commit code to draft PRs, update progress documents, or send Slack updates to maintain visibility into its work. 7. **Review and Consolidate Results:** Once the goal is met, instruct Codex to review its work, clean up ineffective experimental code, and reflect on what strategies succeeded or failed. Ultimately, using goal mode shifts the developer's role from writing prompts to managing a persistent engineering agent—defining objectives, establishing metrics, configuring environments, and conducting final reviews.

marsbit1 ч. назад

Codex Goal Mode Usage Guide: How to Make AI Continuously Pursue a Specific Objective

marsbit1 ч. назад

From Ethereum to AI's 'CROPS': What Exactly Is This 'Slow Variable' That Vitalik Has Repeatedly Emphasized?

Recently, Vitalik Buterin has frequently emphasized the concept of "CROPS," first outlined in the Ethereum Foundation's March mandate as core principles guiding its focus: Censorship Resistance, Capture Resistance, Open Source, Privacy, and Security. CROPS represents Ethereum's commitment to providing foundational capabilities for user sovereignty—enabling asset ownership, identity expression, and coordination without reliance on centralized platforms or surrendering ultimate control. This framework is gaining new urgency with the rise of AI, particularly AI agents managing digital assets and automating transactions. While AI offers convenience, it risks centralizing user data, intent, and control if dependent on opaque, centralized services. Vitalik argues for "CROPS AI"—AI that is open, privacy-preserving, secure, and capable of local execution to maintain user agency. He highlights convergence between "CROPS Ethereum access layers" and "CROPS AI," such as using zero-knowledge proofs for private remote LLM calls and Ethereum RPC reads, ensuring users can access services without exposing sensitive information. Ultimately, CROPS is not just an abstract ideal but a practical guide for Ethereum's development and AI integration. It addresses the critical long-term question: as digital systems grow more powerful, how can users retain control over their privacy, assets, and autonomy? In an AI-driven era, these principles may define Ethereum's enduring value—prioritizing verifiable, secure, and user-centric design over short-term optimizations like speed and cost alone.

marsbit1 ч. назад

From Ethereum to AI's 'CROPS': What Exactly Is This 'Slow Variable' That Vitalik Has Repeatedly Emphasized?

marsbit1 ч. назад

Торговля

Спот
Фьючерсы
活动图片