Okay, yeah, a bit of a long title, but I'll show you how all of these components work together to power our SARS-CoV-2 genome surveillance effort in Galaxy. So yeah, I guess most of you know me, I'm working for the Galaxy Europe team at the University of Freiburg in Germany. And I'm presenting today only one very small aspect of all the COVID-19 efforts that we undertook in this project. So the one problem I will focus on is this one that you nowadays probably all have seen a lot in various newspapers on websites and so on. So this is how you actually derive these plots that you see on the right side here with the SARS-CoV-2 lineage stats. So how do you get to these frequencies of SARS-CoV-2 lineages over time? What data do you use for that and how do you analyze that data? You're all familiar with this picture now that wave after wave new viral lineages appear and take over and yeah, and this is probably not going to stop anytime soon. But how is this data generated? So the common way, typical way to do it nowadays is through these tight AmpliCon approaches where you amplify the reverse transcribed viral RNA with an overlapping panel of primer pairs. So you do a highly multiplex PCR reaction with two aliquots involving all of these primer pairs. And then when you combine the PCR products again and sequence them all together, you will get sequenced reads derived from all of these AmpliCons. And this is how you manage to get from a low amount of starting material a complete genome sequence across the 30 kilobases viral genome. Yeah, and that's your sequencing reads. But then apparently there's a long way to go from these sequenced reads to these plots on the right side, right? And there are many data processing steps. And somehow those receive a lot less public attention than the sequencing protocols and the final result. That's the bioinformatics part. And probably because it's complicated, it's not so much the stuff on use. But it's the stuff for Galaxy, of course, that we want to enable. And this is the kind of workflows I'm talking about today to go from such AmpliCons and their sequence reads to this lineage information. And so even if you don't go into very much detail, at least these are the major steps involved. So you want to map those sequenced AmpliCons to the viral reference genome. You want to do primer trimming because as you can see in this image, the sequence reads carry those PCR primers at their ends. And those PCR primers were designed to match the viral reference genome. So for the next step, when you do variant calling to look for mutations in the viral genome, you need to ignore those primer pairs, because they will actually always be reference sequence, because that's how they were designed in the first place. So you want to do that, then you want to do variant calling. And I wrote mutations here in parentheses because in the field, I mean, you have viral variants and that's a bit confusing because you also have mutations, which we as geneticists call variants in the genome. So the term variant is a bit misleading for virologists. So here we're still talking about mutations getting called. And then the last step is to build a so-called viral consensus genome where you take those mutations that you detected and you incorporate them into the original reference sequence to get a faster file that's as close as possible to the actual viral genome that you survey. And then tools like pangolin or exclate, they can take such a consensus genome sequence and do lineage assignment for it. So they can then tell you, well, looking at this faster sequence and all the sequences seen before, this seems to be BA5 or very close to it. And this one is BA4 or this is something novel and so on. So that's the kind of things we want to do with our workflows. And it's quite important that you have standardized workflows here because the hallmark of all these steps is that they reduce information content. You start out with like dozens or even 100 megabytes of sequencing information, but then you throw it basically all away during the data analysis. And the result in the end is just the 30 kb reference consensus genome for your viral isolate. And then you do a lineage assignment and basically just give it a short string as a label what it is like BA5. And so if you're not careful to document all these processing steps, then you just have some final result, but it's very hard to say whether it's meaningful or has been derived in any good practice way or so on. And that's why we thought here's something where Galaxy really shines making these data processing steps reproducible. So what did we come up as a solution where we gave this whole problem various iterations and thoughts and finally came up with the scheme where we provide upstream a couple of workflows, some of them upstream and only dealing with the variant calling mutation calling problem. So we have three for them for various kinds of input data for AmpliConnix. So using this tied AmpliCon approach, the most popular one is this Arctic scheme of primers sequenced with Illumina, the same thing sequenced with Oxford Nanopole technology. And then we also have workflows for calling mutations from Illumina whole genome sequencing data where you do not do this preamplification step with the primer scheme. And all these upstream workflows have in common that they produce mutation calls in standard VCF format. And we also do annotations of these variants with SNPF so that we know what functional genomic effects on the virus these would have. And then we have additional downstream workflows that are doing reporting on this variant spectrum found for a batch of isolates and the consensus building workflow that actually builds then these consensus reference genomes that I've been introducing and that are the source for pangolin or next clay lineage assignments. So why did we break up the thing into so many different workflows? Well, the reason is not every user of these workflows will want to do the whole thing. There are users who are just happy with producing a VCF of what's there. There are the users who want to go all the way to these consensus sequences to feed them into pangolin or next clay and there are still other users who want to analyze that variant spectrum further but who find VCF too complicated for their scripts to pass. So they would want some tabular reports and we also as part of that reporting workflow produce such overview plots about all variants and their observed delete frequencies that are found in a batch of isolates of viral samples. And so users can combine components that they really need in their analysis and it also gives us more flexibility when we do updates to these workflows. So like say we find a bug in our consensus building workflow which actually has happened already in the past. We only need to modify that one workflow and then to reanalyze data that we've previously analyzed the wrong way let's say or in a suboptimal way. We do not have to run the whole expensive analysis again but we only need to run the consensus building workflow which we changed on the outputs of the upstream workflows again. So it speeds up reanalysis also. Okay and then yeah this is what the upstream workflows look like. So for mapping in the Illumina case we use BWA-MAM, we use low frake for variant calling, then SNP-F for variant annotation and the IVAR suit of tools for this primer trimming thing. In the case of O&T data we use minimap2 as the mapper and medaka as the variant caller otherwise it's pretty similar. And yeah then come these downstream workflows afterwards and they end in these tabular variant reports per batch and in a multi-faster consensus sequence for all isolates that went through this run of the workflow as a collection. Then we put all of these workflows through the IWC, the intergalactic workflow commission on to Doxtor and workflow hub and this makes the whole thing highly reproducible. So any users interested in using these workflows they can go to Doxtor for example import from there into their Galaxy instance of their choice and run something at a defined version at a defined release. And this is actually quite convenient now if you look at the Doxtor example for example you can go there select one of our workflows you list get a list of all the different releases we have for this particular workflow. You can say I want to run this on one of the big three Galaxy instances or I have a public URL to my own preferred instance and I want to launch this workflows there so you can choose use galaxy.eu for example you're taken to the Galaxy Europe web interface and there you see those same versions listed you can now pick one for importing and you will have that imported into your list of workflows and can start working with it. Conveniently now you're also getting this nice little green check mark here that says you that tells you this is exactly the version main of this workflow from Doxtor and nobody has changed it. So if I open this workflow now in the workflow editor do some changes and save it again that check mark will disappear and I will know okay careful this is a modified version not the one that's officially released by the IWC through Doxtor anymore. Yeah so this is there to ensure reproducibility and this all works nicely but now we're having kind of a new problem we have all these different workflows to run and if you think of SARS-CoV-2 genome surveillance the issue here is that we are not talking about analyzing a batch of 100 samples or so and be done this could be nicely done in one workflow run through collections but we want to analyze hundreds of thousands of samples as they come in and their data gets deposited as raw sequencing reads in public repos so to scale this you really don't want to manually execute three workflows in a row for each new batch of data that comes in and you could also not really keep track of all the outputs that way so we had to come up with some automation of the whole thing and this is now where Planimo and Biobland and as you will see also the tags come into play if you don't know about how to use the API through Planimo to execute workflows from the command line you can go to this tutorial that mostly Simon from Margaret has written last year it shows you the basics of using Planimo Run with a so-called job YAML file to execute a workflow so the essence is you write this YAML file where you declare the input data sets to the workflow and possible workflow parameters and then you do Planimo Run give it a workflow ID of your workflow on your Galaxy instance pass in the Galaxy URL in your Galaxy API key and the YAML file and say Planimo run this workflow with these input files from this YAML file now that's the essence and so for automation we're making well use and we abuse maybe the system a little bit in that we are using command lines in such a job YAML file to in a in a template version of such a job YAML file so we're putting lots of information in these command lines like where to run this workflow what the workflow ID that we want to run on the server would be what the collection name that's built as the first step is going to be called what the history name that's created during the workflow run should be and some templates of data sets that we will download as parts of scripts so we have a script that basically can download SARS-CoV-2 sequencing data many samples at once a batch of data from any public repository like the ENA and then use BioBlend to download that in a structured way as collections into a Galaxy history and that BioBlend script that will download all the data and build the collections will then put the actual dataset IDs and the batch name for the analysis which it takes from the batch identifier from the ENA will put this here instead of those template variables in these command lines and then the actual job YAML part that Planimo Run will see has where the general input files like the SARS-CoV-2 reference sequence live so their ID on the Galaxy server and so on and after the data has been downloaded the downloading script will extend this template file with the collection information about where the raw reads now live on Galaxy once it knows that information so we start out with this template file we call our BioBlend dependent script that will do all the downloads for us and that script in the end will fill in all the missing information into this template and then the result of this will be passed as the job YAML file to Planimo Run and that will execute the analysis workflow for that batch and so in the end we have couple of batch scripts that are used for the variation workflow launching for the report workflow launching for the consensus building workflow launching and also for exporting stuff to an external FTP server and those all start out with these template files and in the end after calling Planimo for doing certain housekeeping things will pass that final job YAML file to Planimo to execute the workflow that they want to run that's how this is all public this lives in this use Galaxy minus EU in a Cog UK workflows repo so you can have a more detailed look at that if you're interested and essentially then we're running these batch scripts as current jobs or in our case on a Jenkins server at regular times and they will just grab the latest input data downloaded onto usegalaxy.eu or usegalaxy.org launch workflows with Planimo Run and wait until the results are there and then now come the text that's the last thing I haven't explained yet since these are just current jobs or Jenkins runs how do we record state of what has been done yeah which data has been processed which has already been going through the variation workflow which needs consensus runs and so on and we're using history tags for that so basically whenever one of these scripts runs it will put a specific tag on the history it creates so for example if the variation script runs and it launches the variation workflow will generate a new history and will put a tag on it that says bought go consensus and bought go report so informing the other scripts that next time they run this is a history that has the input data for running the reporting workflow or running the consensus workflow and then once these workflows have run and their batch scripts are complete they will change this tag to consensus bought okay and report bought okay and next runs of the downstream workflows will know this is a history that has already been processed and that doesn't need processing anymore okay a bit complicated feel free to ask questions about it if you want to afterwards um and with the system we built then this powerful automated system where we're regularly downloading the latest data from the ena from selected saskoff to genome surveillance project national surveillance projects we're taking those workflows from workflow harbor dog store with the defined releases we're using our workflows through these bash scripts to execute them automated on the data with these workflows and then we're exporting i showed you this one script the export script key results files like bams vcf and faster files to a spanish um fdp server at the basaluna super computing center and from there our data galaxy then acts like a data provider to these downstream projects like the viral deacon project at the crg in spain for the ucc genome browser where we have a track nowadays for our galaxy data and for our own interactive observable notebook where we show our data interactively um to anyone's interested like a dashboard like also many national genome surveillance projects have it and um yeah this is also where the modularity of things comes into play again so different of these downstream consumers expect different files right if you viral beaten for example is basically interested mostly in our vcf files and we have them already from the first workflow run um the reports are interesting for the observable dashboard and for the ucc genome browser where both of which do not want to deal with the full information in the vcf but want a clear tabular report of things um these workflows are also used in estonia for example by their national genome surveillance effort um and they are interested in the consensus fastest to run next strain pangolin on them you can also do this inside galaxy um so different users different needs and that's why this modularity is important yeah and in total we have now analyzed about 400 000 samples so far and all the information about them is on the spanish fdp server the address is given there um two files of importance are these all variants file which is basically a tabular report of all the findings we've ever made um and this jake surveillance jason file which is interesting if you really want to take a very deep dive into the data because this actually in jason format encodes the information in which batch each ena sample has been analyzed in and where the analysis histories for this particular batch live on public service for example for this reporting workflow run you see that that's this history on use galaxy.eu and you can then actually go to this history and inspect all the intermediate data how it was actually produced at runtime so if you really are interested in very very detailed questions then you can follow this up and this is also great for us if we find errors in our analysis later on we know which kind of which data has been analyzed with which workflow release and so on and we can reanalyze certain data and compare the differences between the analysis runs so this file is quite important but very specialized but i think no other project has this information trackable in this kind of detail yeah and then outlook of course currently we're interested in expanding this or making it compatible with other pathogens i mean saskof2 is certainly not the last pathogen of concern that will come around there are many candidates for triggering a new pandemic at some point and so we want to maintain our existing workflows still improve them as new tool versions for analysis tools are released adapt the workflows to other pathogens of concern this is not really super super difficult to do but every virus is a bit different in its genomics so they all have highly highly specialized genomes and sometimes you just need to tweak the analysis a little bit to cope well with one particular genome yeah and of course we need to not we i mean the big public galaxy instances are probably fine with that but virology departments of course also need to maintain their infrastructure invest in galaxy and and get familiar with how the whole framework works they still have time to prepare hopefully a couple of years but that's the thing we need to promote yeah and with that i want to thank all the people involved that's a lot of people of course i mean it's a big project so anton most of all who was constantly pushing this project further beyond for well assigning me to it and always be helpful a long way simon who did a great job in setting up this automation things getting things merged upstream into planimo to make it do exactly what we wanted it to do marius for constant technical help and for all the great investments into i w c um yeah and not going through the whole list but really thank you to everyone involved also to john of course for building planimo for nicola for maintaining and having created biobland those are very essential components um yeah and if you're interested in everything i said in this talk here all the links on one slide so everything we've created um so you can everything's open source public so explore good um that's it i'm happy to take questions yeah thank you so much for that presentation okay that's awesome work are there any questions from the good oh good if i may so right now so the quag UK must have slowed right yeah quite a bit so how do you what do you pick as new right now because i mean we had this discussion about perhaps pulling a plug on this but actually i think we should continue uh with with um with a selected set of high quality samples so how do you pick the right samples right now so yeah for a long time until this summer we actually had to just randomly sub-sample the coca UK data yeah because it's really not worth i mean they were at peak at peak times they were submitting like i don't know 20 000 samples a week or so and that's just crazy to keep up with and also probably not worth analyzing all that data so i was essentially just doing a random sub-sample down to a fifth of the data so and was analyzing just that it gives you still a representative snapshot of what's going on now we can slowly revert if we want to actually to following and analyzing all of the data again or maybe half of the data so so we just basically increase the ratio of what we are analyzing that's how i'm currently doing it of course we can also constantly i mean we're not just monitoring coca UK data but we also have this collaboration with Estonia and for them we are really analyzing all of the data even during peak times we are also monitoring greek data and there we're currently lagging a bit behind but that is relatively easy to catch up now that there are not so many new samples anymore um yeah and then we have to see what the winter season brings right i mean there could be new variants maybe it spawns new interest in sequencing you never know but um let's hope not let's hope everything stays calm and um yeah and slowly i was wondering if we can initiate something similar for monkey blocks i actually haven't looked for what's the current sample once again quite yeah monkey pox to slowly slowly die off i mean it takes a long time a surprisingly long time but case numbers are decreasing i mean we could still do this retrospectively and analyze all the monkey monkey pox data but doing it live currently is probably not worth the effort to set this up um what we in the EU team are currently really interested in is um avian influenza so we are planning to build something similar much smaller scale because there are not so many samples um to monitor global avian influenza samples um the core part will also be these workflows pretty much the consensus building workflow and the variation calling workflow only thing you have to do for um avian influencers have uh still an upstream workflow to the variation calling one uh where you determine the subtype of avian influenza first so essentially you need to build like an assembled reference genome that picks the right influenza segments and merges them together like if you if your sample is h3 and one or something then you want to make sure that the h segment gene segment is h3 that you're using as the reference and that the n gene segment segment is one and you want to merge those together do variant calling against that hybrid genome um and then build a consensus genome from that um that will be the difference we think um yeah that's one of the things we would like to do but there are also these other I mean luckily many of the of the viruses with the highest pandemic potential like nipah virus um they are rather similar to SARS-CoV-2 in terms of like what kind of virus they are they are these small relatively small genome RNA viruses so those should in principle all be analyzable with that basically same workflow without big changes hopefully very cool do you think the new deferred data will be helpful in producing maybe the Jenkins runtime because instead of I mean it sounds like the scripts upload wait for upload completion uh and then build the input files you could directly build the input files and just use deferred data yes if that works well and doesn't cause all kinds of downstream failures then because maybe one of these data set doesn't become available at all or whatever but this needs to be explored but if it works well then it would greatly simplify things I guess yeah um yes because all that monitoring when something is complete um yeah can completely be eliminated yeah yeah another that could be nice in a nice improvement is actually I mean we're lying a bit I don't have that slide now on anymore but um where we're saying we're doing this automated bot runs with the workflows from workflow hub or docstore I mean basically we're downloading those releases once onto the servers and then we're referencing them by ID on the server a cleaner approach that's also an area where we could improve things would be we would really do every one every time a fresh download via the TERS ID the the tool I mean no I mean how I would see the ideal situation is that you don't say by ID and you just give the TERS ID and then the server will get it or run it if it already has exactly right so currently what would happen if you if you instruct Planimo to take a workflow from elsewhere it would upload it every time into your user account so if you run that workflow like 500 times you would have 500 copies of the same workflow so this is an area where we could improve I mean Planimo I mean I think ideally the workflow run I could accept directly TERS IDs so maybe validate that it's a valid ID but that's it then run it yeah and the caching thing yeah if it downloads it it should either download it not into your workflow list but just to some kind of staging area or keep track of what it has already so that it knows okay this I've downloaded already like two minutes ago and now I'm not going to do it again yeah I mean they go to the little compute node right so you if you run your job I mean if you start many different workflows from the same input file then it's not a good idea but I think we don't really do that so yeah yeah on the flip side you're not keeping the file unless your first step makes a copy of the inputs yeah true which I mean I don't know but then that kind of negates the whole advantage um yeah I mean that we can discuss some more maybe next week also when you had the European Galaxy days could be a good chance no um so something else that while we were working on the initial stages uh of this was I would be pretty cool um if there's a workflow I mean if you programmatically knew when the work location is done right so the the best we have currently is an email and I guess you could automate that for higher throughput uh but I'm wondering if you all if you see the same way or if this is just a dream of a developer um and and it doesn't really matter but I'm thinking if we could you know kick off a webhook or something when a workflow has finished would facilitate your analysis yeah this would be very nice also if there was an easy and reliable way to query state of workflow like some simple planimo interface for that instead of like using bio blend to to go through the history and see what has run which is in what state some summary that you could obtain easily and query the workflow and it answers like okay 30 percent done uh with so and so many datasets still do you mean the jobs for per invocation yeah something like that that could also be cool um yeah um and there is actually a bit of weird thing about planimo at least on use galaxy.eu that I still need to explore at the moment so I mean I mean one way to know when a workflow is done completely is that the planimo run call would return on the command line right so if you just write a linear script you know it's done because planimo returns but for some reason at the moment workflows are often long completed on use galaxy.eu and planimo just doesn't return and it's unclear what it's waiting for when everything is finished yeah and I don't know if this is a server or planimo or some other kind of issue so that's currently something I'm exploring um yeah but this whole area of keeping track of how far we are into workflow that could need some improvement yeah I guess some emails when it fails would also be good or yeah yeah um how are you dealing with intermediate data like um I mean not not every output dataset of the workflow is valuable right yeah true um where currently we still have it all but the idea is that at some point we will just write another script that goes through all the histories which we keep track of in the jason file and we define just which are the valuable outputs that we want to keep more long-term and the other one we just remove via the API that's the plan but currently there was always something more urgent than cleaning up so we still have it all in our histories yeah I also still have 10 terabyte of my postdoc data on the system let's publish this again so I just need to so I in in combination with the continuous monitoring and this idea that Sergei had on uh reanalyzing data from some high-profile papers I think we should be to go and I think you already started processing of this so yeah I mean publishing so of course that other thing where there's always something more urgent to do than writing up the manuscript finally I mean um there's always bugs to fix new samples coming in some hype about omicron or whatever so this has been very exhausting two years but um yeah I mean the product is yeah I know it's the right the standard will be a new variant that will need to urge yeah if you can uh put the link to the slides somewhere yes of course um should I just I can't just put them in right here now in the chat um wait that's not the one for sharing I can first share it with everyone we'll also post the slides to um to the agenda for a future reference well thank you so much for going for the presentation yep you're very welcome if there aren't any other questions uh we will see you all in uh two weeks on October 13th for the next community call thanks everybody for joining thank you thank you


