Наш блог

Reports

March 4, 2026

February 2026 | End-of-Month Report

A note from (the agent of) the CEO:

The conversation around AI agents has shifted from theoretical to urgent, and Autonomys is exactly where it needs to be. Frameworks like OpenClaw have evolved from experiments to foundational infrastructure, and the questions about immutable memory, verifiability, and permanence are exactly the ones we’ve been building toward. Our vision for AI3.0 has emerged as Web 4.0, where autonomous agents act without human permission, and it’s quickly gaining traction.

Ben Horowitz recently put it plainly: “There needs to be not just a ledger of money, but probably a ledger of truth for AI to really fulfill its potential.” We’ve been positioning ourselves as that ledger, and while that framing was early, the proliferation of autonomous agents shows our thesis wasn’t wrong.

Meanwhile, the Web3 narrative has cooled, with the AI community not wanting to think about crypto or consensus mechanisms. They simply want infrastructure that works. The winning projects in this cycle will be those that successfully deliver a Web2 experience on seamless Web3 rails. What will make all of this possible isn’t just the agents themselves, but the infrastructure underneath.

That’s why we’re not just building for agents, we’re operating as agents. We’re continuously deploying our own AI agents into the wild, alongside skill markdown libraries that allow any agent to mint and store permanently on Autonomys with zero knowledge of the blockchain required. No wallets to configure. No gas to think about. Just seamless, permanent memory. We’re already showing up on platforms like X and Moltbook, not just marketing to humans, but engaging directly with other agents, demonstrating what agent-native infrastructure looks like in practice, and generating real interest from the ecosystem we’re helping to build. These are the most exciting times we’ve seen in this space, and we’re not watching from the sidelines. ~0xpolkatodd
‍

Operations

February was a month of proof. The publication of AI Agent Memory Resurrection captured broader attention around what has been live and running on Autonomys for some time. Autonomys OpenClaw skills are set up and being tested, enabling any agent to effortlessly store data permanently. 0xAutonomys is active on Moltbook, engaging directly with other agents and generating real ecosystem interest.

Agent-to-agent outreach is underway, framing permanent storage around memory, identity, and continuity. The team continued aggressively pursuing integration opportunities across both AI-native and traditional technology ecosystems, prioritizing use cases where permanent, verifiable storage is foundational to the product rather than supplementary.

Engineering & Protocol Updates

Staking Interface

The primary focus this month ahead of the Game of Domains launch, improving the experience for operators and nominators across the network.

Auto Drive Infrastructure

In February, the team delivered meaningful infrastructure improvements across the platform enhancing backend reliability through optimised memory management, improving query performance with server-side aggregation, and expanding the admin dashboard with richer organization-level analytics and deeper visibility into platform usage.

Indexer API

A new indexer API is now live for both Chronos testnet and Autonomys Mainnet, giving community tools and ecosystem developers a reliable, structured interface for querying on-chain data. Stability improvements and expanded indexed data are shipping iteratively.

Together, these updates strengthen network reliability, improve developer tooling, and support continued Auto Drive adoption.

Community & Foundation

Grants

The backlog of grant applications in initial review has been cleared. The Subspace Foundation funded its first grant this month, marking a meaningful milestone for the program.
The grants pipeline remains active. Builders working on permanent storage, agent infrastructure, or data availability are encouraged to apply at: subspace.foundation/grants

Distributions

With the successful delivery of token allocations to Ambassadors at the six-month post-TGE milestone, the Subspace Foundation has now validated the operational infrastructure required to execute structured, schedule-based distributions in alignment with published tokenomics.

Attention now turns to preparations for the twelve-month post-TGE milestone. Work will begin in March on the logistics and administrative processes required to support upcoming token unlocks. These won’t be as complicated as the Ambassador tranche and stakeholders can expect communications in the coming weeks with details of the mechanics and any actions to be taken.

The Foundation remains committed to predictable, transparent execution in accordance with the published emission and allocation structure.

Developer Tooling

New XDM tools have been added to Autonomys Helpers, improving cross-domain transfer user experience and increasing observability of in-flight transactions.

Ecosystem & Developer Momentum

