TL;DR: Microsoft Research says its Magnetar system makes proofs of ordinary program execution faster while relying on standard hash-based cryptography.

Zero-knowledge systems promise that a computation can be checked without trusting the machine that performed it. One reason they remain difficult to deploy is the cost of generating those proofs. Microsoft Research’s October 15 Magnetar announcement tackles that bottleneck using a virtual machine designed to prove ordinary programmes.

The researchers say Magnetar supports code compiled from Rust, Go and C and performs between 10 and 39 times faster on average than certain comparable proving systems across their benchmarks. Verification takes roughly 12 milliseconds, according to Microsoft’s tests. The system is built around standard hash functions, a design intended to reduce reliance on cryptography vulnerable to future quantum attacks.

For blockchains, lower proving costs could make verifiable offchain computation and complex application logic easier to use. But benchmark figures are not a guarantee of equivalent improvements inside production rollups or every smart-contract workload. Integration, hardware conditions and proof sizes all matter.

There is also a broader potential use case: institutions and AI agents could produce verifiable evidence that software followed specified instructions without exposing underlying private data. The research suggests a future in which cryptographic proofs are attached to more ordinary computer operations, although that future will depend on implementation outside the laboratory.

More from NewsBTC: Cryptocurrency news · Ethereum coverage · Crypto research and categories

TL;DR: Visa, BILL and Billtrust are piloting trusted AI agents that complete approved invoice payments through supplier portals.

The next stage of automated payments may depend less on how fast a transfer settles and more on proving who authorised it. Visa, BILL and Billtrust announced an October 20 live pilot allowing trusted AI agents to initiate and complete approved buyer-invoice payments through supplier portals.

The project uses Visa’s Intelligent Commerce tools, including Trusted Agent Protocol, to authenticate software agents to portals that historically expected a human user. The companies emphasise preserving supplier oversight and controls. This is a limited business-payments pilot, not an announcement that autonomous systems now have open-ended authority to spend on behalf of anyone.

For cryptocurrency wallets, there is a close parallel. An agent could technically sign and broadcast transfers today, but the difficult questions concern budgets, permissions, revocation, audit trails and responsibility when the agent makes an error. Those are exactly the issues businesses will have to solve before automatic onchain commerce becomes routine.

Visa’s experiment is not itself a public-blockchain settlement launch. Its relevance to crypto is the permission layer: whichever rail eventually carries an automated payment, businesses will want evidence that the software initiating it was known, constrained and acting within instructions. That security problem is becoming a commercial product category of its own.

More from NewsBTC: Cryptocurrency news · Ethereum coverage · Crypto research and categories

Tether is trying to make Bitcoin mining equipment easier to operate as one system. Its October 24 announcement brings 15 industry participants behind an open software framework, shifting the focus from buying more machines to making existing infrastructure work together.

• Mining companies, hardware makers and pools have committed to integrations with Tether’s MDK.
• The framework provides a common software interface for otherwise separate equipment.
• A stable 1.0 release remains a target for the end of 2026.

The challenge is connecting a mixed mining fleet

Tether’s announcement names participants including Bitdeer, Bitmain, Canaan, MicroBT, Foundry and Block’s Proto. Their commitment is to build and maintain integrations. It is not a disclosed purchase order, a new Bitcoin reserve or evidence that every participating company has already converted its mining sites.

The MDK product description separates those integrations into equipment adapters, a core runtime and a gateway for applications. An operator could connect machines and supporting infrastructure through that common interface instead of building a completely different control system for each vendor.

Consider a site that changes cooling equipment while retaining its miners. Monitoring software should not need to be rebuilt from scratch merely because the hardware mix changes. Consistent interfaces can reduce that repeated engineering work, although the quality of each integration still determines how reliably an application behaves.

That concern is different from the capacity additions in NewsBTC’s reporting on Soluna and Bitdeer’s Texas expansion. More electrical capacity creates room to mine; operating software determines how effectively a complicated site uses the equipment connected to it.

Automation will need evidence beyond a participant list

The public documentation already offers a demonstration environment with mock hardware, a gateway and a dashboard. That gives developers a place to examine the design before connecting software to real equipment. Testing against simulated devices and controlling a live industrial site are materially different stages.

An automated controller can make a mistaken instruction faster than a person can. Useful deployments therefore need clear permissions, reliable measurements and a way to stop or override actions. An open interface makes those controls possible to inspect; it does not prove that any particular installation has implemented them well.

The economics also remain site-specific. NewsBTC’s coverage of recovering network hashrate and Bitdeer’s mining and AI operations illustrates the competing pressures operators face. Lower integration costs could help, but MDK has not supplied a universal figure for electricity savings or higher mining margins.

The useful milestones are maintained adapters, successful installations and measured operating improvements. Industry support gives the toolkit a broader starting point. Demonstrating dependable control across different sites is the work still ahead.

Written by the News Desk and edited by Samuel Rae.

TL;DR: PHP released fixes for two critical flaws on October 21 and urged immediate updates. Crypto businesses using PHP-based web infrastructure should check that layer of their systems; the advisory does not announce a breach of Bitcoin or BTCPay Server itself.

Security work for a crypto business does not end at its wallet. A critical PHP update has put ordinary web-server software back on the operational agenda.

The PHP project’s October 21 advisory identifies two vulnerabilities that can allow unauthenticated remote code execution. Fixed upstream releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The project strongly encourages affected users to update immediately.

It says installations serving web requests are at risk and highlights the Apache mod_php configuration as particularly exposed. Distribution vendors may provide patched packages, so the applicable fix depends on how the software is supplied and maintained.

A Payment Stack Contains More Than Its Payment Processor

