Skip to content

Informal Description Header Fix #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _whitepapers/Holochains.md
Original file line number Diff line number Diff line change
Expand Up @@ -288,7 +288,7 @@ O\left(\frac{n}{m}\cdot\left(log(m) + v(n,m)\right)\right).$$</span><br /> Note
<p>We thank Steve Sawin for his review of this paper, support and so much more...…</p>
### Lumber / Notes
<p>This is stuff that may or may not get used</p>
### <h3 id="informal-description">Informal description</h3>
### Informal description
<p>All Holochain installations segment the computing space by application. Each application should be thought of as single distributed computing instance operating on a separate network from other applications. For each application, Holochain installations maintain separate nodes and state and communicate over separate isolated channels. Holochain applications can be connected, but only by external agents connecting one to another. This will be explained further in [sec:bridging]. Each node participating in a Holochain application maintains a hash-chain. The first entry in the chain of all nodes is identical, and we call the DNA. The DNA consists in the entry type definitions, executable source code, and property definitions, and most importantly validation rules that define that application. Nodes also participate in operating a distributed hash table together.</p>
<p>When external agents wish to initiate a transaction on a node they control, they call an “exposed function&quot; which is subset of the executable source code that’s been defined as part of the application’s “API.&quot; These functions calls will result in changing state of the nodes only through adding one of the defined entry types to that node’s local chain. Adding data to a source chain has the side-effect of doing a DHT <span><code>put</code></span>operation for that entry, where the key is the same hash of the entry used for building the hash-chain. Thus entries are accessible to all other nodes on the network via a DHT <span><code>get</code></span>of that hash. However, all nodes receiving a <span><code>put</code></span>must first validate it by verify it with the source node.</p>
<p><span>9</span></p>
Expand Down