Almost 4,000 Bitcoin were moved out of Liquid's reserve on September 6 through a withdrawal that the network approved despite the private keys used to authorize it not being stolen. Software had accepted a withdrawal that should never have qualified. Liquid allows users to move Bitcoin-backed tokens on a separate blockchain designed for faster, more private transactions. Bitcoin enters a shared reserve, and users receive tokens called L-BTC, each intended to represent one BTC. When users redeem those tokens, the corresponding coins are released from the reserve. According to TRM Labs' reconstruction of the attack, attackers exploited a software flaw to create L-BTC without depositing the backing Bitcoin, then exchanged those tokens for real coins. The operators responsible for approving withdrawals trusted information that was incorrect. The incident highlights how private keys, which authorize transactions, can still be used to approve unauthorized payments when software malfunctions. Multiple parties may sign off on a withdrawal while referencing the same erroneous account balance. Once such an error occurs, attention shifts from technical explanation to the broader question of who bears the financial responsibility. Crypto insurance can offer some relief, but policy terms often limit its effectiveness. The company may be insured for specific losses or legal claims, yet still fail to provide full repayment to all affected customers. Insurance payouts might fall short of the value needed to restore the missing assets. Understanding the gap between an insurer's payment and a customer's account requires examining the process between a company's claim and the individual's balance. The term 'financial protection' can therefore mean something different than customers expect. The company holds insurance coverage, but the extent of that coverage for end users depends on policy details and legal arrangements. Insurance typically covers the institution holding the assets, not necessarily the individual account holders. Direct claims by customers and the speed of compensation depend on contractual obligations and available funds. Liquid's case illustrates how asset recovery and accountability are distinct processes. Blockchain analysis by Bitquery showed that attackers returned 3,400 BTC the following day. On September 12, Blockstream declined a request for a bounty related to the incident. Each returned coin reduces the shortfall in the reserve, but repayment by an attacker does not determine who must cover any remaining deficit. That obligation is governed by existing commitments, not by blockchain records alone. Compensation for lost assets does not always equate to receiving equivalent cryptocurrency. A policy might promise repayment in fiat value, which could purchase fewer coins if market prices have risen. Conversely, a drop in price could mean the restored amount buys more. The agreement governing repayment defines who assumes the risk of price fluctuations. Some arrangements specify replacement in cryptocurrency units, while others use fixed dollar valuations. Recovered assets must also be allocated among eligible claimants, a process separate from simply restoring them to wallets. Delays in resolution can prevent users from accessing funds for extended periods, creating additional hardship beyond the loss itself. Reimbursement for lost functionality requires separate consideration. The incident underscores limitations in advising users to 'do their own research,' as few can audit the software validating their withdrawals or negotiate insurance terms. Financial service providers should clarify reimbursement policies as transparently as they explain fees, specifying which losses they commit to covering and how shortfalls will be addressed. Customers need to understand whether protection is backed by sufficient reserves. The root cause of Liquid's shortfall was software accepting invalid withdrawal requests. The broader lesson for asset custodians is that security reduces the likelihood of loss, but financial safeguards determine how losses are distributed. Clear communication about risk allocation remains essential for users relying on third-party platforms.

The European Commission has opened a public consultation on how staking services should be treated under its Markets in Crypto-Assets (MiCA) framework, asking whether the activity warrants dedicated rules. The consultation, which closes on Sept. 30 at 23:59 CEST, does not propose a new licensing regime or capital requirement, but it signals that regulators are considering a separate staking framework that could affect both users and service providers.

MiCA already governs custodial staking, requiring firms that hold client assets to meet specific safeguards, including separation of client crypto from company holdings and procedures for returning assets in insolvency. The Commission now wants to know whether staking, which began as a technical network function, has grown complex enough to merit its own regulatory category.

Staking originally involved participants locking assets to run validator software and earn rewards for securing proof‑of‑stake blockchains. When exchanges, custodians and other platforms began offering staking as a service, the activity started to resemble traditional financial services and attracted regulatory attention. Under current guidance, a company that takes custody of a customer’s crypto and stakes it on the customer’s behalf falls under MiCA’s custody rules, even if the customer retains control of the withdrawal key.

