The post Glamsterdam and Hegota Forks, L1 Scaling appeared on BitcoinEthereumNews.com. The coming year is set to be crucial for Ethereum scaling. In 2026, the GlamsterdamThe post Glamsterdam and Hegota Forks, L1 Scaling appeared on BitcoinEthereumNews.com. The coming year is set to be crucial for Ethereum scaling. In 2026, the Glamsterdam

Glamsterdam and Hegota Forks, L1 Scaling

The coming year is set to be crucial for Ethereum scaling. In 2026, the Glamsterdam fork will bring perfect parallel processing to the chain and ratchet up the gas limit to 200 million, up from 60 million today.

A significant number of validators will switch over from reexecuting transactions to verifying zero-knowledge (ZK) proofs instead. This sets the Ethereum layer 1 on a path to scale up to 10,000 transactions per second (TPS) and potentially beyond, though that target won’t be hit in 2026.

Meanwhile, data blobs will increase (potentially up to 72 or more per block), enabling the layer 2s (L2s) to process hundreds of thousands of transactions per second. L2s are becoming easier to use as well; ZKsync’s recent Atlas upgrade allows funds to stay on mainnet but trade in the fast execution environment of chains in ZKsync’s Elastic Network.

The planned Ethereum Interoperability Layer will enable seamless cross-chain operation among L2s, privacy will take center stage, and improved censorship resistance is targeted for the Heze-Bogota fork at the end of the year.

Ethereum in 2026: The Glamsterdam fork

Ethereum developers are currently finalizing what Ethereum Improvement Proposals (EIPs) should be included in the Glamsterdam hard fork, expected in mid-2026. The confirmed headliner changes are Block Access Lists and Enshrined Proposer Builder Separation. Neither sounds particularly interesting, but they have the potential to supercharge the blockchain ahead of the switch to ZK tech.

At some point, the core devs will come up with cool names for stuff like “Firedancer,” but until then, we’re stuck with whatever boring technical names they choose.

Glamsterdam: Block Access Lists (EIP-7928)

Although “block access lists” sound like a censorship scheme, the upgrade actually makes “perfect” parallel block processing possible.

To date, Ethereum has been running in single-lane mode, with a very long queue of transactions executed in order, one after the other. Block Access Lists enable throughput to scale up to a multi-lane highway, with multiple transactions processed at the same time.

The term refers to a map included in each block that was devised by the block producer, who executed everything first on some fancy high-end equipment. The map tells Ethereum clients which transactions affect which other transactions, accounts and storage slots and what the state differentials are after the transaction. This allows them to parcel up the transactions and run them on multiple CPU cores simultaneously without any conflicts.

Related: Blockchains quietly prepare for quantum threat as Bitcoin debates timeline

“With Block Access List, we are getting all the state that changes from transaction to transaction, and you are putting that information in the block,” explained Gabriel Trintinalia, senior blockchain engineer with Consensys, who is working on execution client Besu.

It also enables clients to preload all the necessary data from disk into memory first, rather than keep going back to read the disk sequentially, which Trintinalia calls “the biggest bottleneck we have.”

Perfect parallel processing will enable Ethereum to run at higher transactions per second and have bigger block sizes without raising the gas limit.

The upgrades made in 2026 will see Ethereum L1 scale to 10,000 TPS. Source: Growthepie

Glamsterdam: Enshrined Proposer Builder Separation

The process of separating block builders and proposers has already begun with MEV Boost, an out-of-protocol solution that uses centralized relays as intermediaries and handles approximately 90% of blocks. Enshrined Proposer Builder Separation (ePBS) integrates this process directly into Ethereum’s consensus layer for trustless operation.

The idea behind separating the two is that block builders compete with each other to select and order transactions in the best way possible to build a block, while proposers choose which block to propose. The aim is to mitigate maximal extractable value’s (MEV) centralizing pressure and to improve security, decentralization and censorship resistance.

