Architecture

Here we going to discuss the architecture inherited by Koboto and what two approaches it can take in order to salivate economical security from the off-chain nodes

Architecture Behavior

1. Consumer Initiates Request:

The consumer, who is the end-user of the system, submits an inference request to the Application Contract on the EVM based chain. This request includes the necessary input parameters required for the AI model to perform the desired computation or inference.

1. Application Contract Relays Request:

The Application Contract receives the consumer’s request and then relays it to the Domain Coordinator contract on koboto . The Domain Coordinator is responsible for managing the overall workflow and coordinating the interactions between the on-chain and off-chain components.

1. Coordinator Validates Request:

The Domain Coordinator contract examines the request parameters submitted by the consumer to ensure they match the requirements of the available off-chain nodes. This validation process may involve verifying factors such as the type of AI model required, the expected input/output format, and any other domain-specific criteria.

1. Coordinator Initializes Payment and Stake:

If the request parameters are valid, the Domain Coordinator initiates the payment and stake processes. This likely involves locking up a certain amount of ETH or in our case koboto chain token (ERC-20) as collateral to incentivize the off-chain nodes to correctly process the request.

1. Coordinator Selects Eligible Node:

Based on the validated request parameters, the Domain Coordinator selects an appropriate off-chain node to process the inference request. This selection may be influenced by factors such as the node’s capabilities, availability, reputation, and past performance.

1. Node Wallet Locks Collateral:

The selected off-chain node then locks a portion of its own cryptocurrency in the Node Wallet, which is a shared wallet managed by both the Coordinator Contract and the node’s own infrastructure. This collateral serves as a guarantee that the node will correctly process the request.

1. Node Executes Inference:

The off-chain node receives the request from the Domain Coordinator, processes the input using the appropriate AI model, and generates the output.

8. Node or Verifier provides (Proof of inference):

After successfully processing the request, the off-chain node generates a cryptographic proof that demonstrates the correctness of the computation. This proof is then submitted to the Coordinator Contract on koboto.

1. Coordinator Verifies Proof:

The Domain Coordinator contract receives the proof from the off-chain node and thoroughly verifies its validity .

1. Coordinator Releases Payment:

If the proof is deemed valid, the Domain Coordinator releases the payment from the Node Wallet to the off-chain node, rewarding it for the successful processing of the request.

1. Application Contract Delivers Result:

Finally, the Application Contract receives the verified output from the Domain Coordinator and passes it back to the original consumer, completing the request lifecycle.

The process flow highlights the key steps involved in the interaction between the consumer, the on-chain contracts, and the off-chain nodes running on koboto . It emphasizes the critical role of the Domain Coordinator in managing the overall workflow, validating requests, selecting appropriate nodes, and ensuring the correctness and integrity of the inference results.