On-chain Randomness
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The Livepeer protocol makes use of randomness for assignment of jobs to transcoders and determining which video segments will be challenged and verified.
Using block hashes is a weak solution because if the value to be gained in Livepeer exceeds the value gained from mining an Ethereum block, then this is subject to manipulation.
Other research includes [RANDAO](https://github.com/randao/randao) and protocols like [Arbit](https://www.reddit.com/r/livepeer/comments/6t1kgw/arbit_protocol_for_on_chain_randomness_from/). It looks like Arbit was shuttered in favor of a more compelling research solution that hasn't yet been published.
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.
Research direction
Start by reviewing the issue’s stated weakness of block hashes and the linked RANDAO and Arbit references. The payload names no implementation files, tests, or acceptance criteria; completion would require a concrete on-chain randomness approach to be selected and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100