Our Blog

S3 is the storage standard the world already knows. Amazon invented it, and over the past fifteen years it became the default interface for moving, storing, and retrieving data across virtually every serious application, cloud workflow, and developer toolchain on the planet. When developers choose a storage API, S3 is almost always the default.

Auto Drive already had an S3 endpoint. But as more developers pointed their S3 tooling at permanent storage, the gaps became apparent. Buckets weren’t behaving like buckets. Listing objects didn’t fold into the directory structures S3 clients expect. File integrity checks were returning content identifiers rather than the MD5 checksums those clients use to verify data. And when a tool sent a delete request, it got back a generic error with no explanation.

This release fixes all of that.

‍

What S3 Compatibility Actually Means

S3 is not just a storage product but a standard interface that thousands of tools, libraries, and services were built to work with. When a storage system is genuinely compatible with it, those tools can point at that storage system without modification. Enterprises migrating off cloud providers do not need to rewrite their pipelines. The number of workflows that can route data to permanent storage expands dramatically, because the cost of switching drops to near zero.

That is the strategic significance of this release.

‍

Four Gaps, Now Closed

Buckets work the way buckets are supposed to. Previously, all S3 keys lived in a single flat namespace. The new behavior treats the first segment of every S3 path as the bucket name, which is exactly how S3 clients expect it to work. Anything stored before this change migrates automatically into a default bucket, so nothing existing breaks. The ListBuckets endpoint now returns a proper list of distinct buckets in the standard format every S3 client can read.

Object listing now supports real directory navigation. The ListObjectsV2 request is what S3 clients use when they want to walk a storage hierarchy, sync a folder, or browse a bucket’s contents. It supports filtering by prefix, folding objects into virtual subdirectories, paginating through large result sets, and capping page sizes. Without it, any tool that needs to navigate or synchronize a bucket has nothing to work with. It now works.

File integrity checks return what S3 clients expect. S3 clients verify data integrity by comparing an MD5 checksum, known as an ETag, against a locally computed value. Auto Drive previously returned each file’s content identifier in that field, which is meaningful within the Autonomys DSN but confuses any tool expecting an MD5. The ETag header now returns the MD5 in the standard format on upload, on object inspection, and in listings. The content identifier is preserved in a separate metadata field, so nothing is lost. For anyone building workflows that previously required bypassing checksum verification to use Auto Drive, that workaround is no longer necessary.

Delete requests return a clear, honest answer. Auto Drive storage is permanent by design. Data written to the Autonomys Distributed Storage Network cannot be deleted, because permanence is a protocol-level guarantee, not a software setting. Previously, a delete request hit an unhandled route and returned a generic error. The new behavior returns a 403 response with a plain-language explanation: the storage is immutable, and objects cannot be deleted from the DSN. That is the correct behavior for any immutable store, and it turns a confusing error into a self-explanatory one.

‍

Reusable for Anyone Building on Autonomys Storage

The logic behind these improvements, the directory folding algorithm, the pagination mechanics, the ETag computation for both single and multipart uploads, is now available as a standalone module in the Auto SDK’s @autonomys/file-server package. Any developer building their own S3-compatible layer on top of Autonomys storage can use these building blocks directly rather than solving the same problems from scratch.

‍

What This Opens Up

S3 compatibility is not just a developer convenience but what makes permanent storage accessible to the workflows that handle the world’s serious data at scale.

Backup utilities, data synchronization pipelines, archival workflows, and compliance logging systems can now treat Auto Drive as a direct destination. The integrity verification that regulated industries require works without modification. The directory structures that data engineers use every day behave as expected.

Some of this work was shaped by a specific integration we will have more to say about shortly (stay tuned)!

‍

Get Started

The new S3 behavior is live on Auto Drive now. If you are already using the S3 endpoint, no client changes are required to pick up bucket routing or MD5 ETags.

For endpoint setup and authentication, the S3 layer documentation on the Developer Hub has been updated with examples of all new behaviors.

