Project Spotlight Episode 1: Identity Day

PSE Project Spotlight · 26 Jul 2024 · 57:18

Explores Project Spotlight Episode 1: Identity Day and how privacy-preserving identity systems can prove useful claims without exposing the underlying person or account data.

Topics

From PSE Project Spotlight, hosted by Privacy Stewards of Ethereum.

Transcript

hip hop bot is it a bot from the past messages with me and Charlie she told me to type Loi in the meeting room but it doesn't work anymore that was like can't remember like one 2 years ago 2022 yeah we'll get it for next time guys no worries okay I think this is a good amount of

people in here already so we can just go ahead and get started um thank you all for joining the first project Spotlight um I'm super excited to get started on this um the way that it works is every every month we'll have one project Spotlight and there will be a certain theme for today's theme it's identity um a huge Topic in the space and we have projects such as TLS notary an non AAR and semaphore that will be giving demos after their demo or presentation there will be a 3 minute Q Q Anda if you have any questions to ask briefly and then after we're done with all of the demos

presentations we will move on to an open discussion and that is where anyone in this room can contribute to the conversation of identity so if you work on identity currently or have any questions or thoughts or something to contribute to the conversation definitely feel free to unmute yourself and contribute so without further Ado the first project that we'll be presenting today is TLS notary and we have Hendrick um who's representing them um so Hendrick you have the floor um share your screen and um take it from there hello everybody uh thanks uh for the introduction so I'm HRI and I

represented indeed the TS notary team so I'll do a quick recap of what TS notary is uh I see uh some team members here that where this will be very familiar so um conceptually D notary solves a really simple problem so it's how to query web servers and share that data with another party in a secure and privacy preserving way so TLS not is built on top of TLS so that's the S in HTTPS that we all know so that's a a very good protocol to get data from a website and TLS ensures that the data is authentic nobody changed

anything to it and nobody can listen in so privacy is guaranteed but unfortunately it also has a downside um the data is not portable because TLS uses a symmetric encryption and that's the um the solution or the challenge that TLS solves is how you can get portability um and thens notary does it in such a way that your privacy is protected you don't need external trust and there's also no changes required to the original website and so the result of all this is that all data on the internet uh becomes

composable especially the private data um how we do this uh is uh too much detail um for this 10minute demo so but there's lots of crypto magic going on in the background with multi-party computation uh and the end result is that uh when Alice wants to share private data that's on the website with Bob she can use tea snry without changes to the website um Alice has full control over what exactly she she shares with Bob and also Bob can uh graphic guarantees that nobody can

cheat uh of course it also has a cost so there's uh a lot more bandwidth between Ellis and Bob than just sharing the data um but uh we're always pushing that limit uh with our talented team so I set privacy uh how exactly does that work so TS doy has two features there on one side we have uh reduction so for example here there's a HTTP request where uh Alis can redact some stuff that's not shared and then the future versions it will be easy to add ZK proofs there to hide or disclose um uh

information so it's all open source but uh let's skip this and go straight to the demo so today I will demo the advances we made with the uh browser extension so I've um I'm running a local build here and so when I open it so uh this was all here but what's new is that we now have a plug-in system so you can um add new uh plugins here to access certain data sources for example I have a Twitter messages plugin here and uh when you run this plugin it shows you some steps so first it said you have to

visit the Twitter website navigate to your DMs and what this plug-in will do is proof um create a notarization proof of this uh GM message I have here uh while this um notarization is happening uh we'll already switch to um uh vs code where we have um code for adding an an extra step so next we will do a Twitter profile proof so that could be like for the identity uh proof where you could use that you have access to a Twitter profile um so building this plugin is as

simple as doing an mpm build and then uh in TLS notary we can um add this plugin um with the uh web assembly the user then has control can decide whether to allow this Plugin or not with some overview and then this uh plugin is added here um and so in the meantime we have our proof here so you see the redacted information also the remove uh and there somewhere in here there should be this uh GM uh message which then can be shared with Bob um and so to prove

our Twitter profile it's very similar here we're already on the Twitter website so it starts immediately and I can go check the history here to see an older version of this proof uh where you can see that uh this is the TLs notary uh Twitter account so I hope I stayed within my 10 minutes so uh I can uh dive a lot deeper uh if there's any questions on how to create proofs ah uh one important thing is so I've only shown like how to get the data of course if you build