The distinction matters because many staking models now exist. Direct staking by an individual who runs a validator with their own 32 ETH involves no intermediary, while liquid‑staking platforms such as Lido aggregate large amounts of staked assets and issue derivative tokens that can be traded or used as collateral. A joint report by the European Banking Authority and the European Securities and Markets Authority estimated the liquid‑staking market at $44 billion in October 2024, with Lido accounting for roughly $25 billion.

Regulators are concerned about several risks associated with these models. Withdrawal periods can be lengthy, validators may be slashed, and reward calculations are often opaque. Providers may also retain a portion of rewards, and liquid‑staking tokens can trade at a premium or discount to the underlying asset, creating additional leverage when used as collateral. A dedicated staking regime could require providers to disclose who bears these risks and how they are managed.

If Europe adopts a separate staking framework, larger custodians and exchanges would likely absorb the added compliance costs, while smaller validator operators might find it uneconomical to serve European customers directly. This could concentrate staking services in the hands of a few well‑resourced firms, potentially influencing how validator sets are chosen and how delegated stake is distributed across networks.

The shift would also affect end‑users. Retail participants who prefer a simple, one‑click staking experience might benefit from clearer rules on withdrawal delays, fee structures and loss allocation. Institutional investors, who have hesitated to engage with staking because of legal‑title and liability uncertainties, could find the regulatory environment more predictable, though higher compliance costs could translate into lower net yields.

Europe is not starting from a regulatory vacuum. Existing MiCA provisions already impose obligations on custodians, and the European Securities and Markets Authority has clarified that firms cannot treat staked assets as their own property. The current consultation merely asks whether the existing distinction between protocol‑level staking and staking‑as‑a‑service remains appropriate.

If Brussels decides that staking deserves its own rules, the move would mirror the regulatory evolution seen in other financial sectors. New products often begin with minimal oversight, expand as adoption grows, and eventually attract comprehensive regulation that reshapes market structure. Crypto analysts note that, similar to the post‑2008 reforms that pushed derivatives clearing into central counterparties, staking could transition from a decentralized activity to a regulated service dominated by large, compliant providers.

Users who wish to avoid regulated intermediaries could still opt for self‑custody, interacting directly with validators or decentralized protocols. However, the growing scrutiny may push more of the staking ecosystem toward regulated custodians, potentially altering the balance between user freedom and consumer protection. The ultimate impact will depend on how the consultation’s findings are translated into concrete regulatory proposals and how those proposals are implemented across the diverse technical architectures of proof‑of‑stake blockchains.

The Securities and Exchange Commission’s five-year innovation exemption creates a pathway for tokenized U.S. stocks to trade on public blockchains through automated market makers. To qualify, the digital assets must retain shareholder rights such as dividend entitlement and voting power, while platforms face caps on trading volume and the number of securities they can list.

Coinbase stands to gain across multiple business lines. Its existing tokenized-equity program already incorporates many of the SEC’s requirements, including dividend equivalence and mechanisms for shareholder participation. CEO Brian Armstrong confirmed that voting rights are slated for imminent rollout, a prerequisite for aligning token holders with traditional shareholders. The company also operates an institutional custody division and offers Coinbase Tokenize, a service that provides on‑chain infrastructure for third parties seeking to issue digital assets. Analysts at Citizens highlighted Coinbase’s reach into custody, tokenized assets, stablecoins and its Ethereum‑based Base network.

A technical hurdle remains: Coinbase’s current exchange architecture relies on central limit order books, whereas the SEC’s framework is built around automated market makers. The Goldman report suggested that Coinbase could either develop new infrastructure or route transactions through AMM‑based decentralized exchanges on Base to meet regulatory expectations.

Robinhood also appears positioned to benefit, despite its present offshore stock tokens falling short of the exemption’s standards. Those offerings expose users to price movements of U.S. equities via derivatives but do not confer full ownership rights. The SEC’s rule grants issuers the ability to block third‑party tokenized versions of their shares, a point that became contentious when AMC Entertainment’s CEO publicly criticized Robinhood for distributing AMC‑linked tokens without authorization. Robinhood’s leadership has indicated plans to add share redemption and voting capabilities to its tokenized products, aiming to achieve compliance.

