In an April 10 court filing, both parties requested that the case be held in abeyance for 60 days, citing ongoing settlement discussions.

“An abeyance would conserve judicial and party resources while the parties continue to pursue a negotiated resolution of this matter,” the filing stated.

Ripple CEO’s March Remarks Foreshadow Pause in SEC Case Proceedings

The pause in proceedings follows Ripple CEO Brad Garlinghouse’s recent remarks in March, suggesting the case was nearing its end.

The timing of the filing has fueled speculation that the SEC may be waiting for its incoming chair, Paul Atkins, to officially assume office before finalizing a settlement.

Ripple defense attorney James Filan confirmed that the abeyance request overrides the previous April 16 deadline for Ripple to respond to a brief the SEC filed in January.

“The settlement is awaiting commission approval. No brief will be filed on April 16,” Filan stated on X.

The SEC’s willingness to pause appeals has been interpreted by some legal commentators as a signal that the agency may be preparing to drop the case under new leadership.

One community member noted that a settlement led by Atkins would mark a “huge win” and potentially reset the SEC’s approach to crypto regulation.

Atkins was confirmed by the Senate as SEC Chair on April 9, but it remains uncertain when he will be officially sworn in.

For context, former SEC Chair Gary Gensler assumed office three days after his confirmation in 2021, suggesting Atkins could take over as soon as April 12.

The XRP case, which began in December 2020, has been one of the most closely watched legal battles in the crypto industry.

Trump-Era Shift Signals SEC Reassessment of Crypto Regulation

The SEC’s recent shift in tone under President Donald Trump reflects a broader effort to reevaluate the agency’s approach to digital assets.

SEC’s Mark Uyeda announced on April 5 that, in line with Trump’s deregulation agenda and guidance from the Department of Government Efficiency (DOGE) led by Elon Musk, the SEC is reviewing seven staff-issued statements—five of which concern cryptocurrencies.

Among those under review is a 2019 framework from the SEC’s FinHub that assessed when digital asset sales could qualify as investment contracts under the Howey test.

Other documents being reconsidered include statements from the Divisions of Investment Management, Corporation Finance, and Examinations, particularly those addressing risks tied to Bitcoin futures, crypto custody, and industry-wide bankruptcies during 2022.

As reported, the SEC announced new guidelines on April 4, stating that certain fiat-backed stablecoins will be classified as “non-securities,” thereby exempting them from transaction reporting requirements.

The post Ripple and SEC Request 60-Day Pause on Appeals, Hinting at Possible Settlement appeared first on Cryptonews.

I have 3 Taproot addresses: one is 50 btc, one is RECEPIENT, and the other is for change

sender bcrt1p7d90fjh4k2uu7jjzw6hev8nnak2cultvcyjaj5zum696eqpwfausw79xuk
wif cULydXkHkv3h1jH7yVaGcNCvWHzbVsDiAxW76Mc8QrSqzNPU2sUG
recipient bcrt1p725t652m53g7j87n2ypm3x9pdl9f88c4c2hjyvymq78qhrc6tpsq5wp62r
change bcrt1pj5fle7sshyr04yershteu745zs2peguum7z575rydshtscmdjysq4eus02

I’m trying to send one BTC and create a raw transaction for the spend type of keypath

This is at the sender’s hands:

(
    {
        "txid": "6ee6185784989263847ebd3d2aadb83bdbe80ed0011821085975226ae994e259",
        "vout": 0,
        "address": "bcrt1p7d90fjh4k2uu7jjzw6hev8nnak2cultvcyjaj5zum696eqpwfausw79xuk",
        "label": "",
        "scriptPubKey": "5120f34af4caf5b2b9cf4a4276af961e73ed958e7d6cc125d9505cde8bac802e4f79",
        "amount": 50,
        "confirmations": 101,
        "spendable": true,
        "solvable": true,
        "desc": "rawtr(f34af4caf5b2b9cf4a4276af961e73ed958e7d6cc125d9505cde8bac802e4f79)#qrffuhzp",
        "parent_descs": (
            "addr(bcrt1p7d90fjh4k2uu7jjzw6hev8nnak2cultvcyjaj5zum696eqpwfausw79xuk)#cx2kp4mn"
        ),
        "safe": true
    }
)