application you will also want to query these proofs um for now this is documented in the TSN extension Wiki uh where we then also explain how you can connect to the extension from a web page and then query the proofs uh to implement the the actual uh useful stuff in your application questions I have a question fast yeah no no I think that was I think that was

perfect um you're right on time uh question is have you you guys like explored using signatures um at all uh what do you mean exactly with signatures I guess um because right now you have to rely on like a notary right um so there's an element of trust within TLS notary um yeah so I was wondering if you guys um if there's any a world in which you use signatures in your protocol or could uh yeah of course but so indeed in the browser extension we work with a separate notary which I didn't introduce in this uh schedule here so if it's also

possible to use TS notary directly between Bob and Alice and then there's no external trust required um but that's that option is not available in the extension yet uh it is available if you use the the native rust Library um and then also uh THS notary is still work in progress so the format of the proofs that we currently have well proof it's more an attestation um will also still change So currently it's a very naive uh Json dump um and we will uh definitely improve

that in the future and that data is indeed signed by the notary so when somebody wants to verify approve he will check the notary signature and also of course the uh uh the signature of the original website or the certificates sorry awesome thank you but so it's all open Source you can go to the TS notary uh website uh find all information there we also have a

separate Discord from the psse one uh so you can also uh find us there uh with more questions okay well are there any more questions for TS notary we have three more minutes for their Q&A okay you can also meet us in person uh so the next events we have on our agenda are the blockchain in tum in Munich uh I think that's half of September and then uh

most of the T Notre team will also attend Devcon in Southeast Asia in November HRI hendrik could you share any are there any um like exciting upcoming releases either like soon or on the horizon like anything that you can um uh share with us um features uh so we're working on features to verify uh DS notary attestations on chain um so that will will be a nice one and then we're also working on improving the algorithm uh to get a huge performance

improvements while still guaranteeing that everything is uh is saved but this will be like a continuous process um but we have we're making good progress there um so that's the core protocol um also for the uh browser extension so we what we currently have is still like the extended prototype uh and we're cleaning up the code now to make it more uh production ready and then next year we plan to start audits of our code so that we uh get ready to to be used really in production

okay well awesome and then what also might be uh a fun thing to do to learn more about TS notary is have a look at our use cases so on our landing page we now have a thanks to our design team uh some use cases here that that allow you to to D deeper and uh get to know how th snow Tre is used in the wild not yet no not yet okay um Rowdy do you have a question

or I think you're maybe okay sorry I apologies no worries no worries at all well if that's all I think we've reached time thank you so much hendrik for your amazing [Applause] presentation it was amazing um thank you yeah and if you guys think of any questions for TLS notary afterwards you can just ask during the open discussion okay so next we have semaphor we have seedor who will be presenting um for semaphor so you have the stage Sor hey thank you so

much uh yeah thank you so much for this event first of all uh I'm cido and I work with the PSC team and I'm a software engineer and I have been working on semop for and mainly on seop for and zik so maybe I can make like a short introduction semop for um this is our website so semop for is um a protocol you can use um users can use to prove that that they are part of a group and they can um generate a proof um like they can prove that they are part of the group and they can um send a message Anonymous

message um without revealing the original identity so sorry because I don't have any presentation so I will use the change log of our uh release we just released some for like two hours ago like the stable version so um I will probably miss a lot of details so I will try to be super quick um but if you have any questions like about any details feel free to ask them later uh TD there like the main uh changes for some for are two uh first it replaces the old incremental mirle 3 with the optimized lean incremental mirle 3 uh for managing groups and

second it updates the identity schema so we are not using posidon anymore but we are using EDSA so let's go into D um the main updates of the new data structure are related to zero ashes and dynamic that uh so we are basically uh not using zero ashes anymore the first version of the incremental mle 3 the one we are using with some of V3 uh was using zero hashes which are like um ashes that we use to um to calculate the ash of the curent node for each level this can help I

think and with a new version we are not basically um we don't need anymore like the the zero because for each level take a look at the three on the right here even if uh there is one child node at the left one uh we are basically using um the same node to we are not calculating the F for the parent node but we are copying the value of the child node [Music] um the other important change for the L three is related to the depth in the first version of the data structure the depth was static meaning that every time

