Bitcoin spent Sunday trading just above $78,000, which would have been a strange sight after the week it just had.

United States spot Bitcoin and Ether exchange traded funds lost a combined $798.9 million on Friday, October 30, in a single session that wiped out four days of buying. Bitcoin was at $78,052.39 on Coinbase at about 09:18 UTC on November 1, up 0.95 percent over the rolling 24 hour window, while Ether was at $2,270.70, up 1.27 percent. Those are spot prices from a weekend when the ETF market was closed, so the two sets of numbers cover different windows. The funds were selling hard on Friday and the coins were still standing on Sunday, and that gap is the part worth paying attention to.

Friday wiped out a week of buying

Farside Investors put net outflows from United States spot Bitcoin ETFs at $643.2 million on October 30, the largest daily withdrawal since June. That came after $440.8 million in net inflows across the four sessions from October 26 to October 29, so one Friday session took out all of that and left the week with a net outflow of $202.4 million. BlackRock's IBIT accounted for $233.7 million of the Friday exit, Fidelity's FBTC lost $201 million and ARK 21Shares' ARKB lost $129.5 million. Those three funds accounted for $564.2 million, or about 87.7 percent, of the day's total, which means this was not a broad panic across every product. It was concentrated selling in the biggest names, on the last trading day of a month that had already been rough for crypto.

Ether has had a worse month than Bitcoin

Ether funds did not get a break at any point last week. They lost $155.7 million on Friday, which took their weekly total for October 26 to October 30 to $431.4 million, and every one of those five sessions was negative. October as a whole added up to about $1.61 billion in net outflows from Ether ETFs, and Glassnode put the run at 23 consecutive trading days of net outflows through October 30. That is the longest losing streak since these funds launched in July 2024. BlackRock's ETHA led Friday with $76.6 million out, followed by $34.1 million from Grayscale's Ethereum Mini Trust and $21.5 million from its ETHE product. That steady drain lines up with the price, because Ether has fallen from near $2,700 in late September to about $2,300. Bitcoin also closed October down 7.3 percent at $77,424, its weakest October in at least ten years.

Why the price did not follow the money out

It is tempting to read Friday as a verdict on Bitcoin itself, but the flow data does not prove why investors redeemed their shares. The selling came a day after the Binance hack on October 29, when about $6.3 billion was taken from the exchange, and nerves were already high across the market. Some of that money may have been investors cutting risk after a shock, and some may have been month end rebalancing. What the data does show is that the selling was real and it was large, and it still did not push Bitcoin below $77,000 on Sunday. United States spot Bitcoin ETFs have taken in more than $57 billion in net inflows since they launched in January 2024. IBIT alone finished October with $932.1 million in net inflows even after its $233.7 million Friday loss, while its smaller rivals lost about $1.45 billion between them in October.

The next test comes on Monday, when ETF trading opens again and the first November flows print. If the outflows continue into a second week, the story changes from a bad Friday to a shift in how big investors are treating crypto after a rough October. If the money comes back, Friday will look more like a sharp reaction to a bad week than the start of a longer retreat. Either way, the weekend gave traders a useful piece of information. A $643.2 million exit from Bitcoin ETFs and a $155.7 million exit from Ether ETFs was enough to erase a week of inflows in a day, and it was not enough to break Bitcoin's hold above $78,000. That does not mean the selling is over, and it does not mean the bottom is in. It means the market absorbed a very large institutional sale and kept trading, and for now that is the most important fact in the room.

-------
Author: Cedric Holloway
New York Newsroom
GlobalCryptoPress | Breaking Crypto News

Binance is promising to absorb a roughly $6.3 billion hack, but customers are still waiting for the withdrawal button to work again.

The attack struck on October 29, and the exchange's October 30 updates describe an investigation that has expanded beyond an initially suspected compromised laptop. Binance says it has reserved more than $6.34 billion of company funds to cover the stolen assets. About $5 billion is already held in the affected tokens, with purchases of the remainder underway. In his latest video transcript, co-CEO Richard Teng said the rebuilt withdrawal service would reopen only after rigorous testing. He said the Sunday deadline remained on track, while expressing hope that users could withdraw sooner.

That is a target, not a reopening announcement. Binance's latest written service notices say deposits are operating normally while withdrawals remain paused. Teng also committed to a full Proof of Reserves report by Monday, November 2, with an initial view hoped for earlier. The Sunday he referred to is November 1. Those dates give customers concrete milestones against which to judge the company's assurances, rather than another open-ended promise that everything is fine. A visible account balance and an operational withdrawal service remain different things.

Billions reserved, billions frozen - different things

The money Binance says it has reserved is separate from approximately $3 billion in assets it says partners have frozen. Its earlier funding update explicitly excluded frozen or protected assets from the $6.34 billion commitment. Those assets still require recovery and verification. Binance says it is buying the missing token quantities through markets and over-the-counter trades, and warns that limited liquidity and settlement times can slow that work. Setting aside a dollar amount therefore does not mean every replacement token has already arrived. The company has pledged to cover the losses, but its promised reserve disclosure is still ahead.

