GuideProjects2 min read
Onchaininator: preserving existing work
Recover the work an existing token refers to and keep its connection to the original collection clear.
Select an underlined word to see what it means.
In this guide
- 01Original work
Keep its collection, token, files, and Parts identifiable
- 02Preserve bytes
Add a verified location for the same content
- 03Revise deliberately
New scripts or presentation need a new version
- 04Retain the trail
Follow the original permissions and history
Find the actual files first.
A token’s metadata is its description and media references. Follow those references to the original artwork, scripts, and required PartsReusable components included in a work, with their own identities and permissions.For exampleSeveral artworks can share the same verified drawing library.Full glossary entry →. Record missing or unsupported files explicitly.
A preview picture might not be the original full-resolution or interactive work.
Keep a checked copy connected to the original.
Onchaininator uses KEEL’s storage, MarkA file's computed fingerprint, also called a digest or hash. A reader recomputes it to check the bytes.For exampleChanging the sketch's background color changes its Mark. A filename alone would not reveal that change.Full glossary entry →, and presentation model to preserve existing digital work. Retain the original network, contract, token, and source references beside the preserved copy.
If the original contract does not permit a presentation update, a new preservation record cannot pretend that the original token was changed.
Saving a file is different from depositing a token.
Preservation concerns the artwork’s bytes. Custody concerns who holds the original SlabThe collectible token recorded in your wallet. It identifies an owned item and points to its work.For exampleYou collect Tidal Study #7. That token is your Slab; the artwork files have their own storage records.Full glossary entry →. A wrapper may add deposit and withdrawal rules, but copying a file does not perform that deposit.
Inspect preservation and custody evidence separately.
| Claim | Evidence to inspect |
|---|---|
| These bytes were preserved | Exact stored resources, receipts, digests, and read-back |
| This is related to the original NFT | Original chain, collection, token, and source bindings |
| The wrapper holds the original | Custody state and deposit/withdrawal rules |
| The original presentation changed | A permitted original-contract update and its resulting state |
Technical detail: preservation identity
Retain original chain, collection, token ID, source URI, recovered byte digests and lengths, and the preserved object bindings. A wrapper or delegation record adds its own authority and custody model. Receipt-backed storage and custody state are independently verifiable.