Apple shares remain under close scrutiny after several notable developments. On 10 August, Jefferies downgraded the stock from Hold to Underperform and lowered its price target from $285.56 to $263.66. The investment bank suggested that Apple may have abandoned plans for an all-glass iPhone intended to mark the product line’s 20th anniversary due to manufacturing challenges. According to Jefferies, this decision could limit the company’s ability to increase average selling prices at a time when memory component costs are rising.

At the same time, Apple announced the opening of a new manufacturing facility in Houston, where Mac mini production is expected to begin at a later stage. The project forms part of the company’s broader $600 billion initiative aimed at expanding its manufacturing footprint across the United States.

Technical Analysis of Apple

The four-hour chart highlights a significant technical event that occurred on 31 July, when the price moved below a rising trendline through a gap accompanied by trading volume well above recent averages. Despite the strength of that move, the breakdown has not yet developed into a sustained decline.

Instead, the stock has entered a consolidation phase, creating a well-defined market profile. Apple is currently trading between the Point of Control (POC) at $305.50 and the lower boundary of the profile at $300.00, while testing the POC area from below. Beneath the current consolidation zone, the next major support level can be found around $273.50.

Should the trend breakdown ultimately fail and buyers regain control, attention would shift towards two key resistance areas. The first is the upper boundary of the profile at $326.00, followed by a more substantial resistance zone near $344.00.

The RSI + MAs indicator currently stands at 42, 39 and 45. Both the RSI and the fast-moving average remain slightly below the neutral zone, while the slower moving average has yet to cross beneath the lower threshold, indicating that bearish momentum has not been fully confirmed.

Key Takeaways

Apple’s current sideways movement around the POC reflects a period of balance following the high-volume gap that disrupted the previous uptrend. While the market has yet to confirm a decisive bearish breakout, buyers have also been unable to push the stock back into a clear upward trajectory.

The divergence between the faster and slower components of the RSI + MAs indicator leaves the technical outlook unresolved, suggesting that the next directional move will likely depend on whether the price can either reclaim the upper part of the profile or break convincingly below the current consolidation range.

Buy and sell stocks of the world’s biggest publicly-listed companies with CFDs on FXOpen’s trading platform. Open your FXOpen account now or learn more about trading share CFDs with FXOpen.

This article represents the opinion of the Companies operating under the FXOpen brand only. It is not to be construed as an offer, solicitation, or recommendation with respect to products and services provided by the Companies operating under the FXOpen brand, nor is it to be considered financial advice.

Crypto has spent years building faster blockchains, cheaper transactions, decentralized applications, and increasingly sophisticated financial protocols. Yet one of the industry’s biggest challenges remains surprisingly fundamental

Building on crypto is still harder than it should be.

For crypto to move from an industry dominated by early adopters and specialized developers into a technology used by millions—or billions of people—it needs more than better protocols. It needs better developer infrastructure.

The next phase of blockchain growth may depend less on creating another Layer 1 and more on making it dramatically easier for developers to build, test, deploy, monitor, and scale applications on existing networks.

The Developer Experience Problem

In traditional software development, developers have access to mature tools for almost everything.

They can use established cloud platforms, databases, authentication systems, payment APIs, monitoring tools, analytics platforms, testing frameworks, and deployment pipelines. Much of the complexity is hidden behind reliable abstractions.

Crypto is different.

A developer building a decentralized application may need to understand wallets, private keys, RPC providers, smart contracts, gas fees, chain-specific infrastructure, indexing, token standards, bridges, signatures, transaction finality, security assumptions, and multiple blockchain environments.

That creates a steep learning curve.

Instead of asking:

“What can I build?”

developers often have to ask:

“How do I make all these infrastructure components work together?”

That is a serious barrier to innovation.

Infrastructure Is the Invisible Layer of Crypto

Users rarely think about infrastructure.

When someone sends a message, they don’t care which database handles it. When they stream a video, they don’t think about content delivery networks. When they purchase something online, they don’t need to understand payment-processing infrastructure.

Crypto should eventually work the same way.