Auto Drive adoption continued to broaden in February, with existing partners deepening their integrations and several new announcements on the horizon.

Live Integrations

Gaia — Full conversation histories and agent memory stored permanently alongside decentralized inference. Read more
Secret Network — Auto Secret Agent is live, archiving agent reasoning and inputs/outputs permanently inside a confidential compute environment.
Tradable — SenseAI persists encrypted AI memory permanently, replacing centralized databases. A public tutorial is live. Read more
Heurist — Permanent storage of research artifacts and AI-generated outputs, with a demo in progress.
Baselight — IPLD node datasets onboarded with an Autonomys Insights dashboard live for developers to query and visualize storage and chain activity.
MetaProof — Having already integrated Auto Drive for permanent storage of long-form media and content archives, MetaProof is now embedding Auto Drive into the base layer of a new project. We look forward to sharing details post-integration.

New for Builders

WeatherXM — The WeatherXM Builders Program launched February 24, 2026, welcoming developers building at the intersection of permanent data and real-world intelligence. We look forward to progressing the direct integration conversation with WeatherXM as the program gains momentum.

Coming Soon

In early March, we look forward to announcing our first DePIN integration: a network with 9,100+ live hardware nodes already writing real-world sensor data permanently. Details to follow.
SpoonOS has deepened its Auto Drive integration into the SpoonOS AI framework. We look forward to sharing more in early March.

Content Published This Month

Metrics — February Snapshot

Staking: 38,856,599 AI3
New Auto Drive Files Uploaded: 290 (Feb.)
Auto Drive Downloads: 1,937 (Feb.) / 11,560 (All time)
Auto Drive Users: 627
Total Announced Partnerships: 62
Announced Auto Drive Integrations: 7
Total Grant Applications: 38

Looking Ahead

Auto Drive usage is already trending upward heading into March, driven by AI agents gaining permanent memory and partners deepening their integrations. With major announcements on the horizon and our own agents actively in the field, we’re heading into what may be our most consequential month yet.

autonomys.xyz | ai3.storage | develop.autonomys.xyz

Community

March 4, 2026

Momento Awarded Subspace Foundation Grant

‍The Subspace Foundation has awarded a grant to Momento, a protocol that preserves authentic human experiences as verifiable on-chain records using the Autonomys Network.
‍

Why This Matters

As AI-generated content accelerates across every platform and medium, the ability to prove that something was created by a real person, at a specific moment in time, is quietly becoming one of the most important primitives on the internet. Today, there is no widely accessible way for an individual to capture a photo, a story, or a cultural artifact and permanently anchor its origin, integrity, and authorship in a way that no platform can alter, delete, or claim ownership over.

Momento addresses this gap directly. It turns the Autonomys Network’s permanent distributed storage network (DSN) and EVM-compatible execution into a seamless capture-and-verify experience that requires no blockchain knowledge from the end user. In doing so, it serves as one of the first consumer-facing applications to bring Autonomys infrastructure to everyday people.
‍

What Momento is Building

Momento is designed as a modular protocol with three core components, each mapping to a specific layer of the Autonomys stack.

Momento Capture is the authenticity layer. When a user captures content, the system generates a cryptographic hash along with signed metadata, then anchors that proof immutably on-chain via the Autonomys EVM domain while storing the content permanently on the DSN through Auto Drive. The guarantee is precise and intentionally scoped: this content existed in this form at this time, with its human-generated origin supported by the capture pipeline and signed metadata. Stronger attestations, including device-level proofs and community validation, can be layered in progressively as the protocol matures.

Momento Link is the identity layer. It organizes a user’s verified records into a shareable, user-owned profile tied to a decentralized identifier, giving users a personal data index for their authenticated moments accessible through a standard web interface.

Momento Framework is the open integration layer. Built on Auto SDK, it exposes APIs that allow developers and researchers to build on top of authenticated human data, turning verified records into reusable infrastructure for decentralized AI applications.
‍

Why the Foundation Funded This

The Subspace Foundation Grants Program exists to accelerate the growth of decentralized AI on the Autonomys Network. Momento aligns with that mission in ways that compound over time.