Independent Elliptic analysis, updated at 13:10 UTC on October 30, estimated the theft at $6.43 billion and verified $2.84 billion frozen onchain. That is its own snapshot, rather than Binance's final accounting. Elliptic calls this the largest crypto theft on record, far exceeding the roughly $1.46 billion Bybit theft last year. Most of the frozen value is in stablecoins whose issuers can restrict transfers. Bitcoin and native ether have no issuer with that same freeze switch, leaving investigators dependent on tracing and intervention when funds reach services. Freezing a token also does not by itself put it back in Binance's wallet.

More than a laptop, and an attribution still under scrutiny

The technical explanation is still developing. Binance first described a possibly compromised DevOps engineer's laptop and said it had found no evidence of wallet private-key leakage. It subsequently disclosed additional breach points, without laying out the complete attack path. TRM Labs' investigation says the Ethereum portion involved EIP-7702, a feature that lets a wallet delegate execution to smart-contract code. The attacker used signed authorizations to install malicious behavior on a hot wallet, while wallets on other chains sent ordinary signed transfers. TRM interprets that wider pattern as evidence of compromised signing infrastructure. Teng's newer account says the delegation bypassed normal approval controls and that attackers destroyed tooling and traces; those remain the company's findings pending a full technical report.

TRM attributes the attack to North Korea's TraderTraitor group with high confidence, while Elliptic considers North Korean involvement likely. Elliptic also cautions that a shared laundering address does not prove the same hackers carried out separate thefts. Its report says no government or law-enforcement agency has confirmed attribution. For customers, the immediate questions are whether withdrawals actually reopen, whether the promised reserves match affected assets, and what the final investigation establishes about the failed controls. Teng says the review now covers devices, cloud infrastructure, key management and signing systems across the company. The next meaningful update is evidence that those repairs and replacement purchases are complete, not simply another repetition of the compensation pledge.

The company behind the New York Stock Exchange wants to bring Hyperliquid-based perpetual futures into a regulated U.S. market.

Intercontinental Exchange announced its agreement with Trade[XYZ] on October 29. ICE is taking a minority stake in the company and would operate its regulated markets. The planned venue targets retail traders seeking exposure around the clock. Regulatory approvals still stand between the announcement and a product Americans can actually use.

The division of work matters. Hyperliquid supplies the underlying technology, while Trade[XYZ] designs and implements markets, according to The Block's reporting on the agreement. ICE supplies the regulated exchange and clearing structure. Contracts are intended to reference assets including cryptocurrencies, equities, commodities and foreign exchange. This would put an established exchange operator around technology that has attracted traders to onchain derivatives, rather than make every existing Hyperliquid market available in America overnight.

A route through brokers, with identity checks

ICE's announcement describes access through participating futures commission merchants after approval. Those are the intermediaries that handle customer futures accounts. Customers would undergo identity and anti-money-laundering checks. Distribution is also expected through ICE's joint venture with OKX, which needs its own approvals. The companies must obtain permission for the proposed leveraged trading as well, so the announcement does not establish what borrowing limits or account conditions customers will eventually face.

Perpetual futures have no scheduled expiry date. As Decrypt reported, Trade[XYZ] already offers eligible users outside the United States continuous trading in contracts referencing stocks, indices, commodities and currencies. The proposed American venue would bring that style of exposure into a different legal and operating structure. A contract referencing a share is still a derivative, rather than direct ownership of that share. Investors evaluating a future offering will need its actual contract terms, rather than assume it works like buying stock in a brokerage account.

The agreement is real; access is still ahead

HYPE rose sharply after the news, with both Decrypt and The Block reporting double-digit percentage gains during the morning. Those snapshots are a market reaction, not evidence that approval has been granted. ICE says the retail business would sit separately from its institutional futures and clearing operations. Its existing participation is more than 99% institutional, according to the company. The planned separation reflects how different a continuously traded retail product can be from markets used by commercial hedgers over longer periods.

The announcement does not give a launch date. It also leaves the eventual contract menu and customer terms for later disclosures. Those details will determine how much the proposed venue changes practical access to these markets. The next meaningful milestones are regulatory decisions and concrete information from participating brokers. Until then, the agreement shows a major exchange operator committing to the business, while the ability to trade through it remains a future step.

CoinDCX has put a nearly $16 million price tag on a wallet incident its CEO initially dismissed as a false alarm.

The Indian exchange confirmed the loss in an October 25 update. It says the missing 15.99 million USDT came from retired infrastructure. The company says it has absorbed the cost and customer balances remain unaffected. Those assurances come from CoinDCX, rather than an independent assessment of its reserves.

The public reversal is a central part of the story. According to The Block, CEO Sumit Gupta initially rejected breach reports before the exchange acknowledged losses. Blockchain investigator ZachXBT challenged that account. The publication connects the affected infrastructure to CoinDCX's roughly $44 million hack in July 2025. That history makes the distinction between retiring a wallet and eliminating its remaining exposure especially important.

