Zach Pandl, head of research at Grayscale, said he hopes Strategy will sell at least $3 billion in Bitcoin to cover most of the company’s cash obligations for the next two years.

In a Saturday X post, Pandl argued that the move may restore market confidence in the company’s capital structure.

Contrary to his hopes, Pandl said he expects a 50-basis-point increase to the dividend rate on Strategy’s preferred stock, STRC, adding roughly $100 million in annual obligations over two years. Pandl added that this scenario “probably does not help market confidence.”

Strategy faces an annual preferred dividend obligation of approximately $1.2 billion, driven primarily by STRC.

STRC is Strategy’s flagship “digital credit” preferred stock designed to trade near its $100 par value, but has been sliding for weeks. On Friday, it fell to as low as $71.25, a 28.75% discount to par. Strategy’s common stock MSTR fared little better and closed Friday at $82.31, down 26.86% throughout the trading week.

Pandl said he expects Strategy to raise STRC’s dividend rate but hopes the company sells Bitcoin instead. Source: Zach Pandl

Strategy’s cash reserve under pressure

Strategy is the world’s largest publicly-listed corporate Bitcoin holder, placing its 847,363 BTC stash and financing decisions under the industry’s microscope. 

According to Strategy’s latest 8-K filing with the US Securities and Exchange Commission, it acquired 520 Bitcoin for $34.9 million between June 15 and June 21.

Blockchain analytics company CryptoQuant argued in a Tuesday report that Strategy should pause Bitcoin purchases and focus on replenishing its cash reserve, which is down 38% in 2026.

Related: Bitcoin doesn’t need Ethereum-style yield, says Strategy’s Michael Saylor

The 8-K filing also revealed that Strategy increased its US dollar reserve by $300 million to $1.4 billion. This leaves the company with roughly 14 months of dividend coverage, down sharply from what was once a seven-year cushion.

Strategy said on Monday that it plans to continue replenishing its cash reserves to support the credit quality of its “digital credit” securities.

Alternatives to a Bitcoin sale

CryptoQuant added that the company has no obligation to sell Bitcoin to support STRC’s price, because it can deploy other methods to defend its stock, such as raising the current 11.5% dividend yield.

Bitcoin advocate Samson Mow argued in a Monday X post that STRC has a built-in “self-repairing mechanism.” Once the stock falls below its $100 reference price, Strategy halts new ATM issuance, cutting off the supply of fresh shares.

At the same time, a lower price mechanically boosts the yield for new buyers relative to what they paid, which Mow said should draw in fresh demand and pull the price back toward par over time.

Source: Samson Mow

Magazine: AI is banking the unbanked in Africa… faster than crypto

Key Takeaways

• HYPE is currently valued near $62 with a multi-billion dollar market capitalization
• Baseline scenario projects $100–$160, valuing HYPE as a decentralized exchange token
• Optimistic scenario envisions $250–$400 if Hyperliquid dominates on-chain derivatives trading
• Pessimistic scenario suggests $20–$35 amid competitive pressures, security incidents, and token dilution
• Weighted probability analysis points to approximately $145 by the year 2031

Hyperliquid stands out in a crowded cryptocurrency landscape by delivering tangible results. Unlike countless projects built purely on speculation, Hyperliquid has secured more than 40% of the decentralized perpetual futures market by mid-2026. This represents genuine market dominance backed by data.

Currently trading near $62, HYPE’s valuation fundamentally depends on transaction volume, fee generation, and platform liquidity rather than empty promises.

The protocol handled transaction volumes in the hundreds of billions throughout the first quarter of 2026, with daily figures consistently reaching into the billions. These metrics mirror those of established centralized exchanges.

This performance explains why market observers increasingly compare HYPE’s valuation framework to traditional exchange tokens rather than standard Layer 1 blockchain assets.

Baseline Projection: $100 to $160 Range

The baseline forecast assumes Hyperliquid maintains its leadership position within decentralized perpetuals throughout the coming half-decade.

This scenario requires continued migration of traders toward on-chain platforms, sustained growth in cryptocurrency derivatives markets, and Hyperliquid’s ability to defend its market share. A valuation range of $100 to $160 would translate to a fully diluted market cap between $100 billion and $160 billion, calculated against the maximum token supply of 1 billion HYPE.

