Hey everybody, we're here, we're excited. As you can see there's me, even the foreign staff, we have Azure joining us. And then down with more is Julie from the team. We're excited to do this new series with you guys. It's sort of a revamp. If you remember last year, we did a few future Fridays. We're just kind of showing off some things you may have missed. Fridays are already busy with videos on WikiTrees, so we decided to do it on Monday, so we needed a new name. So we went with WikiTree Tours because we're showing off stuff on WikiTree. So we're excited to be here today. We're gonna take a little trek through the trees, show you guys some new changes that have been made and just some of the fun stuff that you can be using. Azure, Liza said you look far away. Sorry. She's there. I see her. I'm here, I'm here. Oh, Stanley likes my tie-dye shirt. Thank you. I love tie-dye. So yeah, we'll just jump in it. Azure's gonna be our primary tour guide today. All right. So what we're gonna do first is I've disabled the beta test version of adding profiles so that we'll walk through the old version of adding profiles or the current version of adding profiles, sorry. So I'm just gonna go ahead and click to add it. Person, whoops. Once my design back in again, sorry about that, folks. Ever two weeks. Frederick Wayne, is this a close family member, Azure? No, just a couple of weeks ago. No, just one of the return New Mexico one place study profiles. So I'm just gonna go through and I've already got saved source information here. This is what everybody's used to. One page and then turn the information. So we'll go ahead and add. The child or Orville. So there we go. So nothing really different about that.  We'll go over to Orville's brother, Erlin. And oh, sorry. First I need to change my settings. Scroll the way down to your settings at the bottom of the page here. And this is where you'll turn on beta test for creating profiles of a new way. And then click save settings. And then we'll just go back to Garland's page here and add a child to him. All right. So right away you're gonna get the option to create a new profile or connect to an existing profile. And we're creating a new profile today and Valley Pauline Arnold is our person. Cool. And now the birth date. Already we noticed that her middle name is at the top now instead of down at the bottom. Yeah. And it prefilled with the last name at birth from when you click the link to add a child. Right. So- All the data elements right at the front. And then when you click continue, it's going to ask is this the child of his wife? Yes she is. And it actually went through and passed one of the steps. You'll see here at the top the breadcrumbs after you entered the basic data it checked the system to see if there were any matches for that person. So were you- If there were then they would have showed up in a list. Yeah. If there had been- And the list is formatted a little differently. I hope we can show that at some point here, Azure, I don't know what you- Sure. We can do that next. So I'm just gonna, there's two options for entering. You can have what it used to be like with just a box for the source or you can use the advanced option going right to the wiki markup to do the text there, text editing. And I've got this all ready to go here. I'm gonna create this new profile. And when you click to create a new profile it dumps you right into after it's created it dumps you still back into the edit page. So you can make any necessary edits after it's created. So let me grab a, actually, let's see. Well, you're doing not, we'll have Julie answer this question. Okay. Is there a way to create a recently- Oh, are you gonna read it? Go ahead. Go ahead. Oh, please. Is there a way to create a recently created profiles list only for me? Which app, et cetera, can I use? I need this rather than going back through my contributions to pick them out. So there's a couple of ways that you can do that. You can go to your watch list and sort by the last edit date. And that would bring those new profiles up to the top of your list there. You can also go to, make sure I get the name right. The special trusted list changes, I believe. I'm over there now. And if you click on the remove yourself from trusted lists, I'm assuming that's what you wanna do. There will be an option at the top. I'm waiting for mine to load. Hang on a second. There's a big button that says show only recent additions. And if you click that, it will narrow your watch list down to those. And I don't know what the timeframe is. Do you, Aowyn? For that button? It'll narrow it down to the most recent batch, but I don't know how far back it goes. It's probably a week or a month or something like that. It's probably a week. Yeah, that makes sense. But you can just type in special colon trusted list changes or let's see, if you go to your watch list, there's a link at the top that says watch list changes. And that will take you to that page where you can remove yourself from trusted lists and have the big button. So I hope that's helpful. Yep. She said the watch list. And then I noticed that, what's that? She said the watch list is a great idea. Thank you, because she's trying to make corrections. Not necessarily. Oh yeah, I do that all the time. And then GSL had a comment earlier about the middle name field. He or she is probably in a country where they don't have middle names where they combine them all as fore names. And if you go to your, my wiki tree settings and scroll down to the bottom where Azure turned on the beta testing, there's also an option there to ignore the middle name warning. And so then you can put both fore names in the same field and it won't keep bothering you about that. Yeah, that's right here. Yeah. So I'm just gonna go through, I won't click through to actually create the duplicate. I'm just gonna walk through and act like I'm gonna create value again so you all can see what it looks like when there is a duplicate in the system. Or that you're trying to add somebody that already exists, what it looks like. Okay, it's not showing her. I think it takes a bit for the system to recognize. It may even, I think it's faster than overnight now but I think it still takes a little bit to process. Yeah, I think it takes probably half an hour or something like that. So here you can see what that looks like. Other matches? Yeah, other matches. So this person's like got a private profile so you can do a trust-and-list request or you can set as child or set as ridiculous match. So that's what that review matches page looks like. And then we were going to share. See here. The public view link. So on, let me get to it's Garland's profile here. So there's no longer the public view tab. There is now this link off to the side public view. So it's gonna do the same thing that the tab did. It's going to show you whatever elements that are available for that privacy setting that they're set to. Anybody have any questions about that? Public link or the view link? And then go ahead and just show how you can get back to the... Sure, you just click right back on this link at the top there, takes you right back to it. So just back and forth. Cool. All right, so now I just want to share about the problems and questions button that's right here in the profile manager section of the profile there. And this is gonna open up a little popup. Everything's right there for any kind of problems or questions you might need to... Or that you have for this profile. And right here go in and ask a question about this profile in D2G, ask a tech question. It's really, I think it's a great new feature. It's a nice directory. Yep. Yeah. What do you guys think about that? Has anybody taken a look at that yet? I'm curious to know if others have noticed it yet. I wasn't talking to you too, by the way I was talking to those people over there. That's why we didn't answer you. We just did it awkwardly in silence. Do you have to have the other Wikitree add-ons for Chrome? Or for the beta? Not for the problems and questions. These are all these, this is just a base feature. If you want to do the Wikitree extension, browser extension, there are other features that become available if you enable that. But you don't need it for these things that we've just covered. We'll feature the Wikitree browser extension in another one of these Wikitree tours coming soon. That's, there's so much to cover there. Oh, and they're adding to all the time. Yeah. Okay, so we were gonna share next about the Ancestors button. So right here, where it has the parents listed, there's a button for showing ancestors. And what it does is it just kind of pops open a little section at the top of the profile for you to see the ancestors for this person. Okay. That used to be under the Family Tree and Tools tab, but now it's just a button that you can easily click from the profile page. And then for the Descendants button, here's what that looks like. So from the same page profile in where it says that she's a mother, then you can click the Descendants button and it'll list the descendants there. And it's one thing to note, I had somebody ask me about that the other day. If there is only one generation connected in either direction, you won't see those buttons. So for example, if you have a profile that has parents connected, but they don't have grandparents connected, you won't see the Ancestors button because there's really nothing more to show other than what's already there on that page. And same thing goes for Descendants. If your kids do not have kids or the profiles children don't have children, you won't see the Descendants button. Yeah. So talking about that, the change, this is now just says Tree Apps instead of Family Tree and Tools. It now just says Tree Apps. And when you go there, when you first click on that, let me, got to log out of this. So let me do that real quick. So when you first go there, you're gonna need to log in to be able to use the features to view the different options. And it's just here with Tree Login again. Yeah. And you don't have to do that every time, right, Azure? Right, once you've logged in and you've kept, if you keep your browser, browser windows open, then you don't need to keep logging in. It's just that one time that you get logged in. So here's a... Or clear your cookies or something. Right, yeah. So here's a view of the Anantaffle. Is that how you pronounce that? Anantaffle, yeah. Tree App. So it's, I think pretty much exactly what we had before. It's just that you get to it a little bit differently. So that's what that looks like. Yeah, I don't think anything really changed with that one except the location. Yeah. So in the dropdown, then you can, these are all the options of just the different ways you can view the Tree Apps. So the next one we're gonna share is the Ancestor Webs. There we go. There we go. So I have it set so that it'll show where there is so that it's on repeat. And that's where it's showing where there's a, somebody has, you know, ancestors have the same ancestors. What's that called? Pedigree Collapse. Pedigree Collapse, sorry. Had a little pause there in my brain. So that's an option on the page. And the next one that I really love is this couple's dynamic tree. Yeah, this one is really cool. So I have up here, so you can see this person is the center person. And you can see the children and the ancestors.  If there are multiple spouses, this is where you select a different spouse next to that person's name. So if I wanna see, oh, sorry, if I wanna see the spouse that is through my line, I just select that there and it changes the spouse to be that other person. This was George F. Anderson.  And then it has an option down here of a drill down for the children so that you could change who your center person is from here by selecting that little icon of the tree. And because these children had children, you have a plus sign going down the descendants. So this is a really great full-featured option of viewing your tree. One of the things I liked because we're all talking about CC7 numbers and growing all that and I think this is another way where you can kind of see gaps that can be filled. Like with the question mark one over there on the left, that would be a hint of a place you can get a connection. Yeah, yeah. It's a wonderful app. I love it.  They've beefed it up quite a bit to make it much more useful. And I believe when you sign in for the first time the default is that couple's dynamic tree. Nice. Okay, so this is the family group view. It's kind of just a summary of this couple and the children that they had. And it will have a different section for each of the spouses and then list out the children information down below. And if you click the little icon here to the right of the person listed, it will change it so that this page now is for that person. So if I click on that, it's gonna be a family group view for this person. All right. I've always liked using this view to, because usually, yeah, it has their marriage date up there. If you have a person who's married several different times, it's a great way to like look and make sure the kids are connected to the right parents. Yeah. Definitely. Okay, and then this is a cool feature I love, the family timeline. So this is for Lucy Amanda Jones. And so if you scroll down here, it shows her parents kind of as the starting point, their births and then all her siblings. And then I'll start listing out the spouses, their births, when they were born on the timeline and then her children. So it's really a neat feature. We're out. View it, view it. Okay. This is a fun one. Great, Clark. He's so clever. Okay, so we're just gonna play a game. If nobody has any questions about any of the other ones, if we have any questions about any of the other views, throw them in the chat and we'll get them answered. Well, we're keeping watch as best we can. All of this stuff's so fun, I'm not paying great attention to the comments. I know, I'm like, this is so good. Okay, so here it is. I will. Let's see how, let's see if I can do this here.  Oh, customer skills. Okay, I know. Let's see. Let's all memorize Azure's ancestors.  Exactly. Nope, that was wrong. Oh no. We need some jeopardy music or something behind us. Oh no, I don't think we have. Or a clock ticking. We've got a timer. Oh no, not a timer. Oh no, not a timer. Oh no, not a timer. Stress. Oh, thank you, Eoin. She played a lap track for you, Azure. Okay, we'll do acoustic cinematic. Oh, that's very calming. Counteract the timer mindset. Yay, she did it. Good job. It is a fun way to get to know your ancestors. Yeah. Or anyone's ancestors, you could put in William Shakespeare and learn four generations of William Shakespeare's ancestors. I love that you can put it in there and start from there. Yeah, it's fun. It is fun. She's a president. Play around with the president and see if you can remember everything. So there are lessons. How are you doing over in the chat? Good. Jelena's making lunch. No questions. Yeah, she's making us hungry. Oh my goodness. Rice cakes and spice kippies. Don't you think about it? That sounds good. Oh, country vegetables. When you're six. Which also sounds good. Yes, I know. Oh, Margaret. Yep. The family group sheet has always been one of her favorite sounds like. I use that one a lot too. It's very useful. And hello, Margaret Summit. Good to see you. Good to see you're typing. She said, good to see your faces. I wish we could have all of you in here and converse, but that wouldn't work out very well. Oh, the biofaker isn't still there. I think that's, I think you have to turn on the extension. The extension for that. It's my job today to just remind you what the words are. Apparently. I'm usually the one going, oh, what was that? David wants to know if the charts are printable. That's the wrong one. So, you guys are talking really fast. I think, doesn't, I think he was saying on Saturday that he has not made this one printable yet, right? Yeah, the fan chart isn't, but you can go to the printer friendly view of somebody's family tree. Somebody's family tree. Yeah, and that's ready to go. Doug is asking if anyone uses wiki tree X and this would be a good time to say that wiki tree X is not really being supported anymore. I think it still works for some websites, but it's a little bit touchy. I had to stop using it because I was using it on family search and it doesn't really work very well there anymore, but that's not, it's not being supported anymore. Our developer that created that didn't have time for it anymore, apparently. Is there a way, I use Sorcerer, but I don't do this with it. You can import information with Sorcerer. Is that right? Yes. Or is there one of that, one of the apps that allows you to do that? Yeah, let me do that real quick for you. Let's not get too far off our topics for the day, though. Sorry. It's exciting, I know and we wanna talk about everything, but like for the sake of a little bit. Cover that at some point. Yeah, just to the new level, though. I don't know what I would do without the Sorcerer app. Man, I love it. That's a great app. Not use it all the time. I have to turn mine back on. I have sugar and pains. I disabled it all, so I have to turn it back on now. Or re-add it because I took it off. So when I went through this walkthrough with y'all, I didn't show that all there. I wanted to show you the basic part of it. But yeah. We have some very clever members that have been creating all these fantastic apps for us. My gosh, they're amazing. Yeah, so just really briefly, once you have Sorcerer enabled, you can go to it up here and then just click save person data. And then if you go to add a new person, you just say set fields from person data. And it sets it all up for you. That's my new thing for today. I haven't used that before. Yeah. And then also when you go into the fields where it tells you where you wanna add this information. Oh, it didn't work that time for some reason. Might just be because I need to refresh, but it will load up a narrative. Oh, okay, cool. I'll play with that. Based on the parents that are attached to them in this profile. Mm-hmm. Cool. Yeah. So that's all we had for today for sharing because anybody have any other questions? Do you two like the beta version of adding profiles better? Or do you like the beta one? Yep. You know what? I very much, yeah. But once I just gave it some time to work through adding some profiles. Yeah, I really love it now. I love having the different screens that it goes through. And if you have that, when you browse and enable another feature that's great, is it on that page where it shows you possible matches, you can filter out for location, which is wonderful. Oh, yeah, I'd forgotten about that, yeah. Jelaine is asking when the beta will go live for real, and I don't think we have a date yet. We don't, we're still too late to be back. We're still too late to be back for members, and then our tech peeps are still tweaking and so we don't have a specific. But anybody, it's available to everybody by just turning that beta switch on in your settings page right here. So here's a question for the chat people. Next month, I think we had talked about doing challenges for the WikiTree tours, like going through the different challenges and how you can participate, which we can still do. But it seems like maybe there would be a little more interest if we did like the WikiTree browser extension and maybe some of the apps. So you can tell us in the chat if you have a preference and we'll consider that when we're planning the stuff out. We're flexible. We're here for you guys, really. So we wanna talk about what you wanna hear about. Yeah, that's what's all about. So Jelaine says extension and apps. We can rearrange that, not a problem. Shall we give them a preview of some of the topics we've got on the agenda? Can you share it with us? Yeah, so next month we were talking about challenges, but it looks like that might change. Yeah, do you remember some of the other stuff? Because I don't have that pulled up. I've got it. We were gonna talk about the CC7, the connection finder and my connections. And of course the browser extension, which sounds like we might move that up. We're gonna talk about G2G and the different features in there and using tags and et cetera. Merging categories, stickers and templates, an overview of the different apps and we'll take a deeper dive into some of the more complicated apps like BioCheck and Sourcer. We're gonna talk about projects too and how to create one and what they're for. And Wikimarkup. We had talked about doing Wikimarkup at some point, but that's not a, that you have to be on a side because it's not gonna take that long to go over that. I do that too. Good to go. Good to go. Well, I think extensions and apps win for March. It looks like overview of projects is one. G2G, a couple of people. D says she's too shy and going to ask in G2G. We'll help you get over that. It's one of the best tools Wikitree has really. Yeah. Easy. Yeah, we can talk about Discord at some point. Oh yeah, good idea, Bill. That was just something we threw in a few years ago, but it's actually turned out to be quite helpful for a lot of things. I'll add that to our list. And you can always go to this space page, Wikitree Tours, that's linked in the G2G post for this broadcast and make a comment. If there's something you would like to see, there's a big comment on the space page. David said if you'd love to hear more about categories and stickers, he finds them confusing and unsure how to get the most value out of them. I hear ya. Yep. And there's a lot of different stickers for different things. Like I know, I don't even know how the stickers we have. Yeah. There's, yeah, I always go to the category, the stickers category, to look for what I'm trying to find. This is exactly what I have. Do I have it actually a link on my navigational page for stickers? Right here. Oh, good idea. Yeah. This is because it's like, yeah. I wanted to mention to... Oh, sorry, go ahead. No, go ahead. I was just saying I wanted to mention to Doug, he was talking about Wikitree X. And I think, Doug, what you'll find is a lot of the features that were there are now in this source or browser extension. So that would be pretty equivalent to what you were using before. It probably works a little more solidly now. Jolene asked, what's the status of the academy? If you don't know yet, we're starting something called the Wikitree Academy. And it's this cool thing we're developing where basically you can go and take courses and learn about Wikitree. It's brand new. I don't have a lot of courses yet. There's one there that's geared towards new members, but anybody can go and try it out and take it. I think there's one there now for projects about the project. And basically it's there. We just are looking for people to help develop the courses and the more people come and help develop courses, the more courses will help. So I know there's people interested in creating them for a lot of different topics. So hopefully before too long, we'll have a nice little academy. There's a space page for the Sorcerer if you want to check that out, Doug. I think it's just, it's Space Wikitree Sorcerer, isn't it? Yep, that's a great extension. I've become dependent on it. All right, and you had, how? Deal, it was just commenting about the watch list. But Julie was talking about the watch list for the basketball, she appreciated that. Dogs, oh, Julie's dogs are barking. Her husband just came home, I think. Just to share a little bit of her life with you. It's all about the dogs here, yeah. Tyrenda mentioned that G2G is frustrating when she doesn't get an answer. And I think one of the things that people forget to do out there, and this isn't the problem, let me know. You have to make sure you get the right tags on your post, because then that alerts people from the different projects that can help you. So if you're not tagging your posts, sometimes people just won't see them. And yeah, that is why Discord is nice because it is an option because it's kind of like a live chat. But it is nice also, G2G's good for maybe covering more official things so that everybody in the community has access to that, because not everybody's on Discord. So it's something to think about. Right. When you're asking a question. And D asked if there's a solid list of post tags, and we'll get deeper into this, only covered G2G as a topic. But yes, if you look at the top of any G2G page, let me go look at one now so I don't tell you the wrong thing. There should be a tab there for tags. And that will give you the most used tags. So like the top number one tag is wonderful wiki tree ears. I love that, that's awesome. I know. I always use when I'm looking for a particular tag, I'll use control F on this page on my keyboard to type in, to search the page for whatever tag I'm looking for. Unfortunately, and we've asked about this before, we can't get the G2G is a separate piece of software from wiki tree. So it's almost like a third party. It's not almost like it is the third party software. And so we can't really modify it very well. So we can't get an alphabetical list of the tags, unfortunately. That's something I've always wanted into this. We do have a space page that lists a lot of the tags, but I don't know if it's still up to date. I'll have to see if I can find it. And that's a lot of readers project but kind of looks after that, right? Yeah. Yeah. Yeah, there are a couple of them that we'll go through and kind of retag if they see a tag that could be added or something's missing or some people are really creative with their tags. Sometimes we just try to fix those so that, like we were saying for a trend of, you know, having the right tags helps people see. Yeah. Yeah. If you start typing a tag, like for a project or something, you'll get, it should show a little prompt at the bottom to give you some ideas of what will work. Yeah. Am I right about that? I don't do that very often. Yeah, I'll give you suggestions. Yeah, as soon as you type in the question, it'll, it pops up some. Pops up with the options. Yeah. And I'm just sharing the, Oh, sorry. Go ahead and answer. Who does the answering turret does a question about where do you get discord? So there's a help page for discord. So it's just help, pull in discord. And that, and it tells you how to, how to go about getting that set up. And Steven Tamazowicz was asking about a zoom port. And no, we don't have a, we don't have a live zoom going most of the time. I will say after, maybe after wiki tree day, there were some people who asked if we could have something like that, maybe like once a month on a Saturday or something and just have a zoom be open, which we talked about at the time and then it just got lost in the shuffle. So if that's something that people are interested in, we can certainly, certainly do that. I think it would be cool. Yeah, you do. Nice to see people's faces and chat and especially when you're trying to collaborate, it helps when you know the other person is a person. Definitely. So we'll, we'll, we'll be back with another wiki tree tours on, I think it would be March 20th. Time flies. After Roots Tech. Yes. Gotta make it through Roots Tech. Here, I have to put a plug in for Friday, date night zoom. It's not a secret. Every other Friday, we have Friday, date night. That's my little baby. I love that. I love the people that come join and help us date profile. So look for that in G2G2. It'll pop up every other week. And that's this. And, and I think so. Yes. It is. Thank you for reminding me. Despite it. I have it on my calendar. I just haven't got the stats updated or anything. Roots Tech is on Margaret's birthday. Oh, happy birthday Margaret. All right. Well, I think we'll wrap it up for today. But we will be back in a month. And there's plenty of other stuff happening between now and then you can check G2G. There's the what's happening in February post. There's what's happening in March post. So you can get links to things there and just make sure you're not missing all of the fun and exciting and educational, entertaining stuff that we're doing. Yep. So much. Great to see you all coming. Yes, thank you. I'm glad everybody popped in. Tell it, tell your friends to come next month. Tell your friends and like the video, please. Please. Thank you. Bye everybody. Yes, please. It helps us. Bye.