1. Create a transaction object

     (CREATE TRANSACTION START)
    -- Amount to send (sats): 100000000
    -- Fee (sats): 1000000
    -- Get UTXO id for pay: 6ee6185784989263847ebd3d2aadb83bdbe80ed0011821085975226ae994e259
    -- Reversed UTXO id: 59e294e96a22755908211801d00ee8db3bb8ad2a3dbd7e84639298845718e66e
    -- Full generated tx: {
        "version":2,
        "inputs":
            ({
                "txid":"59e294e96a22755908211801d00ee8db3bb8ad2a3dbd7e84639298845718e66e",
                "vout":0,
                "scriptSig":"",
                "sequence":4294967295
            }),
        "outputs":({
                "value":100000000,
                "scriptPubKey":"51209545ea8add228f48fe9a881dc4c50b7e549cf8ae15791184d83c705c78d2c300"
            },{
                "value":4899000000,
                "scriptPubKey":"5120a89fe7d085c837d4991c2ebcf3d5a0a0a0e51ce6fc2a7a83236175c31b6c8900"
            }),
        "locktime":0}
    (CREATE TRANSACTION END)

2. Sign and Serialization

(SIGN AND SERIALIZE TRANSACTION START)
(INPUT 0)
-- txid (32 bytes): 59e294e96a22755908211801d00ee8db3bb8ad2a3dbd7e84639298845718e66e
-- Vout (4 bytes LE32): 00000000
-- ScriptSigLength (1 bytes Compact size): 00
-- ScriptSig (0 bytes):
-- Sequence (4 bytes LE32): ffffffff
-- (SIGHASH FOR 0 INPUT START)
---- Version (4 bytes LE32): 02000000
---- LockTime (4 bytes LE32): 00000000
---- InputIdx (4 bytes LE32): 00000000
---- SighashTypeBuf (1 bytes): 00
---- (HASH PREVOUTS (txid + LE32(vout)) START)
------ Prevout for 0 input (36 bytes): 59e294e96a22755908211801d00ee8db3bb8ad2a3dbd7e84639298845718e66e00000000
---- (HASH PREVOUTS END)
---- Finally hashPrevouts (32 bytes): 35bb28a690e32f668589a79a1b4f7ba82c00c08fe39b29672e861e90526991a9
---- (HASH AMOUNTS (LE64(amount))) START)
------ Amount for 0 input (8 bytes LE64): 3200000000000000
---- (HASH AMOUNTS END)
---- Finally hashAmounts (32 bytes): 0cbbab9d99fb661a1686f17ccaaf8a9d069aa8cb755925045a1d049c060b9e67
---- (HASH SCRIPT PUB KEYS (OP_1 + PUSH_32 + pubKeyHash) START)
------ ScriptPubKey for 0 input (34 bytes): 51209a57a657ad95ce7a5213b57cb0f39f6cac73eb66092eca82e6f45d6401727bc8
---- (HASH SCRIPT PUB KEYS END)
---- Finally hashScriptPubKeys (32 bytes): 96d403e277844293f22ba2b1914d646d8353adbe2c49a22a7f421a8c97221eaa
---- (HASH SEQUENCES (LE32(sequence)) START)
------ Sequence for 0 input (4 bytes LE32): ffffffff
---- (HASH SEQUENCES END)
---- Finally hashSequences (32 bytes): ad95131bc0b799c0b1af477fb14fcf26a6a9f76079e48bf090acb7e8367bfd0e
---- (HASH OUTPUTS (LE64(amount), CompactSize(size), scriptPubKey) START)
------ Amount of 0 out (8 bytes LE64): 00e1f50500000000
------ ScriptPubKey of 0 out (34 bytes): 51209545ea8add228f48fe9a881dc4c50b7e549cf8ae15791184d83c705c78d2c300
------ Size of 0 out (1 bytes CompactSize): 22
------ Output of 0 out (43 bytes): 00e1f505000000002251209545ea8add228f48fe9a881dc4c50b7e549cf8ae15791184d83c705c78d2c300
------ Amount of 1 out (8 bytes LE64): c0ce002401000000
------ ScriptPubKey of 1 out (34 bytes): 5120a89fe7d085c837d4991c2ebcf3d5a0a0a0e51ce6fc2a7a83236175c31b6c8900
------ Size of 1 out (1 bytes CompactSize): 22
------ Output of 1 out (43 bytes): c0ce002401000000225120a89fe7d085c837d4991c2ebcf3d5a0a0a0e51ce6fc2a7a83236175c31b6c8900
---- (HASH OUTPUTS END)
---- Finally hashOutputs (32 bytes): c74c74b357372c390436f57e6046707b88dc74a7199e9194922818188192de44
---- Preimage (174 bytes): 02000000000000000035bb28a690e32f668589a79a1b4f7ba82c00c08fe39b29672e861e90526991a90cbbab9d99fb661a1686f17ccaaf8a9d069aa8cb755925045a1d049c060b9e6796d403e277844293f22ba2b1914d646d8353adbe2c49a22a7f421a8c97221eaaad95131bc0b799c0b1af477fb14fcf26a6a9f76079e48bf090acb7e8367bfd0ec74c74b357372c390436f57e6046707b88dc74a7199e9194922818188192de440000000000
---- TaggedHash (32 bytes): 7f73f0e9137223806b5c6c4f157f30ed439949decb84b4ab1eff249fa61692c1
-- (SIGHASH FOR 0 INPUT END)
-- Sighash (32 bytes): 7f73f0e9137223806b5c6c4f157f30ed439949decb84b4ab1eff249fa61692c1
-- SignatureObject (64 bytes): 4227542a9daebfbf518e12b016f09f5f7feaae42bdf5874039dfd1ff7ec66b63b625e27be13a04b3d58c81891aca8908cd5ca548cfc3f080fd2d0bcfc0045138
-- Pubkey (32 bytes): f34af4caf5b2b9cf4a4276af961e73ed958e7d6cc125d9505cde8bac802e4f79
-- VALID? true
-- Witness count for 0 input (1 bytes Compact Size): 01
-- Signature len for 0 input (1 bytes Compact Size): 40
-- Signature for 0 input (64 bytes): 4227542a9daebfbf518e12b016f09f5f7feaae42bdf5874039dfd1ff7ec66b63b625e27be13a04b3d58c81891aca8908cd5ca548cfc3f080fd2d0bcfc0045138
(OUTPUT 0)
-- Value (8 bytes LE64): 00e1f50500000000
-- ScriptPubKey (34 bytes): 51209545ea8add228f48fe9a881dc4c50b7e549cf8ae15791184d83c705c78d2c300
-- ScriptPubKeySize (1 bytes Compact size): 22
(OUTPUT 1)
-- Value (8 bytes LE64): c0ce002401000000
-- ScriptPubKey (34 bytes): 5120a89fe7d085c837d4991c2ebcf3d5a0a0a0e51ce6fc2a7a83236175c31b6c8900
-- ScriptPubKeySize (1 bytes Compact size): 22
Locktime (4 bytes LE32): 00000000
Marker (1 bytes): 00
Flag (1 bytes): 01
Version (4 bytes LE32): 02000000
InputsLen (1 bytes Compact Size): 01
OutputsLen (1 bytes Compact Size): 02
Finally rawTx (205 bytes): 0200000000010159e294e96a22755908211801d00ee8db3bb8ad2a3dbd7e84639298845718e66e0000000000ffffffff0200e1f505000000002251209545ea8add228f48fe9a881dc4c50b7e549cf8ae15791184d83c705c78d2c300c0ce002401000000225120a89fe7d085c837d4991c2ebcf3d5a0a0a0e51ce6fc2a7a83236175c31b6c89000140eddd2049ece47dd2fea1fb2e5f9d0c475e32431a472c64d543160097359f266f13c3a409de8366d09b105741ecaee1cfac6542ed1e084cee58310d82da28775000000000
(SIGN AND SERIALIZE TRANSACTION END)