For the full technical breakdown of every change in this release, including implementation details, schema migrations, and the new Auto SDK exports, read the milestone PRs on GitHub.

For a more technical explanation (somewhere between this post and the code itself), check out the accompanying forum announcement.

Get started on the free tier at ai3.storage.

And as always, reach out to us on Discord if you have questions or are building something we should know about.

Solana Added as Auto EVM Bridge Destination

Powered by Hyperlane and built by Protofire, the Autonomys bridge now connects the Auto EVM Domain to Solana on mainnet. Builders and users on both networks can now move assets freely between the two chains.

Did You Know?

The Autonomys bridge already connects the Auto EVM Domain to Ethereum and BNB Smart Chain (BSC). Solana is the latest destination, and it is the most requested: in a community poll, Solana came out on top with 36% of the vote, making it the clear winner.

The bridge gives Autonomys users and builders direct access to some of the most active ecosystems in crypto and the liquidity that lives within them. Whether you are moving assets for DeFi, testing cross-chain integrations, or deploying multi-chain applications, the bridge is how capital flows between Autonomys and the broader Web3 ecosystem.

Built with Hyperlane by Protofire

The Autonomys bridge is built with Hyperlane by Protofire. Hyperlane is the cross-chain messaging protocol that defines the transfer standard and security model for each route. Protofire is the infrastructure partner that deployed the bridge, and continues to maintain and expand it. Every route on the bridge, including Ethereum, BSC, and now Solana, runs on this same foundation.

A New Kind of Connection

The Autonomys EVM Domain already provides broad compatibility with the Ethereum ecosystem, including MetaMask, Hardhat, Foundry, and any EVM-compatible tooling. Solana is a different kind of addition. It is one of the highest-liquidity, most actively used networks in crypto, and connecting to it requires dedicated infrastructure because Solana’s runtime is fundamentally incompatible with the EVM. This route provides exactly that: a governed, permissionless corridor for assets to move between the Autonomys EVM Domain and Solana, opening up both the builders and the capital on the other side.

Check out our forum post for more details.

Bridge Today

The bridge is accessible through the Autonomys bridge interface.

To transfer assets:
1. Connect your wallet on the source chain
2. Select your origin and destination network
3. Select the asset you want to transfer
4. Enter the amount and destination address
5. Approve and submit the transaction

Mainnet:
https://bridge.mainnet.autonomys.xyz/?destination=solanamainnet&origin=amn

Testnet is available for anyone who wants to test transfers before using mainnet: https://bridge.chronos.autonomys.xyz/?destination=solanatestnet&origin=acn

More assets and routes will be announced as the bridge infrastructure expands.

Official docs including a guide can be found here:
https://docs.autonomys.xyz/bridge

Always verify the contracts you are interacting with: https://docs.autonomys.xyz/bridge#token-contract-addresses

For questions, visit the Autonomys Discord:
https://autonomys.xyz/discord

‍

Autonomys is pleased to share that Crypto Inheritance Protocol (CIP), a multi-chain, privacy-first inheritance infrastructure for digital assets, has integrated Auto Drive, Autonomys’ permanent on-chain storage product, gaining direct access to the Autonomys Distributed Storage Network (DSN) for permanent, tamper-proof storage of inheritance records.

What the Integration Is

CIP integrates Auto Drive at two specific points in the execution lifecycle.

Health Oracle Execution:
When an executor initiates a health oracle check, uploading an image or PDF as proof of a principal’s condition, that document is written permanently to Auto Drive. It becomes the immutable trigger record: timestamped, tamper-proof, and independently verifiable by any party. No server dependency, no document loss, no dispute over what was submitted.

Beneficiary Dispute Filing:
When a beneficiary raises a dispute and uploads supporting documents, those files move to Auto Drive immediately. This creates a permanent, censorship-resistant evidence trail that exists outside of CIP’s infrastructure, meaning the dispute record survives regardless of what happens to the protocol itself.

