Verification Workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, c, docker
- Domain
- backend, blockchain, cloud, distributed-systems
Research direction
Start with the workflow diagram and the linked verification-truebit prototype, then review the stated transcoder, verifier, Ethereum protocol, and S3 assumptions. Done would require a concrete implementation scope and a validated workflow, but this issue names no repository files or tests to run.
Written by the indexing model from the issue text.
Description
Verification Workflow
The verification module assumes the following workflow:
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.
- Dominant language
- C
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from livepeer/TranscodingVerification
-
livepeer/TranscodingVerification#12 · 1 assignee ·
-
Transcoding demo Open
livepeer/TranscodingVerification#11 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Write a cli tool Open
livepeer/TranscodingVerification#9 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in livepeer/TranscodingVerification
Similar issues
-
internal.h中，漏掉了1个定义。 Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zephyrproject-rtos/zephyr#120011 ·