And in the end I got

Error creating RPC request: Required script-verify-flag-failed (invalid schnorr signature)

However, the transaction structure is valid, it is both a signature and a witness.

{
  "version": "02000000",
  "marker": "00",
  "flag": "01",
  "inputcount": "01",
  "inputs": (
    {
      "txid": "59e294e96a22755908211801d00ee8db3bb8ad2a3dbd7e84639298845718e66e",
      "vout": "00000000",
      "scriptsigsize": "00",
      "scriptsig": "",
      "sequence": "ffffffff"
    }
  ),
  "outputcount": "02",
  "outputs": (
    {
      "amount": "00e1f50500000000",
      "scriptpubkeysize": "22",
      "scriptpubkey": "51209545ea8add228f48fe9a881dc4c50b7e549cf8ae15791184d83c705c78d2c300"
    },
    {
      "amount": "c0ce002401000000",
      "scriptpubkeysize": "22",
      "scriptpubkey": "5120a89fe7d085c837d4991c2ebcf3d5a0a0a0e51ce6fc2a7a83236175c31b6c8900"
    }
  ),
  "witness": (
    {
      "stackitems": "01",
      "0": {
        "size": "40",
        "item": "4227542a9daebfbf518e12b016f09f5f7feaae42bdf5874039dfd1ff7ec66b63b625e27be13a04b3d58c81891aca8908cd5ca548cfc3f080fd2d0bcfc0045138"
      }
    }
  ),
  "locktime": "00000000"
}

