OpenTHC :: P2P

<h2>A Peer to Peer Network for Cannabis Software</h2>

<h3>The Problem:</h3>
<p>
Isolated systems make data-exchange difficult which in turn slows business operations.
Manual data entry is both error prone and tedious.
It distracts from the main-line of business.
</p>

<p>
The centralized regulatory systems (eg: Franwell/METRC, LeafData) also do not convey all of the business relevant data.
Even in these environments (eg: Colorado, Oregon, Washington) there is considerable manual work when moving materials between businesses.
</p>

<h3>A Solution Proposal</h3>
<p>A peer-to-peer network between software providers will facilitate data exchange and improve business flow.</p>

<div style="text-align:center;">
	<img src="https://docs.google.com/drawings/d/e/2PACX-1vQKKKaOQ_Exn0IRPp3krKyt5PlnvN63s7yQYg7M6DYZ1O9pKzxlnyVrsAN1bqpViXF9xqPGGb-0cwg_/pub?w=800">
</div>

<h2>The Business Case</h2>

<p>
Reliability and Stability of the line-of-business software for this industry is critical.
</p>

<p>
I believe the way forward is through a decentralized, peer-to-peer communications protocol between the software providers and their respective customers.
When the software communicates it makes it easier for the businesses to communicate -- by which I mean <strong>transact business</strong>.
</p>

<p>
We have a dozen software providers in Washington State, there are almost 100 nation-wide.
The common problem is that all these softwares talk to each other through a central regulatory engine -- a BioTrack, METRC or LeafData system.
Many times this engine does not accomplish the goals of the software-service, which are goals outlined by our paying customers -- YOU.
A peer-to-peer network enables the software to bring about your <strong>business needs with more efficiency, reliability and stability</strong>.
</p>

<p>
For many months we (OpenTHC) have been working to bring the software providers together around some standards.
Multiple one-on-one meetings, phone calls, emails and one face-to-face group meeting have shown that nearly all of the providers agree, to some extent, this is the way forward.
To that end we have posted some <a href="https://github.com/openthc/api">API specifications</a>, protocol specifications and <a href="https://github.com/openthc/p2p">reference implementation</a> to a public repository for comment, inspection and usage by all other software vendors.
This is a system we could all begin implementing today.
</p>

<p>
Peer-to-Peer creates an environment where systems can communicate through a trusted secure channel, that is SoftwareA and SoftwareB establish their own trust.
And the combination of SoftwareA+LicenseC and SoftwareB+LicenseD are their own trust channel -- not just software trusting software but <strong>one business trusting another</strong>.
Once the trust level is established the necessary data can flow freely -- between businesses (via software) -- sharing the necessary details with each other.
Imagine never having to re-key data because it was transmitted seamlessly.
Imagine being able to transmit, regardless of the status of LeafData (or whatever vendor comes next) the product details, order details and other necessary data.
What would you when things are working better?
<strong>How would you grow your business if you weren't wasting so much time?</strong>
</p>

<p>
We need more reliability and stability to operate our respective businesses successfully.
A decentralized, distributed, peer-to-peer software solution would create that environment for us.
The beta version of this system is ready to go, some software vendors appear to be on-board.
</p>

<p><strong>How do we build the future we want?</strong>

<h2>How It Works</h2>

<p>Each node joins the network, by connecting to at least one known node.</p>
<p>Each node shares a secret key with each of the other nodes they peer with.</p>
<p>A node responds to object queries from other nodes, and a node issues object-queries to other nodes.</p>

<p>Nodes share data using a common <a href="https://github.com/openthc/api">data model</a>.</p>
<p>A reference implementation of a peer-node is <a href="https://github.com/openthc/p2p">also available</a>.</p>

<div style="text-align:center">
	<h2>A Node Diagram</h2>
	<img src="https://docs.google.com/drawings/d/e/2PACX-1vTjioFjO2uODTPPdSg3zfPOpBPetng7vQTYLKroVPW1ELjky_0_8S9chkRhmHBA9p794iTQ6VNmHvnU/pub?w=800">
</div>