How a retired wallet still held money

In its official update, CoinDCX dates unusual activity to October 21 and irregular fund movement to the following day. It says some users continued depositing to old addresses. Customer accounts received credits when those transfers arrived. A separate sweeping process was supposed to move the tokens into secure wallets. The company says that process failed for a period, allowing funds to accumulate.

That explanation separates two things customers can easily mistake for the same event. A balance appearing in an exchange account does not, by itself, demonstrate that the underlying tokens have reached their intended storage location. Here, the exchange describes a gap between crediting balances and moving assets. Closing that gap requires operational controls as well as instructions to use new addresses. Calling infrastructure retired offers little comfort if it can still receive valuable deposits.

The questions the loss leaves behind

CoinDCX says trading, deposits and withdrawals continued normally. It also says user assets are held in separate cold wallets and acknowledges that its communication could have been more proactive. The update does not establish who carried out the theft. Nor does a statement about uninterrupted services independently resolve the security investigation. Customers need a clear account of the failed process, the length of the exposure and the checks introduced to prevent a repeat.

For users making another deposit, the exchange's immediate instruction is to check the current address in its app or website every time. An address saved from an earlier transfer can outlive the system that was meant to handle it. The broader issue is whether CoinDCX can demonstrate that obsolete infrastructure no longer leaves money exposed. Its promised absorption of the loss addresses who pays for this incident. A detailed explanation of the controls that failed would address why customers should expect a different outcome next time.

HSBC is putting its first stablecoin inside an app millions of Hong Kong residents already use to pay people.

The bank announced RedCoin, ticker RCHKD, on October 23. It is denominated in Hong Kong dollars and launches through PayMe. HSBC says more than 3.3 million users will be able to activate a stablecoin wallet over the coming days. That is a potential audience, not a count of people already holding or spending the token.

The initial uses are straightforward: sending money to friends and paying merchants. HSBC's launch announcement says payments will reach more than 100,000 merchants through PayMe. The bank tested wallet activation, minting and live transfers with nearly 100 staff before launch. HSBC Digital Assets Custody provides safekeeping for RedCoin. The practical appeal is giving an existing payments audience access to stablecoins without first persuading it to adopt an unfamiliar app.

A licence becomes a consumer product

This launch follows a regulatory decision made months earlier. The Hong Kong Monetary Authority granted licences to HSBC and Anchorpoint Financial on April 10. At that point, the regulator said the firms intended to prepare their businesses for launch in the following months. Receiving permission and having a usable product were separate milestones. RedCoin's October rollout is the consumer-facing step that turns HSBC's earlier plan into something customers can start using.

When HSBC announced its licence in April, it said the coins would be fully backed by high-quality liquid assets in segregated accounts. That is the bank's stated reserve arrangement. It is a more specific promise than simply saying a token is backed by a famous financial institution. The same April announcement put PayMe and the Hong Kong mobile banking app at the centre of the plan. Friday's release makes clear that those channels are arriving on different schedules.

Payments first, investments later

The HSBC HK Mobile Banking App is due to gain stablecoin wallet functionality later this year. The bank also plans to let customers subscribe to tokenised investments with RedCoin. A new share class of its HKD money market fund is among the planned products. Those features are future additions, rather than services confirmed available at this launch. Users should distinguish the payment wallet they can activate from the investment offering still to come.

The important test now is what customers actually do with this access. An established app and a large merchant network give HSBC distribution, but neither proves repeat stablecoin use. Wallet activations and sustained payment activity would tell readers more than the size of the eligible audience. For now, the confirmed development is a bank-issued HKD token reaching everyday payments through PayMe. The next milestones are the wallet rollout and whether HSBC delivers the promised banking-app and investment features.

Standard Chartered has signed a deal to take full ownership of Zodia Custody, bringing another piece of crypto's infrastructure closer to a major bank.

The October 21 announcement moves the transaction from an accepted non-binding offer to definitive agreements. Standard Chartered I H Limited would acquire 100% of Zodia Custody Limited. Regulatory approvals and customary closing conditions still stand between signing and completion. The distinction matters: this is a binding deal announcement, not confirmation that the custody operations have already moved.

Standard Chartered is technically British, it's roots going back to 1853 United Kingdom, when starting a bank required direct approval from Queen Victoria herself.  Since then they've grown into a multinational finance company covering everything related to banking and investing. 

Zodia supplies some of the behind-the-scenes tools and services used in the finance industry when a company or firm decides to expand in to the crypto market. Standard Chartered was one of those companies, but why just buy the software when you can own the company that makes it?

Under the bank's announced plan, the regulated custody business will join its existing digital asset custody activities within Securities Services after completion. The parent being acquired owns regulated operating entities in Singapore, Hong Kong, Australia, the United Arab Emirates and Luxembourg. Standard Chartered says existing custody clients continue to receive service as usual. It expects no disruption from the transaction. Those are the bank's assurances about the transition, rather than an independent assessment of how integration will unfold.