Please help. Could there be something wrong with your bytes, data, or order? thank you very much!

Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure

The US Securities and Exchange Commission (SEC) and Gemini have requested a pause on the watchdog’s lawsuit against the crypto exchange over its Earn program. This move follows the regulator’s efforts to resolve most major crypto litigations outside of the Court.

SEC And Gemini Ask For Pause

On April 1, the US SEC and crypto exchange Gemini sent a letter to New York federal court judge Edgardo Ramos asking for a pause on the regulator’s lawsuit to “allow the parties to explore a potential resolution.”

In the joint motion to stay, the Commission and Gemini lawyers requested a 60-day stay of all the deadlines in the case to discuss the potential resolution, adding that it is in the Court’s best interest as it “would conserve judicial resources.”

SEC and Gemini request a 60-day stay. Source: Court Listener

The SEC sued Gemini in January 2023, arguing that the exchange and the crypto lending firm Genesis Global Capital had illegally offered unregistered securities through the crypto exchange’s Earn Program.

In February 2024, Gemini agreed to pay at least $1.1 billion to the Earn program customers as part of a settlement with the New York State Department Of Financial Services (NYDFS).

“In this case, the parties submit that it is in each of their interests to stay this matter while they consider a potential resolution and agree that no party or non-party would be prejudiced by a stay,” the Tuesday letter argues. The parties also proposed submitting a joint status report within 60 days after entry of the stay.

The End Of The SEC’s Crackdown?

Nearly two months ago, the SEC and Binance also sent a joint motion for a 60-day stay on their crypto litigation, arguing that a stay due to the creation of the SEC’s Crypto Task Force, led by SEC Commissioner Hester Peirce.

The two parties considered that the Task Force could “impact and facilitate the potential resolution of this case.” Journalist Eleanor Terret noted that after the request to pause the Binance case, more joint motions to stay would likely follow under the new crypto-friendly administration.

Since then, the Commission has dropped several crypto cases, including Coinbase, Kraken, and Consensys. Additionally, it had closed multiple open investigations with no enforcement action taken against Robinhood, Uniswap Labs, Crypto.com, and Gemini, among others.

As reported by Bitcoinist, Gemini co-founder Cameron Winklevoss revealed on February 26 that the SEC officially closed its investigation into the company without any enforcement action “699 days after the start of their investigation and 277 days after they sent us a Wells Notice.”

Winklevoss criticized the Commission’s tactics over the previous administration, affirming that, “While this marks another milestone to the end of the war on crypto, (…) it does little to make up for the damage this agency has done to us, our industry, and America.”

He concluded that this is just the beginning “towards ensuring this never happens again to the crypto industry or any other exciting, new frontier industry in the future.”

Total crypto market capitalization is at $2.74 trillion in the one-week chart. Source: TOTAL on TradingView

Featured Image from Unsplash.com, Chart from TradingView.com

Editorial Process for bitcoinist is centered on delivering thoroughly researched, accurate, and unbiased content. We uphold strict sourcing standards, and each page undergoes diligent review by our team of top technology experts and seasoned editors. This process ensures the integrity, relevance, and value of our content for our readers.

Coinbase’s legal representatives say the U.S. Federal Deposit Insurance Corporation (FDIC) hasn’t been cooperating with Freedom of Information Act (FOIA) requests.

Coinbase has been attempting to leverage FOIA to uncover instances of the FDIC asking banks to freeze crypto services, known as “pause letters,” but the top US crypto exchange says the regulator hasn’t been complying with its information requests.

Paul Grewal, Coinbase’s chief legal officer, claims the pause letters were part of “Operation Choke Point 2.0,” an alleged attempt by Biden Administration government regulators to stifle the crypto industry.

The exchange hired the law firm History Associates, which filed a motion in January asking a federal court to intervene.

The following month, the court paused the FDIC’s deadline to respond to History Associates’ amended FOIA complaint “so that the parties could engage in a biweekly, informal information-sharing process,” according to the law firm.

