Building In Public Season 2 — Working Beta(Launch Soon) 📱

uh maybe uh vibe code an intro video through replit would be kind of cool to do like an intro video yeah yeah yeah i need to test that out yeah have you used it yet or not i haven't used replit um with the animation videos but i use like vibe code app to vibe code like uh an application and then i ran out of tokens on the free version so i said i don't want to uh buy it but i've been using claude and clad is blowing me away so um i used it like six months ago for a year and like now i'm using it again and it's way better than chat gpt yeah so um yeah yeah i didn't expect that i didn't expect that so definitely want to do more repli but we're we are live guys how's it going everyone yeah good good good to be back on our fortnightly bit cool hello everyone um hi indeed hi petri hey guys hey um yeah we're gonna get some nice violin is it a violin petri your daughter's practicing or is it cello it's the cello one actually it's my son this time oh it's your son they both play amazing okay so we're gonna get a bit of background noise but that's fine um all good and yeah what are we what are we going to talk about today um we got a big agenda i think today no yeah there are a couple things we wanted to talk about just to reflect some conversations that petri and i were having earlier in the week um And yeah, I think, you know, central to what we're doing with stream of video app is using decentralized technologies in order to build a better video experience. So we were talking about the importance of unstoppable communications and the importance of open source. So just to, and then there were a couple of other things we were talking about as well in terms of how our technology is more private than, say, StreamYard and Restream and these sort of platforms. So, yeah, just to kick the conversation off, Petra has actually shared an article with me, which is almost a year old now, this incident, but Trump basically, the judges from the International Criminal Court based in Hague, he's put them on the sort of terrorist ban list, which means that they can't get access to certain payment rails, whether they be fiat. crypto but also communications platforms like uh zoom and google or the us-based ones and we were talking about it because it's another example of how uh you know reliance on us tech is a problem for uh certain european agencies uh we also talked about this call a couple of weeks ago but france announced that all government agencies are going to be banned from using Meet and Zoom and Teams going forwards for privacy and security reasons. And we also said in this call, it's quite a sad time, really, because it feels like the European states are kind of dividing on a geopolitical level anyway. I don't think that's necessarily the case at a sort of human individual level. We're still friends, Steve. It's okay. Europeans and Americans work together all day, every day. um it's a bit of a strange dynamic but certainly that's happening at the sort of geopolitical level so yeah um petri and i are talking about you know how do we truly make streamer video unstoppable and by that we mean because it's built on decentralized technology making it very very difficult for or impossible for third parties to to take the service down and um i think and i think a lot of people don't really understand it because there's not many applications that are like doing doing this still that aren't built on decentralized like info and um it's exciting because we will like be able to showcase that and i think like we would have to have we have to have like test you know like people testing it to showcase that it's it's possible where i mean it there is limits of what we want to test right what what can be taken down and what won't be taken down or not nothing really at all but just the idea of um overload of of um you know computer processing and if any cloud flare were to happen where it went down we we would be fully operating like i think rumble showed a good rumble showed that um showcased that pretty well because they do have a lot of distribution within their their cloud um resources and they don't fully rely on like an aws or you know google google cloud but um something like that were to go down and we're fully operating fully functioning uh have a little very low latency and everything is working well and any other you know mayhem that's going on in the world that's those are really good use cases and and shows the beauty behind what we what we have yeah and i think we're trying i think we're trying to work through like how do we structure ourselves so that we can offer that kind of as a benefit you know leveraging the technology because it is unstoppable by nature um but you know how do we how do we do that from a sort of company perspective as well and i think the other thing that's trending at the moment that we're seeing blow up across social media is uh id verification for under 16s for certain social platforms so discord and reddit have come under fire in recent weeks and you know they're sort of those on the sort of this end of the spectrum are saying look this is just a guise for more government surveillance, more government control. It basically means that if you want to use these massive social media platforms, then you have to upload your ID now. So that is another huge infringement on the world of privacy. And this is a slippery slope, as we've talked about before. You know, we can't allow this slippery slope to happen because over the longer term, this does materially result in reduced freedom for individuals. and that's really really important because we live our lives on the internet nowadays and when privacy is compromised then you know bad things can happen and do happen so um so yeah it's uh you know there's a lot going on at the moment in this in this kind of space so yeah um lots there and i think part of this is you know as we as we bring stream of video to market you know how much we how much are we leveraging sort of decentralized technology um to solve those problems and the other thing is open source is really really important so streamer network the underlying infrastructure behind streamer video uh is open source already and that's a great thing um and so in all likelihood we'll be making the streamer video code based open source as well in due course which is working out you know how to do that how best to do that um actually you know a lot of the code is kind of front end anyway and if anyone knows what they're doing they can they can have a good snoop around already but formally we'll open source the code almost certainly we're just working working through that discussion and trying to work out you know how to go about doing that and what the license looks like etc so streamer network there is a general level license it's like a copy left type license gnu and so Yeah, we'll probably follow something similar to that. But, you know, it's important that we, you know, we operate in as transparent manner as possible as we bring this new standard for video broadcasting to market and video conferencing. And that's like, is that the main idea behind why we're open sourcing streamer app? Well, I think a central tenant of what we're doing is about security and to a certain degree privacy as well. Now, our bullseye users are gonna be security and privacy conscious. We can't solve all of the problems around security and privacy, but we solve a bunch of them, especially when it comes to secure video communications. And I think it's important for anyone in the security and privacy space to be very open about what it is they're doing and how they're doing it. It's almost a hygiene factor in this space. If you're not open source, then you become a trusted partner. And of course, we're all about being trustless. And part of being trustless is decentralization and part of it is about open source. And so, yeah, these are all the things that we need to do in order to be credible, essentially. Yeah, that makes sense. Yeah. Petri, do you want to talk a little bit about what we were discussing earlier in the week in terms of... how StreamYard, Restream, these types of platforms ask you to connect to your YouTube account, your Google account, get full permissions and so therefore there's a privacy infringement there and how our system does it differently and does it more in a more private manner because we're not asking for full permissions? Yes, so our... our approach to to this this one will be that we we shall be running a very simple server component that is basically only a web socket to tcp proxy all these platforms well what they have in common is this rtmps ingest protocol i mean the protocol with which you can feed your live video to them and they common denominator there is this RTMPS protocol. Some providers, they support some other protocols as well, but the easiest way to get connected to all is to support RTMPS. And RTMPS, because it has this S in the end, it implies that it's this TLS encrypted protocol, so it's end-to-end encrypted. the same way as https is and it has exactly the same security implications as as with https so it is safe to use a simple proxy like it is in the case of https when this connection is end-to-end encrypted between the client and the server it doesn't matter if if there is a proxy in in between the connection is still secure but the problem arises if if you have a if this secure connection is terminated at the server for for whatever reason and when it comes to video the reason usually is something like transcoding the video into different formats or it's about sending the video only once to the server to save bandwidth from which it will be transmitted to the targets. So our approach here is that we will go follow this proxy route where all the connections are end-to-end encrypted. between the client which in this case is your browser and the streaming service which is like youtube or twitch or x or what whatsoever so so this is this is how we are we will be safer than the others so so there's not going to be any server-side processing happening there's no need for us to terminate the connection at the server so the server doesn't doesn't need to be able to see the video or edit it in any way it will go encrypted through the proxy directly to the streaming service so this this enables us to use untrusted proxies so so the end user i mean this this guy who is broadcasting their live show to youtube doesn't need to trust the server component which is running this proxy at all because whatever goes through that to youtube for instance is end-to-end encrypted and it's just as safe as using https proxies so if we look at the competitors this is often not the case for instance if you try stream yard and try connecting your try adding this youtube destination there you shall quickly see a prompt that stream yard wants to have certain rights to your youtube account and the rights basically give StreamYard unlimited access to your YouTube account to do whatever they please with your YouTube account and in our case we are not going to do anything of the sort and this is a very important thing especially for corporate users or those like large-scale let's say YouTubers who have something to lose they they have like been doing the streaming for for several years and now if you are to give access to some unknown server to all of your youtube account and the server can do whatever they wish to your youtube account i mean that that sounds rather rather scary but but in our solution you you don't need to give any rights whatsoever. All that you need to give us is this stream key. And that key basically only gives the right to send video to that particular stream that you have created in the YouTube user interface yourself. Yeah, I love that. Awesome. Thanks, Petri. So, yeah, we're going to be bringing this restream re-streaming feature with the beta launch. And for the reasons Petra was just explaining, not only is it more private, because we're not asking you to connect all of your and hand over all of your YouTube or X data in your account. But we're going to have all of the features of re-stream, StreamYard, but a fraction of the cost as well. So yeah. When it comes to the cost, so this solution is part of the reason why we can be cost effective as well because we don't run any complex server-side, we don't do any server-side video processing and if you have ever tried doing any video processing in the cloud you will soon know this. that you will need the high-end virtual machines in the cloud in order to do video processing and if we were doing that our costs would be much much higher than this cost that comes from running this simple web socket TCP proxies those can be run on the I mean the lowest end of virtual machines And in the future we foresee that we can also start using the operator nodes for running these WebSocket TCP proxies as well. Awesome. Just explain what operator nodes are for those that are in the audience that are not that close to the streamer project, so the underlying infrastructure network and protocol streamer network. is powered by a backbone of decentralized nodes, which support peer-to-peer connectivity. So we employ those as we video stream via streamer video and streamer app to do a number of things. So yeah, just explain what streamer operator nodes are. So with this, since it's more cost-effective, Petri, most people think oh cheaper means lower quality why is that not true in this case that is not true because i mean basically you are sending the the video stream directly to the target through this web socket tcp proxy so it means that the latency will be as low as it can be because there is no server-side processing happening there. And often when doing this server-side processing of videos using tools like FF Impact or GStreamer, so the quality of the video itself often also goes down if you try to keep the latency low. But we are basically sending the original video as it is from the browser. directly to the to the streaming service without server-side processing of course here here is the kind of the trade-off that comes with this end-to-end encrypted connections to the streaming services is that this video needs to be sent individually to each of these streaming services So it will consume more bandwidth from the client who is streaming. From the actual source. So if they have low bandwidth... But this is actually not such a big problem nowadays considering what kind of network connectivity people usually have. So this kind of full HD stream basically is... around six megabits per second. So you can calculate from there how many megabits of bandwidth it will require to stream out to, let's say, three services. It means 18. It's not much. Most people have at least 100 megabits of upload bandwidth nowadays. Yeah, that's basically the minimum for most people, Madrid. okay that that makes sense that's what i was going to ask you like what's the like what what's the limit or the threshold of bandwidth per per like individual that's the streaming sounds like probably around the depending on the how many channels they're streaming to um but it sounds like around that 10 that like 12 to like 36 range megabits almost if you're streaming to six platforms or streaming to two around that yeah yeah it depends on It depends directly on the number of targets. And in the beta version for the restreaming aspect, which is going to be very similar to the platform like StreamYard, how many platforms will we have that we will be able to restream from? Like how many channels will be open? Well, at least we are targeting to implement YouTube and Twitch. So we are currently... looking at those hopefully we can also do more but let's let's see there's also there are also some security security constraints here so if if we were to open this our web socket to to tcp proxy to to connect to to arbitrary addresses so so this would open a door for some some attackers to attack some arbitrary addresses from from web socket using our proxy so so that's not desirable so we we we would rather like to keep those target addresses i mean the set of target addresses strictly defined by us so then you cannot do any ddos attacks too to your government if that's what you are what you are after so so there's of course we are also considering this this opportunity not opportunity but this option that you could actually run this kind of proxy yourself in that case there would be no such limitation because you would be responsible for the actions of the proxy and not us so in that case we could open up this to like sending the arbitrary targets as well but let's see it's not coming in beta yet or if we look at our competitors so for example in StreamYard these arbitrary targets arbitrary destinations are a premium feature only available in the most expensive packages so so we we might do something like that as well but um let's let's see let's start let's start easy with with a couple of targets and and add more as we go makes sense yeah i was even going to ask like we have a so we have so many different options or i guess like maybe features you can call it inside streamer app so we have the restreaming we have the streamer tv we have the video video business conferencing um side um we have you know a lot of sides to what streamer app offers will there be like one price that includes all i know we have some talked about um different tiers and all that maybe we can dive more into that just to clear things up maybe there is a side where you get everything included based on like an enterprise uh tier so there may be more clarity around there yeah so um yeah just to recap we're bringing a freemium model so we want everyone to be able to use the core product with unlimited um meeting lengths unlimited audience sizes for broadcasting, and access to serverless secure video conferencing and broadcasting, and serverless chat as well, which is built into the product, obviously. We want everyone to be able to access that in a permissionless manner and for free. So that's kind of the free tier. And then there's a pro tier as well, which we think is going to be about $9.99 a month. And with that, you get all of the added benefits that Petri's just been talking about. So re-streaming, self-recording videos for distribution for business development and async of team comms. So kind of the Loom use case. There's a metadata detection feature that we're bringing in. And for that, what we do is we leverage the operator node base of streamer network. Petri can talk. bit more about that at the moment in terms of how it works but the the one-liner on how that works is is we the operator node essentially holds the the metadata for the broadcaster and for the subscribers and we randomize which operates nodes we're using for every different call and so therefore there's no one pointless source of truth for the metadata and so obfuscating it This is a key feature for us, actually, because in peer-to-peer networks using WebRTC, which we do, typically metadata is exposed for all to see. So it's important that we close the gap on that as much as we can. So that's in the kind of pro tier. There's a few other features as well. One's called Broadcast Booster. And so it's for those that are broadcasting in challenging network conditions or internationally around the world. And the other feature is called Bandwidth Saver. As the name suggests, it helps optimize your bandwidth at any point in time. Both of those last two features, we also used the operator node-based streamer network. So yeah, there's a whole bunch of features coming through the launch of the beta. And we're close now. So we had said originally March the 1st. I think we're going to slip on that slightly, but only very slightly. And the core product is working, which is good. At the moment, it's kind of limited to Chrome browser because there's a limit to how much the guys can do ahead of launch. But we'll, you know, fast follow-on, we'll have it tested and optimized for other browsers as well, including Firefox and Brave. And then there's going to be some other features that will be fast follow-ons as well. So, you know, we've talked about our referral marketing system called Meet to Earn. And so that will come again as a pro. pro tier for pro tier users um so as they bring people in they stand to earn some monetary rewards built in for a marketing system essentially um so yeah there's this free tier there's the pro tier there's also going to be an enterprise tier as well and enterprise um is going to come later in the year but we want to start those conversations now in fact we've started one or two of those conversations early stage on those the enterprise takes it to a whole other level. So with that, what you can expect is potentially private networks using the stream of technology, SLAs, which are key for enterprises to use products such as ours. And then we'll be introducing certain regulatory standards as well, like HIPPA for health insurance companies in the US and SOP2. So yeah, lots to be done on the enterprise side of things, but that will come. I mean, we know that naturally over time, we're going to monetize this business more with enterprise versus retail. That's what we've seen with every other similar type product. But it's a journey. It takes time to get to that. Oh, there's one other key feature, which I forgot to mention, which is self-hosting. So we think we're going to introduce self-hosting capabilities to the pro level tier. That's not going to come with the beta launch. um in a few weeks time we're gonna have to wait till later in the year for that but certainly it's possible and certainly we'll bring it at some point as quickly as we can nice yes if you want to check out the latest go to streamer.com um actually we've got a re-release of the site or an upgrade of the site coming end of the week hopefully um but yeah if you want to check out what's coming in terms of features and how they're going to work then yeah check out our website it's all there awesome yeah that's that's deep yeah a lot of stuff coming i'm just gonna ask petri when um can we talk a little bit about timings um like what's realistic now uh because obviously our first users are kind of excited to start using the product um yeah it's always very difficult to to tell the future i think it's easier to tell that what we are currently working on what we have done because it's always unpredictable what will come next. So what we are currently working on is implementing this scene setup. So like in StreamYard, there are these different scenes that you can set up in Streamer. So that's what we are currently working on we have um we have already this permission system ready where you can request to speak so and and we have the viewer mode so so so so uh yeah so so there's a quite a lot of fine-tuning and and implementation to be done uh today today actually I made the first implementation of this streaming from the browser through a web socket to the ECB proxy to a RTMPS server. I'm going to start testing that. But as I said, it's very difficult to tell when these things will be completely ready. full picture here is that okay most let's say that nine ninety percent of the features have been like started we we have some kind of implementation i mean it's not it's not ready yet but we we have started so one thing another thing that has been started and actually user our web3 expert has been working on this week is the authentication and he he's got to get that ready by the end of the week and this authentication will will happen using openfort smart wallet provider that's that's that is a cool cool thing that we we get that one implemented in parallel now with this video video side yeah this is super cool because as you as you come in and create an account on stream video We're not going to ask for your email address. We're going to ask you to create a Web3 wallet, write down a seed phrase. So you can either create a new Web3 wallet from scratch, or you'll be able to import your existing Web3 wallet, which means that you could use an ENS name, for example, if you have an ENS name, or you could even use your ledger device in theory. So, yeah. You could also open for this wallet infrastructure that... that allows you to authenticate using using biometrics or even google and other authentication providers so you create the wallet and then you choose the method that you want to log in with to using the wallet and your biometrics stay on device right yes that's built in into the operating systems, actually. Yeah, if you are using your biometrics, make sure they stay on your device and don't go into the cloud, because also in the cloud, there's no going back, because you can't change your fingerprint. Yeah, okay, awesome, very exciting. Yeah, what else, what else? Yeah, so we already have Stripe payment mail built into the product, like that's in MVP2, a stream of TV, so that's ready to go. as you subscribe to protea uh you'll do so via stripe account with fiat um do we think that's the optimal long-term solution no it's just the easiest starting point you know we're building lean at some point we'll introduce crypto payments as well using the data token or staple coins um but that's going to come later in the year it'll probably be like a discount you get for using data token versus a stable coin yeah yeah um I had a question on creating an account. How would that process, how does that flow go for a new user when they're creating a streamer app account? Maybe I just, so I can paint a picture so I can see it a little bit more clear. Actually, do you want to answer that or you're close to it? I mean, I can if you want me to. Yes, yes, sure. So basically, we are using the OpenFort. account creation. Is it possible to run it through? Can we showcase that right now on Figma or no? Let's see. Actually, we could have a look at the OpenFort demos for this. Let me find those. It takes a little time before I find those, so maybe you can. No worries. Yeah, no, I put you on the spot here, so no problem. Okay, here it is. I don't know if the screen sharing, how does it work? Press present. Present, yeah, and then just share the screen. Share screen. I'm assuming we'll have a similar feature with the restream feature. Allow, yes. Now let's see. So can you now see my screen? Yes, we can. Okay, so this is how you sign in to OpenFort and also to our solution. So you just press register. So it asks to give you a biometrics. Okay, my biometrics. Okay, now my biometrics failed because my fingerprint... that's apparently changed with the winter because now so they dried off your fingerprint they have dried off but now you can see the fallback so remember apaches in finland and it is seriously cold actually what's the temperature outside uh well currently it's only minus two but it was like only minus two yeah it was minus guys can you can you see now this what is happening as fallback okay the biometric failed so this is just enter your password yes this is the master password of of this mac all of this comes from the operating system itself so now i press unlock and now it's registering so now it's creating the wallets okay and here here here i already have a crypto wallet with a known address so People can actually send crypto to this wallet. This is a real crypto wallet. And you saw how easy it is to create. So then I can go on to execute the transaction on chain. Does this happen on Polygon? Yes, this is actually on Polygon. So let's see. Does the touch work now? No, no, no, no. So probably this will... Fail again, I need to sign in with password again Okay, now it's minting the tokens and in the stripe integration With this is it happening through this? Do this was it called open fort is it happening to open for the stripe integration? In the sense that you when buying a license on on stripe We will pass this wallet address as metadata of that Stripe transaction. So then we know exactly that which user has bought the license. Gotcha. So that is the way this is integrated to this fiat payments at the moment. So now this transaction on chain, it went through. I can press view, and here it's in the transaction scan. So we can see that it actually happened on chain. So it is very, very easy nowadays to onboard people to become Web3 users. We're going to leverage this now. It was a totally different story way back when you needed to ask people to... install a browser extension and then give some passphrases whatsoever. But this is how it goes nowadays. So now what happens from here? Basically the account is made and the person is technically, their ID of who they are is technically the string of this Ethereum public address key? Yes, yes. So now Now, this wallet, I mean, the secret key has been securely stored by this browser slash operating system. And well, technically, it's more complicated than that. This is actually an on-chain wallet created by OpenFort. And this private key that was created by the operator. and stored by the operating system that is that has been granted right to act as a signer for that on-chain wallet so so this kind of works the same way as this multi-sig wallets that you have maybe heard of in the crypto world so so you have this multi-sig wallets where Where you can configure that. Okay, these secret keys need to sign the transaction in order it to happen So it's the same here This works the same way. So so this this private key that is generated and stored by the operating system that is configured as a signer To this actual wallet that exists on chain Super secure really secure. Yes, it is So now, okay, you have this wallet, and now you are ready to operate. You can, for example, buy a license from us, and this Ethereum address will be passed in the metadata to Stripe, and we will have a Stripe hook, I mean server-side hook. that gets launched when the payment has been made and this hook will write to to on-chain smart contract that okay the user with this ethereum address has a license to to pro level in streamer for for one month and that will read there in the smart contract and then everybody everybody will be able to check that including our operator nodes they can check that okay is this a licensed user or not nice nice really cool stuff so essentially like once you do the subscription through your account how would i this is the base this is a sign-in process of stream wrap so i'm on stream wrap i want to start going live as a user or as like a business for like my business meeting I go through this process for OpenFort, and then once I have this all made, every time I log into StreamRapView, the browser, I'm always logged in. Or do I need to do a browser wallet login? No, you do the login the same way as you did the registration. So whether you use the biometric or whether you use the master password of your computer, it's exactly the same. Same way, but you are known by this Ethereum address and then you can sign things using this Ethereum identity. You can say that, okay, hey, by the way, I'm Petri. You sign this with your private key. Yeah, I'm trying to... And then everybody knows that, okay, this Ethereum address claims to be Petri. So if you want to log in from product, click log in, fingerprint on your biometric, app opens, one click to live stream. Wow. Yeah, because I'm trying to see it from a user's perspective that's never used any Web3 app before, never connected a wallet before. This seems really simple, like super simple to use. I can give this to anyone and they would just do register your wallet, boom, sign in, and then that's it. it's really register wallet and then you then after you register your wallet you sign in and then i'm assuming it directs you straight to the stream wrap page after that right yeah once you sign in wow yeah super simple yeah that's like we've talked a lot and thought a lot about you know how do we strip out well how do we make the ux as effective as possible and as easy so that everybody can enjoy this sort of secure private product um like a lot of security and privacy based products are quite technically difficult to use and set up We're trying to solve that problem here. So we all know decentralized Web3 technologies bring a ton of advantages, features that we can build, but historically Web3 apps have always been tricky to use. So yeah, we're solving that problem. It's really cool. It's good to see too, to get the visual of it, because before I was confused on how exactly we were doing it, but now it makes a lot more sense. So what I did here is I logged out, and now I try to log in. How did you log out? You just exited? I just pressed the log out button there. Oh, there's a log out button. Gotcha. So I press sign in. So now, because I have been testing this out, so I have several of these accounts saved on this device, but I can choose one from there. and then give my biometrics again, which seems to, there I am. And then now you're logging in, and then you can log out and log into any, maybe you can make a couple more outlets if you wanted to, it seems like. So that's kind of cool. Nice. And why would people want to emit 10 tokens? Is this going to be part of it too? No, this is just their demo. You can do a crypto transaction. So on the streamer app, it's going to be more built around the streamer app. It's going to be curated to a streamer app, this page. Yeah, yes, yes. So you can do different kinds of transactions in the streamer app. Cool. no really cool i i'm actually really uh this is it makes it it makes it now it's so so much more clear on the aspect of identity like not not giving your identity anyone can participate if you're 10 years old if you're 80 years old and no one's going to know who you are and this is actually the beauty behind these type of rails where like no i it's weird to see this because typically me being a web3 user since you know eight nine years all i did was use my metamask connect which that's cool too but this is so much more simpler and it feels a lot more safe where i especially because you said it's multi-sig as well so like you can't really like mess up here and you can't have a lot of um you know vulnerabilities or hacks that happen because it's not i don't know how the multi-sig happened but it just you said there's multi-six i'm assuming you know that's the safe yeah so that's in in open fort that is used for like account recovery so so you can you can set you can actually set up multiple signers for the same wallet so so let's see let's say that okay this this is your primary computer and you do this process here, but there is a way of adding additional allowed signers to the same wallet. So that's how you stay safe. You can add another one on your mobile phone and so on. Yeah, most people have multiple Web3 wallets, right? So you can create a backup with your other Web3 wallets. but you know worst case scenario if someone can't get in then they just set up a new account um and repeat the process what i'm what i'm thinking about is more like if they end up having tokens on this wall right right like let's say they're getting tip tokens via other people from this um from streamer app yeah yeah obviously we're not quite on we're tipping more for the stripe account right now but eventually we'll probably get to the point where we're tipping the actual eth wallet And I'm assuming people will actually add that ETH wallet on the bottom of their stream, but you can also tip me in crypto for the time being, and the people that are in the crypto world will understand how that works. There might be more friction there, but eventually we'll be able to probably just tip them straight from the app itself. Yeah, yeah, yeah. Actually, one of the good features of this OpenForge system is this that you can see on the center of the screen. screen that executes sponsored transactions so in this demo there is a paymaster set up just for this demo for paying the gas fees so there there is no more playing around with having having certain tokens in your wallet for paying for the gas nice so basically because the author of this demo is now paying for doing these transactions so it's free for the users and we are planning to do the same if and when we are doing some real on-chain transactions in the streamer app so we're gonna do the same we're gonna set up a paymaster to pay for the transaction fees none of this that's the worst feeling to pay for the gas yeah i know that feeling i think there's a cool world where we can maybe even have like open fort like talk with them because this is um maybe talk with them get them on a building public call and showcase this with them and or do some type of integrate partnership with them um or announced because this is we have a great use case of of how i think more people should utilize this tech is there it's pretty cool pretty cool stuff yes yes yeah this the these technologies they have emerged during the last 12 months or so and it's it's rather it's kind of sad that this happens so late this this should have happened like five years ago and everybody would be using web3 The obstacle of adopting it was so high, but now it's gone. This is easier than setting up an account in a Web2 environment where you need to play around with emails and such. I think it's easier now when they allow you to connect with one of your Gmail accounts or your Microsoft account, but you have so much data at risk and so many things at risk when you do that. that is kind of scary yeah it's scary so it's like it's easy but you're still putting so many things at risk when you integrate your email accounts and stuff so it helps on a lot of fronts right because you can connect when you have one thing i connected to the email account then so many other things can integrate when you have like your email account connected but you put yourself at a huge risk when it comes to if your email gets compromised or other things get compromised so um yeah it's interesting it's an interesting fork in the road of what people want easy act like easier sign-ins that don't allow for integrations onto other apps maybe eventually there is a point where you can have integrations onto other apps from your eth wallet or an eth address right where this eth address is connected to this app so then if you connect this eth address to this app it automatically sees it and there's like an integration right like a notion connection happens via this open fort connection or this like streamer app connection and then like all the transcriptions that happen on stream wrap would go automatically onto like notion right because this the eth address was integrated onto both apps like right now you can do that with gmail with certain things right but it's there's probably some future with that too yes there's a lot of things things that this enables and i think one of the important things is that you are in control of what you share what kind of information of yourself you share i mean when when using ethereum addresses and private keys you you can sign whatever info you want you you you can for example if if you want you you can sign your passport photo and distribute that one but okay This is my Ethereum address, and by the way, here's my picture. You can do that if you want, but nobody's forcing you to do that. Good point. Yeah, it can be extracted from the actual sign-in process or from the credentials. Cool, yeah. Awesome. Should we jump into questions? Yeah, looks like we got one. How do you stake the token? Toppad hamster. yeah good question so for those new to sort of stream a project then as i was explaining the beginning of the call this is stream of video application layer and then we've got the network and protocol and the native token is called data and to stake it what you want to do is set up and run an operator node um which is a little bit technical um i don't think you have to be at petri's level but you need some technical expertise and with the help of claude or chat gvt pretty much anyone can do it um but it does take a bit of time But to get started with that, go to the website, streamer.network, and then go to probably open the hub, which is an application on that website. And on the hub, you will see a button, set up operator node, or you can go to the documentation as well, and there's instructions in there as well. And what you're doing when you set up an operator node is you are supplying your latent bandwidth um to the network and you are going to run your operator nodes against what's called sponsorship contracts and as you do that you stake your data token and you'll get data tokens back in terms of apy from the sponsorship contract it's a little bit complicated at first but uh yeah i mean ask chat tpt or or claude how it works if you want any clarity on that if you're not technical and you don't want to set up an operator node the easiest way to to stake your token is to delegate. So we use the language delegate, and that is for non-operator nodes that are data token holders, and they can go to any operator node on the hub, and they can delegate their tokens to those operator nodes, and they get a cut of the APY back. That's the easiest way to do it. So yeah, go onto the hub, and you can take your pick of operator nodes, think of them as pools, and delegate your data tokens there. Super easy to do. right apy on on delegation or yeah it's probably north what is it north of 25 30 percent it says 65 right now yeah yeah a while actually yeah wow okay cool pretty high yeah there's opportunity there yeah okay um any other questions before we wrap up no not three questions this week okay yeah all right cool good session guys yeah um we're close we're close to launching streamer beta exciting um yeah and i can't wait for the day when we can host this call on on streamer which will be soon as well that's gonna be fun because then we'll be able to stream it via um we'll basically be able to do everything we're doing on here but on streamer app so yeah yeah 100 cool that'd be great all right thanks petri thanks steve um yeah enjoy the rest of your day yeah okay

On today’s Build in Public:

- Why being “unstoppable” matters
- Open-source direction(It’s the only way)
- Recap of FREE / PRO / ENTERPRISE tiers
- Product updates + Beta timing 
- Working Beta launch details
- What’s shipping now vs what’s fast-follow (Meet2Earn 👀)