Custody and software will take different paths

The transaction also separates two businesses that can easily get bundled together in a crypto headline. Zodia's software and professional-services assets are set to move to Zodia Solutions, an independent entity to be established under SC Ventures. Standard Chartered would be one of the institutions using its technology. The bank identifies a group of supporting investors that includes Northern Trust, NAB Ventures and Emirates NBD. Buying the custody company therefore does not mean folding every technology activity into the same operating unit.

The Block reported that financial terms were not disclosed. Its account places the signed agreements five months after shareholders and noteholders accepted the earlier non-binding offer. It also reports that earlier targets had contemplated definitive agreements by late June and completion by late August. Those dates have plainly given way to a later process. The fresh announcement still makes completion conditional, so treating an old target as a current closing promise would overstate what is known.

A bigger bank offering, not a new retail wallet

The acquisition fits a broader expansion that was already under way. In an October announcement, Standard Chartered outlined plans for Singapore custody services covering selected cryptoassets, stablecoins and tokenized real-world assets. The intended customers are institutions and accredited-investor corporate clients. That service remains subject to applicable regulatory requirements. The bank described it as complementing traditional asset servicing and tokenization, rather than replacing those activities with a separate consumer crypto app.

For ordinary investors, the immediate significance is the business structure around institutional safekeeping. This agreement does not establish that a new wave of customers has bought bitcoin or that assets have already migrated. It shows a bank committing to consolidate custody operations while keeping a separate technology supplier in the picture. The next concrete milestones are regulatory approvals, closing and details of the integration. Until those arrive, the most useful reading is that the deal has advanced substantially, with execution still ahead.

Stablecoin issuers now have a final OCC rulebook, but submitting an application will not necessarily be enough to keep issuing coins after January.

The Office of the Comptroller of the Currency announced its GENIUS Act final rule on October 21. It takes effect on January 18, 2027. The agency also laid out a waiver process for existing issuers still awaiting a decision when that date arrives. For people holding stablecoins, the transition deserves attention because an issuer's application, approval and permission to continue operating are different things.

The OCC's rule summary covers reserve assets and redemption, along with risk management, custody and supervision. It also addresses capital and an operational backstop. Its reach includes relevant banks, nonbank issuers and foreign issuers under the agency's jurisdiction. Certain state-qualified issuers fall within that scope as well. This is a completed OCC rulemaking, a meaningful step beyond the industry requests for clarification that have dominated much of the recent stablecoin debate.

The deadline and the application queue...

The regulator's separate waiver guidance identifies a practical timing problem. An existing issuer could submit a substantially complete application on time and still be waiting for approval in January. Continuing to issue without a waiver could then breach the prior-approval requirement. The OCC generally expects to grant qualifying existing issuers relief from that requirement unless stronger reasons support a denial. Each request still needs a decision, so an application receipt should not be read as permission.

That relief has limits. The statutory waiver period can run no longer than 12 months from January 18, and the OCC expects to allow only the time needed to address the reason for granting it. The agency does not identify a general reason to waive other requirements for everyone. It also generally expects prospective issuers that are not already operating in the United States to wait for approval before starting. Those distinctions make a blanket claim of a one-year extension misleading.

What to watch for next...

The October 21 announcement did not open the application window. The OCC says it will announce that step separately after the relevant information collection receives final approval from the Office of Management and Budget. Its final rule also leaves Bank Secrecy Act, anti-money-laundering and sanctions provisions for a separate rulemaking with Treasury. Other agencies have their own implementation responsibilities. The arrival of this rule therefore does not mean every part of the federal stablecoin framework is finished.

For holders, the next useful updates will be specific to the issuer behind the token. A company's statement that it plans to apply provides less certainty than a confirmed approval or granted waiver. The final rule is also not a finding that any particular coin has satisfied every requirement. Issuers' public explanations of their transition plans will help show how they expect to handle the deadline. The practical question is whether the company can document its status clearly, rather than simply point to a new law and call the job done.

Moving crypto without copying a wallet address sounds like a small improvement until you remember what a wrong transfer can cost.

Zerohash just announced their new feature "AUTH" - account linking for transfers involving crypto, stablecoins and tokenized securities. Its launch announcement describes a system that removes manual address entry and blockchain selection from the customer experience. Users choose a supported account or wallet, authenticate and authorize the movement. The pitch is straightforward: make moving assets feel more like choosing an account than operating a blockchain.

Basically, you'll enter your wallet info once, or link an exchange account by logging in, and from that point onward the process resembles a bank transfer more than a typical crypto transaction. 

The process is outlined in this graphic posted by ZeroHash:

A simpler interface still has rules behind it

The current product documentation places AUTH inside account-funding and crypto-transfer flows. In the funding flow, a crypto deposit can become a fiat balance on the receiving platform. In the crypto-transfer flow, the balance stays in crypto. Customers still review and approve the transfer, while the integration handles the network routing in the background.

