The post FTX estate says Justin Sun still owes it millions appeared on BitcoinEthereumNews.com. The FTX estate has filed a motion for leave to amend its complaintThe post FTX estate says Justin Sun still owes it millions appeared on BitcoinEthereumNews.com. The FTX estate has filed a motion for leave to amend its complaint

FTX estate says Justin Sun still owes it millions

The FTX estate has filed a motion for leave to amend its complaint against HTX, Poloniex, and Justin Sun.

The amended complaint claims that the FTX-Alameda Research estate had approximately $27 million in funds on both HTX (then Huobi) and Poloniex when it declared bankruptcy.

The original version of its complaint was filed in November 2024.

What’s in the lawsuit?

The proposed amended complaint, filed by the FTX Recovery Trust, has as its defendants: Huobi, Poloniex, Sun, and a variety of entities that the suit alleges are “alter-egos” of Sun.

It claims that Alameda Research had funds on both Poloniex and HTX (then Huobi) at the time Alameda Research-FTX declared bankruptcy, “then-valued at approximately $27.5 million.”

Unfortunately for the FTX estate, “both Huobi and Poloniex had locked the Alameda accounts, rendering the debtors unable to recover their assets.”

Read more: Justin Sun-advised HTX has redeemed 7,300 WBTC it did not disclose

The “Alameda Huobi Account” wasn’t opened under Alameda Research’s corporate name but instead “was nominally held in the name of the former Alameda employee.”

This account held approximately $22 million when the FTX-Alameda Research criminal organization declared bankruptcy, according to this complaint. Huobi has yet to turn over these assets.

Similarly for Poloniex, Alameda Research had opened an account associated with Sam Bankman-Fried, which held approximately $5.5 million at the time FTX-Alameda Research declared bankruptcy.

Despite repeated follow-ups, Poloniex and Huobi/HTX have apparently been unwilling to return these assets to the FTX-Alameda Research estate.

Read more: Coinbase to delist WBTC months after Justin Sun controversy

The complaint also noted that Sun maintained accounts on FTX, specifically, through entities called Orange Anthem and Black Anthem.

Orange Anthem, according to this proposed amended complaint, filed a customer proof of claim against the FTX estate for approximately $12 million.

The complaint alleges that “Justin Sun operates Huobi, Poloniex, Orange Anthem, along with his TRON Network, as a unified, integrated enterprise.”

Outside of the complaint, we can find evidence of this overlap in the entities in the support documents for these exchanges; consider the “Poloniex OTC Transaction Policy,” which claims that “the P2P merchants and services on Poloniex are provided by Huobi.”

Furthermore, there are documents on the support sites for both exchanges that discuss a “strategic partnership” between these two exchanges.

Justin Sun’s liquidity ploy

After FTX halted most withdrawals on November 8, Sun “entered into discussions with Bankman-Fried concerning a limited liquidity arrangement focused exclusively on Sun-affiliated digital assets.”

Sun then posted about this, claiming that he was helping to facilitate withdrawals by providing liquidity.

The complaint alleges that this behavior by Sun “affirmatively facilitated a breakdown of creditor equality by providing preferential treatment unavailable to others who didn’t have tokens associated with Sun.”

Read more: Justin Sun, crypto’s most shameless marketer, play-acts the hero

This facility ended up “effectively reallocating estate value away from the general creditor body and towards Sun and his enterprises.”

Furthermore, the complaint claims that this ploy “was designed to — and did — artificially inflate the prices of Sun-affiliated tokens by inducing a surge in demand on FTX.”

What does the complaint say about Justin Sun’s entities?

The amended complaint provides us additional insight into what the FTX estate believes the current status of Sun’s web of companies is.

It names two Sun-affiliated firms as responsible for the acquisition of Huobi, specifically About Capital Management and Digital Legend.

Furthermore, it details how Huobi Global S.A. currently owns the HTX trademark in the United States.

Read more: Justin Sun’s Poloniex and HTX withdraw huge amounts from AAVE

It also reveals that Polo Digital Assets, Ltd., which was incorporated in the Seychelles and previously operated the Poloniex exchange has been “stricken from the Seychelles registry in January 2022.”

Despite the fact that this entity has been struck from the registry, it’s still the entity referenced in the Poloniex privacy policy.

Based on the Poloniex user agreement, which claims that “the laws of the Republic of Panama shall govern this agreement,” it’s likely that the successor entity has been incorporated in Panama.

