Bitcoin investors face a real, long-term risk from quantum computing, but the danger is not equally distributed across all wallets. Will Owens, a research analystBitcoin investors face a real, long-term risk from quantum computing, but the danger is not equally distributed across all wallets. Will Owens, a research analyst

Galaxy: Quantum Risk Varies Across Crypto Wallets

For feedback or concerns regarding this content, please contact us at crypto.news@mexc.com
Galaxy: Quantum Risk Varies Across Crypto Wallets

Bitcoin investors face a real, long-term risk from quantum computing, but the danger is not equally distributed across all wallets. Will Owens, a research analyst at Galaxy Digital, outlined in a recent briefing that a sufficiently powerful quantum computer could derive a private key from a public key, enabling an attacker to impersonate the wallet owner, forge a signature, and steal coins. Yet he stressed that the current landscape is not uniformly vulnerable: most wallets remain safe today, with risk primarily arising when public keys are visible on-chain.

Owens described two primary exposure paths. The first concerns wallets whose public keys are already exposed on the blockchain, making them potential targets if a quantum attack becomes feasible. The second occurs when a wallet’s public key is revealed at the moment of spending. This distinction has practical implications for how wallets are designed, upgraded, and secured as the crypto ecosystem moves toward post-quantum resilience.

Key takeaways

  • Public-key exposure matters: funds are at greater risk if a wallet’s public key is visible on-chain or revealed during a transaction.
  • Today’s wallets are largely shielded from quantum risk, but the threat is recognized and being studied by developers and researchers.
  • The Bitcoin community has accelerated quantum-related proposals since late 2025, though governance remains non-centralized by design.
  • Near-term guardrails have been discussed, including practical approaches from prominent voices advocating safer storage methods until post-quantum solutions are ready.
  • Investors should monitor post-quantum developments and the timing of proposed mitigations, as the threat is real even if not imminent for most users.

Quantum risk landscape for Bitcoin wallets

The core concern is the possibility that a quantum computer could reverse-engineer a private key from a corresponding public key, enabling an attacker to impersonate the wallet owner and authorize transactions. This would undermine the cryptographic foundations that underwrite Bitcoin’s security. However, Owens cautioned that the vulnerability is not uniform across all wallets today. “Most wallets are not vulnerable today. Funds are at risk only when public keys are exposed on-chain,” he explained.

The two exposure routes identified by Owens—on-chain public keys already visible, and keys revealed at spending—are important for both users and developers. If a wallet’s public key remains hidden until it is used, the risk profile differs from wallets whose keys have already been disclosed on-chain. This nuance shapes how wallets are designed to mitigate potential quantum threats, including the timing of key disclosure and migration to post-quantum-secure mechanisms.

Quantum computing’s potential to disrupt conventional cryptography has circulated in crypto discourse for years, with some observers arguing the threat is distant. Yet the consensus forming in academic and industry circles is that the question is not if, but when—and how quickly the ecosystem can adapt. Owens noted that the debate extends beyond the technical layer and into governance, as coordinated action will be required to implement robust, long-term protections.

The right people are on top of the issue

Despite some critics who argue the quantum threat is overstated or decades away, Owens contends that development activity in this area has intensified. He said there is substantial developer work addressing quantum vulnerabilities and mitigations, and that the ecosystem now has a concrete, maturing set of proposals spanning the full problem surface. “The proposals are not theoretical. They are being actively developed, reviewed, and debated by some of the most experienced contributors in the Bitcoin ecosystem,” he affirmed.

In parallel, other voices in the space have proposed practical approaches to reduce exposure in the near term. Crypto veteran Willy Woo suggested last November that holding Bitcoin in SegWit wallets could reduce risk while a more permanent solution is devised. The idea reflects a broader appetite for interim safeguards as the community weighs longer-term protocol changes such as post-quantum cryptographic schemes.

The broader push toward post-quantum readiness has historically been framed as a balance between innovation and conservative risk management. While some markets may still debate the immediacy of the risk, the Bitcoin ecosystem appears to be aligning incentives around security and resilience. Owens emphasized that a non-centralized governance model—where Bitcoin has no CEO, no board, and no single authority to mandate updates—does not preclude effective action. Instead, the universal and external nature of the risk—affecting participants across the network—can catalyze broad, voluntary alignment around practical mitigations and gradual upgrades.

As the conversation evolves, the community continues to explore concrete, actionable paths forward. In addition to BIP-based discussions and potential soft-fork mitigations, researchers and developers are evaluating post-quantum-ready signatures, key-management innovations, and more robust on-chain privacy and security architectures. The goal is not merely to react to a theoretical threat but to engineer a resilient system that preserves user sovereignty without compromising the Bitcoin network’s open, trust-minimized ethos.

Looking ahead, observers will want to watch how quickly post-quantum techniques mature and how they can be integrated without creating new vectors for risk or fragmenting the ecosystem. The next few years are likely to bring a combination of protocol-level experiments, community-led governance decisions, and gradual deployment of protective measures that could gradually harden Bitcoin against quantum threats while maintaining its decentralized ethos.

As quantum resilience work progresses, readers should stay attuned to updates from core developers, security researchers, and stakeholder communities. The exact timeline for wide-scale post-quantum adoption remains uncertain, but the direction is clear: the industry is treating quantum risk as a real, evolving concern and mobilizing to address it with practical, collaborative solutions.

This article was originally published as Galaxy: Quantum Risk Varies Across Crypto Wallets on Crypto Breaking News – your trusted source for crypto news, Bitcoin news, and blockchain updates.

Market Opportunity
QUANTUM Logo
QUANTUM Price(QUANTUM)
$0.00283
$0.00283$0.00283
+2.90%
USD
QUANTUM (QUANTUM) 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 crypto.news@mexc.com 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

Trump-backed WLFI  launches AgentPay SDK open-source payment toolkit for AI agents

Trump-backed WLFI  launches AgentPay SDK open-source payment toolkit for AI agents

The Trump family has expanded its presence in the crypto community with a major development for artificial intelligence (AI) agents. According to reports, World
Share
Cryptopolitan2026/03/20 19:03
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
Tom Lee Declares That Ethereum Has Bottomed Out

Tom Lee Declares That Ethereum Has Bottomed Out

Experienced analyst Tom Lee conducted an in-depth analysis of the Ethereum price. Here are some of the highlights from Lee's findings. Continue Reading: Tom Lee
Share
Bitcoinsistemi2026/03/20 19:05