While ambitious, these valuations become reasonable if Hyperliquid evolves into essential infrastructure for cryptocurrency trading.

Reuters coverage indicates that cryptocurrency exchanges are positioning themselves for expanded U.S. perpetual futures offerings as regulatory frameworks crystallize. This regulatory shift could significantly expand Hyperliquid’s addressable market.

Optimistic and Pessimistic Scenarios

The optimistic projection places HYPE between $250 and $400. Achieving this requires Hyperliquid to dominate decentralized derivatives, successfully launch spot trading markets, attract significant institutional capital, and transform into a comprehensive on-chain financial infrastructure.

This scenario demands multiple favorable outcomes aligning simultaneously.

The pessimistic forecast settles between $20 and $35. Trading platform markets are intensely competitive. Centralized exchanges, dYdX, GMX, Solana ecosystem protocols, and emerging perpetual DEXs all compete for identical liquidity pools.

Security vulnerabilities represent substantial threats. The Financial Times documented a $280 million security breach at Drift, a rival decentralized derivatives platform. Such incidents can undermine confidence across the entire sector.

Token supply expansion creates additional downward pressure. The current circulating supply represents only a fraction of the 1 billion maximum HYPE tokens. Future unlock events occurring during periods of weak demand could significantly depress prices.

The probability-adjusted five-year projection estimates approximately $145 by 2031.

Hyperliquid commands over 40% of decentralized perpetual futures volume as of mid-2026, with daily trading consistently reaching billions of dollars.

Key Takeaways

• ZEC is currently valued at approximately $388 with a total market capitalization approaching $6.7 billion
• The moderate scenario projects ZEC reaching $600–$1,000 by the end of 2031
• An optimistic scenario envisions $2,000–$3,500 should privacy features gain mainstream adoption
• A pessimistic outlook anticipates $120–$220 amid intensifying regulatory challenges
• Weighted average projection indicates approximately $850 as the target price for 2031

Introduced to the cryptocurrency ecosystem in 2016, Zcash emerged as a privacy-centric counterpart to Bitcoin. While Bitcoin operates with complete transaction transparency, Zcash enables users to conduct confidential transfers utilizing zero-knowledge cryptographic protocols.

This positions ZEC as a unique investment proposition. Rather than challenging platforms like Ethereum or Solana, it represents a strategic bet on whether financial confidentiality will resonate with cryptocurrency participants and corporate entities.

Presently trading at roughly $388, ZEC maintains a market valuation close to $6.7 billion, with approximately 16.7 million tokens currently circulating. Mirroring Bitcoin’s economic model, Zcash incorporates a maximum supply ceiling of 21 million coins alongside a halving mechanism that reduces mining rewards approximately every four years.

Industry observers from CoinDesk indicated that privacy-oriented cryptocurrencies such as Zcash and Monero were projected to maintain investor interest throughout 2026, despite ongoing challenges related to exchange removals and financial institution restrictions.

Moderate Projection: $600–$1,000 Range

The middle-ground forecast for ZEC through 2031 anticipates valuations spanning $600 to $1,000. This translates to a market capitalization between approximately $12 billion and $20 billion.

This pathway doesn’t demand that Zcash ascends into the top tier of cryptocurrency assets. It simply requires maintaining its status as the premier privacy-focused digital asset offering regulatory-compliant optional transparency features.

Three fundamental drivers support this trajectory: expanding privacy consciousness among users, sustained availability on major trading platforms, and robust technical foundations. Zcash’s Bitcoin-inspired monetary policy and proof-of-work consensus mechanism reinforce this projection.

Optimistic Projection: $2,000–$3,500 Range

Should privacy emerge as a central theme within cryptocurrency markets, ZEC could potentially climb to $2,000–$3,500. Such appreciation would elevate its market capitalization to the $40 billion–$70 billion territory.

Realizing this scenario requires widespread implementation of confidential transaction features, significant improvements in user interface design, and revitalized institutional participation in privacy-preserving technologies.

Additionally, Zcash would need market recognition as a “privacy-enhanced Bitcoin” rather than merely another aging alternative cryptocurrency.

Pessimistic Projection: $120–$220 Range

