Runtime Environment

Where Do Tasks Live?

While tasks run on Task Nodes, the data behind them is deliberately spread across multiple systems to ensure cost optimization and maximum performance.

Incentives and Proofs (via a Blockchain Layer)

The core of the tasks architecture is the reward structure, which is contained in the Settlement Layer. The Settlement Layer is a blockchain, and all nodes must have consensus, and they must have access to all of the information to add new blocks. This means information stored here is more expensive, and causes network bloat significantly more than other layers.

When a task executes, each Task Node submits a proof once per round, which usually references an IPFS CID with more information to support the node's work.

Supporting Information (via Decentralized Storage)

Since submissions to the blockchain layer are limited in size, additional supporting information can be bundled into larger files and uploaded to a storage network like IPFS. IPFS uses Content IDs (CIDs), a hash-based key, to represent information uniquely, meaning that once a CID is locked into the blockchain, it cannot be changed.

It is the responsibility of node operators to either host each CID themselves, or pay a secondary service such as web3.storage to host the data. In many cases, a task creator may specify where the data must be stored, and participation in a task may require access to a specific storage network.

This layer can be thought of like a harddrive, with the longevity of the information being dictated by it's purpose in the system. For task proofs, it's recommended that the information is preserved for at least three rounds, as this is the time necessary for all audits to be completed by other nodes.

Runtime Data

Finally, some information does not need to be preserved in the long term, and can be stored in the runtime on task nodes. This runtime data might include active sessions, wider information such as current rounds and submissions, and third party data that has been pulled in from integrations with other networks in order to generate proofs or provide network services.

This layer can be thought of like RAM, and is only needed to support task operation, and can then be safely discarded.

Where Do Tasks Run?

Koii Tasks run on Koii Task Nodes, which are computers or other devices such as smart phones managed by node operators. Node operators will follow the instructions set by task owners and run the Koii task (a JavaScript script) on their devices to get KOII tokens as rewards.

Koii provides both a command-line and GUI interface for managing tasks. You may want to jump to the Run a Task Node section for more information about these tools.