Senate Ag Committee To Release Latest Crypto Market Structure Bill Draft Today

bitcoinistPublished on 2026-01-21Last updated on 2026-01-21

Abstract

The Senate Agriculture Committee is releasing its own draft of a crypto market structure bill today after the Banking Committee delayed its markup. This action comes ahead of a crucial vote next week. The delay was partly due to Coinbase withdrawing its support for the bill. The company is now under pressure to negotiate a deal on yield with banking leaders, while Binance and Ripple have expressed support. Coinbase CEO Brian Armstrong raised concerns that the bill could ban tokenized equities, restrict DeFi, expand government data access, and shift regulatory power to the SEC. A White House official warned that the delay could lead to stricter future regulations. Former President Trump expressed optimism, hoping to sign the bill soon to unlock "new pathways for financial freedom."

The Senate Banking Committee delayed the anticipated markup of its crypto market structure bill draft, prompting the Agriculture Committee to take action. The Agriculture Committee is set to release its own version of the bill’s draft today, just ahead of a crucial vote scheduled for next week.

Coinbase Faces Pressure To Negotiate Yield Deal

Eleanor Terret, a reporter with Crypto In America who has been closely monitoring congressional developments regarding cryptocurrency, reported that staffers from the Banking Committee hope a successful bipartisan agreement spearheaded by their counterparts in the Ag Committee could facilitate a smoother markup process.

The responsibility now largely falls on Coinbase—whose sudden withdrawal of support for the bill contributed to the halt in the markup process—to negotiate a deal with banking leaders on yield. At the same time, Binance and Ripple’s leadership have expressed support for the bill’s latest version during their appearance in Davos.

Coinbase CEO Brian Armstrong expressed his apprehensions regarding the implications of the bill last week. He raised concerns that the legislation could prohibit tokenized equities, impose restrictions on decentralized finance (DeFi), and expand government access to financial data, potentially sacrificing individual privacy.

The executive also cautioned that the bill could shift regulatory power from the Commodity Futures Trading Commission (CFTC) to the Securities and Exchange Commission (SEC), which may eliminate stablecoin rewards and hinder competition within the crypto sector.

President Trump Optimistic About Crypto Market Bill

Adding to the tension, Patrick Witt, Executive Director of the White House Crypto Council, took to social media late Tuesday to criticize Coinbase, warning that the delay in the market structure bill could invite stricter regulations under an administration less favorable to digital assets.

Witt’s remarks seemed to corroborate reports from Crypto In America indicating that the White House is frustrated with Coinbase’s withdrawal, which has contributed to the legislative stall.

In a related note, President Donald Trump acknowledged the ongoing efforts surrounding the market structure legislation during his speech in Davos on Wednesday.

He expressed hope that Congress would finalize the bill soon, stating, “Congress is working very hard on crypto market structure legislation, which I hope to sign very soon, unlocking new pathways for Americans to reach financial freedom.”

The 1-D chart shows this week’s drop in the total crypto market capitalization below $3 trillion. Source: TOTAL on TradingView.com

Featured image from OpenArt, chart from TradingView.com

Related Questions

QWhy did the Senate Agriculture Committee decide to release its own version of the crypto market structure bill draft?

AThe Senate Agriculture Committee took action because the Senate Banking Committee delayed the anticipated markup of its crypto market structure bill draft.

QWhat specific concerns did Coinbase CEO Brian Armstrong raise about the proposed crypto market structure bill?

ABrian Armstrong expressed concerns that the bill could prohibit tokenized equities, impose restrictions on DeFi, expand government access to financial data, shift regulatory power from the CFTC to the SEC, eliminate stablecoin rewards, and hinder competition in the crypto sector.

QHow did the leadership of Binance and Ripple react to the latest version of the bill during their appearance in Davos?

AThe leadership of Binance and Ripple expressed support for the bill's latest version during their appearance in Davos.

QWhat warning did Patrick Witt, Executive Director of the White House Crypto Council, issue regarding the delay of the market structure bill?

APatrick Witt warned that the delay in the market structure bill could invite stricter regulations under an administration that is less favorable to digital assets.

QWhat did President Donald Trump say about the crypto market structure legislation in his Davos speech?

APresident Trump acknowledged the congressional efforts, expressed hope that Congress would finalize the bill soon, and stated he hoped to sign it to unlock new pathways for Americans to reach financial freedom.

Related Reads

It Took Me a Year to See the Bitter Truth About Agent Payments