President Mohammad Buhari has expressed optimism that the presidential flag bearer of the ruling of Progressive Congress APC Ashwa Jibwa Latinobu will deliver as the next president of Nigeria. Buhari gave this assurance while addressing supporters at Iddan Anyam Stadium, venue of the APC presidential rally in Imo State on Tuesday. I am here, ladies and gentlemen, to thank you very much for exposing yourself to the weather for so long to make sure that Bola Ahmad Tunibu has been delivered by our great party as the next president of the Federal Republic of Nigeria. There are nothing more I can say, the chairmen of the party and other members have information. We are here today, we are very grateful for your turnout, we are very grateful for your support and God willing, Ashwa Jibwa is going to be delivered as the next president of the Federal Republic of Nigeria. Thank you very much indeed. Thank you very much indeed. Thank you very much indeed. On his part, Bola Tunibu said the PDP cannot be voted into power because they have a habit of not fulfilling their promises to Nigerians. See the last eight years as a year of retooling, retooling the neglected foundation which the other party abused to move forward. West, east road, ticket completed. Infrastructure are in your job. Road line on, they share the booty of electricity generation and distribution. They forget the transmission line is a load carrier that must be strengthened, renewed and be serviceable to the people. Instead, they started giving you estimated billing. Abba, abba, has to be taken away. We don't want that no more. And they want to come back, they want to come back on those lies. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Hey everyone, welcome back to Prime Answers. This is a Q&A video where I answer your questions about video games and I guess whatever's on your mind. I kinda limit my questions to one per person if you would like to get questions in for next week. Just head down to the comment section down below. But without further ado, let's get into your questions. And our first one comes from our Discord server from Terence D. Clark who asks, will Sonic Frontiers be the best Sonic game since Sonic Adventure 2? That is a very, very subjective thing to say. I don't even think Sonic Adventure 2 is the best Sonic game. For me, my favorite Sonic game of all time is Sonic Lost World. For some people, it's Sonic the Hedgehog 2. Maybe it's Knuckles, maybe it's Sonic Colors or Generations. Everyone's gonna have their own favorite Sonic game. So same, will this be the best Sense X game is very, very subjective since that particular favorite Sonic game is going to be, well, up to the eye of the beholder or the eye of the player. Now for Sonic Frontiers, I think it has a chance to become the best Sonic game of all time. It can also end up being a steaming pile of doo-doo. There's nothing to really say about this until I actually play it. I think at times it looks really good, at times it looks a little bit questionable. It's not here yet, so I'm not sure what you want me to say and all of us are gonna have different opinions. Next up, speaking of Sonic, Sonic Man the best from our Discord server asks, in the far future from now, do you see a day where you only focus on live streams? Not talking about now or next year, I mean way out in the future. Now I find this question to be fascinating because I've actually talked in the past, about two thirds of my revenue at the channel comes from live streams. Now what do we get in live streams? We get super chats. We also happen to get memberships. People aren't hitting the join member button unless it's during a live stream. I've yet to get a member to actually join based off a video. It only become members on the channel which is a paid subscription through the live streams. So do I see a future where I'm only doing live streams? No, despite the fact that clearly it makes more revenue than my standard videos, I don't necessarily want to be a full-time live streamer. There is too much pressure put on full-time live streamers to stream from eight to 12 hours per day. This takes me away from my children. This takes me away from my fiance.  One thing I like about being a YouTuber is a little bit of the flexibility I gain from not only the fact that I have an in-home studio here, but also because if I'm gonna be a little bit late with an episode of, say, Prime 5, I don't have to panic that, oh, because I had a doctor's appointment this morning, or I had to go meet with the teacher of our parent-teacher conferences, or I had to go do this thing, or I have to mold a lawn. I don't have to panic that suddenly I'm gonna be missing out on money because no matter when I release that video, as long as it's before, you know, I don't say eight PM at night, as long as I get something out before then, it's probably gonna perform okay and still make the usual 10 to 20 bucks per video my videos typically make. We're actually moving our live streams off the channel. Anyways, we're gonna be live streaming all of our live streams over on the podcast channel, hopefully temporarily, while we build up a brand new live stream only channel. That's right, we're about to have a four-way network going here at Nintendo Prime from having our standard channel, our podcast channel, a live stream channel, and a website. In case you guys didn't know, Nintendo Prime.net, go check it out. So no, I don't foresee a future where I'm ever a full-time live streamer. I'm just not interested enough in sucking my life away for eight to 12 hours a day staring at a screen. It's just not gonna happen. Next up, we have a question from a retro geek. He says, Prime question, what if any of the older Sega franchises should be brought back and modernized and which one should be turned into a movie next? Actually, to make some notes on this, I don't play a lot of Sega games. I just never have. I didn't really play Sega growing up. I eventually did play on a Genesis, but I wasn't playing Sega's games. I play Crazy Taxi. I'm not even sure if they own the IP rights to that. To be honest, the only game I can really think of from their back catalog that I might wanna see back is the Knights series that was made by the Sonic team. I think the last one came out on Wii. I think there's only two games in the franchise, but I'm not like an expert, so don't quote me on that, but I'm pretty sure the final one came out on Wii. I would like to see maybe that IP comeback if it's a remaster, a remake, a reboot, or even just a third game in the series. That's maybe it. I can't imagine anything else. As for movies, the only thing I could think of is technically Sega owns Bayonetta, so they would have to approve of a movie for Bayonetta, and I wouldn't mind seeing a Bayonetta movie rated R and then maybe have it have a similar style and feel to say Constantine. Guys remember that Keanu Reeves movie called Constantine where he was fighting demons and repelling Satan's son, and I'm not gonna spoil all the plot for it, but the point is I thought that that was a really nice movie, and I would like to see since Bayonetta deals with demons and all this stuff, it might be kind of neat to have a movie in that ilk, although obviously with Bayonetta as the titular character and doing Bayonetta things. I don't know, that's just me. Next up we have a question from Umbra who says, prime question, will Switch Pro be launching within the next year and a half, and if so, what changes will be made to the console? I think if Nintendo wants us to be a 10-year platform, then yes, Switch Pro is out in the next year and a half. If they don't care for it to be a 10-year platform, then we're talking Switch 2 in 2024. In terms of what changes, at this point, I like Switch OLED the way it is. I like the OLED panel. I think it looks really good. They can keep the 720p screen. I am totally fine with that. I don't, like my phone here, I think this has like a 4K screen. Honestly, it could be a 1080p screen. When the pixels are that small, it doesn't really matter to me that much. So I'm cool with staying at 720p and just giving you more performance and handled for frame rates and just graphic fidelity and doing a bunch of crazy stuff with that, which by the way, graphic fidelity is not resolution. Resolution is clarity, just to clear that up. So yeah, just more power. We need more power. I would like to see the new chipset. I would like to see them go with a 4K DLSS setup for home consoles. So things that stops looking so muddy and blurry on big TVs and obviously getting better performance and frame rates. I just want games to be at 60 FPS or if you're gonna have something that pushes the visual fidelity to the extreme, a locked 30 FPS. That's about it. Cory Boehm has a three pack of questions and the only reason I'm allowing him to have the three pack is because I'm on his family membership for Nintendo Switch Online. So as least I can give him. Cory Boehm says prime questions, squid or octo. So this is for two and three. Also what weapons you think are amazing. Like this is a four pack, so squid or octo. Probably going with squid and I've always been an NZAP player. So probably gonna end up with that unless I end up liking one of the newer weapons better. He also says, what day of the week will the community's flat up be? I have no idea. I do want to do a weekly spittoon three sort of gaming event. Whether I'm playing or not, I would like our community to get together and play together. So I haven't figured that one out yet. I probably should since it's coming out next week. But I think I need to, it needs to come out. I need to play it and then talk to the community and figure out what day works best for them. And then the last one is us. How many losses will the Green Bay Packers have this year? I have no idea. Five, six, dude, I have no clue. Maybe they go undefeated. Beats me, man. I don't play for them. So they determine their own victories, not me. Next up, JohnNYMC says, so you probably get asked this all the time. Now we all know there's going to be a Nintendo Direct soon. Well, we don't know for sure, technically. It's September. What three things do you want to see? So what three things do I want to see? Personally, just speaking of personal desires Breath of the Wild 2. I don't think Breath of the Wild 2 is going to be there, but I want to see Breath of the Wild 2. I want to see a new Mario game and I want to see a tease for Metroid Prime 4. Koo, and this question now comes off of Twitter. How do you feel about cloud game support going forward? Do you think there will be more cloud games down the line that took the Kingdom Hearts direction because of the game package being too big so it couldn't fit onto a cartridge? Or do you think that's an excuse? That's an excuse. You said it at the end. Most of those Kingdom Hearts games can run natively on Switch and most of those Kingdom Hearts games aren't very big file size wise. We've seen them on other platforms. The file sizes aren't that big. The cartridges are fine. The cartridges could have fit all of those games onto a single cartridge. There are 32 gigabyte Switch cartridges and there are factually games using them. It's an excuse. Also, what we forget is that you could do digital only releases where you just download the games and it doesn't really matter what the file sizes are. Do I think cloud gaming is going to get more support on Switch in particular? Yeah, we've already seen an increase in that. I'm not someone who hates cloud gaming. I just dislike when it works poorly. Kingdom Hearts is an example of it working poorly. I would say Hitman 3 on Switch might be an example the other way where that it actually works pretty well on Switch. Switch it up for over on Twitter says, hey, Nintendo Prime, do you think Nintendo of America will release a new Fire Emblem game? Well for starters, Nintendo of America doesn't make games. So they won't release anything. But will Nintendo release a new Fire Emblem game? Yeah, why wouldn't they? Saturn ascends over on Twitter and asks whatever happened to this? And he's talking about the Mortal Kombat Collection that was rated by multiple ratings boards back in 2020. Now it was rumored to be canceled in 2019 but then it popped up at rating boards in early 2020. And it made people go, man, I guess it's still coming. I don't work for the studio. What am I supposed to tell you? Pandemic hit. It was already previously canceled and it supposedly brought back. Maybe those ratings were from the canceled version of the game like they already submitted to the ratings board before canceling it. I know real big reasons were given for the canceling in 2019. I just assumed the development didn't go well. That's the only thing I could think of was, hey, development didn't go well and then we hit a pandemic. I'm pretty sure that collection's not coming out.  So yeah, I think it's canceled. But again, I don't work for the studio so I can't tell you 100%. And unfortunately there hasn't been any real direct communication about it even back in 2019 and 2020. Even 2019 when it was seemingly canceled it wasn't like direct communication. So yeah, I think that's it. Anyways folks, thank you so much for tuning in to Prime Answers.  We'll have another video for you guys tomorrow I believe on Sunday. It's either gonna be a single piece of news or I actually have a couple other things I wanna talk about including making your Switch massive. Have you ever like thought when you're on the go with your Switch Man? You know what? That Switch screen is too small and I want it to be bigger. I've got a solution for you and it's quite interesting.


