Verification Workflow

Verification Workflow

The verification module assumes the following workflow:

source

Transcoder

The transcoder is a GPU running on a machine. We assume the verification module is shipped as a part of the code running on the GPU. The verification module is invoked for every transcoded segment, resulting in an array of values for validation and a single value for ranking. This list of values is published with the transcode result.

Note: We should make sure this assumption is viable. What if the machine running the GPU is a stripped down crypto mining rig that may not have the ability to run the verification module?

Verifier

In the ideal world, the verifier would be a Truebit module running on the Ethereum chain. There is a prototype built with a modified version of ffprobe, but we haven't ran it in production yet. In the mean time, we can assume it's a docker instance running on a cloud hosted instance with access to Ethereum.

The verifier invokes the quality measurement module, and compares the result with the input validation values (created by the transcoder). The verification reports fail if the values are different.

Protocol

Smart contracts running on the Ethereum blockchain. The transcoder needs to monitor the challenge event in order to invoke the verification request.

Object Store

We can assume it's a S3 bucket with public access.

Inizia con il diagramma del workflow e il prototipo verification-truebit collegato, poi esamina le ipotesi dichiarate su transcoder, verifier, il protocollo Ethereum e S3. Per considerare il lavoro completato servirebbero un ambito di implementazione concreto e un workflow validato, ma questa issue non indica alcun file del repository né test da eseguire.