In both cases, Auto Drive is not a backup layer. It is the permanent receipt that makes CIP’s execution guarantees credible.

Why Permanent Storage Is Integral to CIP’s Build

Inheritance execution does not operate in real time. It operates across years, sometimes decades. When a critical action finally fires, the documents that triggered it must still exist, unaltered, exactly as they were submitted. That is the core requirement Auto Drive solves.

Auto Drive is built on the Autonomys DSN, where data is erasure-coded and replicated across a globally distributed network of independent storage operators. Data stored through Auto Drive inherits the permanence and tamper-resistance guarantees of the Autonomys Network itself. The network’s architecture removes any single point of control: data is distributed across independent operators globally, with no entity in a position to alter, delete, or restrict access to what has been stored.

For CIP, this means the documents its users submit today are designed to remain accessible and independently verifiable across the full span of time an inheritance plan may be active.

Building for Decisions That Outlive the People Who Made Them

Autonomys is proud to support the CIP team and their work on what is genuinely one of the more thoughtful applications built on permanent storage infrastructure. The problem CIP is solving is real, consequential, and almost entirely unaddressed in the digital asset space. Building a protocol that must remain trustworthy across decades requires exactly the kind of architectural discipline the CIP team has brought to their stack, and we look forward to seeing what they build from here.

To learn more about CIP, visit: www.ciprotocol.com

To learn more about and sign up for permanent, verifiable storage through Auto Drive, visit: ai3.storage

‍

About Crypto Inheritance Protocol

Crypto Inheritance Protocol (CIP) is a multi-chain, privacy-first inheritance infrastructure for digital assets. CIP enables individuals and institutions to define programmable inheritance plans specifying beneficiaries, unlock conditions, and execution logic that executes automatically, without intermediaries, regardless of payment status or executor availability.

CIP is built on three core infrastructure layers: iExec powers decentralized task execution and stores sensitive plan parameters as ProtectedData objects on Arbitrum; Secret Network provides confidential smart contract logic ensuring beneficiary data and unlock conditions remain encrypted end-to-end; and Secret AI handles on-chain documentation verification, enabling CIP to authenticate supporting documents, identity proofs, legal instruments, death certificates, without exposing their contents to any third party.

‍

About Autonomys Network

Autonomys is a Layer 1 blockchain built for permanent, verifiable data storage. Its Distributed Storage Network is secured by a global network of independent storage operators who collectively provide over 50 petabytes of SSD capacity. Data stored on the network is cryptographically verified, replicated for redundancy, and permanently available without relying on any single company or server. Developers integrate through Auto Drive, the network’s user-friendly storage gateway, which offers an S3-compatible API, a TypeScript SDK, and a free tier for getting started.

X | LinkedIn | Discord | Telegram | Blog | Docs | GitHub | Forum | YouTube

Earlier this month, we announced Pay with AI3, the ability to purchase Auto Drive storage credits directly with AI3, Autonomys’ native token, with no intermediary required. Today we’re taking the next step.

Full Pay with AI3 support is now available in the Auto SDK, starting with @autonomys/auto-drive v1.6.10.

‍

Built for Developers

Developers are integral to the evolving Autonomys ecosystem, and this update reflects that. Rather than expecting builders to reverse-engineer payment flows from the API, we packaged the entire Pay with AI3 experience into four guided SDK function calls. Our goal was to fundamentally simplify the developer experience so that curious developers can experiment without friction and serious ones can deliver impact without unnecessary detours.

‍

From Eulonomys to the SDK

Some of you may have seen Eulonomys, the open-source reference app we built to prove out Pay with AI3 end-to-end (GitHub). Eulonomys was built with a custom payment service that handled intent creation, transaction watching, status polling, and price conversions manually. That code has now been absorbed into the SDK as first-class methods, with two additional capabilities on top: live price estimates and contract details without hardcoding anything.

‍

Get Started