you need to um uh create a Merle tree you have to think about the right T um at the beginning and you and you have to specify that um and there is also like a maximum number of leaves so if you choose let's say that a 10 you will have a maximum number of leaves which is equal to 10,24 with a new data structure the that is dynamic and and um the tree dep is updated as the leaves are inserted and the number of Ashes is like um to be computed it grows as the tree grows so as you can see here in the tree on the left uh the depth is

true um and before inserting a A4 after inserting A4 the depth is three so the the depth of the three goes and the other uh important update related to um to the new version is the the new identity schema we are not using posidon anymore um in the in sem for V3 the identity commitment which is like the public value of semop for the seop for identity was the posidon hash of two secret values basically the tractor and the NF fire in the new version um the the identity commitment is the posidon

hash of the public key of the vdsa public key um this was necessary because we have noticed that in many use cases uh developers needed something more than posidon for signing messages for example or for verifying uh those signatures you know Zer knowledge proofs um it it had some constraints uh to the ciruit but not so many so that the times for generating and verifying approv are pretty much the same I would like to show you some benchmarks uh this for is pretty interesting um so in the first table you can see different groups with different

leaves um this is the the previous um incremental mfield 3 we are using on in SE 4 V3 and um creating a group with 1,000 members uh cost something like $8,000 uh this is the mainnet of course and this is like the was the the current price um of yesterday whereas with the new insert function of the new incremental Merc 3 the L Inc Mer tree um the cost is much less is $4,400 and additionally we also implemented a new function the insert

Min function to insert multiple members and that reduces further reduces the costs and um in order to create a group with 1,24 members this is wrong um you need like less than $11,000 basically so for example if you have on offchain group with 1,000 members and you want to transfer it on chain to the main net considering the cost above uh with V4 you you save basically $7,000 um of course the JavaScript implementation as well has improved uh inserting new leaves is um much faster you can take a look at the table here

and we also implemented in an insert menu function in the JavaScript implementation as well so another section I wanted to show you is related to developing experience so we have worked on some improvements in terms of performance but also theable experience these are just the the main um the core JavaScript libraries um for the identity Library it doesn't change so much you just need to pass a value uh that value was the secret in the SE version but in the like in the new version is uh the EDSA private key but it's pretty much the same the group library is a little bit different because you don't need to pass any

parameter anymore you don't need any ID which was used to calculate this zero ashes and you don't need to pass any depth anymore because it's not static it's Dynamic um what changed more is the proof package and the function to generate proofs uh takes the same first two parameters the identity in the group but the external fire um is now in another position so they are inverted the external fire and the signal and they have different names so the the external fire is now um called scope and the signal is now F message we decided to change them for clarity um and you don't need to pass any art artifacts

anymore it's optional of course you can do it but um both on nodejs and browsers you um you can omit that parameter because they are they are downloaded automatically um the verify proof function as well uh needs only one parameter it it doesn't need the dep because as I said before it's um it's um Dynamic and it's part of the proof um and that's it I think I don't have so much time do anyone have any questions for

semor okay go ahead I a question yeah a question sorry um have you sedor have you benchmarked or is semaphor supported on uh any l2s I think the benchmarks you were looking at was like mainnet uh Bas layer ethereum but I'm curious about

like L2 support no we don't have uh this benchmarks yet but yeah it will be like to have them okay so there we yeah s oh no no I was just asking so there are uh some before you can deploy sema4 or use semor on on l2s or I guess which which l2s or um which ones do semor is can can you Deploy sem4 on sem4 is already deployed on let's see on for networks now mamoy so the new test for

polygon um but we are going to deploy it in as many networks as possible so yeah possibly like the main ones maybe 10 20 that's part of um our my aome thank you so one question I have is like where like what projects um or where have you seen the biggest use cases for semor [Music]

currently I think z pass is the like biggest and of course worldcoin as well but warin is not using all the libraries only the Contours only some some libraries uh yeah after workcoin I will say Zas um which is one of those use cases that uh led us uh to uh implementing the EDSA identity schema and yeah if you want like a list of projects you can even go to the website and you will find a nice dashboard to navigate them based on categories uh yeah maybe another update is that we

are going to um publish a paper for the new data structure the lean in comment Merle 3 uh so viian is working on that and we probably publish uh it next week or in two weeks there will be more details so I know that this is quite complicated and 10 minutes are not enough to explain everything okay awesome thank you so much cedor really excited for the semaphor project and to see where it goes this is like one of psc's biggest projects So yeah thank you so much for presenting that um thank you yeah of