A user shouldn’t need to understand RPC endpoints, nonce management, transaction simulation, gas estimation, block confirmations, or chain abstraction simply to interact with an application.

Developers shouldn’t have to rebuild those systems for every project either.

The more infrastructure becomes standardized and invisible, the more developers can focus on product design and user experience.

RPC Infrastructure Needs to Become More Reliable

Remote Procedure Calls, or RPCs, are one of the fundamental interfaces between applications and blockchains.

Yet developers frequently deal with issues such as:

• Rate limits
• Unstable endpoints
• Network congestion
• Provider outages
• Latency
• Inconsistent responses
• Difficult debugging
• Chain-specific configurations

For a consumer application serving thousands or millions of users, infrastructure reliability isn’t optional.

Crypto applications need RPC infrastructure that feels more like mature cloud infrastructure: predictable, scalable, observable, and easy to integrate.

Better infrastructure providers can abstract much of this complexity away from developers.

Indexing Is Another Major Bottleneck

Blockchains are excellent at recording transactions, but retrieving meaningful application-level information from raw blockchain data can be complicated.

Imagine building a decentralized marketplace.

You may need to answer questions such as:

• What assets does a particular wallet own?
• What transactions occurred during a specific period?
• Which NFTs changed hands?
• What is the user’s historical activity?
• What events occurred across multiple contracts?
• What are the current balances and positions?

Developers often need specialized indexing infrastructure to transform blockchain data into something applications can efficiently query.

Better indexing tools could turn blockchain data into something closer to a traditional developer-friendly database experience.

That would significantly reduce development time.

Testing and Debugging Need a Revolution

Smart contracts are immutable once deployed in many environments.

That makes testing especially important.

A small mistake can result in financial losses, broken applications, or serious security vulnerabilities.

Developers therefore need powerful tools for:

Simulation → Testing → Security Analysis → Deployment → Monitoring

The industry needs better local blockchain environments, transaction simulation, automated security testing, debugging tools, and production monitoring.

Imagine being able to reproduce a complex on-chain transaction locally with a few clicks and understand exactly why it failed.

That kind of developer experience could dramatically improve both productivity and security.

Wallet Infrastructure Should Become Invisible

Wallets are another major source of friction.

Traditional applications allow users to create an account with an email address, phone number, or social login.

Crypto often introduces concepts such as:

• Seed phrases
• Private keys
• Network switching
• Gas management
• Signature requests
• Transaction approvals

These mechanisms are important for self-custody, but developers need better ways to integrate them into applications.

The goal shouldn’t necessarily be to eliminate wallets.

The goal should be to make wallets easier to use without sacrificing security or user control.

Account abstraction, smart wallets, passkeys, embedded wallets, and better transaction flows are moving the ecosystem in this direction.

Chain Abstraction Could Change Everything

One of the biggest infrastructure challenges is fragmentation.

Crypto users and developers increasingly interact with multiple chains.

Ethereum, Layer 2 networks, Solana, appchains, alternative Layer 1s, and specialized networks can each have different architectures, tooling, transaction models, and developer environments.

For developers, supporting multiple networks can mean maintaining multiple infrastructure stacks.

For users, it can mean confusing network selection and asset management.

Better chain abstraction could allow applications to interact with multiple blockchain environments through a much simpler interface.

Instead of forcing developers to think about every chain individually, infrastructure could handle much of the complexity underneath.

The blockchain becomes the backend. The application becomes the product.

That’s a much more scalable model.

Security Must Be Built Into the Infrastructure

Crypto has another problem that traditional software can sometimes avoid at the same scale:

The infrastructure can directly control financial assets.

A vulnerable smart contract isn’t merely a software bug. It can become a financial catastrophe.

Developer infrastructure therefore needs security to be embedded throughout the development lifecycle.

That includes:

• Automated smart-contract analysis
• Dependency monitoring
• Transaction simulation
• Runtime monitoring
• Threat detection
• Permission analysis
• Key-management systems
• Automated alerts
• Formal verification tools

Security shouldn’t be something developers remember at the end of the project.