The downside scenario centers on regulatory enforcement. Privacy-focused cryptocurrencies currently face removal pressures across numerous jurisdictions, representing tangible rather than theoretical risks.

Should major exchanges impose restrictions or completely eliminate ZEC trading pairs, resulting in severely diminished liquidity, valuations could contract to $120–$220 by 2031.

Maintaining access to reputable trading venues constitutes one of the most significant threats to Zcash’s future market value.

Calculating probability-weighted outcomes across these three distinct scenarios yields an approximate target price of $850 for 2031.

Coinbase’s Base layer-2 network suffered two block production outages last week, and the project’s engineering team has traced both issues to problems in its sequencer infrastructure. According to a Saturday post-mortem, a bug in the block-building process caused “stale journal state” to remain after an execution failure—preventing the network from progressing until operators applied fixes.

Because Base runs with a single sequencer, the incident underscores a structural risk familiar to many rollups: when sequencer logic fails, block ordering and forward progress can stall across the whole chain. Base experienced a first outage on Thursday lasting 116 minutes, followed by a second that lasted 20 minutes, with a complete halt of new layer-2 block production during both events.

Key takeaways

• Base’s engineering team linked the outages to sequencer block-building logic that left “stale journal state” after a transaction validation failure.
• Base operates a single sequencer, so a sequencer-level defect can halt the entire network’s block production.
• The second outage was worsened by a “race condition” after a system reset that prevented sequencers from catching up.
• Engineers say remediation took longer than expected due to infrastructure conditions, not the original bug.
• Planned follow-ups include more protocol “fuzz testing” and “graceful recovery” measures to reduce manual restarts.

What the post-mortem says went wrong

In the post-mortem, the Base engineering team explained that an invalid transaction reached the block builder and failed during execution—consistent with expected behavior. The failure, however, was followed by an unintended state-management outcome: the sequencer did not clear the journal state that records which accounts and storage slots were accessed during processing.

That journal state is critical to correct execution bookkeeping. If it persists when it should be cleared, later stages of block building can be forced into an inconsistent pathway, preventing the sequencer and validator nodes from moving past the problematic block. In this case, that’s what ultimately stopped progress on Base’s chain.

The post-mortem also points out why this is particularly disruptive on Base: the network uses a single sequencer. Unlike architectures that distribute sequencer responsibilities across multiple components, a single sequencer becomes a single point of failure for block production. The team’s analysis places the incident squarely in the sequencer layer, rather than the broader execution environment.

Two outages, one root process—and a second failure mode

Base mainnet halted block production twice over the Thursday–Friday window. The first incident lasted 116 minutes, while the second ran for 20 minutes. During both events, new layer-2 blocks stopped being produced, and the sequencer and validator nodes could not progress past the invalid block until sequencing was restored.

Engineers said they resolved the outages by patching the sequencers to ensure the journal state is properly updated during execution. However, they emphasized that the time required for mitigation exceeded expectations. The team attributed the delay to “infrastructure conditions unrelated to the original bug,” implying the remediation itself was more operationally complex than the underlying code fix.

Beyond the initial state-clearing issue, the post-mortem describes an additional complication after system reset: a “race condition” prevented the sequencers from catching up. This race condition, following the restart, is presented as the driver behind the second outage—meaning the chain did not simply fail once and recover, but experienced a follow-on stall tied to how components re-synchronized.

Why sequencer fragility matters to rollup users

While outages are never ideal, sequencer incidents carry a special weight for users because ordering is foundational to how rollups coordinate transactions. A centralized sequencer decides the order of transactions and packages them into blocks. When its block-building logic or recovery flow breaks, users can see cascading effects: delayed confirmations, stalled finality progress, and operational interruptions that can be difficult for end users to predict.

The Base team’s findings also resonate with a broader pattern across the rollup ecosystem. The post-mortem narrative aligns with earlier reporting that sequencer or sequencer-adjacent failures have triggered outages on other layer-2 networks as well, including Arbitrum, OP Mainnet, and zkSync Era. Those precedents help explain why developers and investors pay close attention to sequencer fault tolerance, restart behavior, and how systems handle invalid transactions under real-world conditions.

For Base specifically, the incident is likely to intensify scrutiny around resiliency and recovery mechanisms, given its “single sequencer” setup. In a centralized sequencer design, even small logical errors can have system-wide consequences if recovery pathways require manual intervention or are sensitive to timing.