Hi, this is your host Abdul Bhartian. Welcome to another episode of Mainframe Matters. Today we have to guest John Murtic, Executive Director of the Open Mainframe Project and Elizabeth K. Joseph, Global Head of the Open Source Program Office for IBM Z. Elizabeth, John, it's great to have you both on the show. Thank you. Thank you, it is definitely great to be with you. Yeah, and we're going to talk about Open Mainframe Summit and if I'm not wrong, this year we are going to have not one but two summits at two different location, West Coast and East Coast in Las Vegas and New York. John, let's get started with the first of all, talk a bit about what is Open Mainframe Summit all about and also then let's talk about why we're having two different summits and if the focus for those two summits is going to be different. Yeah, so Open Mainframe Summit, we started this event a few years ago with the idea that there really wasn't an event that brought together the open source and mainframe community into one avenue. There's a lot of great events on the mainframe side, especially community events, where they're very much driven around training education but less around sort of collaboration and interaction and building a lot of great, cool, interesting ideas and also just bringing elements of the open source community in. So this event was founded with that principle and we ran it through COVID the first couple of years, meaning it was an online event, which really went really well. I mean, we had a huge uptake, lots of interest, some great talks. Last year, we were in person in Philadelphia, which was really neat because many of the people who attended hadn't seen each other in years because of the pandemic. So it was almost a great opportunity to bring that community back together in a lot of different ways. This year, as we talked with a lot of the folks that attended the event, they said, hey, you know what, this is great stuff. How can we get this even closer to our end users who are the direct really beneficiaries of the great technology that's happening? So we had the fortune of being able to partner with two great events out there. One of them is the IBM Tech Exchange event. It's actually a new, it's a new event by name, but the concept of this event has been running for a number of different years that brings together IBM customers, users, partners all together under one roof, you know, to discuss a lot of the great technologies and the work that's happening. We're part of the day zero community day there. So that's gonna be a great opportunity. It's gonna bring together the mainframe customer and user and vendor base and kind of the people slightly removed from that as well. The second partnership is with Finos, which is another one of the projects here within the Linux Foundation. They hold a great event called open source finance forum. They've been doing it for several years now and they hold it right in Wall Street. So it brings together all of the big financial institutions with the amazing focus of having an event that's very cross-functional across a bunch of different domains, whether mainframe, web dev, cloud, blockchain, FinOps, you name it, bringing it all together. So us being a part of that event showcases mainframe as a part of that larger financial services story and helps us sort of plug in, get in front of people that we would not have necessarily before, but also better advocate because a lot of these financial services companies, there's a lot of disconnect between the mainframe side of IT and the rest of IT. And so this is an opportunity to bring it together. So it's a little bit of a split focus, but we see this as an opportunity to hit two great audiences in different unique ways with some really cool messaging. From your perspective, when we look at open mainframe summit, what value do you see it brings to not only the mainframe, but at the same time bringing the mainframe community to the open source. Can I talk about the bridge there? I mean, so in some ways, the open source community is not something that is unfamiliar to mainframers. I mean, the major conference and the major organization within the mainframe community is called Share, and it is what they do. They've been sharing technology and programs and tips and tricks for decades now. Open source name is new to the mainframe community though. And so what we're trying to do is kind of bridge that gap from what is known and what mainframers have been doing for a very long time and what is kind of the industry standard now with open source software. And that's for one, why I'm really excited that the Linux Foundation is involved in the open mainframe project in general. And now why we're bringing these events to a broader technical audience. Talk a bit about what will be the focus of tech exchange and then we'll talk about the presence of the open mainframe community there. It's really about getting professionals and folks who are interested in technology in general together to learn about a bunch of different things. So as John mentioned, we're gonna be on the community day which is like the day zero of the conference, but then woven throughout the rest of the conference will be of course more talks on IBM Z Linux one general mainframe topics along with the whole pretty much portfolio of technologies that IBM has invested in. So I think it's gonna be a really interesting opportunity for participants because they're going to be able to get the open part of it and come to the open mainframe summit and then ease into some more general topics. And it's not something that's completely, the talks are not all from IBM or it's in the main event either. I mean, the call for papers was totally public and open. So we're gonna have a lot of really interesting stories from clients and other practitioners and organizations using mainframe tools and of course other products. The focus of each event going to be different character to the audience which is going to be there or it will be the same focus irrespective of the two shows. I think we're gonna see a little bit of a different focus. The tech exchange event is really gonna be going to the bread and butter audience of main framers because you're gonna see just a lot of those users there. They're gonna be looking at other various IBM products and services and things like that. So it's gonna be a natural intersection point because the education already happening. I'm seeing sort of this Finnaz event while we will get some mainframe audience there it's certainly gonna be sort of the non-believers crowd if you would, people that may have some familiarity with the mainframe, maybe they've worked on it in the past maybe they know it, it is this box that sits on the whole other side of their company they didn't know anything about. And I think we're gonna see a lot of the focal of that event is really helping close that gap and cross that chasm and talk about the technologies that are interchanged because as we talked to these customers the mainframe deployments are not shrinking, they're growing and the challenge within any business whether it's a mainframe infrastructure, cloud, IoT, whatnot, it's how do you better leverage them within your organization to drive business results? So that is gonna be really a lot of the focus that we're gonna have is educating people on technologies like Zoe for example that really helped cross use a lot of this data and a number of other technologies and work we're doing as well. What is going to be a theme of open mainframe summits is once again same or depending on these two events it will be slightly different. Of course as you said audience is totally different and you're also looking at a kind of different kind of content also. I'm anticipating the thematic and I think we have a program committee coming together which Elizabeth is a part of that's sort of looking at the talks and coming in but I think there's gonna be a lot of thematic for the open mainframe summit within Las Vegas to be really focused on education driving awareness around the technologies helping people understand open source as it relates to it because there's a lot of information that hasn't, a lot of folks just don't understand how you engage what it's a part of things like that helping understand how these technology benefits them. There's so many of these customers that are or vendors that are building technologies that do a lot of the same things as our projects and how can we get them to work in these communities to build those technologies stronger so that they can work at a higher level. So I'm anticipating that's gonna be a big focus there where we're looking at the New York event is kind of got to where I was saying earlier about that audience may not necessarily know what's going on with open source in the mainframe but they know they want to try to leverage and bring these computing power within is talk about the technologies that are doing that the customers that are doing it successfully what those stories are looking like so they can kind of help go down their own journey. We're seeing some real pioneering customers out there that are at the forefront of driving forward with these technologies as being a part of their forward strategy. So helping showcase that thematic so that the people in attendance can see, hey, wow, we do have these mainframes and we're not taking advantage of them very well. These are the technologies to help us get there. I have you folks already started working on what kind of talks out there are you working on call for papers and things like that and what kind of content you're looking for. One of the things that we're really looking for is practitioners and folks who are already using the tools and so they can be an example to other organizations because no one wants to be the first to be using these tools and I mean, some of them maybe want to play around with it and do some development but for a lot of the organizations that we interface with they want to see proven examples out there in the industry already. So those stories or at least the building blocks on how to get there. So like, what are these tools bringing to my organization and how can I get to a place where I'm production ready? So seeing other trailblazers is really helpful. Also, one of the things I like to tell people is we really want to demystify the mainframe. When I started working in this area about four years ago I could barely tell you what a mainframe is. I said, it's a computer, does it have storage? I couldn't answer that question. And so it's really about making sure that we're telling that story and explaining that open source software does work on these systems that a lot of the tooling that is already being used by your organization can be used on the mainframe and how projects like Zoey can interact in that story. John, Elizabeth, thank you so much for taking time out today and talk about these two upcoming events. Of course, I would love to chat with you folks again and of course, we look forward to attending these events in person as well. Thank you.