It should be integrated from the beginning.

Better Infrastructure Could Unlock More Developers

The crypto industry has often focused on attracting users.

But there is another equally important growth strategy:

Make it easier for developers to build things users actually want.

A developer shouldn’t need years of blockchain-specific experience to create a crypto-enabled application.

Imagine a world where a developer could integrate blockchain functionality using a few familiar APIs.

Want stablecoin payments?

Use an API.

Want tokenized assets?

Use an SDK.

Want wallet authentication?

Use an authentication layer.

Want on-chain analytics?

Query an indexed data service.

Want to deploy across multiple chains?

Use a unified deployment framework.

That is how crypto becomes accessible to the broader software-development community.

Infrastructure Is Becoming a Competitive Advantage

As blockchain networks become increasingly similar in areas such as transaction costs and performance, developer infrastructure could become a major differentiator.

A technically impressive blockchain is not enough if developers hate building on it.

A network with excellent documentation, SDKs, debugging tools, indexing, analytics, security infrastructure, and reliable APIs can potentially attract more developers—even if its raw technical specifications aren’t dramatically different from competitors.

This creates a powerful flywheel:

Better Infrastructure → More Developers → More Applications → Better User Experience → More Users → More Economic Activity

And more economic activity creates demand for even better infrastructure.

The Next Crypto Breakthrough May Not Be Another Blockchain

Crypto has historically celebrated protocol launches.

New chains receive attention. New consensus mechanisms generate headlines. New token standards create excitement.

But the next breakthrough may be less visible.

It could be an infrastructure layer that makes blockchain development dramatically simpler.

The biggest crypto innovation might not be another chain competing for blockspace.

It could be the tools that allow developers to stop thinking about blockspace altogether.

That’s the paradox of great infrastructure: when it works perfectly, nobody notices it.

What Better Developer Infrastructure Could Look Like

The ideal crypto developer stack could eventually resemble modern cloud development.

A developer could have:

One unified API layer
Connect to multiple blockchain networks without managing dozens of endpoints.

Powerful indexing
Query blockchain data without building custom data pipelines.

Built-in simulation
Test transactions before they reach production.

Integrated security
Automatically detect vulnerabilities and suspicious behavior.

Simple wallet infrastructure

Provide secure authentication without forcing users through confusing workflows.

Cross-chain tooling
Build applications that operate across networks without maintaining completely separate systems.

Real-time observability
Monitor contracts, transactions, users, and application health from a single dashboard.

One-click deployment
Move from development to production with significantly less operational complexity.

When these pieces work together, blockchain development begins to look less like a specialized discipline and more like ordinary software engineering.

The Real Goal: Hide the Complexity

Crypto doesn’t need to eliminate complexity.

It needs to move complexity away from developers and users.

The internet succeeded partly because developers didn’t have to understand every layer of networking before building websites and applications.

Cloud computing succeeded because developers didn’t need to operate physical servers to launch software.

Crypto can follow the same path.

The underlying blockchain technology can remain highly sophisticated while the developer experience becomes remarkably simple.

That is the infrastructure revolution crypto needs.

Final Thoughts

The future of crypto won’t be determined solely by transaction speed, token economics, or the number of blockchains competing for users.

It will also depend on how easy it is to build on those networks.

Better developer infrastructure can reduce complexity, improve security, accelerate experimentation, and open blockchain development to a much larger pool of software engineers.

The winning crypto ecosystems may ultimately be the ones that make developers forget they’re building on blockchain at all.

Because when infrastructure becomes invisible, innovation becomes visible.

Crypto doesn’t just need more developers.

It needs to make development easier.

And that may be one of the most important infrastructure challenges—and opportunities—of the next decade.

REQUEST AN ARTICLE

The Hyperliquid Policy Center and Douro Labs submitted a joint comment letter to the U.S. Securities and Exchange Commission on Aug. 17 supporting the proposed repeal of Regulation NMS Rule 611.

Rule 611, commonly called the trade through rule, generally prevents trading centers from executing orders at prices worse than protected quotations displayed elsewhere. The framework uses consolidated market data to establish the National Best Bid and Offer, or NBBO.

