02 - Swarm One: Bee Client & Testnet Airdrop by Eknir

so let's get started with this information packed event and i would love to go to our first speaker um please if you are here show your face and talk to us hi hey there you are my friend how are you doing well it's been like very very last day and i'm very excited about everything but i'm doing well yeah how much sleep did you get like the last couple of nights uh the last night i went to bed at the decent time but before that it was like yeah it's good awesome so uh if i'm correct you have prepared a presentation for us yeah i think so okay let's dive into that right now you're supposed to see my screen right exactly we see your screen now it's in full screen mode and now you don't have any black bars correct all right so let's start with my presentation um hello world b and i'm going to explain what is different today from tomorrow but i mean yesterday so what is different today from yesterday well first of all b made it you know like we have the first stable version version 1.0 i think the developer team right now is like doing really the last things but in the upcoming i would say half an hour hour the first stable version v 1.0 will be released on github and then rolled out later today so we made it to the base camp and we have time right now to kind of consolidate and see where we are sending and enjoy the view so um i'm really happy personally about this i'm really happy to be part of the swarm team and to like experience this moment with everybody so yes and um yeah so about b right so if you go to our github you see this so for those who have been i don't know living under a stone or like maybe tuning into this form for the first time so b is a swarm client implemented in golang it is the basic building block for the swarm network which is a private decentralized and self-sustaining network for the permissionless publishing and access of your application data so b was the very was the third iteration actually of this whole swarm project b consists of more than 100 000 lines of codes created by 1 000 201 commits and the b project itself started a little bit more than a year ago but again the b was already the third iteration and b received contributions from 36 contributors so this is much bigger than our team so we also have open source contributors and b of course is not the only repository that we have we have in total as a swarm we have 121 repositories that all work together into creating this this form network but b definitely is is a very important one because it contains the client codes that's right now people all around the world can run and are running already b is there for node operators to join the swarm network and put their storage to to use for the swarm network b is there for that developers to make decentralized applications and above all i would say b is there for anybody who wants back the digital freedom so hello worlds b and what is difference today from yesterday well the stable release and then what does this really mean right the stable release um well for those who have been working with us for the last half a year and bearing with us and trying to keep up the dates you probably know that that b so far has been anything but stable i mean we have been rolling out the code so fast we had to break our testing network a couple of times right but that's why your testing network is there is to test and to be broken but with the onenote serial release we are releasing a domain net and the mainnet will be stable but the main ads also will have the real utility token pcc so we're going to see the incentives playing out for real b contains all the essential features for this form to work and we provide more stability for developers and node operators and i go into each of these points so the b nodes work with bcc which keeps node operators honest and ensure collaboration we have kind of two subsystems inside b that are working so we have to swarm accounting protocol which allows node operators to earn money by providing the bandwidth services and basically it helps everybody to collaborate with each other to route all the requests in the network and then we have the postage stamps and this very shortly ensures optimal storage allocation over this big shared network all around the world then i think it's important that the node operators earn bcz because they are providing their service and the end users pay the bcc because they're using the service for the network and it's powered by the xdi side chain all right so b also contains all the essential features for swarm to work and what does it mean so the essential characteristics plus form are well of course it's a decentralized storage and communication service but it has privacy preserving and permissionless uploading downloads robust defenses against blocking or changing access to content once it is published auto scaling with increased demands interactively protected content and eventually for getting content that is no longer relevant to preserve so for those people you know like the numbering is a bit weird but yeah i was what i said we've been working very hard but i think you get it and yeah so these are the points i don't have time to go into each of those but if you are triggered by this and you're very curious to hear like how nerves this form and this form network can can realize all these these points i invite all of you to read the swarm white paper which is the 13 pages i think it's very accessible for people to read and then if you're really interested and you want to dive even more further and learn more about the vision and the background you can read the books form so both of these papers are recommended to read if you want to know how swarm has these characteristics how it works then the last part i already mentioned it more stability for developers and node operators so shortly from this point onwards we care about your data and we care about not breaking your application and in practical this means that um yeah whenever the swarm network receives protocol updates if needed and possible we are going to provide the migration pulse to migrate your data if you are using or consuming the apis or you're consuming data in the network it's good to know that all the apis are versions so i advise you to directly reference one of those fixed version apis and all the api's endpoints and data structures are supported for at least three months so that will give you ample time to update your application but of course swarm is also a network and uh it's a rather complex piece of software that's going to be run all around the world so we need to also have this um possibility uh to do an emergency response and an emergency response kind of like yeah then we cannot adhere of course to the three months um backwards competitive compatibility but these are only for very critical bugs that would severely impact the retrievability or upload possibility of content in a network or for those kind of bugs that may cause the loss of bcc for for node operators so these are rather critical of course and whenever there is such an emergency very emerging bug you can be assured that we will update you as soon as possible yeah and then the last point um i want to mention it as well always keep a backup of your data especially in the beginning and what does it mean so we want to have it there for you to be able to repair your data in the network and also to facilitate migration if this is needed it's very easy you should always upload your content with the swarm pin header to true and you also keep a local backup of all your data on your own file system yeah well let's start b there we go thank you amazing uh acne uh i can imagine you feel very excited right now about all this um you know the only thing that that i really really really want to ask you is what about the airdrop because in this course you know there was such a number of questions about the airdrop so can you shed some light on that yeah i can i can even shed a slide on it oh yeah here you are so i didn't put in too much effort for this slide because i think the communications thing was one already did an amazing job so anyways i would like to reference everybody to our post on medium the swarm airdrop is finishing june 21st that's the date so you can all find it with that um but there's going to be like a couple of phases i think it's important that you know it's referenced in this blog post but i just repeat it right now so june 21st this evening the trusted node stopped operating so these are the nodes we've been running on the girly node and who are kind of gathering uh who is uh getting like checks right um we're also going to reset our network so there will be this network from tomorrow onwards for the test network will have a different set of boot nodes and if you still want to run the testnet mode which i highly advise please don't try to migrate your own old node just start a node and you right um june 12th is the last moment to cash out your checks uh in june 15 you can see your gurley abcz balance on airdrop.ethan.org july 22 a pcc freeze and august the second bcc airdrop on extra awesome i think it might be interesting to just explain a little bit more like so we're dropping the bcc on xdi right not on ethereum mainnet yeah can you can you maybe explain why we are doing that yeah sure i mean um the whole reason of this error right is to incentivize um to ensure that the tokens are there around in the network and the tokens in the end are there to be used right and um swarm what i already said we are working with the xdi side chain is operating the swarm network so of course we could send this like die on the main net right but then people need to convert it to the to the side chain so just by dropping it on the side chain people have it immediately at the place and they can start using it i'll definitely be doing that in the coming weeks so uh acne thank you so much for your presentation and for being here and especially for the amazing job you did you know getting b ready for me at launch yeah has been right thanks so much