Planning - Truebit/Livepeer Prototype

I wanted to kick off this thread so we can plan what we'd like to accomplish with the Truebit team on the Livepeer/Truebit prototype work on February 21st and 22nd. (Related to #1)

Goal: Get a working prototype of verification of transcoding work using a TruebitVerifier working.

Challenges

1. Setting up the Truebit environment.
2. Getting the systems integrated.
3. Isolating our "Job" code, which is essentially a binary that performs transcoding on video.
4. Compiling this code for execution on the Truebit VM (WASM), or creating a custom verification game implementation. We need more info here.

I think that for 3+4 to be accurate and production ready is far beyond the scope of the 2-3 days that we spend together.

My initial instinct would be to consider the prototype successful if we can do verification of work on some reduced Job binary, which has something to do with the underlying libraries that we use for transcoding. So for example, we write a simple C program that links with the underlying library that does some sort of much more trivial transcode job, like just rescaling the video from the input profile to one single target profile.

If we can compile this for the Truebit VM and run a version of our protocol that accepts this option as the only transcode profile, and then verifies it correctly, that would be a HUGE win, and good starting point for the collaboration going forward.

Open to other ideas and thoughts as to what we need to do to plan for this. @j0sh what do you think about this goal, and potentially preparing a much more simple "program" for us to use as the sample transcoding job as we try the first integration?