Stablecoins may see heightened demand as tokenized securities gain traction. Both Goldman and Citizens projects pointed to Circle as an indirect beneficiary, given that USDC could serve as settlement currency, collateral and a bridge for on‑chain market activity. Coinbase would similarly gain through its economic exposure to USDC and its distribution channels.

Traditional exchanges such as Nasdaq and Intercontinental Exchange are not expected to face immediate pressure from the new venues. The SEC’s caps, issuer opt‑out rights and the inherent limitations of automated market makers in deep liquidity markets are likely to restrict competitive impact for the time being.

Solana has lowered its target slot time to 250 milliseconds, a change that increases the frequency of block production opportunities while shortening the window validators have to hand off leadership. The adjustment took effect at epoch 1037 on September 18, as recorded in the Solana engineering changelog and confirmed by a Solana Compass report that timestamped the transition near 05:06 UTC. A snapshot of network activity from early September captured an average slot duration of about 266 milliseconds across 60 one-minute intervals. During epoch 1037, approximately 0.05 percent of scheduled slots were missed, a figure that reflects an early, limited sample rather than a sustained performance trend. The primary focus now is whether critical processes such as leader handoffs, transaction forwarding, repair mechanisms, and multi-client compatibility can remain reliable as the network explores a further reduction to 200 milliseconds. A draft design known as SIMD-0525 proposes lowering per-slot work limits in line with shorter slot durations, setting a block budget of 62.5 million compute units at 250 milliseconds and 50 million at 200 milliseconds. Both thresholds remain below the protocol’s theoretical ceiling of 250 million compute units per second. Shorter slots alter not only throughput potential but also the rhythm of block arrival and the latency experienced by users. Each block carries less permitted computational work, meaning that actual transaction processing depends on demand, scheduling, and how effectively leaders utilize available blockspace. Geographic factors already influence timing margins. Analysis from the Solana Foundation indicated that median first-slot penalties amount to roughly 28 milliseconds when consecutive leaders are located within 500 kilometers, but rise to 122 milliseconds when separation exceeds 8,000 kilometers. The latter figure represents 61 percent of a 200-millisecond target slot and accounts for more than simple network latency. It highlights a trade-off: while broader geographic distribution can mitigate risks tied to localized outages, long-distance handoffs consume a larger share of an increasingly constrained production window. To safeguard against such pressures, engineers have outlined two mitigation strategies in the September 18 changelog. Agave development teams are investigating pessimistic forwarding techniques that route transactions toward the next expected leader in cases where delivery to the intended destination might fail. Simultaneously, client teams are conducting conformance testing across different software versions and implementations to ensure consistent execution behavior. Recovery procedures are also being evaluated, with proposals to maintain a 250-millisecond repair-defer threshold even as target slot times shrink. These measures represent forward-looking engineering buffers rather than indicators of current instability, but they delineate the conditions under which reduced latency can coexist with dependable operation. A prior incident on August 12, occurring before the 250-millisecond adjustment, illustrates how shared infrastructure dependencies can impact multiple validators simultaneously. During that event, TeraSwitch experienced a routing failure that affected 12 sites, including one in Miami that was isolated for containment. Solana Compass estimated that 28.83 percent of network stake experienced delinquency for approximately 33 minutes. Despite the disruption, block production continued and transactions were still processed. The episode underscores limitations in decentralization metrics, as stake concentration on a single provider can obscure systemic exposure. Independent data from September 7 indicated that Solana’s stake-weighted Nakamoto coefficient stood at 18, with the largest validator controlling about 4 percent of active stake. At the infrastructure level, a provider report from the same date attributed 22.1 percent of active stake to TeraSwitch, though earlier figures had placed its share above 30 percent before a reduction was implemented. These numbers reflect distinct measurement approaches and timelines, making the September 7 snapshot the most current and comparable reference point. Software heterogeneity introduces another layer of complexity. A stake-weighted assessment conducted on September 20 found that roughly 87.4 percent of stake was running on client versions labeled 4.x, 7.3 percent on 0.x, and 5.3 percent on 26.x. Major version numbers serve only as broad indicators for distinct client families — Agave-family, Frankendancer, and Firedancer — as they do not fully differentiate between scheduler variants or downstream builds. These categories address separate dimensions of risk: validator stake reveals how many leaders would need to fail or coordinate, client lineage exposes shared exposure to implementation flaws, and hosting share highlights dependencies on single providers or routing domains. Accelerating slot times does not generate these concentrations, but tighter handoff and repair windows can amplify the impact of correlated failures. The threshold for advancing to 200 milliseconds remains conditional. As of September 20, the feature was still pending mainnet deployment, with no fixed activation date listed in Anza’s feature-gate schedule. Solana’s public planning documents have referenced targets ranging from the third quarter to an October Agave 4.3 release window, though neither specifies an exact date. Early measurements from the 250-millisecond transition have not revealed spikes in skip rates, suggesting a stable initial phase. However, achieving 200 milliseconds will require sustained performance under more variable conditions, including higher load and potential geographic stress. The decisive test will be whether transaction forwarding, leader transitions, repair cycles, and cross-client interoperability can maintain reliability when timing margins shrink further. A separate upgrade path, known as Alpenglow, targets finality times near 150 milliseconds but operates on a different schedule than slot-time adjustments. Public timelines for both initiatives remain approximate, with no confirmed deployment dates. Current data suggest that the network can absorb short-term reductions in slot duration without catastrophic failure, but the path forward depends on continuous monitoring of skip rates, transaction inclusion latency, and leader handoff behavior across diverse client implementations and infrastructure providers.