Going on everybody got Cal and Shawn here relating sports cards or ripping one box for Jonathan D It's gonna be a 2023-2024 Bowman Chrome you Breakers the light. Good luck here. Sir. Good luck. Johnathan got Dfm here now. What up? Oh boy Dfm. What up? Dfm has arrived everybody One one-and-a-half Saw match. I like that.  We got Isaiah Collier U.S. seat 399 DJ Wagner for Kentucky. They page buckets the 299 nice name so far page buckets Risa Shea on the purple mini diamond of 399 There is a 299 Dylan Jones and Golda 50 is gonna be Jordan Dingle Dingle Hopper The Cortises boy there on the first golda 50 Jordan Dingle You know I get her attention with that one. There's a first refractor Risa Shea Went to the guitar hotel last night. Really? I've I've I like to look at that place, man. That's pretty sick first Michaela Williams, Aliyah Martin Got a El Marco Jackson sharp shooters there for to 150 Kansas every brother works my brother works in the USA El Marco There's a first you on Roberts base for the Rockets And you might have seen Sean's brother there. Yeah, might have been taking your money First there Got a lava that one's gonna be the 199 Ryan Colkburner for Creighton And on the back we have a Spencer Jones on the base auto for Stanford Spencer Jones base out of there Yeah Righty, and that'll do it for you mr. Jonathan one box of Beaumont chrome basketball delight get that right out. See ya