course okay so last project that we have for today before our open discussion is a nonar and we have Giannis who is going to be giving a presentation on a non a soas you have the floor next yes uh hi everybody um can you see can you see my screen yes all right perfect um yes um thank you uh thank you everybody for being for being here and uh to hear about all this uh amazing identity

project um I myself I'm yanis I'm PSC member I'm a software engineer and currently contributing to anadar and alongside the anada team with r salil and Andy so what is anada anada is a zero knowledge protocol that allows Indian um citizen to prove their identity through the their Adar uh card so I'm just going to briefly introduce um what is the uh problem we are currently solving so so um the status of the current solution right now like in the digital space to when it comes to prove your identity um it's quite bad like when you usually when you have to

do KAC you have to R like your full ID card all the information about yourself uh sometimes take picture about yourself and send it to a server that then like will assess if you're human or not um and um yeah also like on some identity systems like add for example you have like a um it's prone to like a lot of hacks and and privacy leaks so you have like a bunch of add that are like available in the dark web for example which is quite bad um and also like when it comes to like on new cases and you want to prove like that you are human or you want to add like a um s resistance layer to your uh contract um there is no uh perfect solution to to do that

today so um yeah just wanted like to here the goal is not to compare but like more like to give just a mapping about where we are so one approach would be like Biometrics uh when it come to like prove your identity on chain uh which is like the approach that uses um W coin for example uh you have aggregation which is uh used uh by gon passport so if you were able like to prove that you have some activities on platforms like GitHub Discord or Twitter U then I can uh compute the score and assess like how much I think you're uh human um and then so the last approach that we are working on uh is actually leveraging uh the signatures that you can find like on

some identity documents um and use um ZK to um generate a proof of this signature so um here is just a a little scheme to explain a bit like what is the current architecture in the digital identity space um so it's the architecture that uses Adar for example so the government basically they have like a private key they will compute they will take your uh identity with uh which can be represented in a BL a blob of data like your name your date of birth uh the city where you're born or you live then they're going to Ash it they're going to sign it with their private key and then they are going to uh from this process there there there

are going to be like two thing that would be that are going to be like outputed is the signature and the message uh so then the signature and this message are like inserted like in some documents through um a an NC chip or a QR code and then when Bob like wants to verify your document he needs to have access to the signature the message and the public key the public key that you can you can fetch from the government website and then BB is able to verify the signature but the issue here is that bu have access to now your the message which actually is your identity and the signature so yeah just to illustrate so here is how it works like on Adar so you

have like two ways to get like the QR code which is which represent like signed data uh and the signature U so here is a PDF that you can request as a as a Nadar citizen um like as a Indian citizen uh you can request like your as a PDF format and you have like the QR code uh stored inside of this this PDF or you can have use the Madar app is an official ad application and you can redeem like at any moment like freshly signed QR code through this application so um I'm I'm I'm I'm going to be brief here because I guess that everybody like knows knows a bit about about about ZK but just to introduce

that we are we are using vnar uh to have like the same signature verification process I show before for but like just ZN like uh give us the ability to have private inputs so now the verification process uh is actually hiding the signature and the message from the verifier so the verifier would just receive like a snack proof uh that states that u a signature verification of a document were done properly uh with the public key so then Bob can check the public key check that this is the same public key that was like published on the Govern on government.com and he's now able to

access if you're like a human so here is a sorry like the the schema can be a bit overwhelming but the the goal here is not to go into the detail just to um explain a bit what is happening into into snackland so basically like the C code is signed with a signature algorithm which is called RSA um and RSA you're going to sign the chat 56 Ash of your identity your name your date of birth Etc and so what we are able to do now in Star is that we are able to verify the signature to authenticate the data and then once we authenticate the data we can extract some fields of the data that will uh that can or uh can't be revealed so for

example we are Computing a nudifier which which is going to be like your new unique identifier uh in front of everybody with your new an an on identity we are currently using the time stamp as a proxy that you have access to some freshly signed data um and we are um also achieving selective disclosure on four Fields so you can prove for example that you're above 18 uh you can prove your gender you can prove the state where you live and you can you can also prove your PIN code so just a quick demo so here is our boil app so here I already connected my wallet for example and I'm going to uh generate uh a proof of my identity so