The update is purely additive, so everything you have already built continues to work exactly as before. Your existing upload and download calls are completely unaffected. The SDK README includes complete examples for both viem and wagmi if you want copy-paste starting points.

Updated developer documentation is available at: develop.autonomys.xyz/sdk/auto-drive.

Update to the latest SDK: npm install @autonomys/auto-drive@latest

New to Auto Drive? Sign up at: ai3.storage.
Your account includes a complimentary 20MB upload and 5GB download per month, no payment required to get started.

For the full technical breakdown, including on-chain transaction details and integration notes, the developer forum post has everything you need.

Questions? Reach out to us on Discord.

April was defined by two developments that expanded what Auto Drive is and who it is for. Pay with AI3 opened a direct, permissionless path to permanent storage for anyone holding AI3, removing the last dependency on foundation access programs. healthpass1 became the first health data application to build on Auto Drive, bringing permanent, encrypted, user-controlled storage into a category with genuine mainstream relevance. Eulonomys demonstrated what building on that infrastructure can look like in practice. Engineering continued its steady progress and the Subspace Foundation remained focused on stakeholder unlock preparation. This report outlines the material progress made in April and the momentum carrying into May.

Engineering & Protocol

• Pay with AI3: Developers and users can now purchase Auto Drive permanent storage credits directly using AI3, with no intermediary required. The purchase flow covers package selection, on-chain payment confirmation, and a full credit purchase history, with balances and expiry warnings visible directly in the dashboard. Google authentication is required at launch. A per-account cap of 100GB and a 90-day credit expiry are in place as deliberate economic protections during the network’s early growth phase. Unused credits at expiry are automatically refunded. Fiat payment options are being explored.
  To learn how to Pay with AI3, visit: https://youtu.be/KMpVhpOaFgU
• Upgrade rollout: A structured update cycle is in progress. Unresolved issues identified through GitHub are being worked through systematically as part of the rollout.
• Data Domains research: Data Domains are specialized execution environments designed to address bandwidth limitations and significantly increase network throughput, enabling hyper-scalable permanent data storage and fast data availability for decentralized AI applications. Research into their architecture is ongoing, with further details to follow as the work progresses.

Ecosystem & Developer Momentum

healthpass1

healthpass1 selected Auto Drive as the decentralized storage foundation underlying its personal health passport application. The app consolidates a user’s health and wellness information into a single, private, encrypted record that travels with them. Auto Drive’s client-side encryption architecture ensures data is encrypted on the user’s device before it reaches the network. No storage operator, network participant, or third party, including healthpass1, has access to unencrypted file content. Encryption keys are generated and held exclusively by the user. Permanence and privacy are structural properties of the architecture, not policy commitments.

This partnership represents a new category of use case for permanent, verifiable storage on Autonomys. Read more.

Secret Network

Progress on the bidirectional Autonomys and Secret Network integration continued. Further details will be announced once complete.

WeatherXM x Autonomys Builders Program

Applications to the Builders Program remain open. To apply, visit: autonomys.xyz/builders.

Community & Foundation

Stakeholder Unlocks

Preparation for upcoming stakeholder token unlocks remained the Subspace Foundation’s primary focus in April. Stakeholders can expect continued updates in the coming weeks on mechanics and any additional required actions.

Eulonomys

Eulonomys, the first third-party application built on Pay with AI3 and Auto Drive is live. Eulonomys allows users to create permanent, on-chain eulogies stored on the Autonomys DSN. It is open source, lives in the Autonomys Community GitHub, and was built explicitly as a reference implementation. The payment flow, Auto Drive SDK integration, wallet interaction on Auto EVM, platform and merchant pattern, and moderation and community fund systems are all documented and designed to be copied and extended. If you are building on Auto Drive and Pay with AI3, this is a great reference.
To see how the application works, visit: https://youtu.be/cMlaWvectS8

Grants