HPC and Douro argued in their 22 page letter that this quotation system does not map cleanly onto automated market makers, onchain order books and markets operating continuously outside traditional exchange hours.

Douro Labs is a core contributor to Pyth Network. HPC is an independent advocacy organization focused on creating a regulated path for U.S. users to access onchain markets, including markets available through Hyperliquid.

SEC Rule 611 repeal would change order protection

The SEC proposed rescinding Rule 611 and Rule 610(e) on June 11. Rule 610(e) restricts locked and crossed quotations, where bids equal or exceed available offers.

The agency’s proposal would also remove related definitions from Rule 600 and make corresponding changes elsewhere in Regulation NMS. The SEC has not adopted the proposal, meaning the existing rules remain in force.

Rule 611 was adopted as part of Regulation NMS in 2005. It requires trading centers to establish procedures designed to prevent executions at prices inferior to protected quotations available through other connected venues.

SEC Chairman Paul Atkins said in June that the proposal was intended to simplify market structure and reduce costs. He also said the agency would take a “careful, deliberative approach” while reviewing public feedback.

HPC and Douro supported the repeal “without qualification.” They argued that the current framework assumes executable interest appears as firm quotations collected by securities information processors.

Automated market makers work differently. They calculate an execution price from a liquidity pool when an order is placed. Some onchain central limit order books display bids and offers, but those prices are not currently incorporated into the consolidated feeds used to calculate the NBBO.

Onchain markets require updated best execution guidance

Repealing Rule 611 would not remove brokers’ duty to seek favorable execution terms for customers. HPC and Douro said that obligation should remain the central investor protection standard.

Their letter asked the SEC to coordinate with the Financial Industry Regulatory Authority on principles based guidance for onchain execution. The groups said existing guidance does not fully address network fees, atomic settlement, transaction ordering risks or markets operating when the NBBO is unavailable.

An onchain venue may also calculate prices based on the size of an order and the liquidity available when it executes. As a result, one displayed reference price may not capture the final cost that a customer receives.

The groups proposed evaluating the effective execution price after accounting for protocol charges, network fees and market movement caused by the order. Settlement speed and reduced counterparty settlement risk could also form part of that assessment, according to the letter.

HPC and Douro further asked regulators to recognize qualifying independent reference prices when an NBBO does not exist or does not reflect onchain conditions. They said such benchmarks should use transparent methodologies and resist manipulation.

The filing cited Pyth as one possible model. Pyth receives pricing information from exchanges and trading firms involved in price formation, then publishes aggregated data onchain. The proposal did not request that the SEC endorse Pyth as the mandatory provider.

Tokenized stocks would stay within securities rules

HPC and Douro asked the SEC to confirm that tokenized versions of NMS stocks remain inside Regulation NMS and the wider best execution framework. Under that approach, investor protections would not depend on whether ownership records use a blockchain.

The request comes as tokenized stock products expand across crypto networks. As previously reported, Ondo brought 35 tokenized stocks and ETFs onto HyperEVM in June.

Such products can use different legal structures. Some represent claims against an issuer or special purpose entity rather than direct legal ownership of the underlying company shares. The structure must therefore be assessed separately from the blockchain used for trading or settlement.

In related coverage, an onchain platform launched trading for more than 70 tokenized equities across Ethereum and Solana. That system uses public market information to help keep token prices aligned with the underlying shares.

HPC and Douro also argued that onchain transactions may qualify for Rule 611’s existing exception for trades that do not use “regular way” settlement terms. They asked the SEC to confirm that interpretation if the repeal is delayed or rejected. This remains the groups’ legal position, not an SEC determination.

The SEC must decide whether to adopt the repeal

The public comment period for file S7-2026-20 closed on Aug. 17, according to the SEC docket. The joint submission arrived on the deadline alongside comments from exchanges, investment firms, trade groups and other market participants.

The SEC will now review the responses before deciding whether to adopt, revise or withdraw the proposal. A repeal would require a final Commission vote and an adopting release establishing the final text and effective date.