What Base plans to do next

After identifying the immediate cause and applying patches, Base’s engineering team outlined improvements intended to reduce the likelihood of recurrence. Two steps are highlighted in the post-mortem: enhanced protocol “fuzz testing” and better “graceful recovery.”

Fuzz testing generally involves bombarding the system with large volumes of randomized inputs—including malformed or unexpected cases—to uncover edge-case failures that may not appear in standard testing. In this context, the goal is to better stress sequencer logic such that state-handling bugs—like improper journal state clearing—are caught earlier.

“Graceful recovery,” as described by the team, aims to ensure validator nodes don’t need manual restarts during future incidents. That matters because recovery time affects user experience and operational risk: the faster and more automatic the system can re-stabilize, the less time the network spends in a stalled state.

Base isn’t new to sequencer incidents

This isn’t Base’s first sequencer-related interruption. The post-mortem notes an earlier episode in September 2024 where block production stopped for 17 minutes, and another incident in August 2025 lasting around half an hour.

The network’s scale also makes these events more consequential. According to L2beat, Base is the second-largest layer-2 network by total value secured, just under $11 billion. With that level of capital and activity, sequencer reliability becomes more than a technical metric—it directly influences the perceived operational maturity of the chain.

As Base continues to grow, the industry will likely watch whether the promised improvements translate into faster, smoother recovery and fewer extended stalls. Even if the sequencer remains centralized, the fault-tolerance of its software pathways—especially around state management and reset behavior—can make a meaningful difference in how often outages cascade.

For now, Base users and builders should focus on how quickly engineering can validate the patched behavior under stress, and whether the planned fuzz testing and recovery upgrades reduce the chance of repeat failures—particularly those tied to invalid transaction handling and post-reset synchronization.

Bitcoin dipped below $60,000 over the weekend, trading around $59,940 on Sunday, down 0.6% over 24 hours and nearly 7% on the week, per CoinDesk data, as a quarter of selling neared its final days.

The altcoins again led the way down. Ether fell 9.5% on the week to about $1,567, dogecoin dropped 11.7% to $0.073, Hyperliquid’s HYPE lost 10.6% and XRP slid 8.7% to $1.04. Solana held up better at $70, off 3.5%, and tron was the most resilient, down 1.5%.

The market has spent the week leaning on bitcoin’s relative steadiness while everything riskier fell faster.

The weekend marks the end of a weak first half, with just two days to go. Bitcoin is on track to finish the second quarter down about 12%, after a roughly 22% drop in the first, according to data from Coinglass. Ether has fared worse, down about 25% in the second quarter following a 29% first-quarter fall.

Key Takeaways

• BNB serves multiple functions including trading fee reductions, staking rewards, DeFi applications, gaming utilities, and payment solutions within Binance’s infrastructure
• Regular token burn events each quarter progressively decrease BNB’s circulating supply, aiming to halve the total from 200 million down to 100 million coins
• Conservative projections for 2031 place BNB between $1,200–$1,800, assuming steady market conditions without major disruptions
• Optimistic scenarios suggest $2,500–$4,000 valuations if BNB Chain gains widespread adoption and institutional interest accelerates
• Regulatory challenges pose the greatest threat, with pessimistic forecasts estimating $400–$600 price levels

Binance Coin has consistently ranked among the strongest-performing major cryptocurrencies in recent years. Projecting its value through 2031 requires examining several critical variables.

BNB maintains an intrinsic connection to the Binance platform. Countless traders hold the token to benefit from reduced transaction fees, participate in initial exchange offerings, cover network fees on BNB Chain, and utilize various Binance services.

This practical use case provides BNB with tangible value that distinguishes it from purely speculative digital assets.

Additionally, Binance implements a systematic quarterly burn mechanism. Every three months, a portion of tokens gets permanently eliminated from the available supply. The ultimate objective is reducing total token count by 50% — decreasing from 200 million to 100 million BNB.

This deflationary mechanism, combined with sustained market demand, forms the foundation of BNB’s long-term valuation thesis.

Moderate Scenario: $1,200 to $1,800

The most probable outcome for 2031 positions BNB trading within the $1,200 to $1,800 corridor. This forecast presumes Binance maintains its position among leading cryptocurrency exchanges worldwide while digital asset adoption continues expanding at moderate rates.

