Race of Sloths - UA Rust Giveaway Announcement
Nothing is loaded from YouTube until you press play, and then without tracking cookies.
Transcript
4,094 wordsCaptions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.
- 0:09
helloo are we live that's something new for me to go live this way um I think you may be wondering where is Joe Joe is here around us and we have a special um case today to talk about the race of sloth and the rust conf uh and some some other topics that I'd like us to share with the audience uh during today short life special one uh and uh just FYI I guess uh let me uh share the uh some information why we are actually here if you missed the announcement somehow you couldn't
- 0:57
right uh just one sec I sharing the screen can you see it now yeah all right so Ros SLO it's a gamified open source contributions that are built uh as part of near system and uh today we have the this uh very special day to have a giveaway for tickets to the r conference um the UI rust that is happening um this weekend and uh I think it was a fun exercise for all of us given that RAC of SLS just started
- 1:50
um a couple weeks ago and we already have a bunch of people contributing through it and uh the um um the fun part that was announced just a few days ago was about the a new so-called Quest contest I don't know call it as you like but it's uh basically here the first race of slos contest and the rules were super simple the we wanted people to retweet and show the love to rust and
- 2:34
race of slw and Mir system and today we want to summarize what the outcomes and um what's happening there um we see that there was um quite a number of people who actually saw this announcement um and we will today try to find who will get the tickets if anyone at all and as we can see the rules were simple R this announcement and get this loss points so we see 16 potential retweet uh candidates and we see
- 3:22
over 27 over 30 people contributing to uh race of loss and uh gaining some points let's discover if we have a match here today or we will uh use some other way to uh distribute the tickets uh before we go there just a quick reminder the Ros CLA is a project that was started as part of near Dev Hub is our um community of communities uh in N system uh so I think it's important to say that um our
- 4:08
community is not only focused on Rust even though we love rust a lot and there are plenty of other contributions that you can um help with and uh yeah check out all the resources that we currently have uh on our channels uh of Hub to learn more about what's going on in near system and as you can see the latest edition of near Dev news was about rour loss as well all right and yeah and let's uh let's see wow we have pretty
- 4:49
strong competition here I to show the page it was super simple to get um definitely to take the lead more time uh but look it basically is fully uh on GitHub um the process is super simple and you just need to get um a couple of extra comments from contributor and the maintainer uh to get your scores and then you can participate in various quests and contests like this today that we're talking about the uh rust UA
- 5:40
tickets and uh speaking of rust UA uh let's see what's what's up there and it's a Ukraine Russ Community organizing the RAS conference second year um and uh the conference is held in in English and Ukrainian so some of the talks will be in English some others will be in Ukrainian but the the content is pretty uh I would say in depth of rest and uh various use cases and various uh um gotas that you can encounter working
- 6:28
with rust so we are are sponsoring this conference because we definitely uh like near has been built with r and basically I think uh there is a lot of attribution that we can say uh we owe to rust um in a sense that's why it's very important for us to keep contributing back to this community and ecosystem and race of loss is also built for this uh major purpose to give away back
- 7:01
to uh to the open source Community some fun and uh fairness and um gain more contributors to open source projects so please join races sloth and uh um and open source as well uh and then let's um what should we do next I think it's time to invite glb and uh um so I'm not alone here speaking um hey guys hey hey so I'd like you to help me here with the um with the giveaway and with the county
- 7:57
and getting the elgible um people who were interested in participating in this um contest and uh I've heard that we may have not have enough people but let's uh let's see let's get the numbers out let me stop sharing and uh um and uh yeah be one second so basically this contest uh went a bit messy for us uh as a first contest so we were like the the main requirement was to retweet our announcement uh from
- 8:51
the U Ras conference and many thanks to the conference organizers who retweeted uh us and uh spread uh the board uh the second requirement was to get some Source points uh in the in the race so we have two people so basically yesterday we've asked to let us know the GitHub profiles of the people who retweeted the original post uh which was the requirement we have uh two people
- 9:21
retweeted this uh and uh Unfortunately they uh to people who let us know their GitHub profiles Unfortunately they didn't get any SL points so the but the special things for people who who read our Twitter goes to I may misspell the GitHub nick names a bit but it's yanel s near and the the best Fara uh which I guess we some some of our audience knows what does that means uh we have uh GMO uh gajus uh the nickname on GitHub gajus
- 10:03
who retweeted and DMD us his um his GitHub nickname and uh let me show uh the screen probably yeah I mean definitely it it it is I want to remind you all it all started just two weeks ago and uh we also the the contest was uh a bit rushed because the conference has been already scheduled and we were trying to prepare all this fun in very short period of time uh and but still we wanted to give
- 10:43
away the tickets we wanted to engage with the community so we'll see maybe it will be a very easy uh contest and people will be jealous like you know uh Bitcoin pizza kind of opportunity that was missed here um yeah so you want to share something here yeah actually I want to share the original post where we ask people to share their GitHub profile so we can see the two people uh who Reed here and one people one person Giller Mo
- 11:18
has DMD us unfortunately I can't show you the DM uh but in any case uh there should be some level of trust for us here and uh I think one more person who we know like who is the user of Twitter is Arthur Kinski uh so basically I would say that we have only for the three tickets we only have two eligible people who uh did everything to get these tickets and uh we have basically one ticket left and uh let's think how what
- 11:55
would be the fair way to distribute it I think we can ask people to reach us out if you are on this list if you have at least scored at least one Sloss point maybe you don't have a Sloss Point yet because your P request has not been scored yet but if you are in this list with your GitHub account reach us out we have uh you have a lot of places to do it uh just post post a comment to this uh live stream and we will pick it up we we
- 12:28
see all the comments on Twitter um YouTube and twitch so we will be able to see those yeah we have a telegram group or you can send us in telegram group right now the the the point is let's do it right now we want to like the conference is happening uh this Saturday so we Cann really postpone this uh process any longer so I suggest indeed we uh we come up with some solution um right on the spot I think one of the um options I
- 13:08
have in mind we could go with uh using all the list of um of the race of loss leaderboard and um um and uh and maybe select like so well we we we do have two eligible people right already um you can say there was no competition for those and we reward those people already and then one ticket is left and then we can say we can select it we can select top 10 uh um randomly random contributors from the or maybe we like Shuffle the list of
- 14:05
contributors of race of sloth and then we'll try to reach out to all of them and whoever will be the first one um will get the ticket um yeah I'm I'm I'm trying to think of uh what would be the best approach here and the the most Fair one yeah I think uh what we've learned that not a lot of developers spend much time on X and uh in telegram so they put they push their PRS they code that's what we're all about here so ideally we
- 14:54
have a lot of ideas like we have a lot of ideas how to uh make these competitions better more structured more well organized in future and we will work on that we've already started working on that to be honest uh but now yeah I think whoever reaches us first whatever Chanel that's a good point uh what we discovered when we started to share our the the contest rules with the audience that uh
- 15:26
um probably like half of the contributors that we know said that they at least do not have the Twitter account or they were like okay my Twitter account is empty or something and it's just pointless for them to uh retweet in in in in a way so we will definitely need to come up with a better approach here um and I wonder if that is that is fair to even include then the those who are elgible right now with uh like should we prioritize those who actually
- 16:06
completed the rules I think they they made the effort and they fully completed the requirements at the same time ulab said that uh indeed the uh um the main point is the open source contributions and we can easily evaluate that using the Sloss points um the problem is the challenge that they we wanted to avoid is to uh to avoid rewarding people who didn't indicate that they would even want to
- 16:42
use those tickets in the first place so for example if we would just randomly select sloths based on the um leaderboard or we could have a problem of basically burning tickets um because they would be used um that's why I was thinking out loud that maybe we want to select uh more than just like one or like one or three winners and uh select like 10 of them and reach out to them to 10 of them
- 17:22
immediately and that would whoever is reaching us first will be the will get the ticket tough tough decision here yeah I think um for the next contest we will try to use GitHub more uh maybe get some something when you interact with a bot uh so the bot can advertise some contest and it would be easier for a person if he sees that in a pool request that like for example this PO request is eligible for a contest and he needs to go to a specific issue in our project by
- 18:09
the way race of SCE is open source so and the project is open source so we have everything that we do is open to public and maybe they can go to a special issue and leave their contacts there uh maybe it would be easier for developers yeah we definitely want need to probably create a an issue to subscribe to uh so developers can get be up to date with any contents contest that we are creating for developers gu indeed
- 18:40
like um probably it's very messy and uh hard to manage uh keeping up with all the content content being published on X or telegram or any other social media and GitHub is part of our blood system as developers and we we can use the GitHub notifications as our primary source of information um yeah so I see that in the comments there was a suggestion to take top five winners uh it might be working
- 19:43
probably okay probably I I don't see any other options here so let's let's at least give it a try and we'll see um the the only remain question do we only use random shuffle for uh to to select one ticket winner or three tick winners like those who red I think we can decide right now we can take Alex but for sure we won't do that yeah I think um like we started this project in a vanry friendly Neco
- 20:31
system and I think uh that a lot of the people that are participating right now are earning their SL points and doing pool requests into near repositories so with everybody we are in one handshake probably maybe like worst case scenario to handshakes I mean I do see more contributors that I didn't recognize before we actually started r lome i I would say we are already growing Beyond one handshake um but it doesn't mean that we
- 21:10
cannot reach out to those the problem is not to reach out the problem I see they like U whether they need this ticket in the first place but we can yeah probably within those few days that are left we would be able to go and if somebody wouldn't respond to us we would go to the next one yeah I age they respond to us that they don't like it they don't want that ticket um we'll proceed to the to the next
- 21:42
ones um so just a summarize you suggest we take all the um slots to the to this race yep cool um would you be able to prepare the the um as as we as as in a format that um the contest selector contract um expects it and mean meanwhile I will explain the audience what the contract does yeah of course of course so uh just to confirm we have two people fully eligible and we want to select only one
- 22:26
so I would exclude those two for the list yeah let's do that mhm okay just give me a second I mean we still need to select uh Al so it's not the ranked list right or maybe we can we can turn it into rank list let let's select uh um 10 people and we will go through that list of 10 from top to bottom uh so the first we will reach out to the first person on the list second we will reach out to like if the first person doesn't want the ticket or didn't reply to us in the
- 23:16
timely manner we will go to the second one third one and so forth so for so so on so forth yep that works awesome so let's see let's see uh uh near devop I'll share a screen in a moment uh please B is me I'm trying to find the relevant
- 24:30
to here you you are yeah I see it just one
- 25:51
moment I also know that you are participating in the race as well but I didn't include you as I guess you have the ticket for yourself we'll see maybe I will not win and I will not have the tickets the stakes are high uh share screen yes screen share so here we go we have the um a smart contract that will select the um the winner today and or rather a list of potential winners uh so we decided to build a t chain so basically it's very small but uh um pretty interesting contract um
- 26:41
which leverages many of aspects of near ecosystem and I hope for you will uh appreciate how it's all implemented especially if you already in Mir system you will understand what exactly it is but if you are not I want to highlight the the that the fact that um the um the contracts are the programs that are deployed to to the blockchain and then when whenever you execute it it's all public visible and you can always refer to it and it's always clear that the execution has happened um there
- 27:21
with no um influence from outside so it's uh deployed to contest. race of sloth um near and currently okay we had some test calls before you can also refer to them uh but uh so it was two hours ago but we will do our own execution we'll run the method ourselves so we have the the um the instructions provided here so we will needed a a call call a function on that application on on the blockchain and
- 28:09
provides the parameters as Json is a list of users that glb just collected and we expect to see the just the list of we'll configure it of 10 um and we will use that list um to give away the ticket so let's get it started so we need to come up with the Json file um let's put it here participants H did they cut one person no way yeah everybody is participating and we will have as I said
- 29:13
let's have 10 winners and uh the participants list don't need this and we add it here oh I forgot to add comma anyway and here we are list is here you appreciate my Vim right um skills ready I think it's ready and now we have this command so what do I do and let's use Alish uh R me and on the
- 30:24
side start near contract call function s transaction the call contest do race of sloth do near and we call yeah contest results oh nice we have the autoc completion here contest results is what we want to call and uh we want to pass the parameters as file arguments nice and the file is in TMP participants Json call um I think yeah default value should be fine and we don't need to pay for it which nice and what who will be the
- 31:28
signer I'll be the CER on mainnet I'll sign it so let's re reviewed yeah that's exactly what expected participants winners 10 and um let's see send in transaction nice we have the list right here I think it's fair look at this and we can open the block Explorer oh which one which one we'll use the recommended one blocks here where is the outcome output H and logs logs logs logs logs yes winners
- 32:25
here nice so congrats the first attempt we will go to Peter um and we'll try to reach out to him and U then if not the chances are going to these folks do you feel it's fair I do uh but I think it's fun giveway uh as the first one yeah I think as a first one it's really good I mean it's looks much better for me than you know people in other contests people opening random.org uh randomizing some stuff it's like it's the contract it's not any
- 33:13
website it's done without us we just provide the list and we get the results magic yeah and now you have a proof of contest yes yes that's the most important so it was there it was maybe it was easier for somebody maybe not we'll see but I think um that's it um Leb do you want to add anything here I just want to encourage other people to join uh you see we've made this Contex contest we just used the
- 33:48
contributions from different people uh initially the project was built without any incentives it's just like um it was a chance to do this giveaway we did this we hope to do same things in the future so yeah just join the race you will see more more things more interesting results we don't have any ranked people yet I would not tell you what a rank of sloth is you can always check the code if you are curious enough but sooner or later we're getting
- 34:23
rank Sloss uh SL Hall of Fame and yeah join now and uh let's build near together let's build other open- source projects together and yeah let's do it in a fun way yeah it was a cool way to say go and read our code to uncover all the eggs um I encourage you to go to to the race of SLO repo where the contest contract that we used today is published and where the uh B implementation is also published
- 35:03
and the contract of Ros SLO um itself the the one that is holding the leaderboard is also published and by the way the implementation of this contest contract is like it it it doesn't require any permission from race of sloth team uh to to operate so basically the contest contract pulls the data pulls the scores of race of this loss right from the contract as a cross contract call and
- 35:39
then decide makes the decision uh who is eligible or not does they have we could have added more uh conditions there we could say only those who are uh who collected more than 100 points this week uh are eligible we did it um lightweight this time but I would Envision that others could be more selective and decide that to that only top three slots will be uh allowed to enter the race um we W be uh ever I guess be that selective but I definitely
- 36:25
see the power of blockchain here and the power of our implementation um that makes it fully transparent easy to join so I think we are getting in the in the weeds of um simple usage of web3 without even knowing that you're using web3 yep and then um enable activities and experiences um that are Beyond there like that are not as um um as flowed as uh web 2 contests and web two type of events where you do not
- 37:13
know whether it was uh if it was cheated or there were Bots over there I guess this uh race of sloth allows us to actually build trust um in open source e system of contributors yeah you can also think about it as a reputation system that we're building on chain and everybody else is also eligible to use it so if you want to use it for I don't know what purposes you know how people build
- 37:46
products you don't you don't even know like especially in web 3 you don't even know who would build what on top of what you are building so it's open for everybody just use it contribute to race of SLS contribute to all our projects you're always welcome yeah thanks thanks everybody thanks for watching it is uh nice to have you all here um see you next time y see you