The October announcement also follows an earlier beta, rather than marking the first appearance of the technology. Zerohash's release notes dated August 3 already described AUTH for its Account Funding SDK. Existing clients could add it to their setup, and new integrations could include it. That release also described exchange-account linking and access to hundreds of non-custodial wallets. The distinction helps put the new announcement in context: this is a broader launch of a product that had already been available in beta.

Arriving onchain and becoming available are different steps

Zerohash's current control documentation explains why a cleaner transfer screen does not settle every question about access to funds. Platforms can configure name matching between their customer records and information from an external account. One approach checks after a deposit arrives but before the balance is credited. Another handles exceptions after crediting through reporting. The timing therefore depends on the platform's chosen configuration, so an onchain arrival alone does not establish that a deposit is ready to use.

Platforms can also request a control that withholds ordinary availability for deposits initiated outside AUTH. The documentation tells them to plan how they will explain the status and direct customers toward recovery options. For a user, that makes the receiving application's supported funding route an important part of the transaction. The useful questions are which assets and accounts it accepts, whether a deposit converts into cash, and when the balance becomes available. Removing address copying can make the process easier, but clear transfer status and recovery instructions will determine how comfortable it feels when something needs checking.

Bitcoin funds just had a strong day, but almost all the good news came through one door.

Data reported on October 20 shows BlackRock's IBIT attracted $665.2 million on Monday, October 19. Across U.S. spot bitcoin ETFs, the combined net inflow was a smaller $526.7 million, according to Farside Investors. Fidelity's FBTC lost $83.6 million and Grayscale's GBTC lost $54.9 million. The other products in Farside's table recorded zero net flows. That makes this a story about concentrated demand, rather than a wave of buying across every fund.

I mention this because the it's an important distinction - a overall total for a segment of the market can conceal very different experiences for individual products. IBIT's intake exceeded the entire group's net gain because withdrawals elsewhere offset part of it. Those withdrawals totaled $138.5 million. This does not establish that investors moved money directly from Fidelity or Grayscale into BlackRock. The figures show the totals entering and leaving each product, not the identities or intentions of the people behind them.

A big day does not explain every buyer

Using SoSoValue's data, The Block reported that Monday was IBIT's strongest daily intake since October 7, 2025. Its more precise IBIT figure was $665.16 million, while its combined fund total was $526.6 million. Those small differences reflect the separate data series, and this article uses Farside's rounded figures consistently. The report also put IBIT's net assets at $66.37 billion. Assets under management and daily inflows measure different things: one is the size of the fund, while the other tracks net subscriptions over a period.

Presto Research's Min Jung told The Block that the exact reason for the inflows was unclear. He suggested investors could be positioning for bitcoin to catch up with other risk assets. That is an analyst's possible explanation, not something the flow table proves. A fund subscription cannot reveal whether the buyer plans to hold for years or is using a more complicated trading strategy. Nor does the size of a subscription tell readers what bitcoin's next price move will be.

Watch whether the demand spreads

The useful follow-up is whether other funds begin attracting money alongside IBIT. A broader run of subscriptions would provide different evidence from a single standout product carrying the total. Continued withdrawals elsewhere would leave that distinction intact, even if the headline number stayed positive. Repeated observations also help separate a persistent change from a particularly large session. For now, the verified development is a substantial intake at BlackRock with weaker demand elsewhere in the same group.

Readers should keep the trading date attached to these numbers. They describe October 19 activity, reported the following morning, rather than completed October 20 flows. Farside's October 20 row was still unfilled when reviewed. Its automatic table can also be updated, so an empty entry should not be read as a final zero. Monday's result is a meaningful demand signal, but the next few sessions will show whether that signal broadens or remains concentrated.

The next fight over U.S. stablecoin rules is about who gets pulled into them.

The Blockchain Association filed a comment letter on October 19 asking Treasury to draw clearer boundaries around its proposed GENIUS Act regulations. The submission, reported on October 20, concerns rules implementing Section 3, which addresses payment stablecoin issuance, offers and sales. The industry group supports the broad objective of regulated issuers and adequate reserves. Its objections focus on how the proposal would apply to other businesses and activities around those issuers. These are requests to change a proposed rule, not newly granted exemptions.

In its comment letter, the association asks Treasury to distinguish customer-facing service businesses from firms trading their own assets. It also wants explicit recognition of statutory exclusions covering activities such as self-custody software and transaction validation. The group argues that participation in peer-to-peer liquidity arrangements should be assessed by function rather than tied to a particular technology. That distinction is important to its case because technical designs can change without changing the underlying activity. Treasury has not accepted those requested clarifications simply because the letter was filed.

When trading becomes participation

Another dispute concerns knowing participation in unlawful stablecoin issuance. As The Block reports, the association wants liability tied to actual knowledge and substantial assistance coordinated with an issuer. It argues that ordinary secondary-market trading should not automatically count as participation. The distinction separates helping bring an unlawfully issued token into existence from subsequently trading an existing asset. That remains the industry's requested interpretation, rather than an assurance that every secondary-market transaction is outside the law.