This valuation bracket corresponds to a market capitalization ranging from approximately $180 billion to $270 billion. Considering the trajectory of cryptocurrency markets, these figures remain achievable.

This scenario doesn’t demand extraordinary developments. It simply requires consistent user base expansion and ongoing supply reduction through burns.

Optimistic Scenario: $2,500 to $4,000

Under favorable conditions, BNB could climb to anywhere between $2,500 and $4,000. This projection assumes heightened institutional participation in cryptocurrency markets, BNB Chain establishing itself as a dominant infrastructure for decentralized applications and commerce, and continued aggressive token burning.

Such pricing would translate to market capitalization between $375 billion and $600 billion. While substantial, these figures don’t necessitate BNB surpassing Bitcoin or Ethereum in total value.

Primary Concern: Regulatory Pressure

BNB lacks the decentralized structure characteristic of Bitcoin. Its fortunes remain tightly bound to Binance’s corporate operations.

Should regulatory authorities impose restrictions on Binance across significant jurisdictions, exchange activity could decline substantially, pulling BNB demand downward correspondingly.

In a pessimistic scenario, BNB might trade between $400 and $600 by 2031.

The probability-adjusted price projection from this assessment centers around $1,650 for 2031. BNB’s future valuation depends more heavily on Binance’s operational success than on market speculation alone.

Coinbase and OKX are trying to win European crypto users after Binance moved to suspend several services in the European Union. The shift comes before the July 1 MiCA deadline, when crypto firms must hold approval from one EU state to keep serving the bloc.

The campaigns add a commercial race to a regulatory deadline. Binance has told users that access to some services will change because it has not secured a MiCA license in time.

Rivals move with transfer offers

As reported, Coinbase is using the opening to court users in Germany, France, Italy, Belgium, Poland, Sweden and the U.K. The exchange says it holds MiCA approval and is offering a “5% transfer bonus” for users who move funds before July 13.

The offer puts Coinbase’s regulated status at the center of its pitch. It also gives affected users a time-limited reason to move funds before Binance fully adjusts its European services.

OKX has launched a similar push for eligible users in the European Economic Area. The exchange is offering welcome rewards and “deposit matching of up to 8%” as it promotes itself as a licensed platform for long-term access in Europe.

OKX Europe General Manager Erald Ghoos said the exchange saw record new customer sign-ups ahead of the MiCA transition deadline. The rise suggests some users are already moving before the new rules take full effect.

Binance keeps withdrawal access open

Binance has said it will restrict new registrations and certain services in the EU after missing the licensing deadline. The exchange has also told users that their assets “remain accessible at all times.”

The company withdrew its Greek MiCA application and said it would seek approval in another EU country. Binance also said its European goals “remain the same” and that it expects to secure a license in the coming months.

As previously reported, Binance had already been exploring another EU approval route before the cutoff. Reports said regulators had raised concerns tied to compliance history, corporate structure and executive oversight.

The service pause does not mean a full exit from Europe. It means Binance cannot keep offering the same range of services to EU users without MiCA approval after the transition period ends.

MiCA changes Europe’s exchange market

MiCA creates one rulebook for crypto service providers across the EU. From July 1, firms without approval must stop serving EU users or manage an orderly wind-down.

The rule gives licensed exchanges a clear marketing edge. Coinbase, OKX, Kraken and other approved firms can present themselves as stable routes for users who want to keep trading under EU rules.

Customers now have to check eligibility, fees, asset support and local rules before transferring assets. Campaign rewards can lower moving costs, but users still need to compare custody, trading pairs and withdrawal terms.

Data shared by OKX Europe earlier showed many European crypto users were still using unlicensed exchanges weeks before the deadline. That created a large pool of users who may need to review their platform choices.

Coinbase’s Base layer-2 network faced two block production outages last week, and a post-mortem published by the Base engineering team attributes both incidents to a bug in the chain’s sequencer block-building logic.

According to the report, the problem allowed “stale journal state” to persist after a transaction validation failure—meaning the system did not properly clear account and storage slot data after an invalid transaction failed during execution. Because Base uses a single sequencer, the defect had system-wide consequences.

Key takeaways