But from a scalability standpoint, the major benefit of ePBS is that it provides more time for the generation and propagation of ZK-proofs throughout the network. Validators are currently penalized for being slow, which disincentivizes waiting around to validate ZK-proofs. EPBS will provide more time to receive and validate ZK-proofs.

This can give attesters more time to receive proofs (and provers more time to generate proofs), explained Ethereum researcher Ladislaus von Daniels, adding that ePBS decouples block validation from block execution and, in that sense, ships another flavor of delayed execution.

“This makes opt-in zkAttesting much more incentive compatible for validators.”

Ethereum Foundation researcher Justin Drake estimates that around 10% of validators will switch to ZK after this point, which will enable further gas limit increases.

Ethereum Foundation researcher Justin Drake demonstrates validating ZK-proofs. Source: EthProofs

Ethereum L1 gas increase and L2 blob target upgrades

The gas limit (which relates to throughput on the L1) has already been increased to 60 million. It should substantially increase in 2026 — although there’s a range of estimates as to how high it will go.

“I think in 2026, I would expect to see 100 million fairly soon. Anything beyond that is probably just too speculative to consider,” said Gary Schulte, senior staff blockchain protocol engineer on the Besu client. He added that the shift to delayed execution could make higher gas limits possible.

Related: Ethereum tripling its gas limit is the ‘floor, we can go higher’ — Sassano

Tomasz Stańczak, co-director of the Ethereum Foundation, told the recent Bankless Summit that the limit would increase to 100 million in the first half of 2026 and predicted it would double to 200 million following ePBS. Further improvements could mean up to 300 million gas per block is possible before the end of the year.

Ethereum creator Vitalik Buterin was more circumspect. In late November, he said to “expect continued growth but more targeted / less uniform growth for next year. eg. one possible future is: 5x gas limit increase together with 5x gas cost increase for operations that are relatively inefficient to process.” Buterin cited things like storage, precompiles and calls to contracts with large contract sizes.

Ethereum is scaling up in 2026. Source: TenaciousBit

Ethereum 2026 fork No. 2: Heze-Bogota 

Expect to see some of the EIPs held over from Glamsterdam in this fork, but according to Forkast, the only EIP currently on the Considered for Inclusion list is Fork-Choice Inclusion Lists (FOCIL). This was up for Glamsterdam but was pushed after a heated debate, as it would have required too much work and made life too difficult.

It’s not focused on scaling but on the cypherpunk ideal of censorship resistance by empowering multiple validators to mandate the inclusion of specific transactions in each block.

“That is a censorship resistance mechanism that ensures that if at least you have part of the network that’s honest … then you’re going to have your transaction included at some point,” said Trintinalia.

Keep an eye out for part 2, when we dive deeper into scaling the L1 with ZK-proofs in 2026.

Magazine: Big questions: Would Bitcoin survive a 10-year power outage?

Source: https://cointelegraph.com/news/ethereum-2026-glamsterdam-hegota-fork-scaling?utm_source=rss_feed&utm_medium=feed&utm_campaign=rss_partner_inbound

Market Opportunity
L1 Logo
L1 Price(L1)
$0.002833
$0.002833$0.002833
-1.18%
USD
L1 (L1) 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 service@support.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

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
Ripple IPO Back in Spotlight as Valuation Hits $50B

Ripple IPO Back in Spotlight as Valuation Hits $50B

The post Ripple IPO Back in Spotlight as Valuation Hits $50B appeared first on Coinpedia Fintech News Ripple, the blockchain payments company behind XRP, is once
Share
CoinPedia2025/12/27 14:24
Solana co-founder predicts that by 2026: the stablecoin market will exceed one trillion US dollars, and 100,000 humanoid robots will be shipped.

Solana co-founder predicts that by 2026: the stablecoin market will exceed one trillion US dollars, and 100,000 humanoid robots will be shipped.

PANews reported on December 27th that Anatoly Yakovenko, co-founder of Solana, released some predictions about 2026 on X, as follows: The total size of stablecoins
Share
PANews2025/12/27 15:04