# Seed: Connecting Livepeer with EthereumPhone **URL:** \ **Category:** Uncategorized\ **Created:** [February 2, 2022, 10:38pm UTC](https://forum.livepeer.org/t/seed-connecting-livepeer-with-ethereumphone/1679 "2022-02-02T22:38:37Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![videoDAC](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.livepeer.org/videodac/32/630_2.png) [@videoDAC](https://forum.livepeer.org/u/videoDAC)\ **Post date:** [February 2, 2022, 10:38pm UTC](https://forum.livepeer.org/t/seed-connecting-livepeer-with-ethereumphone/1679/1 "2022-02-02T22:38:37Z")
## Introduction This seed of an idea is about connecting Ethereum Phone with Livepeer, for mutual benefit to all parties. ## Context **EthereumPhone** ([www](https://www.ethereumphone.org/), [github](https://github.com/EthereumPhone), [discord](https://discord.com/invite/FtVvK7B2KT), [twitter](https://twitter.com/EthereumPhone)) is a part of a project to make the world’s first Ethereum mobile operating system. It is based largely on LineageOS ([www](https://lineageos.org/), [github](https://github.com/LineageOS), [twitter](https://twitter.com/LineageAndroid)), which is successor to CyanogenMod ([wikipedia](https://en.wikipedia.org/wiki/CyanogenMod), [archive.org](https://web.archive.org/web/20161224194030/https://www.cyanogenmod.org/)) In images below, the Ethereum Phone appears to be connected to remote peers on Ethereum mainnet. ![image](https://canada1.discourse-cdn.com/flex030/uploads/livepeer/original/1X/81162e74efda4253e8b0836d0309cfa50ecb8524.jpeg) ![image](https://canada1.discourse-cdn.com/flex030/uploads/livepeer/original/1X/8f2594ebe032d7b79190027e74b63bbaa6da1c0f.jpeg) Photo: markkat#4524 on Discord. Device: Google Pixel 3 XL **Livepeer** ([www](https://www.livepeer.org/), [github](https://github.com/livepeer), [discord](https://discord.gg/uaPhtyrWsF), [twitter](https://twitter.com/livepeerorg)) is a project to build a decentralised livestreaming platform. The project is incentivised via a delegated-Proof-of-Stake (dPoS) mechanism, running as [a set of contracts](https://github.com/livepeer/wiki/blob/master/Deployed-Contract-Addresses.md#mainnet) on Ethereum. Livepeer Public Network consists of an active set of Orchestrators, which manage the work performed by Transcoders on the network. The grafana dashboard of one Orchestrator looks like this: ![image](https://canada1.discourse-cdn.com/flex030/uploads/livepeer/original/1X/28d70442b2a40e86c4fde1dbc09b4f32faec9d54.png) The grafana dashboard of one Transcoder looks like this: ![image](https://canada1.discourse-cdn.com/flex030/uploads/livepeer/original/1X/3b856071e7b9a302e8ad09d3a9c4eda1da379307.png) ## The Seed EthereumPhone will be in control of the device’s camera and microphone… telling them when to turn on, and turn off. - Start capturing **video** , - Start capturing **audio** , > Question: How can these functions integrate natively and elegantly with a Livepeer Orchestrator, _as a way to **offload energy-intensive video processing** _. > This offload from the “resource-constrained” mobile device, onto the powerful servers, can be used to drastically enhance a user’s live experience, especially as mobile network speeds increase. ## Proposed Minimum Viable Integration A basic integration can even be done as an automatic onchain integration. An on-device “livepeer” process can query the device’s own RPC endpoint, which can return the following from the chainstate: - the Ethereum `address` of each Orchestrator in Livepeer Public Network - the `serviceURI` (`http://ip-address:port`) of each Orchestrator A next step could be to request each Orchestrator to provide a summary of their service offerings. ## Nirvana End-State A nirvana end-state may be where a device can offload all of its “live and in real-time” audio/video processing workload to Livepeer Public Network. For example, when a user starts capturing **video** and/or **audio** , the OS can initiate connections with Livepeer’s Orchestrators. A user can then choose to start consuming any available services, at the published rates. Services may include things like: - transcoding, (currently public alpha on mainnet), - object recognition, (currently in closed alpha on mainnet), - detection of copyrighted audio (currently in closed alpha on mainnet), and - other live / real-time “AI on the edge” services provided by GPUs. An Ethereum `address` managed on the device can handle payment for services rendered, as well as allowing a user to delegate to an Orchestrator, in order to earn a share of their fees and rewards, as some kind of “video UBI”. ## Conclusion Cultivating such connections at the operating-system level, between: 1. cameras & microphones inside mobile devices, and 1. farms of live Orchestrators, on Livepeer Public Network, can prove to be a powerful basis for mobile innovation, powered by open and public video networks.