Good morning. Welcome to the first session for today. Sorry for the day we are writing for the video to be working properly. So this session is about months of operations and we will have four talks and the first talk is Assignment scheme with authenticated encryption by Suyash Kandere and Suyash Kandere and the talk is given by Suyash. Thank you for the introduction. Good morning everyone. Today I'm going to present key assignment scheme with authenticated encryption. This is a joint work with Dr. Solajitipal at Indian Institute of Technology, LAI. In this presentation, first I will go over the introduction followed by the motivation and then define the problem statement. Then for the solutions, we will just persecute the definition of CASAE followed by the constructions and then comparison and then I'll conclude. So suppose there is a structure, a heretical access structure as shown in the slide here where the director is at the top and she has some information say a yellow file. She wants to impart a part of this file to the dean FA and he gets a file say a green file. Now the dean FA further gives a part of his own file to a faculty which we call as a blue file and now the faculty gives a part of his blue file to a student which we call as a red file. So these files can actually represent it in this format where a big file belongs to the director, the yellow file containing all the four parts red, blue, green and yellow and the student contains only the red part defines the heretical access structure for the beta. Heretical access control means providing and restricting access to unauthorized ones. It requires a method to generate and retrieve the keys for accessible parts of the file. It finds its deployment in the business and other areas in the private sector and the solution is key assignment scheme CASAE. The key assignment scheme is basically a key generation scheme where the key required for encryption and decryption of a file can be obtained by an authorized user only. It achieves access control privacy and it finds its application in the access control in the hierarchically structured organization. There has been a huge work done in last three and a half decades in defining new and efficient methods of CASAE schemes. The motivation for our work is the fact that authentication and authentication of data are not integral part and therefore forgery is possible. So now we need to combine CAS with authenticated encryption and the question is is CASAE really required as a new primitive or the combination of CAS and AE is sufficient. So first let's see a construction which is a simple combination and a very natural construction for CASAE. Here we are using the CAS scheme which is psi and has two algorithms key generation and key derivation and the AE scheme omega which has three algorithms the key generation encryption and decryption. The CASAE scheme which here has three algorithms will be explained very quickly in the definitions part but let's design the natural construction for CASAE here. So in the encryption algorithm first of all we use the CAS scheme to generate all the keys the secret values and the public values and using each key for every file for every user we encrypt the files to generate the ciphertext and tag. These ciphertext and tag are then stored in the public values which we can assume to be cloud. The key derived algorithm is just invocation of the key derived algorithm for the CASAE scheme and the decryption algorithm is the invocation of key derived algorithm followed by the decryption of AE algorithm. This is the natural construction construction alpha but we have found that there is an attack on construction alpha.  So what he can do is he can compute the values KV using the DER algorithm of CASAE scheme. Then he can generate a new file F prime V which is different from FV and then he can encrypt F prime V to generate C prime V and T prime V. Now he can just replace CV and TV with C prime V and T prime V on the cloud and any user who tries to decrypt the file corresponding to user V will now get the file F prime V instead of the file FV. Because of this attack it's not trivial to construct a CASAE scheme. Now moving on to a secure construction which is construction beta. Here we have made one changes. The changes we have included the tag with the secret information of every user and therefore the attack that was possible in construction alpha here is not possible anymore in construction beta. But the problem here is it is highly memory inefficient. I'm sorry. It's highly memory inefficient because every user has to store a large number of tags. So we have seen that the trivial combination of CAS and AE is insecure and the secure combination is memory inefficient. That's why our question is can we construct a secure CASAE scheme that solves hierarchical access control problem more efficiently than a simple combination of CAS and AE executed in that order. Beginning with the CASAE definition key assignment scheme with authenticated encryption is a key generation scheme where the key required for encryption and decryption of a file can be obtained by only an authorized user and the message encryption and authentication is an integral part of the primitive itself. It achieves access control along with privacy, integrity and authenticity. The three functionalities included in CASAE are first day encryption which is responsible for generation of keys and secret information for each user, encryption of files for each user, generating the public values for the system and distribution of keys and secret information to each user. The second functionality is key derivation DER which is re-computation of decryption key of an inferior node or the subordinate node by a superior node. The third functionality is a decryption algorithm where the decryption and verification of ciphertext corresponding to the same node or the subordinate node takes place. Here is the formal definition of CASAE which is given in even more details in the paper. You can find the encryption algorithm here that takes the graph of hierarchical access structure and all the files as the input and generates the secret values, keys and the public values. The second is key derived function which takes the graph, the superior node, the subordinate node, the secret values of the superior node and the public values to generate the key corresponding to the subordinate node. And similar is the decryption algorithm which aims to generate the file for the subordinate node. The correctness requires that the derived algorithm derives the exact same key which was derived during the encryption process and the decryption requires that the file should be the same as the one encrypted here. Here we are considering three security issues, the key recovery, privacy and tag consistency which have been realized using KR, INDPRV and INTP security games. Now we move on to the CASAE constructions. The first method is to construct CASAE is from CAS chain. So CASAE chain is a special type of CASAE where the access graph is a totally ordered set. There is no hierarchical structure which is having multiple where a node has a multiple subordinate nodes. Every superior node has just one subordinate node. And the second ingredient used here is modified chain partition algorithm. This is a divide and conquer algorithm where first we partition the entire access graph into disjoint chains and then we designed CASAE chain corresponding to each of these chain. Now finally we securely join each of these CASAE chains to form the CASAE for the full access graph. In the paper we have proposed four constructions namely A, B, C and D which have the modified chain partition algorithm in common and they differ just in the CASAE chain schemes. The first CASAE chain scheme that we have described is A chain which is similar to our construction beta where we use the CAS chain scheme psi and the A algorithm omega. And we store the tags as the secret values for every user. The second construction is B chain which is inspired from Emily and we use Emily as a black box here. So in the totally ordered set as shown here the encryption process is described here where first we encrypt the file for the user U3 which is at the bottom of this access graph then for user U2 and for user U1. And whenever we encrypt the file for user we include the key into the file itself before encryption. So while we are deriving the key or when we are decrypting or when we are decrypting on decryption of each ciphertext we actually get the key for the subordinate node. Our third CASAE chain construction is based on the functionalities F1 and F2 which are themselves inspired from APE authenticated encryption given by Entreeva et al in FSE 2014. Let me give the disclaimer that the functionalities F1 and F2 are not exactly identical to the encryption and decryption of APE. They are a modification of encryption and decryption function. Now one more thing to notice is the functionality F1 takes as input message M and two initial vectors IV1 and IV2 and outputs the ciphertext and the key. Whereas the functionality F2 takes as input ciphertext C and the key K and outputs the message M and IV2. Because of this property of outputting IV2 we employ the key of the subordinate node as the value of IV2 which is shown here in the encryption, derivation and decryption diagrams. For the first user we use both of the values of IV as zeros. For the second we use IV1 as the ciphertext and IV2 as the key and we go on. While decryption we get the keys K2 from ciphertext C1, K3 from ciphertext C2 and so on. Our fourth caste-AE chain construction is based on FP hash mode of operation which was given by Paul, Homsrikumal and Kedge in IndoCrypt 2012. These designs are also not exactly identical to the FP hash mode of operation. Instead they are a modification to them. Here also for the encryption we have message and IV1 and IV2 as the inputs and the output is K and C. But for decryption the input is C, K and IV1 and the output is IV2 and message M. Therefore there is a slight change when in the encryption, key derivation and decryption procedure but the efficiency results are exactly same. Now we go for the second method where we construct caste-AE schemes from the scratch. And we propose three constructions, construction one based on MLE, construction two based on APE and third construction based on FP hash mode of operation. Our first construction which is based on MLE uses the idea that encrypting the decryption keys of immediate children, all the immediate children of the node along with the files of the node. Which offers us the advantage of decryption keys for the immediate children nodes are obtained on decryption and MLE itself takes care of the authentication and encryption together via the decryption key. So we do not need to store the tags here. Here is the encryption algorithm for this reference graph where U4, U5, U6 and U7 are the nodes at the bottom. So first we encrypt them, second using the keys that are output from U4 to U7, we prepend them over the files of U2 and U3 and then encrypt them. Finally we encrypt U1 to get the key K1 which is the master key or the key for the root node which is the superior node of the entire graph. The key derivation works as follows. If user U1 wants to find the key for U6, they get it from K3 and then K3 decrypts C3 to get K6. For decryption algorithm, the K6 here is plugged into C6 and then we obtain the file F6. Our construction tool is based on APE authenticated encryption where the idea is reverse decryption property of APE which gives the keys of immediate children nodes while decryption. And during the encryption, we take the immediate children nodes and encrypt it along with the file. This offers us the advantage of allowing efficiency improvements and the decryption keys for the immediate children nodes are obtained on decryption. We do not need to store any tags for the file. Here are the functionalities F1 and F2 that we have already seen in the C-chain construction and this is the same method of encrypting it. Here for the U4, as IV1 and IV2 we are using zeros and for all the children which are at the leaf node. And for the intermediate nodes and the root node, we have the keys of their first children as this first value. This is the encryption, key derivation and decryption module. Now the next construction is construction 3 which is based on FP hash mode of operation where the idea is exactly the same. And it offers us the similar advantages. The functionality in G1 and G2 which are being used in the encryption and G2 being used in the key derivation and the decryption algorithm. Now I would like to show you the comparison table where the first five schemes are actually construction beta. And in this construction beta, we have plugged the CAS schemes which are T-CAS, TKE-CAS, DKE-CAS, IKE-CAS and NB-CAS which are given in details by Crompton, Martin and Wilde in 2006. And we obtain the results here. So we see that for these five schemes, we have N squared lambda times the private storage which we saw in the construction beta that it has a big disadvantage of having a huge private memory requirement. Our construction A which is also based on CAS and AE offers the same disadvantage of having a huge private storage requirement. The construction B which was made using construction B chain and modified chain partition using MLE, this has NW lambda where W is the width of the access graph. And this access graph represents the poset which describes the hierarchical structure of the organization. Our construction B, C and D offer the same private storage requirement of NW lambda and the public storage requirement with a ciphertext expansion of 2N lambda, N lambda and N lambda respectively. Our most efficient constructions are construction 1, 2 and 3 which we just need to store lambda bit values per user. Here N actually represents the number of users in the organization and therefore it is just lambda bits per user. The ciphertext is a little larger but that really doesn't matter because we are storing everything on the public data. And the most important part is storage of private keys which we excel here. In the conclusion I would like to say that construction 2 and 3 have a super advantage of having a reverse decryption and depending keys of subordinate nodes to the file of superior nodes. They are based on easy to invert permutation which offer the advantage of being easy to realize in hardware and have negligible private storage overhead. They are randomized and therefore they avoid all the dictionary attacks. They have one pass encryption, key derivation and decryption mechanism. We leave it as open problems to have more efficient CAS AE constructions and to introduce the functionalities like key revocation, updating the file itself etc in CAS AE. Here are the references of our papers. Thank you. We have time for a couple of questions. I have one question about your construction based on message locked encryption. For message locked encryption you cannot have privacy. You need high entropy messages to have privacy. So does it apply to the resulting construction? Actually what we do is we add a random number to the file and that's why this random number ensures that the total entropy of the message becomes high. And this way we are preventing the attacks for the known message attacks on the MLE. Okay, thanks. Thank you. Other questions? Well if not let's thank Suyash again.