Protos reached out to Poloniex for clarification about which entity currently oversees the platform, but it didn’t provide clarification before publication.

Read more: Justin Sun owns more TRX than everyone else combined, report

A similar problem exists for HTX, where the proposed amended complaint details how “a publicly available Huobi service agreement refers to” an entity called HTX Ltd., which it identifies as being incorporated in the Seychelles.

However, “the Trust has been unable to identify any company incorporated under that name in the Seychelles corporate registry.”

The complaint also mentions that Orange Anthem, the entity that had funds on FTX at the time of collapse, “is part of Sun’s TRON Network” and notes that it registered its FTX accounts with the email “[email protected]” and further noted that its know your customer documents “identified Sun as the sole director and shareholder of Orange Anthem.”

Furthermore, Orange Anthem is linked to Black Anthem, as “when FTX requested proof of Orange Anthem’s assets, the Tron personnel… responded with screenshots reflecting assets that were held not by Orange Anthem, but rather nominally by Black Anthem.”

Black Anthem’s account was registered to the email account “[email protected].”

Read more: How involved is Justin Sun with WBTC’s new custodian BiT Global?

When this proof of assets was challenged by FTX employees, “the Tron personnel… expressly dismissed any distinction among the entities,” suggesting that Black Anthem “uses the director Sun Yuchen, this totally matches the director of Orange Anthem Ltd. Sun Yuchen. The person is the same.”

When, according to the proposed amended complaint, FTX employees suggested this didn’t prove that Orange Anthem owned the assets, the Tron personnel stated that “Yes Sun Yuchen is the sole director for Black Anthem Ltd as same as Orange Anthem Ltd.”

This was an apparent attempt to suggest that Sun’s control of these entities meant their assets were interchangeable.

As we’ve mentioned previously, Sun is a fan of the author Ayn Rand, and Anthem is a book by Ayn Rand.

What happened before this amended complaint?

The original adversary case was filed in November of 2024.

This earlier complaint named Hbit LTD., as well as the other defendants, which was subsequently removed in February of 2025.

In April 2025 the defendants filed a motion to dismiss the suit, and a hearing related to this was held on December 8, 2025.

Following this, the original complaint was dismissed.

Subsequently, on January 7, the FTX estate filed its motion for leave to amend its complaint.

Got a tip? Send us an email securely via Protos Leaks. For more informed news, follow us on X, Bluesky, and Google News, or subscribe to our YouTube channel.

Source: https://protos.com/ftx-estate-says-justin-sun-still-owes-it-millions/

Market Opportunity
HTX DAO Logo
HTX DAO Price(HTX)
$0.000001767
$0.000001767$0.000001767
+0.39%
USD
HTX DAO (HTX) Live Price Chart
Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact [email protected] for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

21Shares Launches JitoSOL Staking ETP on Euronext for European Investors

21Shares Launches JitoSOL Staking ETP on Euronext for European Investors

21Shares launches JitoSOL staking ETP on Euronext, offering European investors regulated access to Solana staking rewards with additional yield opportunities.Read
Share
Coinstats2026/01/30 12:53
Digital Asset Infrastructure Firm Talos Raises $45M, Valuation Hits $1.5 Billion

Digital Asset Infrastructure Firm Talos Raises $45M, Valuation Hits $1.5 Billion

Robinhood, Sony and trading firms back Series B extension as institutional crypto trading platform expands into traditional asset tokenization
Share
Blockhead2026/01/30 13:30
Summarize Any Stock’s Earnings Call in Seconds Using FMP API

Summarize Any Stock’s Earnings Call in Seconds Using FMP API

