 My name is Pablo. Buenos dias. Good day. And today I'm going to speak about StreamEath, a project I've been working on with Ethereum Foundation and the guys from LivePeer. It's a project that we're using right now to stream DevCon. So if you go to live.devcon.org, you can actually follow all the sessions there. So yeah, I'll be speaking about what StreamEath is, how it works, and why we need StreamEath actually, which I think is the most important thing. And then I'll go over a bit of history on how the application came to be, where we used it, and also how the future is going to look like for StreamEath. So what is StreamEath? There is a very official definition that I made up yesterday. So StreamEath is a self-hosted application that event organizers can use to host their virtual events. Like I said, StreamEath was born out of a collaboration between Ethereum Foundation, LivePeer, and myself. It all started with Ethereum Foundation wanting to decouple the search from YouTube. They wanted to do three simple things at first. So our current version of StreamEath, these three simple things, fairly good, I think. So Stream, we wanted to livestream the events, of course, without relying on YouTube. We wanted to also show a schedule of the sessions for each talk. And after the event was done, we wanted to show the recording of all the sessions that we streamed. So when we started designing the application, we decided that we wanted to mimic how the application looked like. We wanted to mimic it to what a real event is. So we designed everything around rooms and sessions. So one event has multiple rooms, and one room has multiple sessions. So then from then on, we started building StreamEath. The first thing we focused on was on live streaming. So each room can have one live stream. Through the whole application, you can concurrently stream on multiple rooms. So today in DevCon, we're concurrently live streaming nine multiple rooms, which I think is pretty cool. We also focused on uptime. We built in a failover mechanism into our playback systems that allows a single room to ingest two sources that have the same content, to failover to one or the other in case there were errors in the broadcasting of one of the sources. You might be wondering what we use instead of YouTube, and that is, of course, very interesting. And that's where Live Here comes in. StreamEath is actually provider agnostic, which means that we don't do any of the broadcasting ourselves. We are just a front end that hooks into whatever video provider we want. In our case, we built a solution by default on top of Live Here, which is an awesome protocol that some of you may know. I know these guys know them because they're the core developers. So yeah. Live Here is a decentralized video streaming network built on the Ethereum blockchain. Live Here can currently distribute live and on-demand content. So yeah, it's pretty cool. I'll go more in depth on why we chose Live Here later. But you can imagine, it's a protocol built on Ethereum. So decentralization, censorship resistant, and all the nice things about decentralization, right? So like I said, the application is provider agnostic, but there's already out-of-the-box solution that integrates with Live Here. So you can start up StreamEath, set up your live here account, and start streaming decentralized. Then we also put a lot of focus into the schedule. This is because StreamEath is not only something you can use to live stream, but it's actually something that event organizers want to use to, like I said, replicate the event experience but virtually, right? So the schedule, as always, is a very important part of any event, especially events like DevCon, where you have a lot of sessions in other rooms. You kind of want to automate the process of scheduling everything and showing the information in a nice, accessible way. So we built a schedule. By the way, I'm talking about the features. Then I will do a live demo and showcase the application, because I know it might be a bit difficult to imagine what I'm saying, right? So yeah, the schedule is a very central part of StreamEath. We built multiple integrations with different schedule providers. DevCon is using pre-talks as a schedule manager, which is an open source tool for management that the DevCon team is using to organize all the sessions and all the rooms. So we built an integration with their API, and that's also available in StreamEath. So if you're an event organizer, you can spin up a pre-talks instance and get going with that and have a pretty nice schedule functionality there. Also, the application has an internal clock, which will basically sync you up with the latest sessions and always display the current information on which stock is happening and all of that. But I think that's better too that you guys see it in a live demo that I'm going to show later. Then, of course, like we said, on-demand video playback. That is also crucial for the event organizers. Actually, most of the views for events happen during on-demand playback. So live video, don't usually get too many views. But then when you start a video and you show it on-demand, because of the content we're sharing here in these talks, it's very interesting. People go and watch it. So yeah, this is also currently all the on-demand video that we are hosting on different StreamEath instances. It's also living on the live peer network. They recently developed their video on-demand features. So it's working very nicely. And I'll also show an example of a StreamEath instance where we used video on-demand. It was at Etherland last month. It worked very nicely. So I'll show a demo of that as well. And finally, plugins. And I think this is the most interesting feature. So the software architecture that we built was thought to contain this plugin feature. So essentially, in the long term, of course, we want different protocols to build plugins into StreamEath so that they can integrate their features into the application. So for instance, we are working with Radical to integrate Radical Drips. And that would allow to, I don't know if you guys know Radical Drips, but it's basically a product that allows to have tipping on web interfaces. So you could have a StreamEath instance where you're live streaming an event, and then you have the Radical Drips plugin. And so users of that, viewers of that event, could donate directly to the speakers, which I think is pretty cool. So the plugin architecture is there. Now we need to develop the ecosystem and bring people in to develop these plugins for us. And this is the slide where I show the live demo. So I'm going to, yeah. Yes. So this is the StreamEath instance that we use for DevCon. And we can see there that the video is buffering because the Wi-Fi isn't the best in the world. But yeah, so like I said, we are live streaming through LivePier. This is the main stage, as you guys can see. So even though network conditions are pretty shit, it's working fine. So props to the LivePier team. In this case, we also added the YouTube link. So the good thing about StreamEath is that because it's an open source application, each instance can be adjusted to the needs of the event. So for this, in this case, for DevCon, we also wanted to include a YouTube stream to have the maximum reach. So we're streaming both on LivePier and YouTube. And we added this nice switcher in the bottom so you can switch between it. Like I said, then the schedule. For this instance, we built the schedule into a nice navigation bar on the right panel of the page. You can look through all the talks. So yeah, when I refresh, you guys can see that the schedule kind of sync to the latest hour. So this should be me. Oh, no, this is talk five. This is not my stage. So yeah, right now in stage five, how to scale the blockchain is happening. So that's the internal clock feature that I was talking about. And yeah, it's pretty simple, but it works. Like we said, I'm going to show also. And this is the Etherlane StreamEath that we deployed. This is a custom schedule page that we built. So this is containing all of the sessions for Etherlane. You can filter by stages and days. And so when you click on a session, it goes to the session page, and it loads up the VOD content and also some speaker information and kind of like the description of the event. And let's see if the VOD video. Go check it out. Watch.etherlane.oo. It's very good content. So yeah, like I said at the beginning, three basic features, but very powerful and very effective as well. Because the main goal was to decouple ETH events and community events of centralized platforms like YouTube, right? So I think even though it's nothing fancy, we're not twitched. We don't do VR. We don't do 3D nothing. It really serves a purpose, right? And now, because I'm talking about purpose, I want to go into a bit of the ethics on why we built this, why we think it's important, and why we built this, and why we think it's important. I think that's it. Most of the Web3 events are being broadcasted using centralized providers. And this sucks a lot. And it's not just because I say that. It actually sucks. We all know YouTube and Twitch don't read a line with the core values of decentralization that we are all here for and that we believe in. So StreamEath should be a good first step to help these communities decouple from these services, right? So now we're going to look a bit of what are the problems about that you get with using YouTube, right? So the first one is pretty clear. YouTube and Twitch and others are censorship-prone. So yeah, here I put two tweets. The first one was at Eath Barcelona. The livestream was taken down because they had some copyright issues, which is usually, I mean, event production is pretty hard. You have all kinds of audio. You have all kinds of music. And sometimes some music segments with copyright can slip into the production. And then your whole stream gets taken down. So that's not good. So Eath Barcelona had one day without streaming. And then there's another tweet about a YouTube account that got taken down because they were talking about web free content on YouTube. So there were some disputes. And YouTube banned their account, right? So what is the solution? StreamEath. So that's why I'm here, talking about StreamEath. No, the solution is having a frontend. So the first one is the frontend, right? You want to deploy the frontend at decentralized storage layer like IPFS or Swarm. And that is actually one of the next steps we're going to take after Defcon, is to make sure the application is lightweight, and we can use it and deploy it in one of these two layers. And the second solution to the problem is using decentralized video providers like LivePure. Since LivePure is a decentralized layer of nodes, the content can be really stopped, even if the government or any platform says so, right? The next problem that arises from using centralized providers is the intellectual property. It is kind of tied to the censorship-prone issue. So like we said, copyright claims can result in streams being taken down, channels being banned, and users being demonetized. We don't want that. And also, it's not only that they're taking down the streams, but it's the lack of transparency in the process to decide which streams are taken down and which content is being shown or not, right? So there's really an ethical discussion around what content are we being allowed to see, right? So using decentralized services, we don't really solve this content because there's no moderation, right? But I think we're heading in the right direction in regards to not allowing this one central entity to decide what we can see or what we can't see, right? Next would be the high fee to connect creators. And this is also fairly interesting, especially recently Twitch increased their share. They're taking from content creators from, I think it was, 15% to 30% or something like this. Because these centralized providers are actually super expensive to run, right? So Twitch is, even though the content is free, it's mega expensive to run an operation like Twitch. So in the long term, they have two solutions. And one solution is to increase the share they're taking from connect creators. The other solution is to display ads, right? So yeah, moving on to a decentralized solution like StreamEath and also LivePeer will basically allow us to give back the monetization power to the connect creator. Because then if a connect creator is using LivePeer to distribute the content, the content is actually theirs, right? So he is then able to decide how he monetizes the content. Also, building on top of the plugin system that I was talking about earlier, we're really setting up this ecosystem for developers to come in and build custom solutions on top of StreamEath that they can use to monetize their content. So radical drips would be a good example. But this is what the best thing we do is create monetization routes that this is Web3 crypto. We're good at monetizing without having someone in the middle taking a share of our money. So you guys can figure out the rest. Just build a custom plugin that sends money to one address or the other. And we should be solving this issue. And finally, and that's for me, this is the most important one, the Web3 ecosystem and how Twitch, YouTube, and others are not really respecting the values that we stand for, right? Especially the open source and the communities. They build solutions sometimes. And they're trying to get into Web3. But they're not actually thinking about the community. They're not making this code public. They're not contributing back to the protocols they use, right? They're not part of our community. And yeah, I think StreamEath is actually existing because we believe in these ideas. And it's coming out of a community effort between the EF, LivePeer, and me and others, the other developers to embrace these ideas and try to help, like I said, communities decouple from these providers. And finally, oh, no, no. The most important slide. The members of the team. And I want to round of applause after I say all of their names. So first, we have Hans, which is the guy that developed quite a big chunk of the code. He's sitting there in the audience. Big props. Applause. Yes. Then we have Wesley Yefer. He's sitting there. Oh, shit. I don't know if Akio is here. I don't think so. He's watching me on the stream, Akio. What's up? He's the designer. And then I'm there with the panda that I set for the merch. It's my PFP for the merch thing. I didn't change it. So yeah, the panda. And that's me. And you don't have to clap. So yeah, it was awesome working with these guys. Really great. Quick things. We used it at DevConnect. That was the first demo that we used. It was awesome. Lots of traction. We hacked a demo in, like, a week. So that's why I'm saying it's a great team, because we didn't really plan the development. It was really a decentralized development effort, because everyone was doing its own thing. So when we go to DevConnect, it was awesome. We got great numbers of viewership and no box, I think. So great. Then we went to Etherlane. And we redid the design. We called it StreamEase 2.0. We added dark mode, which is actually the best feature in the whole application. The schedule, super good. There, really, we had no box. And I know this for sure. And overall, we were super happy with it. And then, yeah, DevCon, which is great. So yeah, and how does the feature look like? We're going to focus on usability. We're going to focus on plugins. And we're going to focus on embracing the Web3 ecosystem, like we said. And yeah. And this is kind of like our vision. I don't know if you guys know WordPress, but the vision that we had since the beginning is to have StreamEase be WordPress. So something, so WordPress for video, right? So something that event organizers can clone and use quickly to stream their events. Hello. Hi, Paolo. Thank you for your talk. I am an event organizer. I have used several streaming providers. And I like Lightpeer, but one thing that worries me is how is the performance compared to other alternatives like Vimeo, YouTube, because this is decentralized. So this is kind of worry for events. Yes. So Lightpeer is pretty good. So I was a pretty early community member. And I've been using it in the early days. It had some issues. So since the beginning, I come from the web 2 world, like production world. And you always have failovers. And when I started using Lightpeer, I was like, hey, we need to build a failover here. So that's why we have built in a failover mechanism into all of our players, right? So on the one hand, Lightpeer got really good already. On the other hand, we have a failover mechanism that allows to basically set two Lightpeer channels for the same room. So you have double the reliability. So yeah. But what about the streaming related to attendees? Because you have attendees all around the world. And streaming providers have like a CDN content network. So how Lightpeer solves that? Yeah, Lightpeer, there's a bit of a more complex question, because you have the Lightpeer protocol, and then you have Lightpeer Studio. But basically, Lightpeer Studio, and that's what we are using, has its own CDN. And latency is pretty good. So you shouldn't have an issue if you have people from around the world trying to watch your stream. Like I said, performance is really good. Etherlin, we had a bunch of people watching. DevCon, a bunch of people watching here is DevCon. Yesterday, we had 3K views on Lightpeer alone, and almost no downtime. So yeah. If you want, we can speak later, and I can explain a bit more. Yeah. Thank you.