Hello, everyone, and welcome to the Circuit Python Weekly Meeting for June 21st, 2021. It's that time of week that we get together to talk about all things Circuit Python. This meeting happens at 12 p.m. Eastern Time, 11 a.m. Pacific Time on Mondays. You can check the Circuit Python channel on Discord for notices of a change in time, as well as add the meeting times to your calendar by visiting the Adafruit Circuit Python Weekly Meeting GitHub repository and using the link there. If you want to participate in this meeting by speaking, you will need to be added to the Circuit Python Easter's roll on Discord. Please ask any one of the moderators or admins to add you if you'd like to join. Development of Circuit Python is sponsored by Adafruit. Please support them by purchasing hardware from Adafruit.com. And just to recap, I think I skipped over this. Circuit Python is a version of Python designed for tiny little computers called microcontrollers. And as I mentioned, it is sponsored primarily by Adafruit. This meeting is held in five parts, which is why we put timestamps in the notes document so you can skip to the parts that interest you the most. The next part is community news and a preview of the Circuit Python and Python on microcontrollers newsletter. After that is the state of Circuit Python, the libraries and Blinka, a numbers based overlook of how the project is doing. Third and the first of two round robins is the hug reports section, a chance for people to thank those in the community around them who are doing great things and helping one another. The second round robin section is status updates where we invite you to let us know what is up in the past week. What you've been doing with Circuit Python and beyond, as well as let us know what you hope to get up to before we meet again. Then the fifth section, if we need it, is called in the weeds. It's a time for longer form discussion. Anything that is just a little bit too long to fit in status updates. And that is how the meeting will go. So I will head over to community news. And this week, I kind of focused on the big headlines, but a reminder there are a lot more community projects and all sorts of cool stuff in the newsletter. So please subscribe and get that in your inbox every Tuesday. So first up, MicroPython 1.16 has been released. It includes a bunch of new stuff, including a new command line tool called MP remote, which is a way to access the serial terminal and the file system and so forth. It works on Linux, Windows, and Mac. And as part of this improvements were made to Pieboard, including opening serial ports in exclusive mode. In the Python core, OS error exceptions now support the Erno attribute. And here's one that they have upstreamed from Circuit Python into MicroPython. The repo was improved so that tab completion is better. It doesn't include private methods and it will tab complete built-in module names after import is typed, which we are very happy to see them able to take features from us. I'm not sure who prepared that to go up into MicroPython, but thank you very much for that. Next up, there is a June 2020 release of Python in Visual Studio Code. This release of the Python extension includes support for VS Code's Workspace Trust, jump to source code with the PyTorch profiler, and completions for dictionary keys with PyLance. And there is a link to Microsoft Dev blogs right there in the notes. Next, Python 3.10 Beta 3 is out. They do a calendar-based release schedule. So things are working towards Python 3.10 as a stable release. There are links to Twitter and the Python mailing list, and I'm sure they would love it if you would test it out with your software and give them feedback. And next up, Circuit Python Speedy Key Switch Handling, thanks to our very own Dan Halbert. We've added Speedy Key Switch Handling. It can handle vector and matrix keyboards all done in the Circuit Python core. It'll make your keyboard projects a lot easier and a ton faster. We do this work in the background and it handles all the work for you and just tells you when you get a key press or a key release event. Lamour did a video which shows her running it on the 12th key macro pad, which is an upcoming product. Last but not least, the Circuit Python deep dive stream with Scott has been offline for a couple of weeks, although I suspect he will let us know that he is back on very soon. And that's what I've got for this week. For more, subscribe to the Circuit Python weekly newsletter at AdafruitDaily.com or check out the complete archives. The link is in the notes document. We like to highlight the latest Python on hardware related news from around the web and we invite you to contribute your own news or project. You can edit next week's draft directly on GitHub and submit a pull request with the changes. You can also tag your tweet with hashtag CircuitPython on Twitter or email cpnews at adafruit.com and thank you very much to whoever is putting those links in the chat. Alright, we go to step two, phase two, the state of Circuit Python, the libraries and Blinka. So I will first give the overall and then hand it off to some other members of the community to talk about the different parts of the overall project. So overall we had a small number of pull requests merged in the last week, 16 of them from 10 authors. The name on weHV is new to me. Reviewers, we had eight and we had 25 closed issues by eight people and 14 open by 13 people. So although our activity and pull requests is lower numerically than in a lot of other recent weeks, we see a lot of good activity on issues and we had a net decrease in the number of issues. That all seems promising. And now I will pass it to Scott to tell us about the core. Although if you don't feel you can do the core overall, you can pass it back to me or we'll put Dan on the spot, your choice. I'm happy to read it off. Okay. So for the core, we had four pull request merged from four different authors. So thank you to all our authors. We had two reviewers. So thank you to our reviewers. We have 24 open pull requests. The oldest, we have three, they're older than 200 days. So again, if you want to get started and help contributing, take a look at some of those old PR. Some of them are just for boards. So they're like relatively easy to take a look at. Although they do require you to have the boards themselves. So please take a look at that. Issues wise, we had 14 closed issues by four people, six open by six people. So we're net down, which is great for a total of 459 open issues, which you can see by going to github.com. We have five active milestones. We have zero six X X bug fixes. We have 75 7.0 issues and we have two issues not assigned to milestone. We track how many issues are not assigned to milestone as a way to know how we are doing in terms of triaging. So that's that. Overall, I would say things are going good. We were just chatting in our internal meeting. I think the next step for 7.0 is to take a look at these 65 open issues and decide which ones are a priority prior to the next stable release, which we would like to start working on and driving the bug countdown so that we can do a 7.0 stable release. That's it for me. All right. Thanks, Scott. And next, I will pass the baton to Ketney to give us an overview of the libraries. Thanks, Jeff. So this applies to all of the Adafruit circuit Python libraries as well as a couple extras. So that's everything that begins with Adafruit underscore circuit Python underscore and includes our cookie cutter in the community bundle as well. So we had six pull requests merged by four authors and four reviewers. We have a total now of 48 open pull requests. We have eight closed issues by six people and six opened by six people leaving us with 312 open issues across all of the libraries. If you're interested in contributing to circuit Python on the Python side of things, go to circuitpython.org slash contributing. You'll find all of this information and more a list of open pull requests, a list of open issues and a list of library infrastructure issues. You can go and search the issues by label. The first issue is a good place to start if you're new to everything or consider bug or enhancement if you're looking for something a little more complicated. You can also take a look and find if you have hardware for something specific and you're interested in doing something with that library. You can check out and see if there's any issues there. In terms of PRs, take a look at any open PRs, see whether or not there's anything in terms of syntax or spelling or that sort of thing if you don't have the hardware. If you do have the hardware, give it a test. That's a great way to get started reviewing and once you're comfortable, leave a comment that you did that and once you're more comfortable with that we can consider upgrading you to our actual review team. So that's a good way to get started reviewing on the Python side of this. In terms of new libraries, we didn't have any this week, but we had a number of updated libraries which are listed in the notes doc. I don't know that I have much to say overall. We've been trying to get through all the open pull requests. The oldest one right now is 549 days old. Jose David has been going through has a bead on every open pull request right now, but we need to discuss his suggestions about what to do with them. So we're trying to get through those. If you have a PR that's open and you're waiting on us to comment or waiting on something, please feel free to comment on it and let us know so we can pick that up and make sure that things don't languish. And other than that, thank you to everyone who's been contributing. And remember that we are always available to help you get started if that's something you're interested in doing. Thank you, Katnie. The next subsection is about Blinka. And for that, I will let make her Melissa tell you what's what. Thank you, Jeff. Blinka is our circuit Python compatibility layer for my Python and Raspberry Pi and other single board computers. This week we had six open or six pull requests merged by three authors and four reviewers leaves four open pull requests. I think a couple of those are mine. There are were three closed issues by one person and two open by two people leaving a net of 57 open issues. There were one. Wow. 11,257 high wheels downloads in the last month. And there were there are 75 boards currently supported. And that's it. Thank you, Melissa. And that brings us to hug reports. I will start off and we will go around in the order that I find things in the notes document. And we're inviting you to tell us about what the people around us are doing to improve our community and make things work better. So I wanted to start off by thanking Dan for some good memory size optimization ideas, although it came to my attention that at least one of these ideas was also from Scott that I will mention a little bit later. I wanted to thank the micro Python team for another release version 1.16 that I talked about earlier. A hug report to foamy guy for chiming in with useful issue, useful information on an issue, a group hug in celebration of reaching pull request number 4900 in the core like to see those double zeros will have a triple zero soon enough. And lastly, hug report for summer soft and Dylan for keeping the adabot running smoothly. There is a little maintenance work required over the weekend, but they completed it in time so we had our numbers for the state of circuit Python section. And with that, I will pass it to catney and after that to Melissa. Thanks Jeff. So my first report is to summer soft for fixing the library reports after breaking them. Sure, but they're fixed now to Dylan for figuring out where the issue was an adabot so summer soft could fix it to JP Noah and Pedro for chatting with me about creating video content making excellent suggestions and agreeing to provide feedback and assistance to Jeff for taking care of the post meeting tasks last week so I could meet a deadline to everyone contributing to the circuit Python community code of conduct PR and to Jeff and in and Mr certainly for suggesting an update to the Adafruit community code of conduct and to and in and Mr certainly for agreeing to put together a draft of the success suggested update here here I should have thank them as well. All right, with that we will go to make Melissa and then to Tanute. Let's say for my ag reports, I just wanted to start by giving one to the samurai corporate for your work with the duplicating code and platform to take the group of different else. That's it. All right, Scott, you are up next. Then it's anybody's guess who is at the top of the alphabet. Hello, just a group from hug from me because I was disconnected from the circuit Python world as I was on vacation. So, all right, we muddled through as best we could without you, but it's nice to see you back. All right, I have notes from C Grover and Charles and then after that it'll pass to Dan so C Grover has a hug report to paint your dragon Phil B for his history of producing awesome graphics code. He makes it easier to understand some very complex ideas and approaches and also C Grover has a group hug and Charles Barnford has a group hug. So Dan, go ahead and then I will read notes from David. Okay, thank you. Okay, I'd like to thank a higher effect for taking over sleep. I think I've thanked him before, but he's really keeping track of how each chip family can do sleep and what are the problems between them. They're all idiosyncratic in various ways and it's hard to find out if you're at a common API and he's working on how to achieve that. That's great. Thank you, Jeff, for getting the bug to take on yet another way of shrinking our firmware even more. And if we keep this up then everything will fit in 20 bytes. Thanks to Lady Aida who has tested my new keypad module in multiple ways with new hardware that she's designing. It worked out great. That's very nice. And she had some suggestions for the API and thanks to TAC for fixing an NRF issue where it took a long time for the REPL to come up for mysterious reasons. And that's fixed now. It may have also caused other things to be fixed. We'll see. Okay, I will read notes from David and then I will pass it to Dylan. So David Goud writes, a hug to Brent for thinking about me as a beta tester for Whippersnapper. A hug for Dan H for the keypad module and to me for the camera library both as demonstrated by Lady Aida. And a hug to Fumiguy for streaming about the GitHub CI. All right. Take it away, Dylan. Then I will read notes from Fumiguy. So hug report to Carbonated Water for lending me a CNC and helping me get it working, which was a lot harder than I expected. Hug report to Sonarsoft for all their awesome work on AidaBot and then in Groupalk. Thank you. All right. Notes from Fumiguy and then Hyrofect gets to round out the section. Fumiguy writes, a hug to Noa M Pedro for making and sharing so many neat 3D printable parts. A hug to Ketney for making the simple text display library to make it easier for people to quickly display text without needing to understand display I.O. as much. And a group hug and Hyrofect, it's up to you. Alrighty. Thanks this week mostly to Dan for his reviews of the incoming PRs that I'm looking at and just a bunch of sleep sanity checks and just thinking about sleep and helping me out with that. And then a group hug to all others. A little quiet over here on the summer I feel like. It is a little bit quiet, but it's also good to be a little bit laid back for a brief moment. So it is. I'm not complaining. That's how I'm feeling. All right. Well, we'll move on to status updates, which is around Robin in a similar vein to hug reports. And by the way, if you wanted to help out the meeting by running one of the round robin sections, just contact the meeting leader in advance and work that out with them. We would be happy to have any one of you do this so that we can just relax and enjoy the meeting a little bit more, if not, no worries. Anyway, so last week was a pretty productive work for me or productive week for me. I substantially completed the library for the OV 2640 camera. I merged MicroPython 1.16 that PR is ready for review and Scott kindly offered to review it. I implemented an idea that was maybe Dan's or maybe Scott's for reducing the size of property objects in the core, but the net savings was pretty small and it probably affects performance in a negative way. So we're likely to leave it out for now. I think that idea was solidly Dan's. It's the second idea that was maybe Scott's to split up the type structure for types in the core. I got this working on the trinket M zero and it saves one and a half kilobytes, which would definitely be enough to let us enable some of the features we want. But it requires more discussion. It requires coordinating with MicroPython and MicroLab about a new way of declaring these type objects in the core, even if we decide we want to do it. And I also need to benchmark whether it affects the speed that also there is a PR on GitHub. It's not ready for review in the sense that I don't think we should say yes to that PR in its current form. It needs more work. So anyway, up this week, I will finish up the OV 2640 library, which I think is just tagging a release. And I will get that added to the bundle. So next week, we will have a new library to list off. I will start writing a guide that will cover the OV 2640 and OV 7670 cameras in Circuit Python. The OV 7670 works on three of our boards, the Metro M4 Grand Central, the ESP 32S2 where I've tested on the Coluga and the RP 2040 where I've tested on the Pico. And then the 2640 doesn't work on the Grand Central for reasons that we're not going to explore for now, but it works on those other two systems. And so those are the five combinations that this guide is going to cover. And then in between that, I'm going to start working on a project for an upcoming guide. I'm excited to do a project guide again. It's been a while and for this one, I get to design and order a PCB. So this will be a lot of fun, but also a little bit of waiting for printed circuit boards. So next, I will read notes from Jose David, and then I will pass the stick to Catney. Jose David, who's missing the meeting this week, wants us to know that this week he'll be working on the PRs and would like to discuss that with Catney. So next is Catney and then followed by Micro Melissa. Thanks, Jeff. So last week I published the Slider Trinky Guide, started the QT2040 Trinky Guide, and along with that created the CircuitPython I2C template. I also managed to figure out a sort of concurrency in Arduino, which is not CircuitPython related, but was definitely a big deal for me. This morning I completed my first successful rebase without help. That was excellent. So this week finished up the QT Trinky Guide. Update the Slider Trinky Guide with a MIDI example. I need to test a PR on PyPixelBuff. That should be a quick one. I'm going to continue working on the CircuitPython Community Code of Conduct PR, discuss open PRs with Jose David. And then something I didn't add here, but will, is that we are going to, after the QT Trinky Guide and the rest of those miscellaneous is taken care of this week, start going back and replacing the, which was the whole point of the templates in the first place, the CircuitPython Essentials pages in other previous board guides with the templates. So that basically instead of a generalized page that has wiring diagrams for seven or eight different boards, it will be a page that is specific to the particular board that the guide is for. And that was the original plan, but we're going to actually start going back through it. So outside of CircuitPython, PyOhio accepted my top proposal the first five minutes, which will be pre-recorded and the conference happens on July 31st. And I received my second COVID vaccine last week after a bit of a debacle, but I have it and it's good. And that's what's going on with me. Thank you, Catney. So PyOhio is pure virtual this year? Yes. Okay. Next up is Maker Melissa and then Scott. So go ahead, Melissa. Okay, last week I finished fixing the remaining repos from the moveover from Master Domain. I figured out how to reassign chip-enabled pins on the Raspberry Pi boards to avoid de-assert conflicts with Blinka. And I wrote a script to assist that and update the Raspberry Pi Blinka guide. I also refactored the Web Serial ESP tool to allow better reuse of the core programming for use of Whippersnapper. And this week I'm going to be testing ESP Home with a recently updated Arduino ESP32 package to see if I square C and Wi-Fi are working. We'll be working on the Whippersnapper package to a Whippersnapper package to create a file system from a table using JavaScript. And I'm going to be starting a guide with Microsoft Flow. And that's it. Thank you. All right, Scott, you are up. And then we'll go back to the top of the alphabet. So last week was vacation for me. So basically I'm buried under a pile of email. Those of you may not know, but I do like this zero inbox thing. So I have no email on red after I do my email every morning. So I have seven work days worth of email to go through. So it'll be lots of reviews and catch up and all of that stuff. I'll also do the forums. So lots of that probably today and tomorrow if not leaking into Wednesday. And then after that it's back to polishing up the BLE workflow code and getting a pull request out for that. And I got to sync up with the folks doing the apps as well to see how well my code that I threw over the wall before I left worked out. That sounds good. And I do think I'll stream on Friday as well. I think a lot of people will be happy to see your return. I may not have anything to work on this. You may still be getting through your inbox. Hopefully not. Hopefully I'm done by then. All right. So I have notes from Sea Grover and then we will hear from Dan. Sea Grover converted another legacy Arduino project to circuit Python. This week's challenge was one of my favorites. Phil Burgess' fake TV for engineers. A successful conversion working on the documentation now. An unrelated ish preserved and reinstalled two interior doors in the 1940 section of the house. This was a week for legacy projects indeed. I think a legacy 1940s door is more legacy than Arduino but anyway. All right. Next is Dan and I'll have notes from David. Thank you. All right. I finished the keypad module as was mentioned which supports scanning keys in three different ways. Lady A did functionality testing of this with some upcoming products. And PR is now ready for review after multiple changes to the API and some more additions over the past few days to kind of flesh it out completely. We talked just before this meeting in an internal meeting and we'd like to try to make a 7 0 0 another alpha or perhaps even a beta if we decide that the APIs are not really going to change. So we could start a beta series so that we can include all the stuff that's been happened in the past few weeks. And now that I finished this I'll be going back to 7 0 0 bug hunting which we'd like to either defer some things or fix them in time to get 7 0 final out. Okay. Thanks. Well David writes this space is left intentionally blank. It's not even top secret. It's just nothing. So I hope you're able to get back to doing some projects soon. David. But next I'd like to hear what Dylan has been up to. And then I will read some notes from some folks. Also before you start I just have to read what Katny said. She said to see Grover. I'm not picturing you having decade themed sections in your house. Anyway, decorating ideas from Katny. Thank you very much. Go ahead Dylan. You're fine. So last week I borrowed a CNC from a friend. And just this morning I actually finally got it working which was really exciting. Just a case of terrible documentation and a bunch of broken download links. But got it working. I did a lot of cutting for the alarm clock. Now I just need to get it from 3 quarters of an inch thick to a quarter of an inch thick. Which is going to take so long. But yeah. And then just 8 about stuff. A bunch of random stuff with that. And then this week I'd like to finish doing the stuff with the CNC. And I have like a bunch of different guys I'm working on right now. Great. Thank you. I will read notes from Alvaro and Foamy Guy. And then pass it to Hirofact. Sorry your name is now Hirofact. Hirofact to once again wrap up the section. Anyway Alvaro fed a two rights last week porting Glinka to two risk vboards. But having issues with Lib GPIOD on both. This week looking into whether this is a kernel issue or a Lib GPIOD issue. No idea at the moment. And next month building a house and moving out of the city. So mostly AFK. And then Foamy Guy also has notes for us. Last week learned a ton about PyPI version strings and GitHub actions. Finalized code and the 3D model for Neo Trinky Brightness Crank. New commits to Stubbs PR to handle the PyPI uploading for separate stable and dev versions of the Stubs. I believe it's ready to have their credentials added to the environment and to be reviewed again. And this week work on the Neo Trinky Brightness Crank guide. And trying to create a bundle library for this. A bundle repository for the Circuit Python organization. And now my last chance to say Hirofact's name for the meeting. Hirofact you are up. Alrighty this last week I merged in and modified the set next file PR. This is a PR that allows you to make Circuit Python start from a different file than code.py on your file system. The next time it restarts and has a bunch of different things. This is intended for use with menus. So you can make a menu or well it's intended for a couple things. But one of the uses is you make a menu and you can select the like a game or something sort of sub program and it'll start that up next. I've brought that up to speed but there's still some work to do because there's a bunch of complications with how this interacts with deep sleep. Deep sleep is basically a reset and so storing the file for the set next for the next file to run is a little bit tricky because deep sleep will basically destroy all of the RAM. And so we have to figure out where we're going to put this file in a non volatile memory. So I'm I have a little perspective new API for how that's going to work across all these different ports which all work differently. And assuming that Scott is all good with that. I'm going to be working on this week that this week which will have kind of a bunch of bleed over work related to sleep memory across all these different ports. So that's my big job for this week. And as kind of a little side thing just because this is the second oldest PR that we have would be rebasing and refactoring the exception tracking. So that's a that's a kind of a related PR that allows you to see what the last exception was on Sir Python. And that's what I'll be working on this week.  Thank you. It will be nice to have those PRs finally merged so it's good to see that work that you're doing. Yeah, we'll have we'll have fewer in the in the code. The core report it'll shorten the number of months associated with the oldest one. And with that we are ready to wrap up status updates and move to in the weeds. I will actually interrupt in the weeds. And I want to mention that we have settled the date for a circuit Python day 2021. And it is going to be August 6, which is a Friday. We will be getting more information out about that soon, probably in the newsletter and also on the Adafruit blog. And we'd like to invite you to think of ways to celebrate circuit Python day with us because it's not just an Adafruit thing. It is a community thing. And yes, 86 2021 if you want to write it as the Europeans do. And unless anybody wants to add a comment to that. David says, what about the calendar from Digi-Key? We decided for a number of reasons that August is a better time. And so we are going with it. Unfortunately, we didn't have a discussion with Digi-Key before they set the calendar that way. They took the date from 2020. And it's what happened. And this is what we're doing. So yeah, no hard feelings, but your Digi-Key calendar does require revision and celebrating twice is also a great idea. I believe that the Digi-Key calendar placed it on 9.9, which was the day in 2020. But historically it's been in August and we're returning to that this year. All right. So yeah, I will pass it to Dylan, who has a topic about the Adabot. Yeah, so over the last, I guess, probably a year or so, based on some initial work that Fome Guy did, then making a lot of scripts that just speed up things that I've been doing with library sweeps, getting the list of all the library stuff like that. And I was wondering what people thought of the possibility of kind of like either maybe like putting some of those scripts in the Adabot repository, making them in their own repository, maybe like writing died on just like using Adabot for those sort of things. Yeah. Are they all related to Adabot? Pretty much all of them are, but not all. Okay. I think including scripts that are related to Adabot in the Adabot repo, perhaps in a folder that's separate so that it keeps it clean would be fine. Okay. Sorry. And then I think it might be alright to have a separate repo for scripts that are unrelated to Adabot. Okay. What I would suggest is maybe create a repo on your own account. Put the stuff in there and we can take a look at it and decide whether it makes sense to transfer it to Adafruit is basically what I would think would make the most sense. Yeah. Okay. Sounds good. Well, those were the two in the weeds topics. So unless anybody has anything else, I will go ahead and wrap up the meeting for the day for the week. This has been the Circuit Python weekly meeting for June 21 2021. Thank you everybody who joined us live and if you're watching this or listening after the fact. Thank you very much for that. We will hold our next meeting on the 28th at the regular date and time, but then the subsequent meeting will be moved a day later due to the American holiday of the 4th of July also known as Independence Day. It's the other part of the end notes that I always forget so pardon me while I look at the document. If you want to support Adafruit and Circuit Python and those of us that work on Circuit Python consider purchasing from the Adafruit shop at Adafruit.com. The video of this meeting will be released on YouTube at YouTube.com slash Adafruit and will also be available on major podcast services. We'll also feature it in the Python on microcontrollers newsletter. Visit AdafruitDaily.com to subscribe. The meeting is held on the Adafruit Discord which you can join at any time by going to adafru.it slash discord. If you'd like to speak in the meeting or just to be notified about the meeting and any changes to the time or day you can ask to be added to the Circuit Python Easter's role on discord. We hope to see you all next week. Thanks everyone. Thanks everyone.


