Open standard · Open tooling · Public infrastructure

Multi-state files for controlled disclosure

Datamorpho is an open file standard for files that remain valid in their original format while containing one or more sealed hidden states. Those states can be reconstructed later through state-specific reconstruction objects.

Read the Specification Open the Whitepaper Use the Tools

Datamorpho enables staged releases, delayed disclosure, secure distribution, archives, interactive assets, and future-proof digital objects without changing the original carrier file.

JPEG · TXT Demo Sparse / Sparse-with-Chaff State-Specific Reconstruction Cryptographic Agility Audio / Video Next

What you should understand first

This is not steganography and not a metadata trick. A Datamorphed file openly tells you that hidden states exist inside it — and where to look for the reconstruction information when the time comes.

Still a valid, ordinary file
Public manifest anyone can inspect
Concealed payload for future states
Separate reconstruction object per hidden state

Overview

What is Datamorpho?

Datamorpho is an open standard for multi-state files.

A Datamorphed file keeps its normal visible form while also containing one or more hidden future states. The file can publicly declare that these hidden states exist, indicate where reconstruction information may later be found, and still keep the actual recovery of those states dependent on a separate secret-bearing reconstruction object.

Datamorpho is not a viewer trick, not a metadata swap pattern, and not steganography. It is a declared latent-state file architecture.

Base Carrier

The ordinary visible file, such as a JPEG, TXT, or PDF.

Public Manifest

Declares Datamorphosis, hidden states, triggers, and MorphoStorage directions.

Concealed Payload

The embedded bytes from which one or more hidden states may later be reconstructed.

Reconstruction Object

The state-specific secret-bearing object used to reconstruct one hidden state.

Datamorpho architecture: a Datamorphed File (containing a Base Carrier, Public Manifest, and Concealed Payload) combined with a separately held Reconstruction Object produces the Hidden State output. MorphoStorage is an optional layer for hosting Reconstruction Objects.

Why it matters

Files do not need to be static anymore

Datamorpho makes files capable of carrying sealed hidden future states without breaking their original format. This enables safer and more flexible digital workflows where distribution and reconstruction do not need to happen at the same time.

Controlled Disclosure

Reveal hidden file states only when the correct reconstruction object becomes available.

Staged Media & Documents

Distribute media or documents early and reconstruct them later at the correct moment.

Archives & Delayed Publication

Preserve files with latent states for future release, access, or recovery.

Games & Interactive Assets

Create items, rewards, unlockables, and hidden assets with file-level latent states.

Financial & Auction Flows

Support information release patterns where some file-linked state should only be reconstructed later.

Censorship-Resistant Lawful Distribution

Spread the carrier file widely first, then release reconstruction material later.

Datamorpho gives files latent states. That is a fundamental new capability.

Current carrier profiles

JPEG, TXT, and PDF first

Datamorpho v0.001 defines JPEG, TXT, and PDF profiles at the protocol level. The first public demo tooling on Datamorpho.io intentionally supports JPEG and TXT only. Audio and video remain the next immediate targets after the first release.

JPEG

A valid JPEG image followed by a Datamorpho binary block.

TXT

A terminal Datamorpho envelope appended after visible text.

PDF

Defined in the protocol specification, but intentionally excluded from the first public website demo until a controlled implementation is ready.

Carrier profiles: JPEG appends a DMOR binary trailer block after the original image bytes. TXT appends a Datamorpho envelope block after visible text. PDF uses an incremental update structure and is defined in the protocol but not yet in demo tooling.

Free tools

Use Datamorpho without reading everything first

Many people will come here to create Datamorphed files or reconstruct hidden states. The tooling layer is meant to make Datamorpho accessible while keeping the protocol itself open and inspectable.

Creator

Create Datamorphed files from supported carrier formats using public manifests, payload layout strategy, and reconstruction objects.

Open Creator

Reconstructor

Load a carrier file and a reconstruction object to reconstruct one hidden state and export the recovered output.

Open Reconstructor

MorphoStorage

A future infrastructure layer for hosting or retrieving reconstruction-related data where appropriate, including IPFS-aligned flows.

Coming Soon

Important

