What it combines
- public declaration
- concealed payloads
- state-specific reconstruction objects
- cryptographic agility
- sparse and sparse-with-chaff layout
Datamorpho Whitepaper v0.001
A public technical release for multi-state files
Datamorpho is an open file standard and protocol model for files that remain valid in their original format while also containing one or more sealed hidden states. These hidden states can later be reconstructed through state-specific reconstruction objects.
Datamorpho is not steganography. Hidden states are declared, not denied.
Abstract
A declared latent-state file architecture
Datamorpho is a file standard and protocol model for creating files that preserve an ordinary visible representation while also containing one or more concealed alternate states. These states are not merely appended encrypted blobs, and Datamorpho is not steganography. A Datamorphed file is expected to declare that hidden states exist and to indicate where reconstruction information may later be found, while still withholding the structural and secret material needed to recover those states.
What it claims
Datamorpho does not claim magical invulnerability. It claims layered resistance: structured composition of cryptography, payload layout, reconstruction secrecy, and digest binding.
Motivation
Why Datamorpho exists
Traditional files are static. Traditional encrypted files are often monolithic. Traditional reveal patterns frequently require changing the public metadata location. Datamorpho addresses a different need: files that can remain ordinary and valid while also carrying hidden future states that can only be reconstructed later.
Controlled disclosure
Distribute or preserve the carrier first, then release reconstruction later.
Static location, changing meaning
Keep the file in place while allowing its reconstructable state to change over time.
Long-lived latent content
Create digital objects that can survive and evolve without replacing the carrier itself.
Model
The four-layer Datamorpho model
The protocol is easiest to understand as four coordinated layers: a base carrier, a public manifest, a concealed payload, and one or more state-specific reconstruction objects.
Base Carrier
The visible file that remains valid and ordinary to standard readers.
Public Manifest
The explicit declaration that hidden states exist and where reconstruction may later be found.
Concealed Payload
The bytes from which hidden states can later be reconstructed.
Reconstruction Object
The secret-bearing artifact that reconstructs one target state.
Security model
Layered resistance instead of one secret trick
Datamorpho’s strength comes from composition. It is strongest when cryptography, sparse layout, optional chaff, non-monotonic fragment ordering, state-specific reconstruction, and digest cross-binding work together.
Why it can be highly resistant
- cryptography protects meaning
- sparse placement avoids one obvious contiguous hidden blob
- chaff increases ambiguity and attack cost
- logical reconstruction order is independent from physical byte order
- each state may have its own reconstruction object and release timing
What it does not claim
- not impossible to break
- not a substitute for sound cryptography
- not a defense against compromised endpoints
- not a guarantee against operational mistakes
- not dependent on “secret algorithms” for credibility
v0.001 position
The reconstruction object is a complete secret-bearing artifact. If it already reveals the fragment map, ordering, and suite instructions, there is no strong architectural reason to prohibit it from also carrying the key material required for reconstruction.
Layout strategy
Sparse and sparse-with-chaff
Datamorpho v0.001 standardizes two layout strategies. Both avoid a single obvious monolithic hidden object, but they optimize for different practical constraints.
Sparse
Useful when a creator wants non-contiguous hidden spans without paying the storage or transfer cost of additional chaff. This can matter for very large files and bandwidth-sensitive environments.
Sparse-with-Chaff
Useful when additional ambiguity matters. Unreferenced bytes may be filler, chaff, or bytes belonging to other states, increasing the cost of naïve extraction.
Use cases
Where Datamorpho matters in practice
Datamorpho is broader than any one niche. It can support controlled disclosure across media, documents, games, archives, and other digital systems that benefit from early distribution and later reconstruction.
Games & Interactive Assets
Unlockable items, rewards, lore objects, and latent assets.
Archives & Delayed Publication
Long-lived files whose additional states are reconstructable later.
Documents & Controlled Releases
Reports, certificates, policies, and alternate document states.
Financial & Auction Flows
State-linked disclosure patterns where some information should emerge later.
Static Metadata Reveal Patterns
Reveal without moving the public metadata location or replacing the carrier file.
Wide Distribution with Later Reveal
Distribute the file broadly first, then release the reconstruction object at the correct time.
Current carriers
JPEG, TXT, and PDF now. Audio and video next.
Version 0.001 focuses on JPEG, TXT, and PDF. The next immediate targets after the first tooling release are audio and video, where Datamorpho’s distribution-first, reconstruction-later model becomes especially powerful.
Why audio and video are natural next targets
They benefit strongly from staged distribution, synchronized reveal, and future-proof handling of media states.
Why they are not in v0.001 yet
They introduce larger payload sizes, streaming constraints, re-encoding issues, and more demanding implementation work.
Public good
Open standard, open tooling, open infrastructure
Datamorpho is being developed as a public protocol project: an open specification, an open whitepaper, open-source reference tooling, free examples, and a free public tooling layer through datamorpho.io.
Open specification
The protocol is publicly documented and discussable.
Open-source tooling
Python and JavaScript tooling are intended to remain collaboration-friendly and reusable.
Free public service layer
Datamorpho.io is intended to offer free create and reconstruct flows and future MorphoStorage support.
Origin
From early prototype to open protocol
Datamorpho’s public origin traces back to an early prototype showcased at ETHGlobal Mexico 2022, where the project appeared as a finalist and already framed the idea of dynamic files and static-location reveal patterns. The present whitepaper and specification are the first formal open protocol releases.
Author
Germán Abal — g@evvm.org
Early prototype contributors
Ben Dumoulin — early PoC implementation support
R. Benson Evans — early PoC research support
Eduardo — early PoC design support
What comes next
The project now moves through implementation, examples, and public review
Datamorpho is currently in the public specification and first tooling phase. The next steps are practical tooling, browser compatibility, examples, testing, and broader ecosystem feedback.
1. Specification
Freeze the first public protocol release.
2. Tooling
Release Python and JavaScript implementations.
3. Public Tools
Offer free create and reconstruct flows on Datamorpho.io.
4. Expansion
Move into audio, video, interoperability, and broader review.