In a world of deepfakes, data brokers, and eroding digital trust, the Filedot Model is more than an alternative architecture. It is a manifesto for rehumanizing the digital sphere—one dot, one file, one self at a time.
Because references are cryptographic hashes, the resulting graph is and content-addressable . This is the Filedot Model’s answer to the blockchain’s distributed ledger but without global consensus overhead. You do not need every node to agree on history; you only need each dot to carry its own provenance.
We are accustomed to thinking of data as weightless, ephemeral, and subject to platform whims. The Filedot Model asks us to imagine the opposite: data as solid, as portable, as legally and cryptographically equivalent to the self it represents. Whether it will succeed depends not on technical elegance alone but on whether individuals and institutions are willing to trade the convenience of centralized services for the sovereignty of the dot. filedot model
Today, individuals bear the risks of data breaches but capture little value from their data. Under Filedot, you could sell access to a dot (e.g., your shopping preferences) via a smart contract, without losing custody. The buyer receives a verifiable copy; you retain the master. Data becomes a tradeable asset, not a leaky byproduct.
First, . If losing your dot file means losing your identity, the model imposes unforgiving self-custody burdens. Proponents counter with social recovery mechanisms and hardware vaults, but usability remains a hurdle. In a world of deepfakes, data brokers, and
This design choice is revolutionary in its conservatism. It returns to the early internet’s ethos of end-to-end principle and dumb networks. A dot file is like a physical letter: sealed, signed, and self-contained. You can store it on a USB stick, email it as an attachment, or host it on a personal web server. The network becomes merely a transport layer, not an identity layer.
Authentication becomes possession of a dot and proof of control over its private key. No more “forgot password” flows. No more credential stuffing. Your dot’s private key (stored in a hardware wallet or a secure enclave) signs challenges from services. This is public-key infrastructure reborn, but with the crucial difference that the public key is derived from the dot’s content, not from a certificate authority’s ledger. This is the Filedot Model’s answer to the
Second, . If a dot is immutable (changing it creates a new dot), how do you revoke an old credential—e.g., a driver’s license after you move to a new state? The answer requires a revocation registry: a public log of “still valid” hashes. That registry reintroduces a central or consensus-based component, partially undermining the model’s purity.