WEBVTT 00:00.000 --> 00:10.400 And this presentation, we could talk about free software, computer reuse, and digital 00:10.400 --> 00:14.000 product passports, experiences from images.org. 00:14.000 --> 00:18.800 This presentation is already uploaded in the platforms, so don't worry, because we will see 00:18.800 --> 00:25.000 some regulations that are difficult to talk, but easy to click. 00:26.000 --> 00:32.000 Unfortunately, Felix and Leandro Cudon attend to this event. 00:34.000 --> 00:40.000 And the one that will manage this, we are related to internet-associated catalog chapter, 00:40.000 --> 00:49.000 technical University of Katanunya, this look at it in Barcelona, and also Panzea Association. 00:50.000 --> 00:55.000 So let's talk about, well, let's briefly present the linear economy problem, which is 00:55.000 --> 00:58.000 basically the model of buy-through buy. 00:58.000 --> 01:04.000 We have on one side, problem with too much energy and raw material required to produce 01:04.000 --> 01:10.000 electronic devices and on the other side, what we do with all this erased, here you have 01:10.000 --> 01:15.000 to picture, reflecting the problem, and there are also other problems like 01:15.000 --> 01:20.000 the ability conflicts, environmental impact, and social inequality. 01:20.000 --> 01:27.000 Sometimes, the erased doesn't look like that, they are just usable devices that don't 01:27.000 --> 01:36.000 fit anymore with the first user, and we just need to find the second, the third, the 01:36.000 --> 01:43.000 fourth user, so that means a plan to extend computer devices lifetime. 01:43.000 --> 01:50.000 And that means enabling processes for refurbishment of the equipment, 01:50.000 --> 01:56.000 receiving donations, and moving the consistent towards two second-use, 01:56.000 --> 02:05.000 third, to, in fact, this is called circular economy, because instead of one way 02:05.000 --> 02:11.000 linear economy, we are reducing, trying to reduce the resources as nature does. 02:11.000 --> 02:18.000 And this is also what we are going in terms of regulation, we will see later, and 02:18.000 --> 02:30.000 of course, digitalization improves transparency, efficiency, scalability of the whole process. 02:30.000 --> 02:35.000 So, we see a reuse as an ecosystem where there are device-zone organizations such as 02:35.000 --> 02:45.000 private companies or municipalities that end the first use of electronic devices. 02:45.000 --> 02:52.000 And when we receive these devices, we can get to them a report on social and environmental 02:52.000 --> 02:54.000 impact of these devices. 02:54.000 --> 03:00.000 Then, the social reform pressures prepare these laptops, social reform pressures 03:00.000 --> 03:08.000 are usually involved in labor inclusions, so it is good impact for society. 03:08.000 --> 03:14.000 And then we have community beneficiaries, which could be individuals, organizations, 03:14.000 --> 03:21.000 with a special focus on vulnerable citizens, NGOs. 03:21.000 --> 03:29.000 And that way also we are providing digital inclusion, social inclusion. 03:29.000 --> 03:36.000 So, we, they reuse, this association is developing tools for the full ecosystem with 03:36.000 --> 03:41.000 HDPLB3 license, here is a digital repository. 03:41.000 --> 03:50.000 And as you see, we have a lot of Python usage, we try to have deployments that work on 03:50.000 --> 03:59.000 Docker Compose, which is a way to make it easily reproducible. 03:59.000 --> 04:04.000 So, for example, the first two-warbency script is a small program that is intended to boot 04:04.000 --> 04:11.000 in a device through USB and PXC, in a deviant distribution, and extracts the hardware details, 04:11.000 --> 04:16.000 which we call evidences, and sends them to device hub server. 04:16.000 --> 04:23.000 The device hub is an inventory system focused on reducing computer devices that passes these 04:23.000 --> 04:30.000 evidences and provide insight information, if its accessibility has to manage these devices 04:30.000 --> 04:37.000 in batches to manage the computers to send them to the beneficiaries and so on. 04:37.000 --> 04:42.000 And of course, we also need the ID hub, which is an identity provider that manages decentralized 04:42.000 --> 04:46.000 identifiers and very file credentials, we will see it, watch this later. 04:46.000 --> 04:54.000 And by the secret is like a cryptographical utility that we use in ID hub that might be for 04:54.000 --> 04:59.000 usage to if you have a Python project and so on. 04:59.000 --> 05:05.000 So, this is how it looks like right now device hub, is a tool intended for referral 05:05.000 --> 05:06.000 publishers. 05:06.000 --> 05:14.000 Here we are seeing a batch with several devices. 05:14.000 --> 05:20.000 So, the evidence has got into the device hub, the device hub parsed that evidences 05:20.000 --> 05:31.000 as unique identifiers, as you see, and with that information, we can group these devices 05:31.000 --> 05:40.000 if you want a slots and from lots we can trigger actions to manage the to give them 05:40.000 --> 05:44.000 to beneficiaries and so on. 05:44.000 --> 05:50.000 The other tool I backup in this case, it could manage in general very file credentials. 05:50.000 --> 05:56.000 In this case, this is an example of an organization membership through very file 05:56.000 --> 06:03.000 registry DLT, which is useful for us, because we have like somehow a federation. 06:03.000 --> 06:09.000 And we are allowing this user, with these users that this is responsible of this 06:09.000 --> 06:16.000 refurbishment company with a secret, but this is the bureaucracy part. 06:16.000 --> 06:23.000 But it is very valuable that says this entity is allowed a grand permission 06:23.000 --> 06:25.000 to operate. 06:25.000 --> 06:35.000 So, we have these early adopters, which are Solidansa, Ekoa, Tao, Hachatai, 06:35.000 --> 06:41.000 these are refurbishes from different countries of Spain and Argentina and Senegal, 06:41.000 --> 06:49.000 and I so-called the catalanceptor is using ID Hub, and with all these users help us 06:49.000 --> 07:00.000 to get an overview of what is the usage, the intended usage globally, 07:00.000 --> 07:07.000 and not as specific to a certain country or cultural level. 07:07.000 --> 07:14.000 So, here there is an internet draft going on about operational practices for digital sovereignty 07:14.000 --> 07:20.000 and meaningful connectivity through circular management of user and network devices. 07:20.000 --> 07:28.000 And then there is a transition to the digital product passport, which according to this ETU standard 07:28.000 --> 07:34.000 is a structural collection of product-specific data conveyed through adunic identifier, 07:34.000 --> 07:40.000 which is something we are already doing somehow with what I showed it with the device. 07:40.000 --> 07:45.000 We get these evidences and from these evidences, we say, oh, this looks like this laptop. 07:45.000 --> 07:50.000 Why? Because we concatenate Hachat, we do like an algorithm, and we get a specific identifier. 07:50.000 --> 08:00.000 We can have different algorithms. There is no unique algorithm or identifier for the right now for electronic devices. 08:00.000 --> 08:05.000 But we also need other things, like a trusted product information across multiple actors, 08:05.000 --> 08:09.000 achieving large-scale circularity with ambitions digitalization. 08:09.000 --> 08:14.000 We also need to provide interoperability with open standards. 08:14.000 --> 08:19.000 So, DPP is supported by regulatory initiatives and standards. 08:19.000 --> 08:34.000 The ESPR from 2024 regulated the EU DPP for entry to EU market with the criteria of sustainability and circularity. 08:34.000 --> 08:44.000 And the ADAS 2, which is a continuation of ADAS 1, ADAS 1, was about signing PDFs with key. 08:44.000 --> 08:52.000 For regulation, but now this is extended with a JSON schema where you can put everything in the previous case. 08:52.000 --> 08:57.000 We saw how to grant permission to be operator of this entity. 08:57.000 --> 09:09.000 You also know this because, recently, they are applying this to know if you are more than 18 years old or not. 09:09.000 --> 09:14.000 This regulation is about the identity credentials, verify all registry. 09:14.000 --> 09:18.000 And from there, we get this standardization processes. 09:18.000 --> 09:25.000 W3C finished with the verify all credentials, decentralized studentifiers. 09:25.000 --> 09:31.000 Sense and Alec is doing the process of a standardization. 09:31.000 --> 09:42.000 And there is also United Nations Transparency Protocol, which is doing the UNTPP to facilitate global trade. 09:42.000 --> 09:46.000 So, this is somehow the TPP agenda. 09:46.000 --> 09:52.000 We have the UN Transparency Protocol, which recently got approved. 09:52.000 --> 09:58.000 The UNC Recommendation 49, with detailed specification and a nice pilot phase. 09:58.000 --> 10:03.000 Here, you have the specification, you can see. 10:03.000 --> 10:10.000 And the EU DPP is awaiting this process from Sense and Alec. 10:10.000 --> 10:16.000 And in 2007, we will have the battery DPP. 10:16.000 --> 10:19.000 And from there, we will move to furniture textile electronics. 10:19.000 --> 10:27.000 In this diagram, we can see the whole process from raw materials to repair recycling. 10:27.000 --> 10:34.000 And in the red line is what focus EU DPP is about the product. 10:34.000 --> 10:40.000 The rest is UNTP, which covers the global supply chain. 10:41.000 --> 10:48.000 So, here is our attempt on this implemented this way. 10:48.000 --> 10:52.000 The EU DPP system prototype for electronic devices. 10:52.000 --> 10:57.000 The repository, Docker Compose, reproducible, SAPLB3. 10:57.000 --> 11:04.000 Here, some of the pieces I was presenting before, device help helps on the inventory of the electronic devices. 11:04.000 --> 11:11.000 I have helped for the identity of product and the different actors through verify-all credentials. 11:11.000 --> 11:20.000 And the VLT, the verify-all registry, helps on the public records and through party verify-ability. 11:20.000 --> 11:27.000 So, of course, as we are working in open source, there's opportunities to collaborate. 11:27.000 --> 11:32.000 These are somehow the main components, decentralized identifiers, 11:32.000 --> 11:38.000 about actors' products, models, which is items to this standard from WFVC. 11:38.000 --> 11:45.000 There's also this pre-file credential thing related to schemas, signature verifications. 11:45.000 --> 11:51.000 There's also this thing of selecting this cluster through zero knowledge proof, which is very interesting, 11:51.000 --> 12:00.000 because allows to hide sensitive data, but proof it cryptographically. 12:00.000 --> 12:07.000 And there's also the part of the verify-all registry about how to handle the public records, credentials, and events. 12:07.000 --> 12:10.000 And also how to handle the whole architecture. 12:10.000 --> 12:17.000 We have this building blocks, but how we work on that. 12:17.000 --> 12:24.000 And there's also other features, tools to assemble and generate DPPs from manufacturing data systems. 12:24.000 --> 12:29.000 And publish, search and look up, update, verify, compare, explore. 12:29.000 --> 12:36.000 With the focus on technological sovereignty for SMEs and for local deployment. 12:36.000 --> 12:41.000 Thanks for your attention. Here are all contacts. 12:41.000 --> 12:44.000 I will be here. 12:44.000 --> 12:51.000 I have plenty of time if you want to discuss on anything questions or you want to collaborate. 12:51.000 --> 13:03.000 Thank you very much. 13:03.000 --> 13:10.000 We have time for a question. 13:10.000 --> 13:13.000 Hi. 13:14.000 --> 13:23.000 On your first diagram, you had what seemed to be that you are always recycling the same system. 13:23.000 --> 13:33.000 Do you plan, or do you actually do parts where some systems, when they get recycled, some parts are replaced. 13:33.000 --> 13:44.000 And so the system will become another system with a part, and the part that do not become part of that system. 13:44.000 --> 13:54.000 Do you create a pool of spare parts, because that spare parts is a demand from repair confessed that I get a lot. 13:55.000 --> 14:04.000 Here I don't have, I just have this screenshot, but when you click on a device, you can see on the components. 14:04.000 --> 14:12.000 They are evidence. It's just few programs that do discover all the hardware in the device. 14:12.000 --> 14:18.000 And right now we are focusing on how to just handle the devices entirely. 14:18.000 --> 14:24.000 But of course, the refurbishes, each refurbishes do the way of. 14:24.000 --> 14:33.000 One, remove the hardware, destroy, change it, automatically or replace some parts within the process. 14:33.000 --> 14:37.000 And we are just helping on their task. 14:37.000 --> 14:41.000 So of course, it's not just the whole device that should work. 14:41.000 --> 14:47.000 We have different components, and we would like at some point to get also the responsibility of a component in different devices. 14:47.000 --> 14:50.000 And so on. 14:50.000 --> 14:51.000 So. 14:51.000 --> 14:56.000 Is there another question we have time for one more? 14:56.000 --> 15:06.000 Um, at the moment.