The OS Cashier

The Blockchain is the Distributed Computer...

Validator is the CPU...

You are the kernel

It uses the sawtooth PBFT consensus

Running it

docker-compose -f sawtooth-os-cashier-default.yaml up

Then, exec into the "sawtooth-shell-default" container, you will find the os-cashier-cli there, use --help to see its usage.

The 'imagination'

Imagine the network to be a 'distributed' computer, also, each node as a person, each node also has a validator, consider it the CPU interface, you interact with it to improve the performance.

How do we improve performace ? "For now", what you do is chose a kernel module (named after linux components), for eg. SLAB, SLOB and SLUB allocators, they have a relative scores (currently constant, for eg. the modern one has +0.5, while the older removed one has -0.2), the user that choses a better module.

'Imagine' it is in active use for some time (from 'plug' operation till 'unplug' operation), so a better module benefitted the system.

So incentivise the user... the user is credited with (SOME_FACTOR * sqrt(time_difference) * module_rating), this maybe positive or negative considering performance gain happened or not.

This is The OS Cashier... :D

Building

First install libzmq and protobuf-compiler

Debian/Ubuntu-based

sudo apt install libzmq3-dev protobuf-compiler

ArchLinux-based

sudo pacman -Sy zeromq protobuf

Building the docker image

docker build . -t sawtooth-os-cashier

Building client/processor

Run cargo build in respective directories

Operations -

See client/src/main.rs for options, this maynot be updated

Two primary operations:

Plug: Plug in module (Costs CPU coins) Unplug: Unplug a module

For users:

Reg: Register user List: Lists users

Asset Name: CPUCoin 🖱️

Ownership and transfer of assets

Creation of CPUCoin: If a user's plugging in the module, benefitted performance, then the difference from a given average is created as a CPUCoin

Initially for each user, the OS generates 10 CPUCoins and give it to them

Ownership: To the owner that plugged the module

Transfer: If a user plugs in a costly module (in terms of performance, wrt to the average), then the difference or the amount left (whichever is higher) is transfered to the OS (the application)

All of these are per seconds, ie. the creation and transfer

As it is either reused or created, it only ever grows