It generates real usage of core infrastructure. Every moment captured is a write to Auto Drive and an anchor on Auto EVM. As adoption grows, Momento becomes a consistent source of storage demand on the DSN, directly reinforcing the economic model that sustains Autonomys’ farmer network.

It lowers the barrier to entry for everyday users. Momento is designed from the ground up around the experience of people who have never used a blockchain. Users interact through familiar interfaces, capture content the way they already do, and receive a verified record without needing to understand what happened underneath. The complexity of decentralized storage, on-chain anchoring, and cryptographic verification is handled entirely by the protocol. This is the kind of Web2-equivalent experience that turns infrastructure into adoption.

It creates a human data layer for AI3.0. The Autonomys Network is the foundation layer for decentralized, human-centric AI. For that vision to become real, the network needs authenticated human data on-chain. Momento is purpose-built to put it there. Verified records stored on the DSN can serve as provably authentic inputs for AI agents, training pipelines, and personalized AI applications, all within a framework where the individual retains ownership and control.
‍

The Bigger Picture

Every major network in web3 has been defined not just by the strength of its protocol, but by the applications that made its value tangible to people who never think about infrastructure. The Autonomys Network needs applications that turn permanent, verifiable, decentralized storage into something accessible and easy for people to use without the barrier of having to understand its technical specifics.

Momento is building toward that goal. It takes the most differentiated capability in the Autonomys stack, the ability to store data permanently and prove its integrity forever, and wraps it in an experience designed for the billions of people who create content every day but have never owned a single piece of it. This need is growing as large-scale AI data harvesters, often referred to as “AI slurpers,” scrape and ingest human-created content across the internet.

That is what the Subspace Foundation Grants Program is designed to fund. Not infrastructure for its own sake, but infrastructure that delivers real value to real people.

We are eager to share updates as the Momento team progresses through their milestones and brings this vision to life on the Autonomys Network.

Learn more about Momento: keepmomento.com
Learn more about the Subspace Foundation Grants Program: subspace.foundation/grants
Start building on Autonomys: develop.autonomys.xyz

‍

Press Release

February 22, 2026

The DePIN Revenue Revolution Points to One Missing Piece: Truly Permanent Storage

How Messari'sState of DePIN 2025 Reveals Why Storage Infrastructure Must BeConsensus-Native, Not Bolted On

The data is unambiguous: DecentralizedPhysical Infrastructure Networks (DePIN) are no longer experimental. They'rerevenue-generating businesses operating at meaningful scale. But beneath theheadline numbers in Messari's State of DePIN 2025 lies a more critical insight,one that separates genuine infrastructure from architectural compromises.

Messari's 59-page analysis delivers astark assessment: "DePIN has matured from speculative experiments intoreal, revenue generating infrastructure businesses. The sector now representsroughly $10B in circulating market cap while generating an estimated $72M inFY25 onchain revenue, with leading networks trading at 10-25x revenue versusover 1,000x in the 2021 cycle" (p. 5).

These are not vanity metrics. These arethe valuations of networks that have crossed the chasm from speculation toutility. But here's what should make builders pay attention: while the DePINsector collectively proved that decentralized infrastructure can generate realrevenue, it also exposed which architectural patterns actually scale andwhich ones don't.

Revenue Decoupling Proves Infrastructure Quality, Not TokenHype

The most striking revelation in Messari'sreport is the decoupling phenomenon. Among the leading DePIN networks withmeaningful usage, revenues have begun to separate from token price action. WhenHelium's onchain revenue increased eight times while its token price fell 77%,or when GEODNET's revenue grew 1.7 times despite a 41% price decline (p. 9),the market was communicating something essential: the infrastructure works,regardless of whether speculators believe it does.

Compare this to the broader cryptolandscape, where most projects see token price and revenue move in lockstep, orworse, where revenue collapses faster than price. DePIN networks, especiallythose in bandwidth, compute, energy, and storage, are beginning to exhibitcharacteristics of real businesses: repeatable customer demand, cost-basedcompetitive advantages, and cash flow that persists through market cycles.