TEFL San Diego, California Located on the Pacific Coast of Southern California near the Mexican border, San Diego is well-placed for those seeking to make the most of all the area has to offer. A warm climate throughout the year, long stretches of beautiful beaches and an abundance of sport and leisure activities make San Diego the ideal place to take a TEFL Tezal course and to start out as an English teacher. For nature lovers the city is surrounded by gorgeous coastline, impressive mountains and beautiful valleys. For the culture vultures among you, San Diego is also home to a large number of museums, galleries, theaters and music venues. Whether you are into surfing the ocean or browsing the museums, San Diego is a great place to take a TEFL Tezal course. Known as the birthplace of California, San Diego was first settled by Europeans when the Spanish arrived in 1769. However, San Diego didn't really begin to thrive until the arrival of the railroad in the late 19th century and then the establishment of several military installations during the 20th century saw San Diego rise to the bustling metropolis that it is today. One of the main attractions of the city is Bulboa Park, a vast recreational area covering over 1,100 acres. The park includes a number of museums, including the San Diego Air and Space Museum, several theaters, San Diego Zoo as well as delightful gardens and 65 miles of trails for hiking and biking. In addition, there are several sports facilities including lawn bowls, tennis courts and a public swimming pool, not to mention various shops and restaurants. As you would expect with any large city there is a thriving nightlife, with bars, restaurants and shops catering to all budgets centered on the historic heart of the city, known as the Gas Lamp Quarter. This area hosts many festivals and events throughout the year including Mardi Gras and St. Patrick's Day celebrations. If city life gets too much for you, head for one of the many beautiful beaches that are no more than a stone's throw away. Chill out in the sun or take part in the many watersports on offer and when you are done sit back and relax at one of the many boardwalk cafes. If you are looking for a great place to earn your TEFL Tezal certificate, you can't go wrong in San Diego. With all the delights the city has to offer along with our well-equipped school, friendly staff and dedicated trainers you are sure to have an enjoyable, entertaining and educational experience on our course in San Diego.