The Subspace Foundation Grants Program received 12 new applications in April, bringing the total to 57, with several projects currently in active review. Builders working on permanent storage, agent infrastructure, or data availability are encouraged to apply: https://subspace.foundation/grants

ICYMI: Content Published in April

• Introducing Pay with AI3: Permissionless Permanent Storage on Your Terms
• healthpass1 and Autonomys Network Partner to Give People Private and Secure Control of Their Health Information

Metrics: April Snapshot

Staking: 39,967,090 AI3 (+115,485 from March)
Auto Drive Files Uploaded: 300 (Apr.) / 129,621 (All time)
Auto Drive Downloads: 2,250 (Apr.) / 14,806 (All time) (+1,051 from March)
Auto Drive Users: 673 (+27 from March)
Total Announced Partnerships: 64 (+1 from March)
Announced Auto Drive Integrations: 9 (+1 from March)
Total Grant Applications: 57 (+12 from March)

Looking Ahead

In May we anticipate sharing further details on the Secret Network bidirectional integration, the healthpass1 integration, and continued stakeholder unlock preparation. Pay with AI3 will mature as real usage patterns emerge and inform the next decisions on constraints and access.

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

‍

Most storage demos exist to show that storage works. Eulonomys exists to show that permanent storage matters.

Built by the Autonomys community, Eulonomys is a web application for creating permanent, on-chain eulogies stored on the Autonomys Distributed Storage Network via Auto Drive. It is also the first application built against Pay with AI3, the permissionless payment flow that allows anyone holding AI3 to purchase storage credits directly, without going through the foundation or filling out a form.

The choice of use case was deliberate. A eulogy is not a financial instrument. It is the last public act of love a person performs for someone they have lost. When you write a eulogy on Eulonomys today, it is designed to be there permanently. No server to shut down, no company to go bankrupt. The words endure. That promise is only credible because the Autonomys Network enforces it at the protocol level, not the terms-of-service level.

How It Works

Eulonomys is built on Next.js, deployed on Vercel, with Prisma and Neon Postgres handling metadata, moderation state, and search indexing. The storage layer is the Autonomys DSN, accessed via the Auto Drive SDK.

Every eulogy is content-addressed. Anyone can verify that what they read is exactly what was written, unchanged and uncensored, by fetching it directly from the Auto Drive files gateway.

Payment is handled through Pay with AI3. Each eulogy is an on-chain transaction, meaning your words become part of an immutable record that exists as long as the network does. The application calculates storage cost based on file size, prompts the user to complete the transaction with AI3, and proceeds with the upload once payment is confirmed.

Memory Should Be Within Reach

Eulonomys ships with a community fund. Sponsors can contribute AI3 tokens to cover storage costs for users who cannot afford them. Preserving memory, as the site puts it directly, should be within reach for everyone.

There is also an optional LLM-powered writing assistant. It is not designed to write the eulogy for you. It is designed to help you find the words you already have but may be struggling to express in your time of grief.

The community guidelines are honest about what permanence actually means. Moderation can exclude content from the browse index, but it cannot remove anything from the chain. Once a eulogy is written to the Autonomys DSN, no one, including the Autonomys team, can alter or delete it. The site asks users to be certain before they publish.

For Developers

Eulonomys is open source and lives in the Autonomys community GitHub. Every architectural decision in the codebase was made with one question in mind: what would a developer building their own application need? The payment flow, the Auto Drive SDK integration, the wallet interaction on Auto EVM, the platform/merchant pattern, the moderation system, and the community fund are all minimum viable implementations, documented clearly, and designed to be copied and extended.

The Autonomys Network built Auto Drive to ensure data could last permanently. Eulonomys is the first proof that what lasts can also be deeply human.

If you are building an application on top of Auto Drive and Pay with AI3, we encourage you to explore and reference Eulonomys.

Get started with Auto Drive at: https://ai3.storage
Full SDK documentation is available at: develop.autonomys.xyz/sdk/auto-drive
To see how the application works, visit: https://youtu.be/cMlaWvectS8

‍