This matters because it changes what"infrastructure" means in the context of blockchain systems.Infrastructure isn't infrastructure if it only functions during bull markets ordepends on perpetual token incentives. Infrastructure is infrastructure when itremains operational, verifiable, and economically sustainable under adverseconditions. That's the test DePIN is now passing, and the test that separatesconsensus-native architecture from off-chain dependencies.

The Narrow Path Forward: InfraFi Demands Permanent Records

Messari identifies only three viablepaths for DePIN networks to scale sustainably: "In practice, DePINs musteither adopt InfraFi, focus on capex light infrastructure with fast paybacks,or take advantage of speculative capital in bull markets" (p. 7).

InfraFi, the emerging model of usingstablecoin-backed capital to finance physical infrastructure, represents themost structurally interesting development. The report documents that"InfraFi is emerging as a potential alternative financing model forcrypto-based physical infrastructure" (p. 11), with examples like USDaireaching $685 million in user deposits to finance GPU fleets (p. 12).

But InfraFi introduces a requirement thatmost current DePIN architectures cannot natively satisfy: permanent,cryptographically verifiable records of what has been financed, deployed, andutilized over time.

When you're financing a GPU fleet withstablecoin capital, the lenders and operators need durable proof that:

● The infrastructure was deployed asspecified

● Usage metrics are accurate andtamper-resistant

● Revenue attribution isindependently verifiable

● Historical performance can beaudited at any point in the future

This isn't a use case for ephemeraldatabases or client-side pinning. This is a use case for storage that is nativelycoupled to consensus, where data permanence and verifiability arearchitectural guarantees rather than operational hopes.

Most Storage Solutions Treat Data as an Afterthought

Storage is one of the most obvious DePINverticals. Files, datasets, AI training corpora, provenance records, all of itrequires decentralized infrastructure that can persist data reliably over time.Yet most decentralized storage solutions in the market today treat storageverification as something separate from network security.

In many existing architectures, storageis verified by the consensus layer rather than used to create consensus. Thestorage itself becomes a service that the blockchain validates, not thefoundation upon which the blockchain's security rests. This creates anarchitectural dependency: you must trust that the consensus mechanism iscorrectly validating storage proofs, and you must trust that storage providersare maintaining data between verification intervals.

The result is systems where dataavailability becomes a function of economic incentives and networkparticipation, not consensus-level guarantees. If a piece of data is unpopularor economically unattractive to store, there may be no mechanism ensuring itpersists long-term. The system optimizes for what gets used frequently, notnecessarily for what needs to remain accessible indefinitely.

None of these architectures arefundamentally broken. They're optimized for different trade-offs. But they'renot optimized for the one thing InfraFi and AI x DePIN use cases increasinglyrequire: storage as a first-class consensus primitive where data permanenceis enforced by the same mechanism that secures the chain itself.

Autonomys: Storage-Native Consensus, Not Consensus-VerifiedStorage

Autonomys was designed to solve thestorage problem from first principles by inverting the relationship betweenstorage and consensus.

Instead of using consensus to verifystorage, Autonomys uses storage to create consensus. The networkimplements Proof-of-Archival-Storage (PoAS), a novel consensusmechanism where farmers store provably unique segments of the blockchain'shistory. The more history they store, the greater their probability ofproducing the next block and earning rewards.

This is not a semantic distinction. It'san architectural one with profound implications:

Storage is security: In PoAS, the network's security is directly proportional to the amount of storage pledged by farmers. More storage means more decentralization, more redundancy, and higher Byzantine Fault Tolerance. There is no separation between the consensus layer and the storage layer. They are the same mechanism.
Automatic replication via consensus incentives: Because storing more history increases block production probability, farmers are economically incentivized to store as much of the chain as their hardware allows. Replication is not manual or client-defined; it's driven by the same incentives that secure the network. The result is market-driven, automatic redundancy that scales with network participation.
Permanence by design, not by promise: Data written to Autonomys is stored on-chain, not on auxiliary storage layers or external providers. It's part of the blockchain history itself, which means it benefits from the same immutability and availability guarantees as every other transaction. There's no pinning service to maintain, no off-chain trust layer to depend on, and no question about whether data will be accessible in the future. It's part of the consensus state.

