Dataflow

After we verified the stake, etc. a company will receive the software.

On- and Off-Chain Relation

Because we need to verify and extract some information off-chain, we need a structure to extract the data from the website and put it on-chain in a trusted and secure way, based on ur legal framework.

To get the data, we have a semi-database where the data we need is for every specific task predefined. With the task, the system automatically knows which contract the information has to be deployed on.

Authority Signatures

Every entry point can make an authority signature, but users also can vote on validators they trust to claim an authority signature. Authority signatures also operate off-chain, if so, the contract provides the on-chain authsignature automatically. With an authority signature, the signer can confirm the minting of tokens, activate all together the emergency protocol, or verify off-chain data. There are 3 main types of authority signatures and one subtype:

• authSign_A: Only we can make this signature.

• authSign_B: Only Entry Points can make this signature.

• authSign_C: Oracle Signature for non-legal related data.

Subtype:

• authSign_N: Authority status none, base type.

But once the development is finished, the authority signature A will be deleted, handing the keys to the network to our community.

AuthSignA, B, and C are also available off-chain.

AuthSign A, B, & C Wallet

An authSign a, b, or c status user does not have to have an extra wallet, the Auth status is saved within the wallet state. The Auth status can first only be changed by our authority signature, later, it will work like a DAO where multiple Auth members can verify a new one.

Audit Database

First, we need an audit database to store everything that has been done by the entry points. This audit contract will be connected to all database templates and will run on our servers, later, we will decentralize it.

For more DB details click here.

Snapshots

We will implement a strategy to take snapshots and send them on-chain referencing to the participants' wallet id at different stages of the off-chain process.

Software requirements

Every entrypoint needs a subsidiary to implement in the software / their system to make sure the data verification is valid. Later we will also accept other official approval companies. The entrypoints also have to have a specific activeness in the network which is predefined based on the size of the company.

Security

Every company will get a generated passcode, after the first login, they can change the password which doesn`t act as the authority signature.