The association also objects to open-ended checks on foreign stablecoin issuers. Many service providers, it says, have no direct relationship with those issuers and cannot readily obtain the requested information. Its preferred approach would let firms rely more heavily on public regulatory lists. The Block also reports objections to requiring additional counterparty identification in permissionless settings where a participant may see only a wallet address. These arguments concern how obligations could work in practice; they do not establish that overseas stablecoins have received blanket approval.

The final wording will decide the reach

For readers who use self-custody wallets or decentralized trading services, the practical issue is the treatment of the infrastructure around a transaction. A rule aimed at issuers can affect more than the business that creates a token if other participants face obligations too. Conversely, an exclusion for a particular activity is not a promise that every business combining it with other services is exempt. The relevant question is what the final text requires of each role. That makes precise definitions more useful than broad claims that DeFi has either won or lost.

The submission should also be read as advocacy from a trade association representing industry members. Supporting reserve safeguards while challenging operational requirements is a policy position, not independent proof that Treasury's approach cannot work. The next meaningful development is Treasury's response through the rulemaking process and the wording it ultimately adopts. A comment letter does not change a platform's services overnight. Until there is a final decision, users should treat claims of new permissions or immediate bans with care and check what the actual rule says.

Mastercard wants the stablecoins sitting in a wallet to become money people can actually use without a complicated detour.

On October 15, the payments company and BVNK launched Global Money Platform, a set of tools linking digital currencies with conventional accounts and payments. Mastercard says it is available now through BVNK. Banks and fintechs can build the capabilities into services carrying their own brands. For customers, the potential benefit is a shorter route from a stablecoin balance to a bank payout or card purchase.

The launch follows Mastercard's acquisition of BVNK in August and is their first major product integration. According to Mastercard's launch announcement, the offering combines accounts holding several currencies with conversion and payment tools. Businesses can also use it for their own treasury operations. Nuvei and Marqeta are among the companies named as early integrators. Being named at launch, however, does not establish that every customer of those companies already has access.

The bank account at the other end matters

A blockchain transfer can move value to another wallet, but that alone does not finish the job for somebody who needs local currency. This platform connects stablecoin-funded payments to recipients' domestic bank accounts through Mastercard Move. Mastercard expects payout coverage to expand to more than 40 currencies across over 200 countries and territories in 2027. That is an expansion target, so readers should not treat the entire footprint as available today. The useful question is whether a provider supports the particular country and currency you need.

BVNK's product explanation also describes virtual card issuing across more than 130 countries. It lists USDC and OUSD among supported stablecoins and says the integration reaches more than 20 blockchain networks and payment rails. These are capabilities offered to businesses building financial products. They do not establish how much people are spending through the new platform. For a crypto holder, a familiar payment app adding a usable feature would be stronger evidence of adoption than another large network-reach number.

A launch still has to earn its users

The commercial idea is straightforward: make it easier for financial providers to combine services that would otherwise require separate connections. BVNK says its embedded accounts include custodial and self-custodial options. Its announcement also mentions rewards on eligible balances. Those details make the terms of the eventual customer product especially important. A reader should look for a clear explanation of who controls the funds and what conditions apply before treating two similarly named accounts as equivalent.

Neither launch announcement provides a universal consumer fee schedule or a guaranteed arrival time for every bank payout. That leaves real comparisons to be made when individual providers introduce their services. Check the amount that reaches the recipient after conversion and charges, alongside the quoted delivery time. Mastercard also places support for AI-driven commerce and tokenized bank deposits on its future roadmap. The immediate test is simpler: whether the products built on this launch make an ordinary stablecoin payment easier to complete at a competitive total cost.

Solana's next speed upgrade could make its transaction charts look worse, even when nothing is wrong.

Alpenglow is scheduled for October 21, according to the Solana Foundation's updated rollout guide. It targets roughly 150-millisecond finality, the point when a transaction becomes irreversible. The mainnet switch is still ahead, rather than an improvement traders can already measure in production. One less obvious change deserves attention before the countdown ends: validator votes will disappear from blocks.

Those votes currently contribute to transaction totals on dashboards that include them. Removing them can produce a sharp numerical drop without customers sending fewer payments or making fewer trades. Anyone comparing activity before and after the upgrade needs to check what the chart counts. A headline number can change because its ingredients changed. For SOL holders trying to judge demand, confusing that accounting change with an exodus would be an expensive reading mistake.

What's the big deal about 150 milliseconds?

The target concerns settlement certainty, rather than a promise that every wallet screen will refresh within 150 milliseconds. Anza's documentation says the target applies under normal network conditions. Its new voting system, Votor, replaces the voting and finality logic of Tower BFT. The network's computers exchange consensus messages, and certificates communicate the result. That is a change to how agreement is reached, with practical consequences for services waiting to treat a payment as final.

