WEBVTT 00:00.000 --> 00:09.000 So I'll just introduce myself and the jealous of them will kind of give you that kind of what 00:09.000 --> 00:10.480 we're going to cover today. 00:10.480 --> 00:15.400 So just for context I'm Connor Fitzmaris, I'm a Ciconda National Expert working in 00:15.400 --> 00:21.160 DG Connect H4, which is a unit responsible for the European Digital Identity Wallach initiative. 00:21.160 --> 00:25.760 I'm on the technical team where my main responsibility is around the large scale pilot projects 00:25.760 --> 00:28.920 that we're currently funding on the digital Europe program. 00:28.920 --> 00:29.920 Thank you. 00:29.920 --> 00:30.920 Thank you, Connor. 00:30.920 --> 00:36.400 And my name is Angeli Sam with the contractors that actually implement the parts of the 00:36.400 --> 00:40.400 open source, the libraries that we are going to see today and you will be able to reach 00:40.400 --> 00:41.400 them. 00:41.400 --> 00:45.920 And we have also people with the team technical team here, like Bobby's and Nico's 00:45.920 --> 00:46.920 around. 00:46.920 --> 00:52.920 So we can all get questions as well for the representatives. 00:52.920 --> 00:53.920 So, Connor. 00:53.920 --> 00:55.920 Thank you. 00:55.920 --> 00:57.920 So what we're going to cover today? 00:57.920 --> 01:01.920 So, I'm going to set out the overall context for the initiative and some of the kind 01:01.920 --> 01:02.920 of policy goals. 01:02.920 --> 01:06.280 I will take too much time as I know we want to get kind of the meter of the matter in terms 01:06.280 --> 01:12.800 of the RF to technical specifications and the reference implementation which we're developing. 01:12.800 --> 01:17.360 So yeah, what I've furthered do, I'll just kick into kind of the context of the wallet. 01:17.360 --> 01:22.360 Some of it might be quite familiar to you, but just a kind of cover. 01:22.360 --> 01:26.360 So one of the kind of, so the motivation for the European Digital Identity Wallach kind of 01:26.360 --> 01:31.920 came around 2020, obviously then going into 2021, we had COVID, the European Digital 01:31.920 --> 01:36.280 Cova, it's certificate, but in general around 2020 there was kind of an assessment around 01:36.280 --> 01:41.560 the existing EID schemes following the original EIDS regulation which was from 2014. 01:41.560 --> 01:46.400 And frankly, it wasn't a huge success in many parts, particularly in terms of usage of 01:46.400 --> 01:48.640 European Digital Identity's cost borders. 01:48.640 --> 01:53.680 Only I think it was 14% of public services were actually accessible, regard it via 01:53.680 --> 01:58.680 EEU, yeah, an identity scheme that was kind of recognized and notified at level of assurance 01:58.680 --> 01:59.680 high. 01:59.680 --> 02:03.920 And this was, that was one challenge, things were moving increasingly mobile and so there was 02:03.920 --> 02:07.920 a need to kind of update and upgrade a lot of digital identity solutions to kind of adapt 02:07.920 --> 02:09.760 for that reality in general. 02:09.760 --> 02:13.920 And then at the same time came kind of COVID and then the digital documents in terms of 02:13.920 --> 02:17.600 COVID certificates and that was kind of another context at the time. 02:17.600 --> 02:21.840 So we kind of, that in mind there was kind of the digital decade program which kind of 02:21.840 --> 02:25.920 governs a lot of what the European Commission does in terms of ejectors kind of governs 02:25.920 --> 02:31.160 what my DG, DG Connectors, which is responsible for a lot of the European Digital Policy 02:31.160 --> 02:33.440 and kind of tech initiatives. 02:33.440 --> 02:37.360 And so there's a couple of of course, one was kind of increasing skills, predictor on new 02:37.360 --> 02:43.040 technologies such as AI blockchain, infrastructure kind of building a kind of sustainable 02:43.040 --> 02:46.680 and secure infrastructure in which Europe, you kind of see that with data centers but also 02:46.680 --> 02:51.320 a lot of other aspects in terms of just making sure everyone has access to internet 02:51.320 --> 02:52.320 with Europe. 02:52.320 --> 02:56.680 So a lot of programs in terms of rolling out about 5G and internet access that we have 02:56.680 --> 03:03.160 business in terms of digitalizing companies of all sizes and to the use of digital tools. 03:03.160 --> 03:07.400 That one has become obviously increasingly important in terms of European competitiveness 03:07.400 --> 03:10.800 and you can see it is a big focus with the European Union. 03:10.800 --> 03:16.040 It was kind of mentioned multiple times about leveraging digital to essentially make Europe a 03:16.040 --> 03:19.800 bit more competitive because frankly we're kind of following both behind, particularly 03:19.800 --> 03:20.800 in the digital space. 03:20.800 --> 03:25.800 I find that there's kind of more my area which is kind of key public services but also 03:25.800 --> 03:26.800 private services. 03:26.800 --> 03:34.040 So the idea is that 100% of public services should be available online so people should 03:34.040 --> 03:38.400 have to choice whether to access a service in person but also online because currently 03:38.400 --> 03:42.680 a lot of public services someone might want to access online are still only available 03:42.680 --> 03:47.640 in a physical format and this would be supported to basically bringing health records 03:47.640 --> 03:52.440 online and essentially secure EIDs which is where the European digital identity will 03:52.440 --> 03:53.840 come in. 03:53.840 --> 03:59.000 So the kind of key concept or kind of let's say line for the European digital identity 03:59.000 --> 04:05.160 identity of a personal digital wallet for all EU citizens residents and businesses and 04:05.160 --> 04:09.640 kind of just to kind of set out what are the kind of key characteristics over European digital 04:09.640 --> 04:11.640 identity wallet. 04:11.640 --> 04:16.120 First it's free for use for all EU citizens so there's no charge model around it so 04:16.120 --> 04:20.400 there's an obligation for a member states to make essentially European digital identity 04:20.400 --> 04:24.880 wallets within essentially two years of the first implementing acts coming into place which 04:24.880 --> 04:29.480 just kind of long story short happened in November so within two years of November but 04:29.480 --> 04:33.280 kind of end in twenty twenty six members states should start make available the first 04:33.280 --> 04:38.040 European digital identity wallets in line with the regulation and it's voluntary so 04:38.040 --> 04:42.440 there's no mandate or obligation on European citizens to use it but there's a right 04:42.440 --> 04:46.720 for you as the European citizen to have access to European digital identity wallets 04:46.720 --> 04:52.960 so it's kind of a very much a choice and there in terms of the next key characteristics 04:52.960 --> 04:58.160 it has to be accepted to a European union so that's by cross all public services but 04:58.160 --> 05:02.600 also private services where there's an obligation on their law of kind of strong customer 05:02.600 --> 05:07.840 authentication so you see that a lot of the context of buying some payment providers. 05:07.840 --> 05:13.160 And finally there was kind of a focus around security privacy orientation orientation which 05:13.160 --> 05:17.120 is a kind of put basically users a bit more in control of the personal data first you 05:17.120 --> 05:21.040 choose to get to your pinch of identity wallet and now the pit data set which will go 05:21.040 --> 05:25.000 into bit later you you need it to be a European digital identity wallet but beyond that 05:25.000 --> 05:29.000 you essentially elect what documents you bring in there basically by interacting so you 05:29.000 --> 05:33.440 can put your driving license you can university qualifications and other documents in 05:33.480 --> 05:38.240 there but it's very much you choose what documents go in and then essentially it supports 05:38.240 --> 05:44.320 selected disclosure so what you're releasing when you're accessing different services. 05:44.320 --> 05:48.360 To kind of go into the functionality of European digital identity wallets there's kind 05:48.360 --> 05:54.040 of tree kind of key pillars and so first we have identification on authentication this 05:54.040 --> 05:58.880 is quite similar to what you see with existing EID schemes nowadays just bringing it 05:58.960 --> 06:05.680 into a very much mobile package. It's kind of leveraging what exists right and pre with 06:05.680 --> 06:09.920 the previous EID as regulation 2014 around kind of level of assurance high which is kind of 06:09.920 --> 06:15.280 identity assurance to make sure that you're very sure if someone's identity and just make 06:15.280 --> 06:20.720 a very secure kind of process there. The next which is the new element with the European 06:20.720 --> 06:25.120 digital identity wallet which is the storing and presenting of what is called in the regulation 06:25.120 --> 06:28.880 attestation of attributes which we think of them as digital documents or credentials so just 06:28.880 --> 06:33.040 could be your driving license it could be a loyalty card it could be diplomas and it could be 06:33.040 --> 06:39.520 different your health records if you also wanted. The final kind of functionality is the 06:39.520 --> 06:44.240 ability to sign and see electronically so with both kind of technical validity so it's 06:44.240 --> 06:49.040 verifiable but also legal recognition try to European union so this is what's called a qualified 06:49.040 --> 06:54.880 electronic signature so the ability basically to sign a document or sign a transaction even 06:55.040 --> 07:02.000 and that would kind of have legal recognition. Maybe one king to keep things explained is that 07:02.000 --> 07:06.880 there just won't be one model it. European digital identity wallet across Europe or even maybe 07:06.880 --> 07:11.440 one in one member's age it's kind of it's very much up to a member's age so there will be 07:11.440 --> 07:16.160 multiple European digital identity wallets there'll all be built to a common set of specifications 07:16.160 --> 07:20.720 which is something we'll get into a lot of kind of detail today and essentially it's up to 07:20.720 --> 07:27.280 each member's state to decide the model so they can either develop it themselves with an 07:27.280 --> 07:31.680 internal digitization agency or such or they can give a mandate or recognition to a private 07:31.680 --> 07:36.960 sector company but there is to essentially issue a wallet in their country and there's no 07:36.960 --> 07:40.720 limitation on the numbers so they can choose to do one one is the obligation because they have to 07:40.720 --> 07:46.640 make one available or they can do many. In terms of kind of the obligation so they all need to be 07:46.640 --> 07:50.640 aligned with the kind of technical specifications which are set down for the European digital 07:50.720 --> 07:56.400 identity wallet and this is just to ensure interoperability and they all need to be certified 07:56.400 --> 08:02.800 to this essentially right now in Niza the European cybersecurity agency is developing a dedicated 08:02.800 --> 08:09.040 cybersecurity schema for European digital identity wallets and so they'll need to be certified 08:09.840 --> 08:14.000 in line with that when it's in place in the future in the meanwhile basically there's kind of 08:14.800 --> 08:20.960 transitionary measures in terms of different certifications gives in member states and that's the 08:20.960 --> 08:27.520 big expected to be in line. So yeah the technical specifications so it's been an open source 08:27.520 --> 08:35.440 process and we originally published the ARF outline in I think it was February 2022 and since it's 08:35.440 --> 08:39.680 standard there's been a lot of work to flesh it out and there's been a lot of discussions but 08:39.680 --> 08:44.640 with member states of what was called the IDISX group but also in terms of the GitHub community 08:44.640 --> 08:51.680 in terms of the feedback we received from private companies large scale pilots and just the kind 08:51.680 --> 08:57.760 of range of stakeholders in the identity space. Essentially the technical specifications we published 08:57.760 --> 09:06.560 among GitHub or currently on version 1.5 I kind of go into a bit of that right now but they're given 09:06.560 --> 09:10.800 legal impairment by basically being set down in implementing acts which are adopted under the 09:10.800 --> 09:15.600 IDISX regulations so that's really where the mandate kind of comes in terms of making it 09:15.600 --> 09:21.280 mandatory for all wallets across the year and so that's one technical kind of workstrand we have 09:21.280 --> 09:26.320 ongoing so we have the regulation we have the technical specifications then we have the reference 09:26.320 --> 09:31.120 implementation which is essentially to provide a kind of reference technical implementation of 09:31.840 --> 09:37.440 European digital identity wallet in line with the technical specifications and there's kind of a 09:37.440 --> 09:41.440 couple of goals behind this one is the providers feedback to see kind of what's working or what 09:41.440 --> 09:45.360 doesn't work we don't kind of want to avoid the scenario where you which kind of happens 09:45.360 --> 09:48.880 in terms of regulations where you kind of write the regulation then you do the implementing acts 09:48.880 --> 09:52.080 and then you realize something you put in the implementing acts doesn't really work but then you'll 09:52.080 --> 09:56.640 have to come to it in five years time and it's kind of a bit late then because you've tried to launch 09:56.800 --> 10:01.520 the thing and it hasn't worked so this was kind of provide feedback towards the technical specifications 10:01.520 --> 10:05.520 which then in fact obviously into what goes in the implementing acts it was also to provide 10:05.520 --> 10:09.280 something to those member states as well as part of projects that didn't want to necessarily 10:09.280 --> 10:13.200 develop their own European digital identity wallet so the idea being they could take this 10:13.200 --> 10:17.600 either as a fully fledged solution and then just re-badget put their own colors make their own 10:17.600 --> 10:22.160 adoptions or they could take certain components certain functionality and integrate it with their 10:22.160 --> 10:26.160 national implementation and we have kind of seen a variation some some members they 10:26.160 --> 10:29.680 are taking a fully summer taking just parts of it others don't want to because they have 10:29.680 --> 10:33.440 very successful solutions and that's kind of to be honest what we were hoping for. 10:34.800 --> 10:39.760 The final kind of technical work strand is the large scale pilot projects which is kind of 10:39.760 --> 10:45.680 my wheelhouse so essentially these are funded under the digital your program and the idea of 10:45.680 --> 10:50.480 it was to kind of pilot and test the usage of European digital identity wallets across kind of 10:50.480 --> 10:56.000 a range of different use cases and so we have two waves of pilot projects so we've had the 10:56.000 --> 11:01.600 first wave which started in April 2023 and they essentially run for two years and it's basically 11:01.600 --> 11:07.360 four consortia involving over 350 entities so it's a huge involvement for public and private sector 11:08.960 --> 11:13.600 in terms of it has almost all member states are included as well as the likes of Ukraine Iceland 11:13.600 --> 11:17.600 and Norway and they're just piloting a range of very interesting use cases so we have for example 11:17.680 --> 11:22.400 nobody which is very coming from the Nordic Baltic identity kind of cooperation and its focus 11:22.400 --> 11:26.480 very much on payments from in terms of the current account separate in some payments then we have 11:26.480 --> 11:31.280 potential which is focused on kind of a range of public service more related use cases we have 11:31.280 --> 11:36.160 WC which is coming more from kind of a business context looking at the leverage usage of wallet 11:36.160 --> 11:42.400 for businesses and then we have DC4U which is kind of coming from the social security slash education 11:42.400 --> 11:46.720 perspective and there's been a lot of activity in these pilot projects so I'd encourage you 11:46.720 --> 11:52.640 to look them up because I regularly publish and on their own GitHub as well as there are deliverables 11:52.640 --> 11:56.800 to work they've done white papers and so there's a lot of interesting material coming out from them 11:58.080 --> 12:04.880 we do have essentially a new round of pilot projects but so which will we hope to start basically 12:04.880 --> 12:12.240 in the future of this year and so we had a kind of call open from May 2024 till essentially November 12:12.320 --> 12:17.280 2024 number of kind of proposals were submitted we're currently going through the grant evaluation 12:17.280 --> 12:23.120 process around them and essentially we'll then move into kind of notifying them of the results and then 12:23.120 --> 12:28.560 essentially hopefully they'll get up and running by kind of Q3 and then we expect them to kind of 12:28.560 --> 12:34.480 take kind of the work that was on in the first pilots a bit further in terms of and also maybe 12:34.480 --> 12:38.000 focus on some new use cases that are quite important at the moment 12:38.160 --> 12:44.960 and I think that's it for me I hope that was informative and I didn't write all too quickly 12:44.960 --> 12:52.720 to everything but I'll hand over to you guys. Thank you. Thank you corner. So from the let's say more 12:52.720 --> 12:59.920 technical side my name is Angelis Center we have Barbies Nichols Center Simo for the product from 12:59.920 --> 13:07.120 the in-skid team and we have a presentation with a lot of information for you I'm going to focus 13:07.200 --> 13:13.040 only on some of them but you will have the chance to see the slides if you like plus the GitHub 13:13.040 --> 13:20.080 that we have. So what we do is we create a representation that is done in open development that 13:20.080 --> 13:28.560 not just open source so we just we do not just release open source versions we keep working on it 13:28.560 --> 13:34.320 and you can see it live. The same goes practically more or less for the architecture reference 13:34.400 --> 13:42.480 framework that is also released in open source in the same way. The main challenges that we face 13:42.480 --> 13:50.480 are the fact that we try to make this right so we go along with the law and the regulation 13:50.480 --> 13:57.040 and the implementing acts. So we code together with the law so that the law is sure that what 13:57.040 --> 14:02.800 can be done will be done in the best possible way and in the meantime we do a lot of let's say 14:02.800 --> 14:09.520 R&D we devise and we standardize protocols because we do not want to break interoperability. 14:09.520 --> 14:15.120 Remember this is about identity and the main let's say way of having identities today 14:15.680 --> 14:22.720 it's when you travel with a passport. It took 15 years to align the passport's worldwide 14:22.720 --> 14:29.840 but today you can go anywhere in 200 countries and you don't afraid of showing your passport 14:29.840 --> 14:38.320 and being rejected that's how important it is it's more important than money because you can exchange 14:38.320 --> 14:44.240 money into something else you cannot exchange yourself into something else when you enter another region 14:44.240 --> 14:50.240 or another service and we want to make this digital for Europeans very fast on the right 14:50.240 --> 14:57.520 on the right hand side you can see several stacks and protocols that we use some of them the most important 14:57.680 --> 15:03.520 ones are coming from the OpenID Foundation OpenID for VP for remote presentation 15:04.080 --> 15:11.520 OpenID for VCI for issuing to standardize how you can connect to and say your identity to 15:11.520 --> 15:17.920 relying parties and how you can connect to issues and retrieve an identity and also in proximity 15:18.720 --> 15:26.240 and I also standard that is there for device to device extends. Of course in the blend in 15:26.960 --> 15:33.760 remote qualified electronic signatures it's the most successful part of VCI that's 1.0 15:33.760 --> 15:39.280 allow me to say it has been done also in open source development that's why it's accessible 15:40.480 --> 15:46.960 these design experiences are being kept and maintained with European Commission effort 15:49.280 --> 15:55.920 more than 10 years now and that's why we can always sign a contact electronically today 15:55.920 --> 16:02.560 okay yes the adoption is low but it's there and it's legally bound if we use it and of course 16:02.560 --> 16:11.920 we recently released a new UI we are by no means the final product but we release everything for those 16:11.920 --> 16:19.680 that are let's say license let's say more savvy and we release everything in Apache 2.0 in 16:19.680 --> 16:27.680 terms of the libraries and the code in order to one or let's say the EU licensing we also 16:27.680 --> 16:33.840 released the the binaries of the apps in the UPL 1.2 but everything is open source and you 16:33.840 --> 16:42.480 can use it and when I walk you through the latest release that is now done end of January 16:43.360 --> 16:49.440 so you can find code for all of these components in the GitHub we have more than 16:49.440 --> 16:57.200 70 repositories out there with modules libraries core modules or the app itself so we have 16:57.200 --> 17:04.400 three and more layers of abstraction in terms of colors here you can see from top to bottom 17:05.840 --> 17:11.520 this is the wallet plus all the ecosystem so in the middle column from top to bottom you can see 17:11.600 --> 17:20.080 the wallet it's the app it's also the connectors to the relying parties to the web browser or 17:20.080 --> 17:28.160 directly to a mobile app in the bottom the pink one is how you connect to the trust anchor whatever it 17:28.160 --> 17:36.960 is it can be on the device it can be on a key that you hold it can be on a remote cloud provider 17:37.280 --> 17:43.440 sorry to say but the regulation says that the member states can choose and this means that 17:43.440 --> 17:48.640 people that vote in the member states can choose whatever they want so yes you can choose to have 17:48.640 --> 17:55.280 your keys on the side of a server if you like and on the left hand side we can see the issues 17:55.280 --> 17:59.680 you see that the issues have been let's say more or less regulated using open ID for this 17:59.680 --> 18:04.960 Y for issuing this helps into the probability meaning I have a wallet from a certain member state 18:04.960 --> 18:11.760 X and then I can issue a new credential from a bank from another member state without doing nothing 18:11.760 --> 18:19.280 on the wallet that's the goal at least that's the mission and the same goes for the right 18:19.280 --> 18:27.200 hand side if you one of the two important things for the presentation the first was what Conor said 18:27.280 --> 18:32.880 about the regulation the second is this Github page so we publish everything in this 18:32.880 --> 18:39.760 Github organization by the EU for this identity wallet you can find there the architecture 18:39.760 --> 18:49.200 and the code so meaning all the legally bound technical descriptions and the repositories 18:49.200 --> 18:56.000 of course the final version of the architecture is not here we are in 1.5 today but we are getting 18:56.640 --> 19:03.200 why is that the regulation gives us several months to create the so-called implementic acts and 19:03.200 --> 19:08.000 therefore find and analyze the details and we are cautious in doing that so that we don't have 19:08.000 --> 19:12.320 a regulation that we cannot implement technically or we have to invent and the clothes that will take 19:12.320 --> 19:22.320 three years from now to to do it and let me show you sorry yeah five ways of approaching this 19:23.200 --> 19:30.640 one you can download an executable for the wallet and use it as a demo you can have it for iPhone 19:30.640 --> 19:39.840 you can have it for Android and the repositories are the ones here if you die for all our repositories 19:40.400 --> 19:48.240 and then you can see either an app or an SRV for a server or a library depending on our 19:48.800 --> 19:58.160 way of naming conventions this is the wallet solution you can download the app you can change it 19:58.160 --> 20:05.120 you can if you like to customize it for your university for your company for your organization 20:05.120 --> 20:12.960 for your member state and then you have a wallet that is based on the UDI that's the first approach 20:13.840 --> 20:20.320 another approach is if you have already a wallet for any reason that works in any way 20:20.880 --> 20:25.440 centralized decentralized doesn't matter and you want to use all the libraries that we have 20:26.480 --> 20:32.000 you we have a little some little it's the case that try to work as a black box 20:32.800 --> 20:38.880 for qualified electronic signatures or for the wallet itself we call them core and kit 20:38.880 --> 20:43.120 these are naming conventions that you know kit is very popular in the IOS world for those 20:43.120 --> 20:48.720 that know about it they launched it so we said it kit and we have a core and it's useful for 20:49.440 --> 20:55.920 a bunch of libraries so instead of learning all the underlying technologies that are there the 20:55.920 --> 21:03.360 PVCI that people are painfully coding them in our team and painfully working with the 21:04.320 --> 21:08.880 writers to find the best way of writing them we have this middle layer here 21:11.520 --> 21:18.400 the third way is yes you are very welcome to navigate towards the repositories they are 21:19.040 --> 21:26.880 I told you like 70 of them one of them a block of them is about the issuing 21:27.600 --> 21:33.600 we have actually two implementations of the issues one is a Kotlin based it's a default 21:33.600 --> 21:39.520 can work with Java things like key cloak etc that exists out there the other one is Python based 21:39.520 --> 21:43.520 you can find them as running them also you can connect to them to test your wallet 21:43.520 --> 21:49.440 you don't have to install anything but you can also download them and create your own instance 21:49.440 --> 21:56.160 and we have a quite a documentation for that that can help you to run it they are 21:56.240 --> 22:04.480 implementing open ID for VCI they have more than 14 different other stations for different verticals 22:04.480 --> 22:10.480 practically we have most of the attestations that the large scale pilots have not all of them 22:10.480 --> 22:15.520 we're getting there but we're trying to have samples for that right these are all samples 22:15.520 --> 22:22.080 we don't have loss for that rule all these attestations yet in those that we have rules we have 22:22.160 --> 22:27.760 rule books that we can have rule books that can demand how an attestation is made for example 22:27.760 --> 22:34.560 a driving license across Europe across the world it has a specific rule book the passport again 22:34.560 --> 22:40.480 but how you make your diploma in the university it doesn't or the prescription to give you an 22:40.480 --> 22:46.880 idea so we give you a way to accommodate anything that an attestation can be 22:47.760 --> 22:54.960 the support for both attestation formats is there for SDJOT VCI and DM doc 22:55.760 --> 23:02.480 now a second block of repositories have to do with the connection to the service providers 23:02.480 --> 23:07.760 I want to book a ticket I want to rent a house I want to lease a car 23:09.600 --> 23:12.240 you call them service providers 23:13.200 --> 23:17.600 technically we call them also relying partners parties or verifires 23:18.880 --> 23:28.720 now we have the code for the verifires we have a verifire that is in verifire.edu.dev 23:28.720 --> 23:35.040 up and running so you can test your wallet with a verifire without actually setting up a verifire 23:35.040 --> 23:40.800 if you want to set up a verifire we have also the projects for that in the backend and the web 23:40.800 --> 23:44.480 if you want to change that web it's a separate project so it's easier for you you don't have to 23:44.480 --> 23:48.960 change the backend code you use it as an API so it's quite modular I'm trying to say 23:49.840 --> 23:57.920 we also have a registration facility where in case you have a verifire or you want to run a verifire 23:57.920 --> 24:04.160 from our site and you want to be compatible with others that run our wallet you can register it 24:04.160 --> 24:10.240 so that the wallets can use also your verifire the idea behind the regulation is that the wallets 24:10.240 --> 24:17.360 cannot sell data to anyone in order to protect people this means that if a bank asks you for 24:17.360 --> 24:23.600 something the bank needs to somehow get a permission from the member state to allow them to ask for that 24:25.680 --> 24:35.120 it's like not not anyone should be able to get your others for example and we also have the 24:35.120 --> 24:43.360 fifth part block for electronic signers so there is digital signature services yes but we made them 24:44.800 --> 24:51.360 into the wallet so that we want to make signing easy so we want to put it in one place because now 24:51.360 --> 24:56.320 there are wallets and apps that help you for signing there are other wallets for payments and there are 24:56.320 --> 25:02.800 a wallets where you can put your passports and the else probably in the United States but we here 25:02.880 --> 25:10.160 we're trying in you to make them all together in one in an open way so you will see all the code 25:10.720 --> 25:18.080 we have the signers for both wallet centric let's say I have a PDF on my phone I want to sign 25:18.080 --> 25:26.240 that centric somewhere that's the idea we have it full stock wallet service and a sharing 25:26.960 --> 25:33.440 I have a PDF in my server and I want to use my typical qualified electronic provision 25:34.000 --> 25:39.600 enterprise is have that so imagine that okay then the prices do not have the documents in 25:39.600 --> 25:44.720 their wallets right they have them in the server the contracts with the customers the contracts with 25:44.720 --> 25:49.200 other people that they'll business with and they want to sign them and they see you or I don't know 25:49.200 --> 25:53.120 somebody wants to sign this thing he gives the command and gets it back 25:56.560 --> 25:58.400 we have all of these online 26:02.800 --> 26:08.960 a step-by-step for local installation of the apps is available and also guidelines 26:08.960 --> 26:13.680 to choose your configuration option you can see on the left our newest UI 26:14.720 --> 26:20.320 that's available for you and you can this is modular you can use the system to change it 26:21.200 --> 26:28.480 another way to do of course elected disclosure select disclosure is actually possible in any 26:28.480 --> 26:35.360 at a station format that we use it's a thing that we need to have privacy by design therefore 26:35.360 --> 26:40.160 we cannot choose that an at a station in this implementation that will not do select the 26:40.160 --> 26:48.000 disclosure so the users can choose what to share and how of course this is an ongoing endeavor 26:48.000 --> 26:56.640 and it's being improved on the protocol side how to run it in the front end how to run it in the 26:56.640 --> 27:06.640 back end for a component that are using Docker compose links to the GitHub ways of running this 27:08.640 --> 27:15.040 these squares we run in these squares so that you don't have to run it and it has already 27:15.040 --> 27:23.440 all of the self samples that you can use but also sample forms where you can test your new 27:23.440 --> 27:30.640 at a stations or like the idea behind this form is the following is not just to create a PID that 27:30.640 --> 27:36.720 is for Batman or for Santa Claus the idea is to get this and extend it to use it for your new 27:36.720 --> 27:40.880 at the station so for example you're student idea I don't know or you know something else 28:06.720 --> 28:31.920 yeah actually the ARF as I said is ongoing thing we try to formulate an ARF architecture and 28:31.920 --> 28:37.360 therefore we talk to protocols and we change them and we have a photographers group under 28:37.360 --> 28:44.640 in this other checks that we need to get a feedback officially let's say or in a more organized way 28:44.640 --> 28:50.080 to do this but remember we're trying to build something for the next and within the next framework 28:50.080 --> 28:55.280 of three years we're not going to solve things that will come up during that period or after that period 28:55.920 --> 29:04.960 so correct correct I understand I completely understand that the decision is on the member states 29:05.680 --> 29:09.120 so the cryptographers need 29:14.800 --> 29:18.560 but we do we do blog it says the decision of the member states again it's a policy thing 29:25.600 --> 29:31.840 so this must is given by the member states we don't we don't propose this we don't propose anything 29:36.640 --> 29:38.880 I don't want to talk about any kind of policy