Not all commenters support removing the rule. Some responses warned that repeal could weaken an objective price protection standard and place greater reliance on individual brokers’ routing systems.

SEC Commissioner Mark Uyeda also acknowledged those questions in a June statement. He said removing Rule 611 could raise issues involving best execution, transparency, trading mechanics and investor confidence.

The next decision rests with the SEC. No final vote, adoption date or implementation timetable had been announced as of Aug. 18.

The Ethereum Foundation has warned that wallets, indexers and gas estimators could break as Glamsterdam changes the 21,000-gas assumption for some ETH transfers, with the upgrade due to activate on the Platåberget testnet on Aug. 20.

The Ethereum Foundation’s Protocol DevOps team said on Aug. 17 that any tool relying on a hardcoded maximum gas limit “will break,” naming wallets, indexers and gas estimators among the software likely to be affected. The team urged application and infrastructure developers to test their systems on Platåberget, a public testnet designed to stay online for several months.

Forkcast data shows Platåberget launched on Aug. 13, giving developers an early environment for Glamsterdam before the upgrade moves to Sepolia and Hoodi. The Glamsterdam fork is scheduled to activate on Platåberget on Aug. 20, according to the foundation, with public validator and builder deposits available as part of the testing process.

Glamsterdam could break hardcoded gas assumptions

Under the planned gas repricing package, the foundation said software can no longer safely assume that Ethereum has a single fixed gas ceiling or that common operations will continue to cost the same amount in every case. The changes are designed around a roughly 200 million gas floor and alter the price of individual operations as well as assumptions tied to the block gas limit.

For application developers, the immediate issue is software that sets fixed boundaries when estimating transaction costs. The Protocol DevOps team said such systems need to be reviewed before Glamsterdam reaches mainnet because the repricing touches wallets, indexers and gas estimators across the network.

The warning follows June 17 Glamsterdam upgrade coverage from crypto.news, which reported that Ethereum developers were already testing the full set of planned EIPs on development networks. At the time, Ethereum Foundation developer Parithosh Jayanthi said the upgrade would change the cost of actions on Ethereum, with high-level computation becoming cheaper while state becomes more expensive.

During the same testing phase, Jayanthi said developers had made “massive progress” but noted that no fixed mainnet timeline had been set. Deployment would depend on the results of testing and whether Ethereum client teams were ready to support the new rules.

EIP-8037 changes how new state is priced

A central part of the warning concerns EIP-8037, which introduces a separate state-gas dimension for operations that create new state. The foundation said creating an account, deploying code or writing a new storage slot will be metered at a fixed cost per state byte and charged at runtime.

Because of that change, a basic ETH transfer will not always carry the same gas cost. Sending ETH to an account that already exists will continue to cost 21,000 gas, with the amount broken into the base transaction cost, cold account access and the value-transfer cost. Sending funds to an address that does not yet exist will also incur a state-gas charge tied to creating the new account.

Developers should therefore revisit applications that treat 21,000 gas as sufficient for every ETH transfer, the Protocol DevOps team said. Gas estimators built around only one gas dimension may also return incorrect estimates once new state is metered separately.

EIP-8037 had already moved close to its final form by May. A May 11 protocol development report said the proposal had reached final-draft status and was being parameterised on a Glamsterdam development network. At the time, its cost-per-state-byte model was designed around limiting annual state growth to roughly 60 GiB at a 300 million gas block limit.

Under the parameters reported in May, new account creation could become roughly 8.5 times more expensive, while contract deployment costs could rise about tenfold. Separate metering for code deposits was designed to keep large contracts deployable, including code-heavy decentralised finance applications.

The state-gas model also changes where Ethereum accounts for the cost of permanent state. The foundation said account creation, new storage slots and deployed code will incur charges based on the amount of new state created, making applications that frequently add permanent data particularly important targets for testing before mainnet deployment.

Ethereum Glamsterdam upgrade also changes block production