here I'm just using uh test data but the logic remain the same so here like the prover will um show you like what you're going to reveal in that case we don't need to reveal anything because the use case is like we are going to vote like on a smart contract and we want to ensure that it's one person one vote right we are committing to the address to avoid front training on chain so by committing to the message sender where um with this the same message sender with whom I'm going to send the vote I can prevent like from so actually the process is taking 26 around 26 seconds on MacBook Pro M1 Pro um and yeah so but the we are actually using um

circum grow 16 to compute the proof um so we can ensure like Fast verify fast verifying time of the proof and cheap cost of verifying a proof on um yes so here here we here we are we generated our proof and then we can uh vote so um I like this up so I'm going to put five uh I'm not sure like the going yeah it's not it's not working because I already voted but uh yeah so uh here it is how we can like just uh uh quickly um like add like this privacy layer to to your app so we have a full edk it takes like bit than 5 minutes to integrate the edk um and you can add

like a new privacy layer to uh your applications awesome thank you so much jannis for your presentation this is a really cool project um one question I have for you actually is like what has the adoption in India looked like of a non- aor like are there new apps that are coming from this or um people that are using it and and yeah just go a little bit more into that yeah so I guess it's like where we

um are goinging to to put a lot of effort on it's like just a you know showed to the Indian Community actually the tool and how they can uh use it we have we have now like a production ready version since a month and a half two months uh and we secur we securi the protocol through a public setup ceremony um and yeah and so actually one cool use case that we developed is um um that you can now uh redeem I can put the link in the chat if there is some Indian folks in the in the room uh but you can now redeem like a discounted discounted ticket for Defcon for example uh because Defcon wanted to incentivize people from

the area uh to go to defon so um they wanted to have targeted discount but without doxine people so you can like generate just a an anonymous proof of your um Indian identity and redeem a voucher okay are there uh any questions for [Music] Giannis or any follow-ups on at all yeah one question

here so is this also uh useful for non-indians yes sure so this primitive about like U SAR ifying the verification of a signature is um you can apply to any identity document that has a signature in it so there is um another team um at PSC which is called the proof of passport that is applying like it to passports um we did also like during the ETC PS house some research uh on the new um European identity card which has also like a chip with sign data inside of it you we know also that there there is

also there are sorry other other digital identity programs out in the world that has like um a representation of your identity through sign data so as soon as you have like a document or at least like a way to have from a trusted issuer which is in this case the government um like a signature uh of your identity then you're good to go and you can replicate it to your um uh identity yes yeah proof of passport is another

quote project that very much is is very similar to a non AAR as well um yeah there there's a couple more um identity projects that are like grantees as well um we'll have to do like an identity Day part two sometime and get some of those projects as well um yeah there is also um Mina wallet for the Japanese ID card we also are maybe we are going to support a team for Europe identity card there is also like some research that done on like the Costa Rican uh identity card so yeah the goal is to have like a a to spread the all the um in all around the world to have like all the

signatures certified amazing amazing okay well are there any last questions before we move on to our open discussion for these last 15 minutes if not then thank you so much uh Giannis for presenting a non AAR and now we can move on into our open discussion and this is uh a chance for us to just talk with each other about

the topic of identity um and if anyone has any comments concerns questions or anything um about identity just feel free to voice your opinions I guess uh one question for the presenters is like right now we have these three amazing identity projects um have you guys like considered potentially how you can work together to maybe come up with like a identity system um I I I know sorry I know on our side

maybe Sal can can can speak more about it than but we we did like try for example like some semaphor integration so um when it comes to like generate a new proof of identity from like a real identity sometimes like one hard problem is that you want tocate it so you want to have like another privacy layer which resolve always the same unque identifi so one way for example to hide any action from the issue of the signature was that generating a SN proof that you have like a signed document and then like using this proof to be added like to a semor group and then you can use this new semaphor identi which is link to the to the verified add group to use

it Al like I think the could be really interesting like when it's comes to like when countries that don't have like actually a signed document but have like I don't know like a trusted API uh so then you can replicate the process but through like a um a TLS proof uh from the the official server yeah indeed so systems like eler in Germany or I think in the US id. me I think uh are like all good sources there um and so we also are looking into uh

setting up u a project with bandada which is also using a semor Under The Hoot do you want to talk a little bit more just a little more detail on that um it's still early days so but the ID is there indeed to use THS notary as a data source to uh check whether you can join an anonymous group or not um I think um PS notary was also used in um ZK PP um right I think with the revolute yeah uh but so that was for