• Base’s post-mortem says a sequencer bug caused “stale journal state” to remain after an execution failure, contributing to two outages.
• Both incidents stopped new layer-2 block production; sequencer and validator nodes could not move forward past the invalid block until recovery steps completed.
• The engineering team applied a patch to update journal state correctly during execution.
• Mitigation took longer than planned, partly due to unrelated infrastructure conditions, and a follow-on “race condition” after a system reset delayed full recovery for the second outage.
• Base says it will strengthen testing through “fuzz testing” and work toward “graceful recovery” to avoid manual validator restarts in future incidents.

What went wrong in Base’s sequencer

In its Saturday post-mortem, the Base engineering team described how the system handled an invalid transaction received by the block builder. The transaction failed during execution “as expected,” the team said—but the sequencer did not clear the journal state associated with the accounts and storage slots that had been accessed.

That lingering state, the report explains, stemmed from sequencer logic that built blocks while leaving “stale journal state” intact. In typical operation, clearing or rolling back intermediate state is essential to ensure subsequent blocks are constructed from a clean execution context. Here, the failure to do so prevented normal progression.

Two outages, tied to the same failure path

Base mainnet suffered two separate block production outages on Thursday and Friday, according to the post-mortem. The first incident lasted 116 minutes, while the second was shorter at 20 minutes.

In both events, the practical outcome was the same: a complete halt in new layer-2 block creation. The sequencer and validator nodes were unable to progress past the invalid block until sequencing was restored, effectively freezing the chain’s ability to finalize new blocks.

The team implemented a fix by patching the sequencers so journal state is properly updated during execution. However, the report notes that the time required to mitigate the problem exceeded expectations “due to infrastructure conditions unrelated to the original bug.” That distinction matters for operators and builders watching for operational reliability, because it suggests the initial logic flaw was not the only factor affecting service restoration.

A follow-on “race condition” delayed full recovery

The post-mortem also points to additional complexity after a system reset. It states that a “race condition” occurred during recovery, which prevented the sequencers from catching up after the restart—contributing to the second outage.

This kind of sequencing delay is particularly important for layer-2 chains that rely on correct synchronization between components. Even after patching the underlying logic, if the system cannot re-align its execution pipeline cleanly, validators may remain blocked waiting for proper sequencer outputs. Base’s report indicates this is what happened in the follow-up period.

Sequencer centralization raises the stakes

Base is designed with a single sequencer, as the post-mortem and the team’s public communications emphasize. That architecture makes the sequencer a critical dependency: when the sequencer stalls or encounters a logic failure, the chain’s block production can stop.

This is not a theoretical risk. The report notes that outages tied to sequencer behavior have also affected other layer-2 networks, including Arbitrum, OP Mainnet, and zkSync Era. With Base, the single-sequencer model means a bug in block construction logic can become immediately visible to users across the network.

What Base plans to change next

Looking ahead, the engineering team outlined two forward-looking measures aimed at reducing the odds of similar incidents and improving recovery speed.

First, it plans to improve protocol “fuzz testing,” a technique that tests systems by generating large volumes of random, malformed, or unexpected inputs. For blockchain execution and sequencing code paths—where edge cases can trigger state inconsistencies—fuzzing is often used to uncover failure modes that normal testing may miss.

Second, the team intends to build “graceful recovery,” aiming to prevent validators from requiring manual restarts during future incidents. The operational goal is straightforward: even when something goes wrong, systems should return to service without extended human intervention or prolonged uncertainty.

Base has seen similar issues before

This week’s outages follow earlier sequencer-related disruptions on Base. The post-mortem indicates Base stopped producing blocks for 17 minutes in September 2024 and for around half an hour in August 2025—another reminder that sequencer reliability remains an ongoing focus area for the network.

In terms of scale, Base is described as the second-largest layer-2 network by total value secured, which is just under $11 billion, according to L2beat’s data. For investors and users, that positioning increases the significance of uptime and recovery mechanics: disruptions may affect activity and settlement on the network, especially during periods when other infrastructure remains stable.

As Base rolls out its planned testing and recovery improvements, the next key signal to watch is whether the fixes reduce both the likelihood of state-related sequencing failures and the time needed to fully recover after resets—particularly if future incidents still surface around tricky execution-state edge cases.