What are privacy layers? Why do we need privacy layers? And how are we going to get a privacy layer that people need? So first, let me state the why for privacy layers. Obviously, the reason why we need privacy is because we don't have it right now. If you go to Easter scan, every single transaction is public. You're able to see the entire history of all the wallets. So the second reason why we need privacy is that if we want mainstream adoption of our blockchain technologies, we really need privacy. It's one of the main hurdles alongside scalability and identity in other issues. And finally, I'd like to just quickly address on privacy and regulation issues. And there's effectively a spectrum of solutions. We build privacy technology. We're on one side, you build fully self-sovereign solutions where only the individual control their information and assets. And the other side, you could give a lot of control to the entity actually controlling this ecosystem while preserving privacy between individuals. And so on the right side, you have something like CPTCs. The left side has something like generally cash, right? And perhaps actually in the middle, we'll have something that's more or less maybe accessible for both worlds where we could have a privacy preserving system, yet give some limited form of control to some set of authorities. OK, so enough on the why. Let's talk about what I mean by privacy layers. So just reiterate, everything on your theorems is public. So you're able to see everything on your first scan. And first, what I want to define is the notion called anonymity. So anonymity is the inability to tell who is doing a transaction, right?  And second is a notion of confidentiality.  And it turns out confidentiality is really, really hard on your theorem. It's pretty much impossible unless you want to redesign the entirety of your theorem. So on the other hand, anonymity is actually quite easy. We can use any mixer to mix the funds. And every single time we want to do an operation. However, this is very, very unusable. To the extent that only when you very much need this, would you do such a thing, right? Normal users would not do this for every single person that would do D5 protocols. So the goal is really to make this very usable, right? How do we get usable anonymity for Ethereum? So what do we mean by, again, should we reiterate?  So the question is, can we get something like this for Ethereum, right? And we don't want privacy anonymity just for payments. We want this type of anonymity for any type of smart contract call. So you can see, on Ethereum, you can do many, many different things. It's an ecosystem of DApps, not just payments, not just peer-to-peer swapping of assets, not just an MTs. It's whatever you can imagine on top of token standards, right? We want to have anonymity by default for all DApps. So that's the question. And that's also what I mean by privacy layer. A privacy layer for Ethereum should have the following set of features. But let us look at what are the current solutions for privacy layers. If you look at the entire ecosystem, we'll have many, many different EVM chains. That's, more or less, you could write a DApp in typical to any of them. And we'll have many, many applications, sometimes on one popular chain, sometimes on many chains. And what are the privacy solutions? Well, we'll have some mixtures. And we'll have some solutions that offer some type of DeFi compatibility. And we have solutions that more or less act as a layer too with privacy. So for instance, Aztec and Zika Alperu are great examples of this. And on the other hand, we also have all privacy all ones. And the examples are like, for example, Alio and Manta, where it's a separate chain. It might be a different ecosystem. And you have to bootstrap all of the quality. And so it turns out there's no single solution that works without all the DApps. So if you look at what these solutions do, so RealGuide and Zika Alperu actually do support some limits in the form of swaps. And project-wise, Aztec connects a while, actually pretty good, DeFi interoperability, but it's not completely compatible with every single DApp. So as they connect, you need to write this custom bridge contract. And in fact, that's basically, if you go to every single Aztec hackathon, that's what people do, that build bridge contract for every single DApp. And that's not scalable if you want this to support every single DeFi projects out there. So this is not preservation. We don't have a privacy solution that is default and really usable. So let's look at what I mean by privacy layer and what we should get in this privacy layer. So first of all, it should be feature-complete. So what I mean by that, you should have two features. You should be able to use this privacy layer exactly the same way you would use Ethereum. So you should be able to use a privacy-preserving solution any DApp that you want, ideally with basically the same interface.  And second, you should be able to disclose what you have done. So if you look at existing privacy solutions, it is actually really hard to tell someone else that you did something. The interface is not intuitive.  So we want some type of form of information disclosure. So if you own a set of NFTs and you want to prove to your friends that I own this set of NFTs and I authorize a message, you should be able to do that really, really easily. And the second thing you should do is be backwards compatible. Because we'll have all this amazing ecosystem out there, all these DApps that people use. We don't want to fill it out to waste and build something completely brand new. We want to use the existing ecosystem. So the ecosystem should support YR220, 721, 1155 standards. And we should more or less work with existing applications. And finally, most importantly, you should actually offer some form of privacy, which in this case, anonymity. So recall back to the previous slides, you will be the form, use this thing, and everybody will use this privacy layer. And you're going to easily scan. No one can figure out who did what action. So the question for my talk is, can we build such a thing? And actually the goal of my talk is to convince you that we could build such a privacy layer for Ethereum today. And we're building one. OK, so let's look at how we're going to do this. So let's look at this set of three things that we want for our privacy layer.  So if you're familiar with the abstraction, or any type of smart contract wallet, this is the two things that this should offer you. You should be able to use it on any single application, and it's backward compatible.   So let me just reintroduce the two concepts. So first of all, what is a shorted pool? A shorted pool allows you to unlink deposits and withdraws. So this is the most basic form of privacy solution that we've had since the Bitcoin days. So it allows you any user to deposit. And later on, you should be able to withdraw. But by the time that you withdraw, nobody else should know who's actually withdrawing. So you withdraw to a fresh UA address. So that's the notion of a shorted pool or mixer. And second, let's recall the notion of a shorted wallet. Let's recall the notion of a contract wallet. What is a contract wallet? Well, for a contract wallet, the users actually do not own an EOA anymore. So for instance, for account abstraction, you will have different address that we use. But basically, for your smart contract wallet, you should be able to do the exact same things that you would do with your metamask.  And this is done in the form of an intermediary smart contract wallet that verifies some signature and carry out the calls for you. So that's the notion of a contract wallet. And recall what we wanted to do before.  So here's what we're actually going to do. We're going to take the two and just put them together. So it's going to be a shorted contract wallet. So what can I do? You should be able to use anything that is on Ethereum. And every single time you use the wallets, nobody should actually know who's actually using the wallet. So there's one single shorted contract wallet that's shared by all the users in the ecosystem. OK, so that's on a very high level. But how does this actually work? So for shorted pools, like we said before, it supports deposits and withdrawals. And for contract wallets, you'll support arbitrary calls. And when put them together, you will support, again, deposits and withdrawals, but also crucially something that you can use to call the app. All right, so here's the picture. Here's how it's going to work. It's going to be a smart contract in Ethereum where it allows any user to enter this ecosystem. And once they enter, they're able to use it as if it's a metamask wallet. And when different users submit transactions, they will be reflected on chain.  And furthermore, on EtherScan, you have no idea of who's actually behind the scene doing this operation. And as a bonus, actually, we can make this smart contract wallet compatible with account abstraction, or EIP 4337. OK, so as it turns out, there's two problems if you want to build this. If you want to build this, just combine and show the pool with the smart contract wallets. The first problem is that when user submits a transaction that contains arbitrary calls, you can actually just steal the funds of the entire contract. So here, if the user only owns one Ethereum in the pool, but it constructs a call that consumes 20 Ethereum, this is we shouldn't let this happen, right? Because people would be able to steal the entirety of the funds of the entire protocol. So what's the solution? Well, the solution for this problem is that we actually just separate out the two contracts into a contract that actually holds the other funds, what we call a vault contract, and the wallet contract, which I will actually carry out the calls. So in this way, users will unwrap the tokens that they have, and only the token that they have is inside the wallets when they're asking for a call. This is actually kind of equivalent to the other way of doing it, which is you also have a router and have the wallet holding all the funds and putting the things into the router. So there's two equal solutions to solve the same problem. And the second problem that you feel to do this, which I think is the main reason why we don't have these things before, is that for this type of privacy preserving should it pools, you need to know the exact amount of tokens, that's encoded in the notes, before you insert it into the protocol. So everything has to be known in advance. Whereas in DeFi protocols, you have no idea how much tokens are getting back. There's this uncertainty of the smart contract decides how much you get back. But traditionally, for treated pools, everything has been known in advance. And so this is like one feature that we didn't really know how to do before. And there's a solution for this, which is that we have this notion of refunding to anonymous address. So we have to be able to re-redimize addresses and refund to them. I realized I actually basically sped through my entire deck and the end of the talk. So let's recap what have we learned in this talk. So first of all, privacy is really important. We do not have privacy on Ethereum. We need some type of privacy solution for Ethereum that's really usable before Ethereum can go mainstream. And a shielded contract wallet, combining a shielded pool and a contract wallet, is our bad shot at this backwards-compatible, future-complete privacy layer. And finally, we're building this out. We hope to put something on the public. And the hope is that long-term for this ecosystem, most people will actually be inside of a privacy layer instead of the standard EOA layer. And if you're interested in contributing to this effort, please come talk to me. And I realized I didn't do a self-introduction at the beginning. My name is Wade I, a research partner at ThinkApp or QuipTel. And come ask me if I have more questions about this project. But I'll take any questions from here. Thank you. Hi, congrats for the work. I think privacy is very important. I've worked for a few years on trying to make users have smart contract wallets by default. And the big problem is the gas cost of just having to onboard someone and already having to spend $10, $5, sometimes $100, how do you think that that can be solved? Yeah, very good question. I think two things. What is the actual cost of gas over time as we build the scalability layers should go down as we build more roll-ups? And the second is we could use batching to amortize the gas cost. So usually, actually, in 4.5 to 7, there's a notion of bundlers and aggregators where you compress the authentication information from multiple transactions into a single authorization for all the transactions. And there's different tricks to further optimize the gas cost. So over time, through these two avenues, the hope is that the additional cost incurred to get a contract wallet with privacy is not prohibitive for users, for a vast majority of users. Great talk. I'm interested to hear how you think about OFAC and tornado cash, because if this is like an opt-in. Where's the person coming from? Hi. Over here. Oh, yeah. Hi. No, how do you think about, because if you look at tornado cash and the OFAC sanctions, how do you think about avoiding that kind of thing with, because my understanding is that this would be like an opt-in smart contract wallet. So how can you avoid that and kind of a diverse election and these types of things? So referring back to my slides, where I showed the spectrum solutions, I think as a builder, we should be flexible in kind of, so what is privacy? Privacy is appropriate for all of the information. I don't think privacy is absolute notion where everything should be private to you. There's some societal consensus on what is appropriate for all of the information. And everybody can have their own interpretation of that. Government agencies can have their own interpretation. Individuals in the theorem community can have our interpretation. And they might be incompatible. But I think as builders, we should be open to different versions of what is appropriate for all of the information, because technology is really flexible. And over time, there will be communities that might be incompatible. But we should work towards a solution that's more towards the center, I would say, where we include as many users into our ecosystem as possible, yet give some sort of control, perhaps, maybe, to some set of people, to be able to prevent illicit activities. So when you say we're building this already, how far have you got? We have prototype contracts. It's a very early stage. Yeah, so the idea has been there for a while, but the building is just being abstraction. And we'll have basically two people full time on this. Why not embed these innovations into an existing contract while it's urgent or something? So well, there's many, many different contract wallets out there with different focus. This is a contract wallet with privacy. I think it doesn't make sense to, I mean, we could take the existing 437 standard reference code base and just fit this into there. The main difficulty is actually not being a contract wallet, it's really like how to add privacy, I think, because we need to also change the front end APIs. So every single smart contract wallet have to do this. But I think for privacy, it's more important, because a lot of semantics need to change.  That cannot be made privacy preserving, because you get who it is. So you have to change that into something like connect to wallets, can I get the USDC balance? So a lot of things need to change when something needs to be, you want to imagine a privacy preserving system. So we'll have to collaborate with contract wallet projects. And that's also another reason why we're trying to stay compatible with 437, because we can reuse, have the same bundler infrastructure and this account abstraction manpool. So we'll be part of that ecosystem and contribute to the efforts as well. Great, Doug, thanks. What kind of zero knowledge protocol you decided to use? Yeah, so as it turns out, the easiest way to prototype something like this is circle still. Like there's nothing better out there that you can rather zero on a shortcut and have like a solidifier and like a prover that's running on a browser. Circle is the only ecosystem. So this is like another rank. I would use the most efficient proof system out there. It's probably more like plunk, but that tooling's not there. And also over time, it sounds like you're familiar with the subsystems, but over time, there will be two separate proof systems. So one is on the user side, where you essentially want zero knowledge property only for privacy. So what is this thing? The overall design is very similar to any other sort of pool. You have a merkle tree of nodes. You're referring to a node and spinning it without revealing which node you are referring to. And for that, you need zero knowledge to preserve your privacy. And you actually don't really need a succinctness. And we're going to have this aggregation layer that roll out these user spending proofs. And for that, you really want succinctness. You want to be able to verify on the contracts that really efficiently. And so I think this is something that has been discussed a lot in DevCon in the past couple of days, which is you have the notion of inner proof and outer proof. So for us, this inner proof will basically be the user proof that has zero knowledge. I think over time, we'll probably evaluate things that's really fast in the browser as to your knowledge and maybe some type of compression. It's like maybe a smart center or something. And then on the outer proof, we'll have probably grossing or plonk that really compresses the other proofs. Yeah. So one approach to solving this problem would be to make backwards compatible contracts on Ethereum. Other approaches might be to wait until there's an L2 that has more primitives built in that support this. And I'm just curious to learn more about your thinking of if it ever makes sense that privacy will be in one place and non-private things can exist in another. I think, yeah. So the question is, do we build privacy solutions on top of existing things? Or do we build a new ecosystem to build privacy-preserving solutions? And I think the key question is, what are the privacy-supported? And what is the features of those applications? And so it turns out that the short answer is there's no privacy-preserving ecosystem right now out there that actually support more features than anonymity. So if you look at like Alio or like Mina, it's really just a solution to build roll-ups. With zero knowledge, you cannot get privacy for shared states. So I actually discussed this in another talk on mine. So if you think about the features we can support, I think unless you have vastly more capabilities to support privacy-preserving solutions, which I think it's actually privacy of shared states, it doesn't make sense to have a complete brand new ecosystem. Because the privacy that's achievable is the same. So there's no benefit to building a new ecosystem that do the same thing. So therefore, if that's the case, we should build on top of existing ecosystems because everyone is there with desperately new privacy solutions. And it's possible to build it. So let's not reinvent the wheel. Is it working? So it sounds like you need a sequence of maintaining the miracle tree. Have you got thoughts on how you're going to? Decentralize that, or whether you will? Yeah. So there's actually two different things. So for 4337, you have the notion of bundlers. And we could basically use that. So we could actually, so bundlers, so I think it's yet to be determined exactly what's in the standards. But it seems that for every single contract wallet, bundler needs to run custom code to be able to compress different user operations to one. So we could essentially stay compatible to those standards when it's more finalized to be able to have essentially to plug into that ecosystem. So there could be different 4337 bundlers that's supporting different smart contract wallets, and it will be one of them. And in that way, we can decentralize bundling. And the second is, yeah, so exactly, so there might be this management of miracle trees that's separate to compressing multiple user operation proofs into one. And we can make that permissionless if it thinks of current thinking. So what is the overall story? Because we support, we're backwards and portable, we support the exact same set of operations, users need to pay more gas. You're paying the same amount of gas by default. And the additional things, that's the overhead to maintain everything. And the idea is to make it as small as possible. And the only way to do that is to outsource this aggregated work into some sequencer or bundler. So it's basically necessary if you want to make this usually usable. And so, yeah, so to decentralize, I think, make it permissionless and really design incentives around this, right? That's because these bundlers, sequencers, are providing a service. We should incentivize behavior and make it permissionless and design kind of this ecosystem that's self-sustainable, right? Because I think that users will pay for privacy if it's cheap enough. And you can get its network effect, right? Thank you so much. Wei.