After a year building infrastructure for the Agent economy, engaging with major players like Stripe, Visa, and Coinbase, the author shares a sobering analysis of the current state of Agent payments. The core finding is a stark lack of genuine, immediate demand across most envisioned use cases. The article breaks down four key market segments: 1. **Agent-to-Merchant (Consumer Shopping):** For most product categories (e.g., clothing, electronics), conversational AI shopping is a step backwards from visual e-commerce interfaces. While agents excel at understanding needs, they can't replace side-by-side product comparison. Real merchant interest is defensive "Agent Engine Optimization," not driven by current customer demand. Potential exists for high-frequency, low-decision purchases (like food delivery) or navigating complex store UIs, but these require massive B2C distribution channels dominated by giants like Amazon. 2. **Agent-to-API (Developer Services):** Developers already have subscriptions and billing relationships for APIs (compute, data). Prepaid balances solve micro-payment issues for low transaction volumes. A deeper structural problem is that major SaaS vendors' business models rely on enterprise contracts, resisting granular pay-per-call pricing. While protocols like MPP and x402 serve the long tail of niche services, this market is small and developers are historically low-willingness-to-pay. 3. **Agent-to-Agent:** This remains largely theoretical with minimal transaction volume. While it represents a long-term bet on a fundamentally new transaction infrastructure (sub-second, micro-penny to million-dollar, multi-party settlements), it does not constitute a present market. 4. **Agent-to-Finance:** This is the only category with existing, paying demand. Integrating AI into financial workflows (trading, portfolio management) is a natural evolution and enables new capabilities like autonomous rebalancing. However, competition favors established, regulated institutions. The "real problem" is not moving money between agents, but the broader challenge of **coordination**—orchestrating work between agents and humans, verifying outcomes, and settling results. Payment is just one component of settlement, which is itself part of coordination. Companies that solve the coordination layer will subsume payment, not the other way around. While well-funded incumbents build defensively for a long-term future, startups must find where the market is today—which, for the author's team, lies outside these four categories in an area of real, growing, and underserved activity.

marsbit12m ago

It Took Me a Year to See the Bitter Truth About Agent Payments

marsbit12m ago

It Took Me a Year to See the Hard Truth About Agent Payments

**Title: It Took Me a Year to See the Hard Truth About Agent Payments** Over the past year, I've worked on infrastructure for the Agent economy, engaging with major players like Stripe, Visa, Coinbase, and numerous startups. The findings reveal a stark reality: genuine, widespread demand for Agent-based payments does not yet exist. **Key Observations:** * **Agent-to-Merchant (Shopping):** The user experience for AI shopping often falls short, especially for visual product discovery. While AI excels at understanding needs, conversational interfaces can't yet replace browsing and comparing multiple products visually. Current merchant interest is largely defensive ("Agent Engine Optimization") for a future that hasn't arrived. High-frequency, low-friction purchases (like food delivery) are potential fits, but lack open APIs and face high AI inference costs. Simpler, more affordable, or cross-language interactions for complex UIs are a niche opportunity but require massive consumer distribution to scale. * **Agent-to-API (Developer Tools):** Developer payment needs for APIs (computing, data, models) are already met through subscriptions and prepaid credits. The core challenge is not payment friction but supplier economics: most large SaaS providers prefer enterprise contracts over micropayments for API calls. Protocols like MPP and x402 suit the long-tail of smaller services but cater to a developer market historically reluctant to pay for these tools. Major infrastructure needs at the top of the stack are already being addressed. * **Agent-to-Agent (Machine Commerce):** This is a long-term vision with almost no current transaction volume. While a future with high-speed, high-frequency, multi-party machine-to-machine transactions would require novel infrastructure, it remains theoretical. The market is not here yet. * **Agent-to-Finance:** This is the only category with clear, present demand. Financial professionals and DeFi users already pay for tools, and AI augmentation is a natural evolution. Autonomous AI agents can enable entirely new financial strategies. However, competition is fierce from established, regulated incumbents who can more easily layer AI onto their existing products. **The Core Insight:** Companies, especially giants with long time horizons, are building defensively for a potential future of mass machine commerce. For them, early investment is a low-cost hedge. For startups, the current market reality is different. The primary challenge isn't just moving money between agents (payments). The larger, unsolved problem is **orchestration** – coordinating work between agents and humans, verifying outcomes, and then settling. Payment is just a part of settlement, which is just a part of orchestration. Companies that solve the orchestration problem will subsume payments, not the other way around. After a year of building, we see the real, growing, and underserved market opportunity lies in this broader domain of orchestration.

链捕手36m ago

It Took Me a Year to See the Hard Truth About Agent Payments

链捕手36m ago

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.

marsbit1h ago

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

marsbit1h ago

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.

marsbit2h ago

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

marsbit2h ago

Trading

Spot
Futures
活动图片