The connection to crypto commerce is practical. BTCPay Server’s official documentation explains how merchants can connect its payment system to WooCommerce, including arrangements involving an existing store or a deployed store environment.

A merchant using that combination has several components to maintain. The checkout website, its plugins, the hosting environment and the payment service have distinct responsibilities. Updating one component does not establish that every other part of the stack has been patched.

The PHP advisory is about the runtime handling web requests. It is not evidence that Bitcoin’s protocol has been compromised, and it does not by itself identify a flaw in BTCPay Server’s core software.

It does provide a reason for administrators and hosting providers to check whether any connected storefront or service uses an affected PHP installation. The relevant confirmation is that the running environment contains the fix, rather than simply that an application plugin was updated.

Follow The Maintainer’s Remediation

The PHP team’s guidance is the authoritative starting point for remediation and version-specific details. Unsupported installations need particular attention to vendor support or migration to a maintained release.

No claim about stolen customer funds or a specific crypto company’s compromise is established by the advisory. The immediate news is the release of critical fixes for infrastructure that can sit underneath a crypto payment experience.

Related Reading

• BTCPay Server Patches Critical LND Credential Bug After Lightning Wallet Drain
• Coldcard Security Notice Puts Bitcoin Wallet Entropy Risk Back In Focus
• EIP-7702 Wallet Delegation Faces Scrutiny After Phishing Research

This article was written by the News Desk and edited by Samuel Rae.

TL;DR: Birdeye has launched Peak, a subscription terminal combining digital-asset market data, fundamentals and portfolio analytics. Its pitch centers on consistent data across venues, rather than another isolated trading dashboard.

Institutional crypto researchers have another terminal to evaluate. Birdeye launched Peak on Wednesday, bringing several of its data and analysis services into one professional workspace.

The company’s October 21 announcement describes coverage spanning centralized and decentralized venues, with ETF flows, filings and private-funding information alongside on-chain data. Access is sold by seat and organization.

The official product page lists token supply and unlock information, holder concentration, wallet-level portfolio analysis, protocol metrics and institutional indices. A command-based interface lets users move between different objects and views, while a research layer called Peak AI is intended to surface connections across datasets.

The Value Depends On Consistent Definitions

Putting several data feeds into one screen can save time. It does not automatically make the figures comparable.

For a researcher examining an asset, circulating supply, fully diluted valuation and an upcoming unlock each describe something different. A wallet transfer might be a sale, a custody move or an internal reorganization. A large volume figure can also look more useful than it is if the methodology does not distinguish between types of activity.

Those are the practical problems an institutional terminal must solve if it is to support decisions beyond simple price monitoring. Users need to trace a number to its source and understand the assumptions behind it.

Birdeye says owning its on-chain indexing infrastructure lets it reconcile records and apply consistent definitions. That is the company’s explanation of its approach, rather than an independent audit of every metric delivered by Peak.

The product has not been performance-tested for this article, and the launch release does not establish that an AI-generated connection between datasets is a verified investment conclusion.

For prospective users, the relevant test will be whether the terminal makes research reproducible: can a colleague reach the same result, identify the same inputs and explain why the number changed? Peak’s launch puts that question in front of institutional desks with a new product built around it.

Related Reading

• Solana’s Tokenized Asset Market Grows More Than Sixfold In A Year
• Tokenized Stocks Reach $262 Million In DeFi, But The Growth Is Not All On Base
• Stablecoin Payments Reach $482 Billion As Token Supply Barely Grows

This article was written by the News Desk and edited by Samuel Rae.

TL;DR: The Zcash Foundation says it merged fixes for Zebra nodes that stopped syncing near the chain tip. The October 21 update places the work ahead of a stable NU7 release and reminds operators of the older client’s approaching stop date.

Zcash’s preparation for NU7 includes a less glamorous but essential task: making sure nodes keep following the chain reliably.

In an engineering update published Wednesday, the Zcash Foundation described fixes for synchronization problems reported after Zebra 7.0.0-rc.0. Its team also confirmed the same underlying cause on a mainnet node.

The changes adjust how Zebra requests blocks from peers and handles failed downloads. At the time of the update, the work was merged into the development branch but had not appeared in a published release. The foundation described Zebra 7.0.0 as the likely next stable NU7 release.

Merged Code Still Has To Reach Operators

That release distinction matters. A fix being accepted into development does not mean an exchange, wallet provider or individual node is already running it.

Operators normally receive the benefit when an appropriate release is published and deployed. Services relying on their own nodes then need to establish that those nodes have caught up and continue to follow the network correctly.

The update also describes improvements to handling ZEC amounts through Zebra’s RPC types and a migration guide for services moving from zcashd’s interface. These are integration concerns that can affect the reliability of downstream systems even when they do not change what an ordinary transaction looks like.

An Approaching Operational Deadline

The foundation repeated that Zebra 6.4.x is designed to stop around November 2, making an upgrade to the NU7 release an operational requirement for affected mainnet users. The broader NU7 planning thread provides the surrounding upgrade schedule.

The October 21 report covers engineering work from October 6–19. It should be read as a dated account of readiness, not as proof that every item was already deployed across the network or that every subsequent release decision had been completed.

There is also no basis in this update for describing the synchronization issue as a theft of coins. The reported problem concerns node behavior and the work needed to deliver a stable client ahead of the upgrade.

Related Reading

• Zcash Fixes Critical Orchard Vulnerability As ZEC Holds $600 Support
• Zcash Crashed 50% On A Four-Year-Old Secret — The Recovery Has Quietly Begun
• Winklevoss Zcash ETF Filing Brings Privacy Coin Exposure To Nasdaq

This article was written by the News Desk and edited by Samuel Rae.