Gas repricing is only one part of Glamsterdam. The foundation said the fork also includes enshrined proposer-builder separation, or ePBS, which changes how blocks are built, proposed and validated inside Ethereum’s core protocol.

Under ePBS, the split between the block-building process and the proposer role is incorporated into the protocol, alongside a new builder API flow and payload-timeliness checks. Infrastructure tied to Ethereum’s block-production and validation pipeline should expect to be affected, according to the foundation.

With Platåberget open for public participation, the Protocol DevOps team has encouraged solo stakers, distributed validator technology projects, custom software operators and large staking providers to test their infrastructure. The testnet allows users to deposit new validators and experiment with validator and builder-deposit workflows before the same changes move to longer-lived networks.

Block-Level Access Lists form another major component of the fork. The foundation said the lists will record state locations accessed during execution and post-transaction state changes, with BAL data stored separately from the block body and exchanged between execution-layer peers through the eth/71 networking protocol.

Earlier June reporting said the access-list design gives Ethereum clients advance information about which accounts and smart-contract data a block will use. The system can allow nodes to preload required data and process transactions in parallel when transactions do not access the same state, according to Ethereum.org.

Glamsterdam will also increase size limits for deployed contracts and initialisation code. The foundation said the maximum deployed contract size will rise from 24 KiB to 64 KiB, while the maximum initcode size will increase from 48 KiB to 128 KiB. Forward-compatible consensus data structures are also included in the planned fork.

Platåberget gives developers a longer testing window

Unlike the shorter development networks used during earlier Glamsterdam work, Platåberget is intended to remain available for several months. The Protocol DevOps team said the longer lifespan should give developers time to test post-Glamsterdam behaviour and identify failures before the changes reach Sepolia and Hoodi.

Its validator set is relatively small but open to public participation. For the initial testing period, the foundation has listed container images for consensus clients including Lighthouse, Lodestar, Nimbus, Prysm, Teku and Grandine, alongside execution clients including Besu, Geth, Erigon, Nethermind, Reth, NimbusEL and Ethrex. Tagged client releases remain optional while development teams prepare their own builds.

After feedback from Platåberget has been incorporated into specifications and client software, a non-finality devnet is expected to follow within the month to test difficult consensus scenarios, according to the foundation. Sepolia and Hoodi are due to receive Glamsterdam after the development networks remain stable, while Ethereum mainnet activation will follow successful upgrades on the long-lived testnets.

Development on Ethereum’s next scheduled fork is also proceeding separately. An Aug. 16 Hegotá planning report said developers were considering 66 proposals for the 2027 upgrade, although Fork Choice enforced Inclusion Lists was the only EIP formally scheduled for inclusion at the time.

Several proposals under review for Hegotá concern future gas and state pricing as Ethereum increases Layer 1 capacity. EIP-8368, for example, would recalibrate state-creation pricing if the block gas limit rises beyond the reference level used by Glamsterdam, while developers have discussed preparing Ethereum for a possible path towards a 600 million gas limit.

BitMine Immersion Technologies added 9,926 Ethereum over the week ending Aug. 16, raising its reported holdings to 5,815,164 ETH.

The U.S. company valued the tokens at approximately $11 billion using an ETH price of $1,893. BitMine said the position represented 4.8% of Ethereum’s estimated 120.7 million supply in its Aug. 17 release.

BMNR stock closed 3.68% higher at $18.73 on the New York Stock Exchange on Aug. 17. It gained another 0.37% to $18.80 in after hours trading, according to Google Finance data.

BitMine stock opened Monday at $18.20 and traded between $18.11 and $19.00. Approximately 30.95 million shares changed hands, compared with its reported average volume of 32.51 million.

Google Finance placed BitMine’s market capitalization at approximately $11.3 billion, based on 603.23 million outstanding shares. The market value was close to the company’s reported $11.4 billion in crypto, cash, marketable securities and other investments.

BMNR remained well below its 52 week high of $65.60. The stock was also above its 52 week low of $12.80. Those figures show that BMNR has experienced a wide trading range while BitMine expanded its Ethereum strategy.