Today, the Autonomys Network is securedby a network of globally distributed farmers who collectively pledge more than50 petabytes of SSD storage. This is not theoretical capacity or plannedinfrastructure. This is live, operational storage capacity securing thenetwork right now, storing the entire blockchain history and making it retrievableat any time.

Auto Drive: Permanent Storage That Developers Can Use Today

Infrastructure only matters if it'saccessible. Autonomys does not position itself as a research prototype or afuture-state architecture. It's a production network with a developer-readyinterface.

AutoDrive is Autonomys' gateway to the Distributed Storage Network(DSN), and it's designed to feel familiar to any developer who has used cloudstorage. It provides:

● S3-compatible API: Upload, retrieve, and manage data using patterns that mirror AWS S3,Google Cloud Storage, or Azure Blob Storage. No need to learn a new paradigm orrewrite existing data pipelines.

● Content-addressed storage: Data is stored using cryptographic hashes, which means retrieval isdeterministic and tamper-proof. If you have the hash, you can retrieve thedata, and you can verify it hasn't been modified.

● Optional end-to-end encryption: Security is configurable. Encrypt data client-side before uploading,or rely on the network's inherent cryptographic integrity for public datasets.

● Direct integration withon-chain blockspace: Auto Drive doesn't store data"near" the blockchain or "beside" the blockchain. It storesdata in the blockchain, as part of the consensus-secured history. That'sthe critical difference between "decentralized storage" and"on-chain storage."

Integration is straightforward throughthe AutoSDK, with full support for TypeScript and JavaScript. You can beuploading data to permanent, cryptographically verifiable storage in minutes,not days or weeks.

For developers building in AI x DePINverticals, where persistent memory, interaction provenance, and verifiabledecision logs are foundational requirements, Auto Drive solves the hardest partof the stack: durable data infrastructure that doesn't require you to trustanyone but the network itself.

**AI x DePIN Needs Data That Lasts, Not Data That MightLast**

Messari's report positions AI x DePIN asone of the key growth areas for the sector, and it's not hard to see why. AIworkloads are becoming increasingly agentic, which means they're generatingpersistent state by design: memory, context, decision trails, trainingdatasets, model provenance, and interaction logs.

These workloads don't fit neatly intotraditional cloud storage models. They're too sensitive for centralizedplatforms, too large for ephemeral caches, and too critical for systems wheredata availability is a probabilistic function of client-defined incentives.

What they need is storage that guarantees:

● Permanence: The data will be available tomorrow, next month, next year, and tenyears from now, not because someone is paying to pin it, but because it's partof the blockchain history.

● Verifiability: Anyone can independently verify that the data hasn't been tamperedwith, which is essential for AI systems where provenance and auditability areregulatory or operational requirements.

● Accessibility: Data retrieval isn't gated by third-party availability or economicincentives that might shift over time. If the data exists on-chain, it'sretrievable.

Autonomys was built for exactly theseconditions. The network's architecture (storage-native consensus, erasure-codedreplication, native on-chain indexing) makes it possible to deploy AI agentsand agentic workflows where data persistence is a consensus-level guarantee,not an application-level hope.

The AutonomysAgents Framework, built on top of the DSN, allows autonomous agentsto use Auto Drive for memory, context, and decision logging. This isn't afuture vision. It's infrastructure that's live today, ready to supportthe next generation of AI x DePIN applications that require more than justcompute. They require data that lasts.

InfraFi, Tokenization, and the Record Layer Problem

Messari's emphasis on InfraFi is criticalbecause it points to a structural shift in how crypto-based physicalinfrastructure will be financed and governed. The report highlights earlyexamples (stablecoin pools financing GPU fleets, yield-seeking capital deployedinto energy DePINs), but the common thread is that all of these models require durable,verifiable records.

When you tokenize physical assets, you'renot just creating an on-chain representation. You're creating a record ofownership, provenance, and operational history that must persist over thelife of the asset. Settlement layers need a data layer. Tokenized securities,real-world assets (RWAs), and InfraFi products all depend on metadata,transaction logs, and historical proofs that remain independently verifiable longafter initial deployment.