proving transactions uh not proving identity uh but of course any data source uh could be used with TS notary so uh all very uh exciting use cases well another um question for everyone here too is like I guess what are the biggest challenges um that we face when it comes to like identity right now

um I guess like the the main issue is standards um so uh because there there are like some uh working groups that works like since uh um several years uh trying to uh you know have like a standard when it comes to like manage identity in the digital space have like privacy and working on selective disclosure and have a like the right to to have anonymity in the digital space but still like have like a bunch of credential link to your identity so I guess I guess it's going to become is going to become yeah way way more used in the future I think the there's just

an issue about standards right now like it's a um we we need to find one main standard when where everybody can build on top of but I guess that the W3 W 3st standers might become like maybe the the way to go in the future sorry what system did you say w what yeah I'm gonna I'm gonna send send the send the link in the chat but uh basically it's like um sorry I don't want to say something wrong but I think it's like a working group link to E f um and they are basically like working on a um protocol or it's more like a standard

um for um the ID like decentralized identity system um and I'm going to send some some links if you if you want to like um dig deeper into this standards very cool I have to look into that I didn't know this existed thank you for sharing honest so also curious like have you guys had any like um regulator issues when building out your projects at all um so sorry uh I'm going to answer no

regulat regulatory issues but I guess that we are too small now to have to have any request but of course I guess the goal is like more work with in the hands with governments and like show them like the Primitive um and yeah I know that for example in the EU um like the we I we saw that in the um AI Parliament discussions they spoke about ZK as a as a tool for privacy preserving um um use of digital identity in the in the digital space really is there like is there like a link or something where I can go check

that out yeah sure let me let me send it to you really cool also no regulatory issues for TS notary um of course uh people could use this for illegal activities but that's uh not what what we build it for so please if you use the ls notary always respect the uh end users agreement of the uh of the website you're contacting e okay

um does anyone have any other like I guess inputs to the conversation or questions or comments on identity if what you've been thinking about um would love to hear from anyone here know there's a lot of bright Minds in the space right now think this EU thing is really cool

though to see that like governments are now starting to talk about ZK um it shows that the technology is actually useful and something that um will be very important in the future um so I'm excited to have conversations like this and to learn more about these Primitives because um I think they're just going to be so important in the future so good for us to learn about these things now and build on them and make the infrastructure it's solid as we can make it while it's early and also like maybe finding more ways in

which we can communicate with these governments um especially since we're the ones that are building out these cryptographic tools um so I think we know the most when it comes to like ZK and this stuff so um yeah I think um it's really important that we engage with um these governments as well especially in the coming years I think we have some people typing

um okay I think he can can hear us now there's a question in the chat um via says hi guys how can we standardize circuits for crypto cryptography Primitives so they can be used by everyone I think maybe s like it isn't it like the goal of zik kit uh yeah not really I think it it's a goal for SEMA for most more than zikit but yeah it's I mean defining what a standard is is quite tricky um but

to answer that question I think uh we need to make uh like a standard or a protocol uh very popular in order to make it the facto standard or maybe we can have an institution like an international institution that can make it a standard I think there are two ways so one if to making like the the to make the protocol really popular and common and the other one is through a like broad consensus from government and institutions okay did did that answer

your question via or did you have like any followups to that [Music] amazing so maybe a standard that it's worth mentioning here is PCD which is like what Zupas used uh last year I feel like that's a great example and yeah I mean we should try to push it I guess I can send the link yes and yeah I just uh anad is also

using the PCD standard for um managing the the the the the pro and the verifier and I don't know why he still can't hear I'm sorry about that um maybe you can we are recording this whole thing so um and I I'll post it on YouTube so you should be able to go back and listen to it um yeah sorry about that

okay well I think we are coming up on the hour um want to say thank you to our amazing speakers and presenters um learned a lot today about um your projects and uh the topic of identity um we're definitely going to have an identity Day part two um featuring some more projects within PSC um because I think there's a lot of um interesting projects projects and PSC granes as well so um stay tuned for that um I'll be posting uh the Youtube video later today and um I will also be putting out our next project Spotlight sometime um maybe

next week or so um so stay up to date with that um thank you all for joining um um it's been really amazing and we we can't wait to see you at the next project Spotlight bye for now guys everyone bye thanks by bye thank you bye