Onchained
Preserve NFT artwork and metadata directly on Ethereum to keep digital art accessible beyond its original hosting.
Onchained - Preserve NFT Artwork on Ethereum 🖼️
Released September 9, 2026
Overview
I built Onchained to preserve NFT artwork and metadata directly on Ethereum. For supported NFTs, it stores the exact files available at preservation time and records how they connect to the original NFT.
Your original NFT stays in your wallet during preservation. Afterward, you can leave the files preserved, create a transferable Remount, or create a locked Twin linked to the original's ownership.
The Problem
An NFT can outlive the service hosting its artwork. The token may still be in your wallet after its metadata server or image host disappears. Onchained stores those files on Ethereum so they can be read directly from the chain, along with the information connecting them to the original NFT.
Key Features
- Exact file preservation: Store metadata and image bytes without normalizing or re-encoding the originals.
- Multiple storage sources: Preserve supported artwork from decentralized storage and conventional web hosting.
- Visible verification method: Show whether a preservation is verified on-chain or attested by Onchained before payment.
- Quoted delivery: Present a fixed preservation price, the files to be stored, and an execution deadline.
- Preserved artwork on display: Remount and Twin tokens display the stored artwork without relying on its original host.
- Independent access: Read stored files and check their provenance directly through Ethereum with the verification and recovery tools.
Verification and Attestation
For eligible files, Onchained verifies on-chain that the preserved metadata and image match the original NFT's source reference.
Other supported sources use an Onchained attestation: a record of what was retrieved and where it came from. For conventional web hosting, this depends on Onchained's account of what the server returned. Your quote shows which method applies before you pay, so you can understand how the connection to the original is established.
Preservation Modes
Remount
The current owner deposits the original NFT and receives a transferable Remount with the same token ID. The Remount displays the preserved artwork directly from Ethereum.
The Remount holder can restore the original by burning the Remount. Restore returns the deposited token without a protocol fee or administrator approval.
Twin
A Twin is a locked companion NFT that leaves the original in its existing wallet. Its recorded owner can be synchronized after the original changes hands. The current original owner can remove the Twin, and holders cannot transfer it directly.
Preservation Record
The stored files and their source records remain discoverable even when the owner chooses neither mode. Remount and Twin are optional actions after preservation completes.
Preservation Workflow
- Select an NFT from the connected wallet or enter its collection and token ID.
- Request a quote that checks supported sources and previews the files.
- Review the price, verification method, and deadline, then pay into escrow.
- Follow progress as the files and source records are preserved on Ethereum.
- Open the completed Gallery entry and choose whether to create a Remount or Twin.
Payment is released once the quoted preservation is delivered. If the job remains undelivered after its deadline, the payer can claim a refund directly.
Accessing Preserved Artwork
The Gallery brings together the preserved artwork, its original collection and token ID, and its verification or attestation details. You can inspect what was saved and choose how to use it without changing the preserved files.
Preservation does not rewrite the original collection. It gives the artwork an additional home on Ethereum, with access that does not depend on the original image host or metadata service. Remount and Twin let owners use that preserved version while keeping a clear connection to the original NFT.
Links
- Live Application: Onchained
- Documentation: Onchained user and developer docs