Welcome to Digital Asset News, the top stories in cryptocurrencies and digital assets. Man, break it down to bite-sized pieces today. Just want to talk about three things. First of all, Bitcoin is not a security. Tether is not a security. Celcius is a security. And why? This is actually great news that I found out about Celcius. So let's back up, first of all. Let's take a look at why we consider Bitcoin out of security. And this was actually in front of the House Appropriations Committee before Congress, the former chairman of the SEC, Jay Clayton, who is out right now, was asked by Congressman Stuart to clarify his view on essentially Bitcoin. And this was in April 2018. And he states, Bitcoin, a pyramid of exchange, the one that's most often cited, is Bitcoin. As a replacement for currency, that has been in term of most people to not be a security. So there was a bunch of different things going around, especially in the Twitterverse, where, well, now that XRP is going this whole thing with the SEC, of course, then the whole cryptocurrency space will be doomed. That's not true. They have to take a look at a lot of different factors. And one of those is Bitcoin's out of security. Also, they've alluded to the whole fact of Ethereum being the same way. So let me back up even farther. So I want to talk to you real quick about what would be considered actual security. And this is the Howie test. And this Howie test was created a long time ago. So everybody doesn't stand up to the complexities of the future or of right now what's going to happen. But we have to take it for what it is, because that's all we got. So there's four criteria. And the three really doesn't really make too much of a sense, right? Investment of money, okay, great. Everybody invests money. And then the third one, the investment money is in a common enterprise. Sure, you can say that. And then any profits comes from the efforts of a promoter or a third party. Well, with Bitcoin, that doesn't happen because it's so decentralized. And that's what they talk about. If it's decentralized, then it's not really a third party because it's decentralized throughout. It's not a centralized product. And that is one of those issues. And the second one is why I want to really harp on before we get into the Tether story. And it talks about there is an expectations of profits from the investment. So here's one of those things about Tether. I don't see how you can get profits from Tether from investing in Tether. Because it's pegged to the dollar. And some people will say, well, you can make profits by spending it on other cryptocurrency. That doesn't make any sense. So it's pegged to the dollar.  Because it's pegged to the dollar.  I'm going to have people pay me as a shoveler. And that's how I'm going to make money. It doesn't make any sense. So Tether is not going to be a security. But this actually just came out a couple hours ago. And I want to go over this real quick before we get into the whole thing with Celsius. So what the heck is going on? Well, this is Qiyong Zhu and he is the CEO at CryptoQuant. And he states, if SEC's next target is Tether, it's going to be very, very bad for this bull run as the market heavily relying on USDT. USDC, the most legally regulated stablecoin, will eventually replace USDT. And of course, Qiyong Zhu over there at CryptoQuant has a vested interest in USDC. So Arduino, who is the CTO at Bitfinex, who they are responsible for Tether, dismisses the rumors and accuses the former Qiyong Zhu of spreading misinformation. Here's what he states. Reminder, Tether is registered and regulated under FinCEN as all the centralized competitors are. Strict KYC and ML is applied to all Tether direct users as the other main issuers are doing. Less regulated is just FUD. Ask yourself who benefits from spreading information for misinformation. So sure, understandable. The big thing about Tether though is about the audit. People are always saying, well, do you really have the billions of dollars that it is supposed to be pegged to or not? And that is the big thing. But that is something completely different from being registered as a security, which I do not think it is from what we just talked about. And it's not just me. Economist Alex Kruger insists that the SEC will not be targeting Tether. Kruger argues that the SEC wouldn't target Tether because the stablecoins issues are not related to unregistered securities and would fall under the purvey of a different agency. And this is Jake Trevinsky. If you don't know Jake, he's a lawyer, specializing in cryptocurrency. And he also thinks it's unlike the SEC is the agency that will go after Tether because stablecoins are just about the hardest thing to classify as a security. Again, what we just talked about as far as expecting profits from investing in a Tether is makes no absolutely no sense. So that clears up that section. Now let's get to something that is pretty interesting to me. And that is that Celsius has been registered as a security. So what's going on here? I didn't know this, so this was good that Daley Hartle actually put this out. So Celsius has shot up by more than 84% in value, which is kind of crazy, but good for all you holders, including myself, Newsflash. I am biased because I own Celsius and Bitcoin and if they're in all the things that I talk about. So that's just how it is. And this is what Alex says from, he's the CEO of Celsius. All the coins that may be deemed a security are down 20 to 50%. XRP, XLM, XEM, TRX, XE, all that stuff. This was interesting. Crow, which is the Crypto.com. While the only token that registered with the SEC is up plus 42% in 14 days. I was like, huh, I didn't know they registered with SEC. We'll get to that in a second. It was only trading at around 46 cents in August and it's gained a whopping 3,765% year-to-date. Yeah, it's been a pretty crazy run. In addition to being registered with the SEC, Celsius Network also recently announced the competition of an audit of its assets through a partnership with Chainalysis. This is what Moshinsky said. Our relationship with our 230,000 community members are built on trust because they count on us to act in their best interests and have access to unique curated financial services, products and rewards, and so on and so forth. With the validation of a third party, we're providing additional transparency into our business, which remains one of the industry's most reliable, secure and rewarding platforms for putting unparalleled economic freedom in the hands of people. So great. So this is fantastic news. I like when these things happen. This didn't just happen recently. It was actually December 9th. And the third party Chainalysis came in and said, we're going to do an audit to make sure that you actually have 3.3 billion of assets that you claim to have. They went in there, they did that, and they said, yes, you absolutely have that. So I like to see other type of entities come in and do some type of audits because I mean, we do that with the FDA. We do that with our hospitals. We do that with a lot of businesses for OSHA and things like that. So why shouldn't we do that with our cryptocurrency where it actually is stored? If you're going to talk about centralized finance like a tether, like a Celsius, and all those things. So it makes sense to me. And actually, this is another reason why I'm big on Cardano. When Charles Hoskins is always talking about it's backed by science and peer reviewed, what they do is they have independent people come in just like you would do with a drug company and say, we need a third party to evaluate these types of medications, in this case, it would be Cardano, to see if this would actually work in a real world situation. And that's why they talk about, we have all these papers and da, da, da, da. It's because they reach out to other third party entities. Okay, so let's get into the meat of this about what Celsius actually is as far as a registered security or what's going on with it being registered if it actually is a security. So there's the website Celsius.network, Why Trust Celsius? It's a pretty good page to put up, especially when I have people trust you a lot. They pretty much just go about what it is, what's going on. And then they talk about license of regulations here. And then if you scroll down here, April 2018, SEC regulation, if you click on the defile, it'll go right to the sec.gov website. And there's two documents. So you have both of them July, actually April 30, 2018 was the initial file, then there was an update in July 13th. If you click on documents right here, it'll take you to the next page. And I'll say this is Form D, notice of exempt offering of securities. And I'm like, what the heck is that? So if you look it up, Form D, the federal securities laws requires a notice to be filed by companies that have sold securities without registration under the Securities Act of 1933 in an offering made under rule, blah, blah, blah. Okay. A company must file this notice within 15 days after the first sale of securities in the offering. So what it looks like to me is that Celsius went ahead and said, yes, we are and have sold securities. And we want to register that with the SEC because we want to stay in compliance. Okay. So if we click on here, the primary document, this is going to open up the SEC, notice of exempt offering of securities. If you scroll down about three quarters of the way down, it's going to state the type of securities offered. And this is just to back up real quick. This is from Celsius Network. Jurisdiction is in the UK within the last five years. Here's the last name, Mishinsky, Alex. Here's their corporate address and blah, blah, blah. And then when you scroll down again, you can see where it says types of securities offered. And right here it says other, purchase agreement for cryptocurrency. So yes, it is 100% a security. It is registered with the SEC. So there is no risk of the SEC coming down on Celsius because they've already registered. So this is great news because this is one of the things that I had in the back of my mind.  Because it kind of fits that mold what we just talked about as far as the Howie test. Now me as an investor, I like to minimize my risk for the potential greatest upside. That's why I've got 50% of my portfolio in Bitcoin and Ethereum and the rest, the alts, I mean, I don't know. But I have invested pretty heavily as well. But again, the lion share, Bitcoin and Ethereum. And that's just how I see it. Now with this news, what I just discovered today, I have been even, I'm going to be even more bullish on Celsius. And yes, it has skyrocketed in price. If we take a look at coingecko.com, you can take a look here at Celsius Network. Today, just this week when I'm 72%, it's at $5. And it's just been on a absolute pair. It kind of reminds me of Binance Coin where it was like nothing, like a couple bucks. And all of a sudden it went like 30, 40, 50 dollars. So this makes me quite bullish on it because I mean, look, SEC, there's no problems there. It's got a great community. It's got a guy who's doing AMAs all the time. It's got the best rates as far as loans. If you took a look at my video, we talked about the alternatives to cashing out. So this is what I'm going to do. I had put out a video a couple of days ago, about a week ago, and I talked about how I only DCA for tokens right now. I bought a lot more of other things, but these are the ones that I buy every single day, Bitcoin, Ethereum, Cardano, and Voyager. And you can watch that video and I'll explain exactly why I have those four. Now I have others, but these are the ones that I buy every single day. But I will just say this, with what I see with the community, with where I see that Celsius is going, especially with Alex behind the wheel. Remember this guy has already been a successful entrepreneur and he's had multiple exits, I think three exits for a billion dollar companies, which are still around and doing quite well. I've never had a problem with Celsius, even when they had that issue with their website. I had Alex come on the show and he explained to everybody exactly what happened, totally transparent. I mean, look, it's, does it get much better than that? That's all I can ask. I have to ask the questions, get much better than that. And especially with the price action. So I think as time goes on, people really want to go somewhere where they can trust and believe in. Trust is the currency you can't buy and I trust Celsius. I've actually got 15% of my entire portfolio on that platform. So I will still keep DCA for, but as I talked about before, I am going to stop buying Bitcoin when it's 30,000. I've explained exactly why you can watch that video. I'll link at the very end. So what I'm going to start to do is actually as soon as Bitcoin switched over above 30,000, I will buy Celsius. So right now actually, I'll be DCing at five. And then when Bitcoin is 30,000, I'm going to stop buying into Bitcoin and buying to Celsius. I mean, I've got, look, I've been DCing since 2017. I've been dollar cost damaging for three years. And I can only put so much in. I mean, I put a good chunk. We'll just say that. So this will be my next one. Now then, if you want to learn how to buy Celsius, because you can't get any exchanges right now, just go over to DanTeachersCrypta.com. It's my 100% free website. You can click on the start learning and then just sign up. Once you log in, obviously watch this video right here. It's going to explain exactly how to navigate the whole thing. But for this one, there's five different modules. The basic safety investing reviews and how do I, you'll click on how do I. And then as you scroll down, there'll be the couple one down here. How do I buy Celsius right there? So that is it. So thanks for watching. All the way to the end. I really appreciate it. It's a little bit, not too long, I don't think, but a lot of good information. Hopefully this clears some things up as far as what is going on out there. So thanks again for watching. If you like these types of videos, you'll be too much. It's going to pop up on your left and right, right, right now. I don't know which ones. YouTube does it's a little magic. And that is it. So thanks again. And I'll see you on the next one.