The Bank of Russia has introduced a draft rule that would cap crypto‑related capital exposure at 1% of a bank’s own funds. The proposal, released on September 18, distinguishes between individual credit institutions and banking groups, applying the same ceiling to both the institution and its consolidated group. Exposure is measured against capital rather than total assets, creating two parallel ratios — N31 for single institutions and N32 for groups. The draft counts direct and indirect crypto investments, price‑linked derivatives, and instruments such as loans, bonds, guarantees, repos and credit lines when their settlement or value depends on crypto or foreign digital assets. Hedge positions receive limited recognition; long and short crypto holdings can be netted only within a narrowly defined lower‑risk category that imposes strict conditions on the asset, settlement, maturity, freezing and liquidity risks. Direct holdings and other higher‑risk crypto exposures are treated more conservatively and cannot be fully offset by opposing positions. Customer assets are included in the calculation only when the bank assumes liability for seizure or restriction; otherwise they are assigned a 50% risk weight, while exposures the bank does bear carry a 1,250% risk weight. The framework is part of a broader regulatory effort that the central bank intends to publish in the fourth quarter of 2026, with the rules taking effect ten days later. Reporting requirements are slated to begin in January 2027, although the precise reporting forms are still under development.

Donald Trump announced plans to establish an AI Force and name an artificial intelligence czar, according to reports.

The president made the remarks on his Truth Social platform on Saturday, stating that the new initiative would oversee the rapidly expanding AI sector without imposing regulations that might hinder innovation. He wrote that the AI Force would be created "much like" the Space Force he launched during his first term, and that he would soon name an AI "czar" who "only high I.Q. individuals need apply."

The post did not specify whether the AI Force would operate as a military unit, a civilian agency, or a separate department, and the White House did not reply to a request for clarification.

The announcement follows growing warnings about AI’s potential risks. Earlier in the week, Anthropic chief executive Dario Amodei outlined a three‑step framework intended to slow AI development if left unchecked, cautioning that unchecked progress could "outrun our ability to understand and control these systems."

Anthropic said on Sunday that it had selected Accenture to serve as its first embedded evaluator, tasked with moderating the pace of AI development — the first step of Amodei’s proposal. OpenAI chief executive Sam Altman and SpaceX chief executive Elon Musk publicly endorsed the proposal, while Nvidia chief executive Jensen Huang expressed skepticism, arguing that additional regulation was unnecessary.

Cointelegraph reported on September 12 that Amodei’s proposal had been published, and that Anthropic had moved forward with the initial step by appointing Accenture as its evaluator.

The article reflects Cointelegraph’s commitment to independent, transparent reporting and encourages readers to verify details independently.

