TOSI staking & asset issuance

Prior to issuing an asset or data for verification, the publisher stakes TOSI tokens. The stake is slashed if the publisher’s asset is found fraudulent by the node network. The purpose of the stake is to increase the publisher’s credibility and showcase that the publisher has an incentive to not submit fraudulent assets.

Whenever publisher creates or updates a datachain (issues or submits assets or data), they pay a fee in TOSI tokens.

Publishers can input any kind of asset and data via APIs, CSV and other files, database accesses, 3rd party signatures, and other methods. Tosi supports both offline and online data, including public, semi-private or private sources, and zero-knowledge proofs about data.

Publishers can use 3rd party services such as Zippie’s dashboard to easily construct a data contract that is published into IPFS and which content identifier (CID) is sent to the Tosi main chain. A data contract is a program used to conduct the verification which can be written in standard programming languages such as JavaScript, and is executed by the Tosi verifier nodes in order to conduct a public verification.