BitMine ETH holdings approach the 5% target

BitMine calls its objective of holding 5% of Ethereum’s supply the “Alchemy of 5%.” Using the company’s stated supply estimate, the target would equal approximately 6.035 million ETH.

The current balance leaves BitMine roughly 219,836 ETH short. Its holdings represent about 96.4% of the tokens required. Changes in Ethereum’s supply could alter the final amount needed.

BitMine has reported weekly Ethereum purchases since adopting its treasury strategy on June 30, 2025. As previously reported, its Ethereum balance reached 5.74 million tokens in early July.

The latest acquisition was smaller than several earlier weekly purchases. In related coverage, the company previously added more than 100,000 ETH during a single week in May.

BitMine did not disclose the average purchase price for the latest 9,926 ETH. It also provided no deadline for completing its 5% supply target.

Staked ETH produces variable rewards

BitMine reported that 5,067,309 ETH was staked as of Aug. 16. The tokens were worth about $9.59 billion at the company’s reference price and represented 87.1% of its holdings.

Approximately 747,855 ETH remained outside staking based on the disclosed figures. BitMine said some of its tokens are staked through MAVAN, its Made in America Validator Network, alongside other staking partners.

The company projected $250 million in annualized staking revenue using a seven day yield of 2.61%. This is a company estimate rather than guaranteed revenue. Ethereum staking returns vary with validator participation, network activity, execution rewards and other factors.

Applying the same yield to BitMine’s entire ETH balance would produce approximately $287 million annually at the cited price. BitMine described that amount as a projection for when its treasury is fully staked.

The staking position has grown rapidly since December. As crypto.news reported, BitMine initially deposited 74,880 ETH for staking before expanding the program during 2026.

Share repurchases reach 20.8 million

BitMine repurchased 1.7 million common shares during the latest week. That raised total repurchases since July 1 to more than 20.8 million shares, according to the company.

The board increased its repurchase authorization from $1 million to $4 billion in April, an SEC filing shows. An authorization sets a spending limit but does not require BitMine to use the entire amount.

The announcement did not disclose the average price paid for the latest shares or the total amount spent. At Monday’s closing price, 1.7 million shares would have a market value of approximately $31.8 million. That calculation is an estimate, not the company’s reported cost.

Repurchases reduce the share count when the acquired stock is retired or held as treasury stock. However, future equity issuance or preferred stock conversions could offset that reduction.

The reported portfolio is valued at $11.4 billion

BitMine valued its combined crypto, cash, marketable securities and other investments at $11.4 billion as of Aug. 16. In addition to Ethereum, the company reported holding 210 Bitcoin and $78 million in cash and marketable securities.

The total included a $180 million position in Beast Industries and a $73 million stake in Nasdaq listed Eightco Holdings. BitMine refers to those investments as “moonshots.”

The reported total is not necessarily equivalent to assets calculated under accounting rules. Its value can also change quickly because Ethereum accounts for most of the portfolio.

Investors will next be watching BitMine’s SEC disclosures for further information about the repurchases and investment valuations. The company’s weekly updates will also show whether it continues acquiring ETH as it approaches its 5% target.

Binance reportedly plans to apply for authorization from the United Kingdom’s Financial Conduct Authority, seeking a potential return to the British market when the country’s comprehensive crypto rules begin in 2027.

The exchange intends to submit an application after the FCA opens its authorization gateway on Sept. 30, according to an Aug. 15 report from The Telegraph. Binance has not publicly confirmed that it filed an application or identified which legal entity would apply.

A successful application could allow Binance to resume regulated services for UK residents after the new framework takes effect on Oct. 25, 2027. Approval is not automatic, and the FCA has not said it expects to authorize Binance.

The regulator’s existing restrictions on Binance Markets Limited remain in force.

Binance must address restrictions dating from 2021

The FCA imposed requirements on Binance Markets Limited in June 2021, preventing the company from conducting regulated activities without the regulator’s prior written consent.

The watchdog’s current warning states that no other Binance Group entity holds UK authorization, registration or a license to conduct regulated activities in the country.

