Morgan explained that Judge Torres’ role in the case has concluded, and the remaining steps are procedural matters between Ripple and the SEC, no longer involving the court.
Morgan emphasized that there is no decision left for Judge Torres to make. “Judge Torres’ role is over,” he wrote, addressing the widespread misconception. According to Morgan, the only action pending is for the SEC commissioners to vote on dismissing their appeal. Ripple has already publicly committed to dismissing its appeal.
https://twitter.com/Belisarius2020/status/1952854544695869707?ref_src=twsrc%5Etfw” rel=”nofollow noopener” target=”_blank
Previously, both the SEC and Ripple had signed a conditional settlement agreement that required the mutual withdrawal of appeals. However, when the court declined to approve the parties’ request to modify the injunction and reduce the civil penalty, the terms of the agreement were not satisfied. While both appeals are still technically active, they are expected to be withdrawn.
Morgan also clarified that August 15 is not a deadline for dismissing the appeals, as Zuccàra’s post had implied. Rather, it’s the date by which both parties are expected to submit a joint status report to the appeals court.
He noted that while it is more likely than not that the appeals will be dismissed before that date, the parties could request another extension, although he considers that unlikely.
“The dismissal of the appeals may happen before August 15,” Morgan explained, “but 15 August is not a deadline on the parties to dismiss their respective appeals.”
https://twitter.com/TimesTabloid1/status/1680250907504656385?ref_src=twsrc%5Etfw” rel=”nofollow noopener” target=”_blank
With Ripple having paid its $125 million penalty into escrow and stating its intent to end its appeal, all eyes are now on the SEC’s internal vote. Once that occurs, the parties can file the paperwork necessary to formally end the long-running case. Until then, both appeals remain legally active.
Morgan’s clarification directly contradicts the framing in Zuccàra’s post and helps refocus public understanding of where things stand. He stressed that any remaining developments are purely procedural, hinging on the SEC’s next move.
While many in the XRP community had anticipated that August 15 might bring the final word from the court, Morgan’s update serves as an important reminder that the court’s role is finished, and formal closure now rests with the SEC and Ripple. If the SEC votes to drop its appeal—as is widely expected—the parties could file dismissal notices well before the August 15 status report.
Bill Morgan’s post provides much-needed clarity and corrects the misleading narrative. Until those final steps are taken, both appeals remain on foot—but the path to resolution appears closer than ever.
Disclaimer: This content is meant to inform and should not be considered financial advice. The views expressed in this article may include the author’s personal opinions and do not represent BitcoinLinux’s opinion. Readers are urged to do in-depth research before making any investment decisions. Any action taken by the reader is strictly at their own risk. BitcoinLinux is not responsible for any financial losses.
Follow us on Twitter, Facebook, Telegram, and Google News
The post XRP Case Update: Legal Expert Corrects Inaccuracies About August 15 Deadline appeared first on BitcoinLinux.
Go to Source
Author: NixCoin
AI SummaryShowCoinbase reported $718.7 million in Q3 net income, driven by a $715 million investment gain on…
Key Highlights Jaipur Police arrested Vikas Dhaka over an alleged network that routed transactions worth…
AI SummaryShowTether’s Q3 2026 net operating profit hit $1.5 billion, driven mainly by Treasury bills and…
Key Highlights Andreessen Horowitz (a16z), the DeFi Education Fund and Uniswap Labs submitted comments on…
AI SummaryShowCFTC Chair Michael Selig pushes federal registration for crypto exchanges, citing Binance’s $6.3 billion breach.Binance…
Even as the largest exchange hack in history continues, Elon Musk’s Grok AI predicts something…
This website uses cookies.
Read More