Different connections can still deliver that result at different speeds. Anza explains that a node outside the admitted validator set can learn finality from a certificate carried in a later block. That route can add a produced-block interval, and skipped or delayed blocks can extend the wait. Direct connections to an admitted validator provide another route, with their own network latency. So a faster consensus target does not make every provider, connection and application equally fast.

A rollout date, then a real-world test

The Foundation places activation in epoch 1064, expected to begin around 15:00 UTC on October 21. Epoch timing can drift, so the clock time is approximate. Its guide also describes a transition window before the new consensus takes over. Ordinary wallet users are not being asked to migrate their assets. The preparation falls mainly on the operators and developers responsible for keeping the network and its data services running.

Validators have a concrete funding requirement alongside the software work. Anza's vote-account guide sets the new admission ticket at 0.8 SOL per epoch, held above the vote account's rent-exempt minimum. An insufficient balance excludes the validator from voting and producing blocks in the following epoch. For readers, the useful checks after activation are whether settlement improves in the apps they use and whether activity comparisons exclude validator votes consistently. A successful upgrade should earn its reputation through those results, not through a countdown or a misleading chart.

Kraken's parent wants a place in your everyday banking, and it has agreed to buy a European lender to get there.

Payward announced on October 14 that it had signed an agreement to acquire Saldo Finance Oy, the Finnish holding company behind Lithuania's Saldo Bank. Its announcement puts the expected closing in 2027. Regulatory approvals and other closing conditions still stand between the agreement and completion. For European crypto customers, the interesting part is what Payward hopes to build once that happens.

The company says the purchase would help it offer interest-bearing deposits and lending products through Payward Banking. Card issuance and services for other financial technology companies are also part of the plan. That could give customers more ways to manage cash alongside their digital assets. But the announcement does not set out a new deposit rate or a customer launch date. A signed acquisition agreement is a meaningful step, not an account-opening invitation.

What Saldo brings to the deal

Saldo already has a banking business, with different products available in different countries. The bank's own release lists operations in Lithuania, Finland, Sweden and Germany, plus passporting into the Netherlands. It offers retail term deposits across its active markets. Consumer lending covers Lithuania, Finland and Sweden, while its small-business lending covers Lithuania and Finland. That footprint matters, because permission to expand and an already available product are different things.

The bank also has direct access to SEPA, the European payments system, and supplies lending services to fintech partners in Finland and Germany. Its credit card is already available in Finland. A Swedish rollout is expected in 2027. Saldo says the transaction's terms were not disclosed, so there is no announced purchase price to judge against these capabilities. The immediate story is the proposed combination of existing banking services with Payward's wider business.

The customer test comes after the agreement

Payward's stated ambition is to become a primary financial relationship for European clients. For someone who currently moves money between a bank and a crypto platform, a more integrated service could be useful. Convenience alone, though, will not tell customers whether an offer is competitive. The eventual rates, fees and access conditions will matter. Those details will make the difference between an impressive corporate announcement and a service people actually choose to use.

For now, the next milestone is regulatory approval and completion of the purchase. After that, watch for country-specific product announcements and clear terms explaining who can use each service. The releases describe an intended expansion, not a blanket rollout across Europe today. Readers comparing future offers should check the actual account provider and withdrawal conditions before moving money. Payward has announced its route into a bigger European banking business; customers still need to see what arrives at the other end.

Bitwise's new NEAR fund brings staking to brokerage accounts, but a third of the rewards is earmarked for fees.

The Bitwise NEAR ETF launched on NYSE Arca on September 29, 2026, under the ticker NRR. Bitwise describes it as the first spot NEAR exchange-traded product in the United States. Its launch announcement highlights network staking rewards of roughly 5%. Investors comparing that figure with the fund's 0.75% annual management fee need to account for a separate charge on the staking rewards themselves.

The prospectus, dated September 24, assigns 33% of the additional NEAR generated by staking to staking expenses. Those fees are shared among the staking agents, the custodian and the sponsor. The trust keeps approximately 67% of the staking rewards. That split does not replace the annual management fee. It means a headline network reward rate cannot be read as the return an NRR shareholder will receive.

How the staking arithmetic changes

A simple illustration shows the difference. If the gross staking rate stayed at exactly 5%, retaining 67% would leave 3.35% before the management fee. Subtracting 0.75 percentage points gives roughly 2.60%, assuming the entire holding stayed staked for a year and ignoring compounding, other costs and token-price changes. That is an illustration of the fee arithmetic, not a forecast or a quoted fund yield. Actual results depend on how much NEAR is staked, the rewards earned and the value of those tokens.

Bitwise's approximately 5% figure is an annualized network rate measured as of September 25. The company says rewards accrue through the fund's net asset value per share, so the figure should not be mistaken for a promised cash payout. Its stated plan is to use its institutional staking team. The announcement does not establish a full year's realized results for this newly launched product. A lower NEAR price can also outweigh the value of additional tokens earned through staking.

The AI pitch still needs to deliver