The first tooling focus is correctness, usability, and protocol alignment: open-source Python tooling first, then browser-compatible JavaScript derived from the tested Python reference implementation. The first website demo scope is JPEG and TXT only.

How it works

A simple conceptual flow

Datamorpho separates a file into distinct logical layers. This makes the system easier to understand, easier to standardize, and more flexible across carriers and implementations.

Start from a valid file

A normal file is used as the visible base carrier.

Add a public declaration

A public manifest declares that hidden states exist and provides directions for future reconstruction information.

Embed concealed payload bytes

Hidden-state data is embedded into the carrier according to the selected carrier profile and layout strategy.

Reconstruct a target state later

A state-specific reconstruction object identifies the relevant payload spans, reassembly order, cryptographic instructions, and secret material needed to reconstruct one hidden state.

Not steganography

Datamorpho does not deny that hidden states exist. Hidden states are declared, not hidden in a deniable sense.

Datamorpho lifecycle: four steps — start from a valid file, add a public manifest, embed concealed payload, then reconstruct a hidden state later using a reconstruction object.

For developers

Technical properties worth understanding

Developers, security researchers, and implementers usually need more than the public explanation. The protocol is designed around layered resistance, deterministic reconstruction semantics, and open technical documentation.

Layered resistance

cryptographic agility
sparse and sparse-with-chaff layout
non-monotonic physical fragment placement
state-specific reconstruction objects
digest cross-binding between manifest, file, and reconstruction object

Design decisions in v0.001

public declaration is required
the reconstruction object is a secret-bearing artifact
different fragments of the same hidden state may use different cryptographic suites
states do not need to be sequential
the standard does not try to norm every viewer or decryption UX

Read the Specification Read the Whitepaper View Examples

Sparse vs sparse-with-chaff byte layout. Sparse: fragments in blue with empty gaps between them. Sparse-with-chaff: same fragments but gaps filled with amber chaff bytes that obscure fragment boundaries.

Examples

Understand the protocol through real carriers

Datamorpho is easiest to understand through practical examples. Each example should include the base file, Datamorphed file, public manifest, reconstruction object, and expected output.

JPEG Example

A visible image containing a later reconstructable hidden state.

TXT Example

A visible text file with a Datamorpho envelope and reconstructable hidden content.

PDF Example

A visible PDF with one or more later reconstructable alternate document states.

Static Metadata Reveal Pattern

A Datamorphed JPEG and Datamorphed metadata file working together without moving the public metadata location. A natural fit for NFT-style assets and on-chain pointer patterns where the public metadata URL must stay fixed.

View Examples

Open protocol

Open specification. Open tooling. Public good.

Datamorpho is being developed as open infrastructure. The goal is not only to publish a specification, but to maintain a reusable protocol, open-source tooling, free documentation, public examples, and free web utilities that benefit the broader ecosystem.

Open Specification

The normative structure of the format is public and inspectable.

Open Tooling

Reference tooling is intended to remain open source and collaboration-friendly.

Public Infrastructure

Datamorpho.io is intended to offer free create and reconstruct flows and future MorphoStorage support.

View on GitHub Join the Discussion Support the Project

Roadmap

Where the project goes next

Datamorpho is currently in the open specification and first tooling phase. The next layers are implementation maturity, browser compatibility, and broader carrier support.

Phase 1 Specification, whitepaper, examples, public repository.

Phase 2 Python creator and reconstruction tooling.

Phase 3 JavaScript and browser-compatible processing library.

Phase 4 Free Datamorpho.io create and reconstruct tools.

Phase 5 PDF carrier support.

Phase 6 MorphoStorage infrastructure.

Phase 7 Audio and video carrier support.

Phase 8 Expanded infrastructure, interoperability, and broader standardization work.

View Full Roadmap

Community

Public discussion is part of the protocol process

Datamorpho is an open technical project. Review the specification, join discussions, open issues, and help shape the future of multi-state file infrastructure.

GitHub

Source code, documentation, and collaborative development. View on GitHub →

Discussions

Protocol questions, design conversations, and community review. Open Discussions →

Announcements

Project updates, releases, and public communications. Follow on X →

Contact

For serious inquiries, collaborations, or media questions, write to g@evvm.org.