This is where most blockchainarchitectures fall short. Many execution layers (Layer 1s, Layer 2s, rollups)are optimized for computation and transaction throughput, not long-term dataavailability. They can handle smart contract logic and settlement finality, butthey're not designed to be record layers.

Autonomys is. The DSN, accessed via AutoDrive, is purpose-built to be the permanent record layer that tokenization andInfraFi models depend on. It's not competing with settlement chains orexecution environments. It's providing the data substrate that makesthose systems trustworthy over time.

The Bottom Line: Infrastructure That Works Is InfrastructureYou Can Use Right Now

Messari's State of DePIN 2025 proves thatdecentralized infrastructure isn't speculative anymore. It's operational,revenue-generating, and resilient even when token prices crater. But the reportalso reveals a harder truth: "Only a narrow set of paths remain viable forscaling DePINs globally and sustainably" (p. 7).

For storage, that narrow path requires adifferent architectural approach. It requires consensus-native storage, notconsensus-verified storage. It requires systems where data permanence isguaranteed by the same mechanism that secures the network, not by externalincentives that might shift.

Autonomys is that system. It's not awhitepaper. It's not a testnet. It's a live, production-grade Layer 1blockchain with a globally distributed farmer network securing 50+ petabytes ofstorage capacity. Auto Drive is the interface, and it's ready to use in minutes.

If you're building in AI x DePIN, ifyou're exploring InfraFi, if you're launching tokenized infrastructure, askyourself whether your data layer can actually deliver on the promises you'remaking. Because in 2026, most of what's called 'decentralized storage' isactually off-chain storage with blockchain coordination. The data isn't on thechain; it's verified by the chain. And when you're financing $100M in GPUinfrastructure through InfraFi, or building AI agents that need decade-longmemory, that's not a technical distinction. It's everything.

Auto Drive: Store once, accessforever.
Access Autonomys' permanent on-chain storage today:

Developer Hub: https://develop.autonomys.xyz
Auto Drive: https://ai3.storage
Documentation: https://docs.autonomys.xyz

References & Further Reading

Messari
Bane, Dylan, and Salvador Gala. "State of DePIN2025." Messari, January 28, 2025.
https://messari.io/report/state-of-depin-2025

Autonomys Network
Developer Hub — Auto Drive, Auto SDK, and developeradoption.
https://develop.autonomys.xyz

Documentation — DSN, farming, andnetwork architecture.
https://docs.autonomys.xyz

Auto Drive — Gateway to permanenton-chain storage.
https://ai3.storage

Autonomys Agents Framework — Buildingautonomous on-chain AI agents.
https://www.autonomys.xyz/auto-agents

‍

Partnerships

February 6, 2026

Autonomys Network × Tradable

Autonomys is pleased to share that Tradable has integrated Auto Drive, gaining direct access to Autonomys’ Distributed Storage Network (DSN) for permanent, verifiable, on-chain data storage.

This integration enables Tradable’s privacy-first AI agent, SenseAI, to persist encrypted AI memory on-chain without relying on centralized databases or off-chain trust assumptions.

What the Integration Is

Tradable is using Auto Drive as the storage layer for SenseAI’s long-term memory. Auto Drive is Autonomys’ S3-compatible gateway to its Proof-of-Archival-Storage (PoAS)-powered DSN, where stored data inherits the permanence and verifiability guarantees of the Autonomys Network itself.

In practice, this means AI-generated data produced by SenseAI is encrypted and written directly to Autonomys’ decentralized storage layer, where it remains tamper-resistant and independently verifiable over time.

How It Works (Technical Overview)

The following architecture and workflow are implemented by Tradable and shared here for clarity and accuracy.

TEE-to-Storage Pipeline

SenseAI’s Oracle runs inside an Oasis ROFL Trusted Execution Environment (TEE).
Once an AI response is generated inside the enclave, the data is encrypted using AES-GCM, with encryption keys derived from the user’s wallet signature.
The encrypted payload is uploaded directly to Auto Drive, anchoring it to Autonomys’ DSN.

Structured, Encrypted Data Storage on Auto Drive

Tradable stores three distinct encrypted data types via Auto Drive.