Bitwise is marketing NEAR as infrastructure for an economy in which AI agents make payments and coordinate transactions. The fund gives brokerage investors another route to express that investment view. It does not establish how much future business those agents will bring to the network. Nor does an exchange listing turn expectations about AI adoption into earnings for token holders. The investment case still depends on demand for NEAR, while the fees apply regardless of whether the AI story delivers.

For traders, the practical comparison is the convenience of holding fund shares against the cost and responsibilities of holding and staking tokens directly. NRR's shares can trade above or below the value of the assets they represent. The product also lacks the same protections as funds registered under the Investment Company Act of 1940. As trading develops, watch the bid-ask spread and the fund's reported staking participation alongside the management fee. The useful number is the reward that actually reaches the fund after costs, considered together with NEAR's price performance.

Block wants Bitcoin to handle the tiny payments AI agents make while getting things done online.

The company announced on September 24 that it had joined the x402 Foundation and contributed Lightning payments to the protocol. Its announcement puts Bitcoin into an open standard for software that can request and pay for services. Block sees fast, inexpensive transactions as essential to that market. The development gives Bitcoin holders a practical adoption story to follow beyond the next price target.

The proposed customer is often a program acting for a person or business. Think of an agent paying for a piece of data it needs to complete a task. The payment could happen within its interaction with the service, without a person stepping through a checkout each time. That is the kind of repeated, small transaction Block is targeting. It is also a very different use of Bitcoin from parking a large balance in a treasury.

A payment request built into the web

The standard uses HTTP 402, the web's Payment Required response. A service receiving an unpaid request can return instructions for payment. The client pays and retries, allowing the service to deliver the requested resource. The x402 project describes applications including paid API access and digital content. Developers can support multiple networks or payment schemes through the same framework.

That flexibility is part of the significance of Lightning joining. The standard is designed to work across currencies and networks, under Linux Foundation governance. Block's contribution adds another way to settle payments inside it. Businesses still need to build services that accept the method, and users need software capable of paying that way. A supported payment option only becomes useful when the two sides actually meet.

The demand still has to show up

At the time of review on September 25, x402's website displayed 75.41 million transactions and $24.24 million in volume for the previous 30 days. Those are figures for the overall protocol. They cannot be counted as activity generated by Block's new Lightning contribution. Block's announcement did not provide a separate Lightning transaction total or a consumer-product rollout date. It would be premature to treat its participation as evidence that millions of agents are already spending bitcoin through the integration.

Block says it will keep contributing to Lightning support and the foundation's working groups. It also plans further tools for agent-driven commerce. The useful test now is whether developers turn that work into services people repeatedly use. Watch for named deployments and payment activity that can actually be attributed to Lightning. The technology has a new route to customers; sustained use will tell us how much that route matters.

Bitget's hack just got more expensive, and customers are still waiting for a withdrawal update.

The exchange raised its estimate to $387.5 million in a September 25 update, replacing the earlier $351.6 million figure. It attributed the difference to previously uncounted Zcash and TRON transfers. Bitget said the revision reflects better accounting of the original incident, not another attack. That distinction matters when an already substantial loss grows overnight.

The original alarm came at 18:31 UTC on September 24, according to Bitget's security notice. The company said only part of its hot and warm wallet infrastructure was affected and its cold wallets remained secure. It paused withdrawals while keeping deposits and trading open. Bitget also said account balances remained accurate. Customers therefore face a separation between what their accounts show and their ability to move those assets elsewhere.

The investigation points beyond stolen keys

CEO Gracy Chen has described a compromise of a backend wallet service, according to Cointelegraph. Her account was that attackers forged transfer information and triggered the authorization-signing process. She said the preliminary investigation did not point to leaked private keys. That would put the weakness in the systems instructing transfers, rather than possession of the keys alone. A complete technical explanation is still important before treating that account as the final root-cause finding.

Chen also raised the possibility of North Korean involvement, citing IP and VPN patterns resembling those associated with a North Korean group. That is a preliminary attribution by the exchange's chief executive. It should not be presented as an independently established identity for the attacker. Mandiant and SlowMist are assisting the investigation, Bitget said. For affected customers, identifying the perpetrators and restoring access are separate problems, even when both are being worked on at once.

A coverage promise still needs an operational recovery

Bitget's original notice said its User Protection Fund held more than $464 million and covered the incident. That was the exchange's assurance about its own resources. It does not mean the stolen assets have already been returned. The September 25 update says some funds have been frozen and introduces conditional 5% bounties for eligible freezing or recovery work. Freezing funds and returning them to the exchange are different stages of that process.

Bitget says it has fixed the vulnerability and is validating security before restoring withdrawals. It promises an announcement about withdrawal status or timing by September 26 at 04:00 UTC. That is a deadline for information, not a guaranteed reopening time. The next useful evidence is a clear service update followed by withdrawals actually working again. Until then, the larger loss estimate and the coverage pledge should be read alongside the access restrictions customers still face.