Turn lengthy earnings call transcripts into one-page insights using the Financial Modeling Prep APIPhoto by Bich Tran Earnings calls are packed with insights. They tell you how a company performed, what management expects in the future, and what analysts are worried about. The challenge is that these transcripts often stretch across dozens of pages, making it tough to separate the key takeaways from the noise. With the right tools, you don’t need to spend hours reading every line. By combining the Financial Modeling Prep (FMP) API with Groq’s lightning-fast LLMs, you can transform any earnings call into a concise summary in seconds. The FMP API provides reliable access to complete transcripts, while Groq handles the heavy lifting of distilling them into clear, actionable highlights. In this article, we’ll build a Python workflow that brings these two together. You’ll see how to fetch transcripts for any stock, prepare the text, and instantly generate a one-page summary. Whether you’re tracking Apple, NVIDIA, or your favorite growth stock, the process works the same — fast, accurate, and ready whenever you are. Fetching Earnings Transcripts with FMP API The first step is to pull the raw transcript data. FMP makes this simple with dedicated endpoints for earnings calls. If you want the latest transcripts across the market, you can use the stable endpoint /stable/earning-call-transcript-latest. For a specific stock, the v3 endpoint lets you request transcripts by symbol, quarter, and year using the pattern: https://financialmodelingprep.com/api/v3/earning_call_transcript/{symbol}?quarter={q}&year={y}&apikey=YOUR_API_KEY here’s how you can fetch NVIDIA’s transcript for a given quarter: import requestsAPI_KEY = "your_api_key"symbol = "NVDA"quarter = 2year = 2024url = f"https://financialmodelingprep.com/api/v3/earning_call_transcript/{symbol}?quarter={quarter}&year={year}&apikey={API_KEY}"response = requests.get(url)data = response.json()# Inspect the keysprint(data.keys())# Access transcript contentif "content" in data[0]: transcript_text = data[0]["content"] print(transcript_text[:500]) # preview first 500 characters The response typically includes details like the company symbol, quarter, year, and the full transcript text. If you aren’t sure which quarter to query, the “latest transcripts” endpoint is the quickest way to always stay up to date. Cleaning and Preparing Transcript Data Raw transcripts from the API often include long paragraphs, speaker tags, and formatting artifacts. Before sending them to an LLM, it helps to organize the text into a cleaner structure. Most transcripts follow a pattern: prepared remarks from executives first, followed by a Q&A session with analysts. Separating these sections gives better control when prompting the model. In Python, you can parse the transcript and strip out unnecessary characters. A simple way is to split by markers such as “Operator” or “Question-and-Answer.” Once separated, you can create two blocks — Prepared Remarks and Q&A — that will later be summarized independently. This ensures the model handles each section within context and avoids missing important details. Here’s a small example of how you might start preparing the data: import re# Example: using the transcript_text we fetched earliertext = transcript_text# Remove extra spaces and line breaksclean_text = re.sub(r'\s+', ' ', text).strip()# Split sections (this is a heuristic; real-world transcripts vary slightly)if "Question-and-Answer" in clean_text: prepared, qna = clean_text.split("Question-and-Answer", 1)else: prepared, qna = clean_text, ""print("Prepared Remarks Preview:\n", prepared[:500])print("\nQ&A Preview:\n", qna[:500]) With the transcript cleaned and divided, you’re ready to feed it into Groq’s LLM. Chunking may be necessary if the text is very long. A good approach is to break it into segments of a few thousand tokens, summarize each part, and then merge the summaries in a final pass. Summarizing with Groq LLM Now that the transcript is clean and split into Prepared Remarks and Q&A, we’ll use Groq to generate a crisp one-pager. The idea is simple: summarize each section separately (for focus and accuracy), then synthesize a final brief. Prompt design (concise and factual) Use a short, repeatable template that pushes for neutral, investor-ready language: You are an equity research analyst. Summarize the following earnings call sectionfor {symbol} ({quarter} {year}). Be factual and concise.Return:1) TL;DR (3–5 bullets)2) Results vs. guidance (what improved/worsened)3) Forward outlook (specific statements)4) Risks / watch-outs5) Q&A takeaways (if present)Text:<<<{section_text}>>> Python: calling Groq and getting a clean summary Groq provides an OpenAI-compatible API. Set your GROQ_API_KEY and pick a fast, high-quality model (e.g., a Llama-3.1 70B variant). We’ll write a helper to summarize any text block, then run it for both sections and merge. import osimport textwrapimport requestsGROQ_API_KEY = os.environ.get("GROQ_API_KEY") or "your_groq_api_key"GROQ_BASE_URL = "https://api.groq.com/openai/v1" # OpenAI-compatibleMODEL = "llama-3.1-70b" # choose your preferred Groq modeldef call_groq(prompt, temperature=0.2, max_tokens=1200): url = f"{GROQ_BASE_URL}/chat/completions" headers = { "Authorization": f"Bearer {GROQ_API_KEY}", "Content-Type": "application/json", } payload = { "model": MODEL, "messages": [ {"role": "system", "content": "You are a precise, neutral equity research analyst."}, {"role": "user", "content": prompt}, ], "temperature": temperature, "max_tokens": max_tokens, } r = requests.post(url, headers=headers, json=payload, timeout=60) r.raise_for_status() return r.json()["choices"][0]["message"]["content"].strip()def build_prompt(section_text, symbol, quarter, year): template = """ You are an equity research analyst. Summarize the following earnings call section for {symbol} ({quarter} {year}). Be factual and concise. Return: 1) TL;DR (3–5 bullets) 2) Results vs. guidance (what improved/worsened) 3) Forward outlook (specific statements) 4) Risks / watch-outs 5) Q&A takeaways (if present) Text: <<< {section_text} >>> """ return textwrap.dedent(template).format( symbol=symbol, quarter=quarter, year=year, section_text=section_text )def summarize_section(section_text, symbol="NVDA", quarter="Q2", year="2024"): if not section_text or section_text.strip() == "": return "(No content found for this section.)" prompt = build_prompt(section_text, symbol, quarter, year) return call_groq(prompt)# Example usage with the cleaned splits from Section 3prepared_summary = summarize_section(prepared, symbol="NVDA", quarter="Q2", year="2024")qna_summary = summarize_section(qna, symbol="NVDA", quarter="Q2", year="2024")final_one_pager = f"""# {symbol} Earnings One-Pager — {quarter} {year}## Prepared Remarks — Key Points{prepared_summary}## Q&A Highlights{qna_summary}""".strip()print(final_one_pager[:1200]) # preview Tips that keep quality high: Keep temperature low (≈0.2) for factual tone. If a section is extremely long, chunk at ~5–8k tokens, summarize each chunk with the same prompt, then ask the model to merge chunk summaries into one section summary before producing the final one-pager. If you also fetched headline numbers (EPS/revenue, guidance) earlier, prepend them to the prompt as brief context to help the model anchor on the right outcomes. Building the End-to-End Pipeline At this point, we have all the building blocks: the FMP API to fetch transcripts, a cleaning step to structure the data, and Groq LLM to generate concise summaries. The final step is to connect everything into a single workflow that can take any ticker and return a one-page earnings call summary. The flow looks like this: Input a stock ticker (for example, NVDA). Use FMP to fetch the latest transcript. Clean and split the text into Prepared Remarks and Q&A. Send each section to Groq for summarization. Merge the outputs into a neatly formatted earnings one-pager. Here’s how it comes together in Python: def summarize_earnings_call(symbol, quarter, year, api_key, groq_key): # Step 1: Fetch transcript from FMP url = f"https://financialmodelingprep.com/api/v3/earning_call_transcript/{symbol}?quarter={quarter}&year={year}&apikey={api_key}" resp = requests.get(url) resp.raise_for_status() data = resp.json() if not data or "content" not in data[0]: return f"No transcript found for {symbol} {quarter} {year}" text = data[0]["content"] # Step 2: Clean and split clean_text = re.sub(r'\s+', ' ', text).strip() if "Question-and-Answer" in clean_text: prepared, qna = clean_text.split("Question-and-Answer", 1) else: prepared, qna = clean_text, "" # Step 3: Summarize with Groq prepared_summary = summarize_section(prepared, symbol, quarter, year) qna_summary = summarize_section(qna, symbol, quarter, year) # Step 4: Merge into final one-pager return f"""# {symbol} Earnings One-Pager — {quarter} {year}## Prepared Remarks{prepared_summary}## Q&A Highlights{qna_summary}""".strip()# Example runprint(summarize_earnings_call("NVDA", 2, 2024, API_KEY, GROQ_API_KEY)) With this setup, generating a summary becomes as simple as calling one function with a ticker and date. You can run it inside a notebook, integrate it into a research workflow, or even schedule it to trigger after each new earnings release. Free Stock Market API and Financial Statements API... Conclusion Earnings calls no longer need to feel overwhelming. With the Financial Modeling Prep API, you can instantly access any company’s transcript, and with Groq LLM, you can turn that raw text into a sharp, actionable summary in seconds. This pipeline saves hours of reading and ensures you never miss the key results, guidance, or risks hidden in lengthy remarks. Whether you track tech giants like NVIDIA or smaller growth stocks, the process is the same — fast, reliable, and powered by the flexibility of FMP’s data. Summarize Any Stock’s Earnings Call in Seconds Using FMP API was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story
Share
Medium2025/09/18 14:40