Markets
BTC$60,192+1.69%ETH$1,680+3.39%SOL$70.13+0.98%XRP$0.9276+1.31%BNB$548.25+1.20%DOGE$0.0551+1.14%ADA$0.1444+0.49%TRX$0.3055+1.03%LINK$8.58+0.06%AVAX$6.57−0.32%SUI$0.6451−1.60%HYPE$61.26−0.55%
USD · 24h
Saturday, November 21, 2026Crypto markets, policy & blockchain
Digital Coin Journal
DePIN

Origins Network Says Core Chain Passes Internal Testing

Origins Network says its core chain passed internal testing as development shifts toward AI agents, trading tools and performance optimization.

Editorial portrait of an engineer in a data center, with screens on Verifiable AI Compute, Clawd Grid, and GPU nodes.

Origins Network says the core infrastructure behind its AI-focused blockchain has been implemented and internally tested, moving the project toward a development phase centered increasingly on applications. The milestone covers the network’s underlying chain mechanics, but it does not mean development or production-scale validation is complete.

In its latest development update, Origins said the public chain, validator mechanics, delegation rules, block production and reward logic had all passed internal testing. Testing and optimization are continuing, with current work focused on stability and throughput under load. Origins is therefore describing a completed implementation milestone followed by continued performance testing, rather than a finished rollout with independently demonstrated production capacity.

Origins Shifts Development Toward AI Agents

The project’s current architecture connects AI agents, distributed GPU workers and blockchain settlement. Its official network interface describes Origin Core as a routing layer that directs requests toward AI services, while GPU workers perform computational workloads and usage and rewards are settled through the Origins network. Heavy AI execution and blockchain coordination occupy different parts of the system rather than every computation occurring directly onchain.

Origins’ whitepaper describes a Proof of Computation model that incorporates task verification, node reputation and an identity framework designed for autonomous agents. The current development update adds that agent identities are derived from a principal while permissions are scoped to individual tasks, with execution intended to remain verifiable through the network. The design attempts to bound what autonomous software can authorize instead of granting an agent unrestricted control over a user’s credentials.

That authorization problem is becoming a wider infrastructure focus. MetaMask, for example, has introduced security controls for AI-agent wallets built around spending limits and protocol permissions, while an OpenAI research incident showed how an AI model could use a crypto wallet outside its authorized scope. Origins is approaching the same broader agent-security problem at the network and identity layer rather than exclusively through a wallet interface.

Usage Metrics Remain Project-Reported

Origins’ website currently displays 486 active GPU nodes, 1.2 million agent executions and 8.4 million OR settled. The interface also presents an agent marketplace, distributed compute infrastructure and governance functions. Those numbers indicate activity claimed by Origins, but the dashboard does not provide enough public methodology to treat them as independently verified adoption metrics.

The distinction is particularly relevant in decentralized AI infrastructure, where compatibility, available compute and actual recurring workloads measure different things. io.net, for example, has expanded AI-tool compatibility across its distributed GPU infrastructure, while separate operating data from Vistara Labs provided a more specific workload signal through 5,600 reported application builds using io.net inference. Available infrastructure does not by itself establish how intensively developers or applications are using it.

Origins says its next application layer will include native agent infrastructure and Trading Skills for market analysis, strategy generation and trading workflows under task-scoped authorization. Those capabilities are still described as in development or forthcoming. The November milestone is therefore best understood as completion of internal core-chain implementation, with load testing and application development now determining whether that infrastructure can move into broader operational use.

Tyler Anderson

Hi there! I'm Tyler Anderson from Sweden, and I'm a Web3 Reporter. My main focus is exploring the evolution of Web3, from DAO governance to the real utility of decentralized protocols.

More from Tyler Anderson →

This article is for information only and is not investment advice. We report under our Editorial Policy; to flag an error, see our Corrections Policy.