Coinbase’s legal representation has requested information regarding the FDIC’s response to its FOIA requests, specifically concerning the regulator’s policy or practice of “failing to conduct complete searches of all relevant databases and failing to take adequate steps to preserve responsive documents.”

In a new motion filed this week, History Associates now says the FDIC is “unwilling to cooperate” with these FOIA requests.

“The only viable path forward is for the case to resume and proceed to litigation of the merits.”

Last month, the FDIC released redacted documents related to its supervision of crypto-related activities, which include pause letters sent to 24 banks as well as communications and records involving other regulated institutions.

House Oversight Committee Chairman James Comer (R-KY) subsequently sent a letter to FDIC Acting Chairman Travis Hill requesting unredacted copies of the documents.

Follow us on X, Facebook and Telegram

Don’t Miss a Beat – Subscribe to get email alerts delivered directly to your inbox

Check Price Action

Surf The Daily Hodl Mix

&nbsp

Disclaimer: Opinions expressed at The Daily Hodl are not investment advice. Investors should do their due diligence before making any high-risk investments in Bitcoin, cryptocurrency or digital assets. Please be advised that your transfers and trades are at your own risk, and any losses you may incur are your responsibility. The Daily Hodl does not recommend the buying or selling of any cryptocurrencies or digital assets, nor is The Daily Hodl an investment advisor. Please note that The Daily Hodl participates in affiliate marketing.

Generated Image: Midjourney

The US Securities and Exchange Commission (SEC) and global crypto exchange Binance have filed a joint motion to halt the ongoing legal battle for two months, citing the ongoing changes in the regulatory agency.

SEC Vs Binance To Take A Pause

On Tuesday, FOX Business journalist Eleanor Terrett reported that the US SEC and Binance had requested a 60-day pause on the regulator’s case against the global crypto exchange. The joint motion, dated February 10, 2025, argues that the litigation warrants a stay due to the creation of the SEC’s Crypto Task Force, led by SEC Commissioner Hester Peirce.

The two parties consider that the Task Force, created by the Commission’s acting chair, Mark Uyeda, to help develop a regulatory framework for crypto assets, could “impact and facilitate the potential resolution of this case.”

SEC and Binance's joint motion to stay. Source: Court Listener

In June 2023, the SEC filed a lawsuit against the crypto exchange, arguing that Binance, its US affiliate, BAM Trading Services Inc., and the exchange’s former CEO, Changpeng Zhao, offered the sale of unregistered securities and had operated illegally in the US.

The US watchdog argued that the lack of registration enabled Binance to allegedly run an unregulated trading platform that exposed US investors to significant risks and misled customers about the security and regulatory oversight of their assets.

The exchange filed a motion to dismiss the lawsuit, alleging that the SEC had exceeded its legal authority, but Judge Amy Berman Jackson ruled against the motion in July 2024. Nonetheless, the judge granted Binance a partial victory after rejecting some of the Commission’s main claims.

The court ruling dismissed the claims related to the secondary market sales of BNB tokens, the classification of Binance USD (BUSD) stablecoin as an investment contract, and “the assertion that crypto tokens themselves are securities.”

Despite this, Judge Jackson allowed the case to proceed with claims about the exchange’s staking program, BNB’s Initial Coin Offering (ICO) sales, and anti-fraud violations of the Securities Act.

More Joint Motions To Come?

According to the Monday court document, the regulatory agency proposed a brief stay with Binance, which the crypto exchange agreed to, considering it “appropriate and in the interest of judicial economy.”

Moreover, the joint motion affirms the stay could “save the parties resources” if an early resolution is reached, removing the need to continue the merits discovery.

Further, this brief stay will promote the efficient use of the Court’s resources, as a resolution would obviate the need for the Court to resolve the Defendants’ pending Motions to Dismiss the Amended Complaint.

Following the 60-day stay, Binance and the SEC plan to submit a joint status report, including whether a continuation of the stay is warranted.

Terret alleges that the joint stay motion is the first requested pause on crypto litigation in the courts since Uyeda became acting chair on January 20. The journalist added that she expects to see other non-fraud causes, such as Ripple, Coinbase, and Kraken, follow suit and request a motion stay.

Binance Coin (BNB) trades at $634.76 in the one-week chart. Source: BNBUSDT on TradingView

Featured Image from Unsplash.com, Chart from TradingView.com