The project has published 1,373 lines of Solidity code across 17 files as part of its latest development release, marking the first concrete layer of its proposed fair-launch platform on BNB Chain. The update, focused on smart-contract architecture, provides developers and participants with a public view of the rules governing token funding, allocation and liquidity. MemeToro, which describes itself as an AI-assisted ecosystem for memecoin discovery and trading, raised over $139,000 in its Stage 7 presale at a price of $0.00430 per token. The code, written in Foundry, includes three core contracts: FairLaunchEscrow.sol, designed to hold contributor funds for a single launch round; ILaunchExecutor.sol, serving as a plug-in point for future token deployment and liquidity integration; and IERC20Minimal.sol, which defines basic token functionality for claim payments. Documentation, architecture notes and a full test suite accompany the release, enabling external review of the proposed system. The contract design enforces strict parameters, rejecting proposals with unsupported URLs, allocation totals that do not sum to 100%, insider allocations above zero, or conflicting funding terms. It also prevents post-launch modifications by locking round settings and storing a fingerprint of the public launch manifest, allowing participants to verify on-chain terms against the information available at contribution time. No owner or upgrade privileges are embedded, and contributor funds can only be released as refunds or through the designated liquidity process. Allocation calculations prohibit insider supply, requiring that contributor and liquidity allocations account for the full token supply, with any rounding remainder directed to liquidity. The project’s native token, $MT, is intended to support staking, rewards, trading and access to a news portal, though its economic model remains illustrative. At the current presale rate, a $500 investment would secure approximately 116,279 $MT tokens, with a theoretical value near $6,028 if priced at the projected $0.05186. Under a $1 billion fully diluted valuation, each $MT might reach $0.8333, implying a potential return of about $96,899 for the same allocation. These figures are not guarantees and do not factor in market dynamics, fees or supply changes. The system still requires completion of the token executor, manifest-to-contract integration, testnet deployment and independent security audits by firms including Coinsult, BlockSAFU and SOLIDProof. The open-source release represents an early stage of development, offering transparency but not eliminating risk. It provides a structured framework for evaluating how funding and token distribution will be enforced, pending further implementation and real-world testing.

Grayscale Investments has filed a proposal to execute a 3-for-1 forward split of its Zcash exchange-traded fund (ETF), ZCSH, with the U.S. Securities and Exchange Commission. The filing indicates that shareholders will receive two additional shares for each share they own as of the close of business on September 28. The move is intended to lower the per-share price, making the fund more accessible to retail investors. The fund’s shares have risen approximately 2,800% over the past year, pushing the price per unit into a range that some investors found prohibitive. A Grayscale press release explains that the split will increase the total number of outstanding shares proportionally while reducing the price per share by one-third, preserving the fund’s total value. For example, an investor holding 10 shares priced at $300 each would retain a $3,000 position after the split, now represented by 30 shares at $100 each. The filing underscores Grayscale’s strategy to align the ETF’s structure with growing institutional and retail interest in Zcash. Meanwhile, Zcash (ZEC), the privacy-focused cryptocurrency underpinning the fund, has seen heightened market activity. Cointelegraph reported that ZEC surged about 20% within 24 hours after Paradigm co-founder Matt Huang disclosed an unspecified purchase of the token. Huang described Zcash as a “private complement to Bitcoin” and emphasized long-term support for its development team, citing concerns about AI-driven cyber threats and quantum computing advancements. The Block noted that ZEC briefly reached $1,521 in early trading, marking a new peak before moderating slightly. These developments reflect broader trends in privacy-centric digital assets amid evolving regulatory and technological landscapes. Grayscale’s ETF structure allows investors exposure to ZEC without direct wallet management, though the fund operates under traditional securities regulations. The proposal now awaits shareholder vote, though no timeline has been set for implementation pending regulatory review. The fund’s performance remains tied to ZEC’s market price and adoption of its shielded transaction protocol, which uses zero-knowledge proofs to obscure transaction details. While privacy features attract users seeking financial confidentiality, they also draw scrutiny from compliance-focused entities. ZEC’s recent volatility highlights the intersection of speculative investment, technological innovation, and evolving market dynamics in the cryptocurrency sector. The split, if approved, would not alter the fund’s net asset value but could influence trading liquidity and investor accessibility. Grayscale has not indicated plans for additional structural changes beyond the split. The filing marks a significant step in the firm’s efforts to position ZCSH as a mainstream investment vehicle within the digital asset ecosystem.