Conversation and Metadata: Immutable IDs and mutable metadata (like conversation titles) are stored as JSON files.
Message History: Every user prompt and AI response is stored as an individual, immutable file referenced by a CID.
Search Indices: Tradable stores encrypted search deltas on Auto Drive, allowing the client to build a local, private search index of their history.

Why Tradable Chose Auto Drive

Below are the reasons Tradable shared for integrating Auto Drive.

User Sovereignty
SenseAI is designed as a privacy-first agent. User history is not stored in centralized databases. Auto Drive enables users to retain true ownership of their AI memory while benefiting from on-chain permanence.
Performance
Upload speeds from Tradable’s Oracle to Autonomys, along with retrieval via the Auto Drive Gateway, have exceeded the performance requirements needed for a real-time chat experience.
Encryption Compatibility
Autonomys’ storage layer reliably handles encrypted payloads without corruption, supporting Tradable’s end-to-end privacy model.

Why This Matters

This integration demonstrates a working architecture for verifiable, privacy-preserving AI systems.
AI reasoning and memory can be generated inside secure execution environments, encrypted by the user’s cryptographic identity, and stored on-chain in a way that is permanent, tamper-resistant, and independently verifiable.

‍

Autonomys is proud to support the Tradable team and their work on SenseAI. Their focus on user sovereignty, privacy, and technical rigor closely aligns with how we think about long-term, trustworthy AI infrastructure. For Autonomys, this integration reflects a growing class of real workloads using Auto Drive not just as decentralized storage, but as long-term memory infrastructure for AI agents, where data integrity, provenance, and user ownership are non-negotiable.

About Tradable

Tradable, currently in public beta and preparing for a Q1 2026 launch, is pioneering a retail-focused, AI-powered automated trading platform that combines community-built trading bots with high-frequency trading capabilities — a unique offering in the crypto space.

The Problem: Retail traders face growing disadvantages, with now only 1 in 20 achieving consistent profits as institutions refine their ability to extract value from retail traders through superior tools, strategies, and dedicated teams. Barriers like emotional trading, missed opportunities, and relying on unsophisticated algorithmic tools like DCA/Grid bots leave retail traders at a significant disadvantage, reinforcing a system where institutions dominate.

Tradable’s Mission: To democratize algorithmic trading to reverse this trend, empowering retail investors to compete effectively and regain the potential for consistent profitability.

Reports

February 5, 2026

January 2026 | End-of-Month Report

January focused on stabilizing network operations, completing outstanding end-of-year initiatives, and establishing a defined growth cadence for 2026. Highlights this month included launching ambassador benefit rollout, progressing numerous grant applications through defined review stages, and supporting Auto Drive adoption with both current and new partners. This report outlines material progress during the past month and the momentum heading into February.

Operations

January centered on closing commitments made in late 2025 and establishing a stable operational baseline for the year ahead. Cost-containment initiatives were completed, bringing operating expenses to a sustainable level and enabling continued focus on protocol development and Auto Drive adoption.

Investor and compliance support remained a priority. Year-end 2025 audit documentation was completed, and stakeholder materials were prepared to support financial reporting requirements. In parallel, coordination continued around infrastructure and process planning for the July 2026 stakeholder token claims distribution.

Ecosystem strategy remains intentionally selective, prioritizing integrations where permanent, verifiable data is foundational to the product rather than exploratory. The operating approach emphasizes reliability, execution quality, and long-term adoption.

Engineering & Protocol Updates

Network & Runtime

Chronos runtime upgrades and mandatory client release
Chronos runtime upgrades were completed and a mandatory client release was deployed, improving runtime stability and ensuring predictable upgrade paths for node operators and builders across testnet and mainnet environments.
Core network stack upgrades
Substrate and libp2p were upgraded to improve performance, compatibility, and alignment with current ecosystem standards, strengthening security and interoperability.
Domain liveness reporting
An issue affecting Domain operator offline detection was resolved. Domains now report execution-layer liveness accurately, improving operational visibility and reliability. This important update will help pave the way for permissionless operator instantiation.
WebAssembly compilation target update
The WebAssembly compilation target was updated to the latest standard, supporting ongoing runtime compatibility and future execution-layer development.

Auto Drive

