Skip to content
Merged
Show file tree
Hide file tree
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
24 changes: 20 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,17 +82,33 @@ copy `wasm/bin/wallet.wasm` and `wasm/js/wasm_exec.js` to you fronted project an
</html>
```

# Schema
# Computantis architecture

The schema below shows how pieces of the computation service are connected together. This is one of the simple examples with high availability where central nodes, db shards and validators may be scaled and orchestrated with k8s or another tool.
Because the central node service, validator service as well as wallet API are compiled to a single lightweight binary running on a variety of architectures we can make the whole system lightweight.
Container size can be kept very minimal without the need for interpreters or virtual engines which is securing containers, minimizing the cold start and the container size to a few megabytes.
Low RAM and CPU consumption of a single node allows to run service on IoT devices.

The task of the whole system is simple, validate transactions, act as a message hub and seal the history of transactions within the immutable blockchain, but be performant with that task.


<p style="background-color:white;">
<img src="https://github.com/bartossh/Computantis/blob/main/docs/assets/img/computantis-cloud.drawio.svg">
<img src="https://github.com/bartossh/Computantis/blob/main/docs/assets/img/computantis-schema.drawio.svg">
</p>


# Use case scenario

The example below describes how Computantis can seal the transactions happening in distributed IoT services.
The data are only encrypted when flowing between services. When in the system it might be the case that data are corrupted or when service is compromised then transactions may be faked.
The Computantis is on its way to discovering probable scenarios of sealing the data with cryptographic signatures and immutable history. It is one of the scenarios when such an approach may be taken into consideration.

<p style="background-color:white;">
<img src="https://github.com/bartossh/Computantis/blob/main/docs/assets/img/computantis-schema.drawio.svg">
<img src="https://github.com/bartossh/Computantis/blob/main/docs/assets/img/computantis-cloud.drawio.svg">
</p>

# GO Documentation

# Go Documentation

<!-- Code generated by gomarkdoc. DO NOT EDIT -->

Expand Down
Loading