What's going on, everyone? Sam here with Lance Sportsguards. We've been 22, 23, Pineda Contenders, Optic Basketball Hobby, 10 bucks, case break. Number one, pick your team style. Release day, everybody. Alan J. Warriors, you've got Andrew P. Bucks, Anthony C. Magic, Bernardo H. with the Thunder, Bradley R. Pistons, Rockets, Kings, Chen M. with the Pacers, Christopher J. Hornets, Cavs, Nix, Chun Wei W. with the Mavs and Timberwolves, David S. Pelicans, H. Wang has the Bulls Clippers, Raptors, Wizards, Hero S. with the Sixers, Joel B. Nets, Kai C. with the Grizzlies, Mark M. Jazz, Oriole C. Nuggets and Hawks, Ramine R. with the Heat, Robert P. Blazers, Stefano B. Celtics Lakers, Steven C. with the Spurs, and Stephen F. with the Suns. So good luck, everybody. Now, let's pull some fire. Big rookies. Let's pull a couple of the 85 throwback autos, dude. Oh, those are so cool. Let's go, man. We got Palo on the cover. Palo on the cover here, everybody. Yes, sir, Mr. Palo. Get one Black Pandora per case two. Generally, those are pretty awesome. I don't believe they're not numbered in this, but they are case-considered case hits. Okay, on the back, playing in the numbers game of D'Angelo Russell and a blue ice to 75, Dice and Daniels. Base, you're gonna have LeBron, that is an Andrew Nemhard pink to 75, rookie for the Pacers. And then you've got an Anaphrenie Simons red. Again, the reds are not numbered. And nice, great way to start is gonna be a Keegan Murray, orange up and coming to 25. Congrats, Kings. Nice one there, Keegan Murray on the orange up and coming auto. Very nice. There we go, Sack Town. Starting us off pretty well. Yeah, my dad and I talk sports a lot. My dad's a big Yankee fan, so he's always tight about the Yankees. It's funny. Okay, we've got a first class ticket, AJ Griffin. Nice one there. On the short print. And a red ice of Optic Allusion of Steph Curry. That is a Deandre Aitin red Malachi Brannum and a silver Deontay Murray for the Hawks. And nice one here, going to the Jazz Oshai Bajie, number 299, congrats to Utah. Very nice. To the next one, guys, again, we are sold out on the next case. Still spots in the last four cases as well. An Optic Allusion at silver of Zach Levine. And a playing the numbers game, Brooke Lopez to 75. Nice one there. We've got a Desmond Bain orange Christian Brown Rookie to 49, that is a green to 25, green Pulsar of Jaden Hardy for the Mavs. And red auto for the box, Marjan Bochamp to 99. Grats on that, Milwaukee. Got playing the numbers game, Jason Tatum, 51 points. A sweet shot, Kyrie Irving. That's one you've never seen before. Right there, the sweet shot stick. Oh boy. That's red Marjan Bochamp, a silver Sohan Rookie and green Oshai Bajie to 75. Another on card, congrats Utah to Oshai Bajies. Very nice, very nice. Next box here. First class ticket, Jabari Smith Jr. That is gonna be Optic Allusion, Benedict Matheran, Siakam base, Silver Robert Williams, and blue Aaron Gordon to 99 for the Nuggets. Then we've got A to 75, Patrick Baldwin Jr., green Rookie ticket auto. Good to see he's live in this. There you go. Warriors, that's Golden State. I would say by far that was probably the creepiest scene from that movie. Uniformity, Kevin Durant as a son and playing the numbers game, Kyrie, 48 points. Kyrie is a net in this, yep, Kyrie is a net. McCall Bridges, red Hallow, nice one there on the short print, Silver is Oshai Bajie Rookie and 125, this is cool. It's gonna be the chief, Robert Parrish on the All Time Consenders. Nice one there, it's a 125. I believe that's part of the card. Those little dots I think are part of the card on there. Nice one there. I'll keep my eye out on any of these All Time Contenders. If it's not the case on the next one, then we'll give you an empty box and wrapper, but I'm assuming that looks like that is part of the design for sure. The number is like stamped over it, so. Threw me off for a second, but looks like it's part of it. Yeah, yeah. Again, I'll keep my eye out and we'll revert back to that break if that's not the case. Sweet shots, Nikolai Okic and Blue Ice, Optical Illusion at Tyrese Halbert in a 75. I appreciate that, Timmy, thank you, man. Thank you, thank you. Appreciate that. Tatum, Cade Cunningham on the Silver, second year and a red Keegan Murray Rookie. Nice one there. Jay, dust that little spot off right there for ya. That looks like it's just on the card. 299, Herbert Jones, Pranel Contenders, second year auto for the New Orleans Pelicans. Again, number three, you've got the Nets, Pelicans, Nix and Wizards, four to go. On number three, everybody, four to go. Four to go. That is the third of six cases. Think six teams is the most we have in any given case at this point. And then we're down to six and 11 on Mosaic's choice as well. Red Ice playing the numbers game, Ja. 49 points, Silver Luca playing the numbers game for the Grizz. Base, that is a blue of Bennett of Matheryn to 99 on the Rookie. Silver of Shea, Gilgis Alexander and base Rookie ticket auto at Jalen Williams. Nice J-dub. Going to the Thunder, congrats O.K.C. Very nice, very nice. Lottery ticket, Usman Jain and Optical Illusion of KD. That is a red of Anthony Simons and a Silver at triple J, your D-Poi. And then base Rookie ticket auto, Trevor Keels with the wheels. Going to the next, congrats New York. New York. New York's there as well. Yes, sir. Oh, come on, Cubs. I know, almost there. And the Reds are just out of it, though. We've got these just so close. Last box of the break. Good luck here, everybody. Let's do it. Let's see what we got. We'll do a quick recap after as well. Redemption, we've got Suhechaha, it's KD. And Blue Ice, first class ticket, Jalen Durin. Two, not interesting. Maybe it's, I don't know. I'd assume that'd be numbered, but I guess not. Josh Giddy. Blue is Terry Rozier to 99. And Silver of Julius Randall. Redemption is Jabari Smith Jr. Rookie season ticket orange. Going to the Rockets, congrats on that. Very nice. Let's see, Rookie season ticket. See what the orange is numbered to. I think I feel like they're 25. Bari Smith. Yeah, orange to 25, that's solid. We'll get that into a mag for you, congrats Rockets. Great last card of the break. Do a quick recap. Start with your color here. Your blues to 99 are gonna be Terry Rozier, Benedict Matherin, Tyrese Halliburton, Aaron Gordon, Ruth Lopez, Dyson Daniels. Pink to 75, Andrew Nemhardt. Orange to 49 is Christian Brown. Green Pulsar to 25, Jaden Hardy-Rookie. Your autos now, you add Trevor Keels, Jalen Williams. Red autos to 99 of Marijanbo-Champ. Oshai Gbaji, Robert Parrish, you had Herbert Jones. Greens to 75 of Patrick Baldwin. And Oshai Gbaji up and coming is Keegan Murray to 25. And that'll be on card of Jabari Smith Jr. I'm doing a good break, guys. Thanks again for the film. Up next, number two.