Decentralized solutions with no bottlenecks and versatile public/private validation strategies.
Data is sharded across a network of full peers. No centralized servers, ledgers, or different user classes.
Rigorously ethical, lossless approach to data integrity and context specific provenance.
Each of us wants to have control over how and with whom we interact. In order to evolve and thrive our communities must support everyone's uniqueness. Yet, today, our online relationships are dominated by centralized corporate structures.
Holochain enables a distributed web with user autonomy built directly into its architecture and protocols. Data is about remembering our lived and shared experiences. Distributing the storage and processing of that data can change how we coordinate and interact. With digital connection under user control, Holochain liberates our online lives from the loss of power over our information.
Holochain applications are held entirely by the people who use them. No trusted third parties. No centralized points of failure. They enable direct communication and consent through development solutions that minimize risk, reduce costs, and optimize for speed.
Holochain apps use a monotonic Distributed Hash Table (DHT) to enforce validation rules on data published from a user's signed source chain. Each agent holds their own immutable hash chain and backs up a sample of the apps public data as a node in the DHT. This makes powerful and secure decentralized computing possible on devices as lightweight as mobile phones.
Every application runs its own holochain, on its own terms, without the need for expensive hosting overhead. Since users are the hosts, as more agents begin using the app, more storage becomes available.
The “DNA” of an app comprises the first entry of an agent’s source chain. These rules set validation requirements ensuring that the application runs securely: that data cannot be counterfeited, tampered with, or lost. An app’s validating DHT randomizes redundancy of public data across nodes in the shared space. When nodes go offline, the DHT continues to maintain the data necessary for the app to perform. And if someone changes the app rules they write themselves out of the shared DHT into an entirely different application.