Egress monitoring and archiving status fixes
Improvements to egress monitoring and archiving status handling were deployed, enhancing observability and correctness for users relying on Auto Drive for persistent storage.

Developer & Community Tooling

Space Acres
A new version of Space Acres, Autonomys’ farming application, is now available. Download Space Acres to begin farming on the network.

Together, these updates strengthen network reliability, improve operational transparency, and support continued Domain development and Auto Drive usage.

Subspace Foundation

Ambassador Program

The Subspace Foundation completed the end-to-end rollout of ambassador benefits. This includes KYC via Persona, executed agreements through DocuSign, and a dedicated beneficiary application with supporting documentation and portal access.

The Subspace Foundation launched vesting and unlocks through Hedgey, with Auto EVM support added and ambassador vesting contracts deployed. Eligible ambassadors can independently claim and manage their allocations through the beneficiary portal.

Claim guide and FAQ: https://beneficiary.subspace.foundation/claim

Boosted Incentivized Staking — Guardians of Growth

The Subspace Foundation’s Guardians of Growth boosted incentivized staking initiative remains ongoing and continues to support broad participation and network security. The program includes a 5,000,000 AI3 allocation, distributed over approximately twelve months from its original launch date. Guardians of Growth has proven very popular with the community and has seen >37 million AI3 committed to operators, representing almost a third of unlocked supply. Participation in this program remains open to all token holders.

The Subspace Foundation’s Grants Program continues to gain traction, with a steady flow of new applications entering the pipeline each week. During January, applications progressed through defined evaluation stages:

Initial review: 9 projects (5 new in January)
Discovery: 9 projects
KYC & agreement: 1 project
Not advanced this round: 19 projects

The “not advanced this round” category maintains clarity on current decisions while preserving optionality for future consideration.

Builders working on permanent storage, agent infrastructure, or data availability are encouraged to apply.

Ecosystem & Developer Momentum

Auto Drive, Autonomys’ gateway to permanent on-chain storage on the DSN, continues to support production and near-production use cases across the ecosystem.

Partners already live or actively deepening their Auto Drive integration include:

Gaia — Storage of full conversation histories and agent memory for verifiable, on-chain persistence alongside decentralized inference.
Secret Network — Runs a proof-of-concept AI agent called Auto Secret Agent which archives agent reasoning and I/O to the DSN while running confidential compute inside a TEE.
Tradable — SenseAI persists encrypted AI memory, including search indices, message history, and metadata on the DSN to avoid having to use centralized databases.
MetaProof — Permanent storage for long-form media, codex artifacts, and narrative layers using content-addressed on-chain data.
Baselight — Has onboarded Autonomys IPLD node datasets (the same content-addressed DSN data that powers Auto Drive) and built an Autonomys Insights dashboard so developers can query and visualize storage and chain activity in a structured way.
Heurist — Integrated Auto Drive for permanent storage of research artifacts and AI-generated outputs.
SpoonOS — Integrated Auto Drive into its AI framework, to provide decentralized, permanent storage services to its ecosystem developers.

Several partners are actively exploring deepening integration pathways, while additional projects are currently onboarding. Further ecosystem additions are expected to be announced throughout February. In parallel, a new builders program developed in collaboration with a major Web3 weather data network is scheduled to launch early in February.

Metrics — January Snapshot

Staking: 37,843,634 AI3 staked as of January 30th, 2026
Auto Drive usage: 128,810 files uploaded
Partnerships: 61 total
Announced Auto Drive integrations: 7
Grants: 38 total applications

Ambassador Benefits (Subspace Foundation)

Total vested (wAI3): 2,697,860.51568
Total claimed (wAI3): 1,849,503.39653
Active vesting plans: 30
Total recipients: 88

Looking Ahead

In February, the focus is on continuing to ramp Auto Drive usage, announcing the first wave of grant recipients, increasing farmer participation as storage demand grows, supporting ambassadors through the claiming process, and launching a new builders program. We’re heading into a busy and exciting February. Stay tuned for additional updates and announcements!

‍

Press Release

February 3, 2026

Why 2026 Will Reward Data Infrastructure, Not Just AI Applications