The FCA previously said Binance Markets Limited was not capable of being effectively supervised. It cited the wider group’s structure and complex, high risk products among its concerns.

Binance later withdrew an application to cancel unused UK permissions in 2023. The move left no Binance entity authorized to operate a regulated cryptocurrency business in Britain.

The exchange also stopped accepting new UK customers in October 2023 after the FCA introduced expanded financial promotion rules. Binance initially relied on an authorized company, Rebuilding Society, to approve its UK marketing.

The FCA later restricted Rebuilding Society’s ability to approve crypto promotions. Binance then announced through an official update that it would pause new registrations while searching for another compliant arrangement.

The FCA application window opens September 30

Britain’s new crypto authorization window will run from Sept. 30, 2026, through Feb. 28, 2027. The full regulatory regime starts on Oct. 25, 2027.

As crypto.news reported, companies operating in Britain must obtain fresh authorization before providing activities covered by the new framework. Existing registrations under anti-money laundering rules will not convert automatically.

Firms that apply within the window may qualify for transitional arrangements while the FCA assesses their applications. Those submitting applications after Feb. 28 will not receive the same protection and may need to stop relevant services until authorization is granted.

The FCA encourages applicants to file early. Its guidance says earlier applications provide more time for assessment and increase the period during which eligible companies can rely on transitional provisions.

An application is not a temporary license. Applicants must satisfy the regulator before receiving permission, and companies cannot assume they will be approved because they met the filing deadline.

FCA authorization would impose broader requirements

The new framework expands the FCA’s oversight beyond financial promotions and anti-money laundering registration. It covers trading platforms, dealing, arranging transactions, custody, staking, lending and certain stablecoin activities.

Authorized companies must follow prudential rules, operational resilience standards and financial crime controls. The framework also applies the Consumer Duty and the Senior Managers and Certification Regime to businesses conducting regulated crypto activities.

Trading platforms will face requirements involving disclosures, market abuse controls and asset admission standards. Custodians must meet rules governing client asset ownership, record keeping, reconciliation and private key management.

David Geale, the FCA’s executive director for payments and digital finance, said the regime would hold crypto companies to “similar standards” as other British financial services businesses.

The application review is therefore expected to examine Binance’s governance, ownership, compliance systems and ability to meet continuing supervisory requirements. The FCA can reject applicants that fail its minimum threshold or “fit and proper” tests.

Binance has not disclosed which UK services it would seek permission to offer. It also has not said whether a relaunch would cover spot trading, custody, staking or other products.

Binance faces competition from registered UK firms

Binance would enter a market where several competitors already hold FCA registrations under the existing anti-money laundering framework.

Coinbase, for example, secured permission to offer cryptocurrency services directly through its British entity in February 2025. IG Digital Assets later joined the FCA’s cryptoasset register.

Those registrations do not guarantee authorization under the 2027 framework. Every company conducting newly regulated activities must submit a fresh application or request a variation of its existing permissions.

Binance’s UK effort also follows regulatory setbacks elsewhere in Europe. The exchange withdrew its Greek application for authorization under the European Union’s Markets in Crypto Assets regulation in June.

In related coverage, Binance suspended most services for European Union residents after missing the licensing deadline. The company said it remained committed to finding another route into the European market.

The UK process is separate from the EU framework. FCA authorization would only address Binance’s position under British law and would not provide operating rights across the European Union.

A filing and FCA decision come next

The first verifiable development will be Binance’s submission of an application after Sept. 30. Neither the exchange nor the FCA has published an application notice.

The regulator does not guarantee that applications submitted during the window will receive decisions before October 2027. Eligible firms can continue specified activities under transitional provisions while awaiting a determination, but only if they satisfy the relevant conditions.

A Binance relaunch would require an affirmative FCA decision and any necessary removal or amendment of existing restrictions on Binance Markets Limited. The legal entity receiving authorization would also need to appear on the FCA register.

Until those steps occur, the reported application remains a plan rather than an approved UK return. Existing consumers should not interpret it as evidence that Binance currently holds an FCA license.