 So, welcome everybody to today's webinar on the live demo Open Pego Choken. I'm pretty pleased to welcome Dr. Nicolas Mokisa and Alain to our today's webinar. Nicolas Mokisa from the ANUIA will give a short introduction on ANUIA's work and the importance of the today's webinar. Later I will give a short introduction on ANUIA's foundation and what the Open Pego Choken has an importance of the sector and why it's important for the intentions today. And then Alain will work through a live demo covering some basics on the Open Pego Choken and also showing on the live screen, sharing how to set up the device. And so you are welcome Nicolas to to present yourself and then we are welcome on stage. Thank you very much Vivian. I'm as Dr. Nicolas as you've highlighted and I'm glad to be on this platform to share with the different private sector players what you know it does and what we envisage in this partnership. I've arranged this organized this webinar to give an opportunity to in access to share some of its works on Open Pego Choken. ANUIA's role is of course to consolidate and mobilize private sector players to see how best the sector can grow and ensure that our end users create the very best of the energy and energy efficiency services. And I have to record that as you go as played a tremendous role in energizing and electrifying Uganda. Today as a country we pride in about 57 percent electrification where about 38 percent is through off grids and mainly the off grids I'm looking at a standalone system plug and pray which have been mainly marketed and costed on the basis of pay as you go considering the income rates and cash flows of most of our people in Uganda and Sub-Saharan Africa at large and it's no secret that pay as you go has played a tremendous role in electrifying Sub-Saharan Africa given that Sub-Saharan Africans their base income base is low so they really want to you know spend less given that they also earn less so the record is good that pay as you go has played a tremendous role but over time I think in the last couple of five years pay as you go has had as stagnated to a level that since 2016 you've only recorded a one percent increment and you've noticed that some of the big players have transitioned from Taiwan solar systems and gone for higher level systems but have also shifted from some have shifted from business to from the low-range to business to business category. Others have completely exited the market and have gone to telecommunications and now they're into phones so but we believe and still think that pay as you go as a road player I also have to mention that at the moment the World Bank is working on a pay as you go toolkit which was drafted for a couple of developing countries where in Africa we have Uganda and Ethiopia the draft was passed last year and at the moment we're undertaking a testing stage we are the testing stage of this toolkit the testing stage is meant to end in next year in March and thereafter we'll start piloting so I believe that this webinar comes at a very critical and timely moment the people can better appreciate pay go and how best to incorporate it in their business models so I don't want to take much of that time I'm glad to be here but also welcome all that sector players that are joining in and those that will be joining over time take this opportunity to learn and see how best they can market and sell their products using pay as you go thank you very much Vivian thank you very much Nicholas that was interesting and I think a great framing for today's webinar and also putting the importance on pay go technology and systems in general for for your businesses and for the electrification sector um so very happy you you joined and we are able to do this webinar together um so let me now introduce the an axis foundation um we are the an axis foundation and we stand for open innovation for energy access um this is because and why are we doing what we do and we believe in open innovation because achieving universal energy access which is the sustainable development called heaven the united nation that it requires a lot of new innovation and approaches and to achieve it because it's an sector and the business that hasn't been done so far extensively and so the energy access organizations companies and governmental players engaged in in energy access generally there are very scarce funds to develop these innovations scare funds and time um however a lot of these innovations are just reinventing the wheel so instead of being able to focus on actually connecting ad customers and bringing electricity to the people tier one to tier three to four or even to a tier five they're whether concentrated on finding technical solutions or tweaks to get their business running or the system but all these challenges they are facing in this week they are doing solutions they're way too often pretty much similar or exactly the same that other organizations or their competitors already have developed um so this is um what we want to achieve in the sector so is to promote the development and adoption of open source innovation um this to build an equitable ecosystem which also allows local companies to take part in achieving universal energy access for all um and this is the we are driven by to believe that only by sharing these innovations as open innovations we can create this ecosystems provides the basic tools and everything what is necessary to actually be able to concentrate on reaching ad customers and not sitting in our laboratories or in offices and everybody reinventing just the same solutions for exactly the same problems um and we have three main arms which once we do it we support we curate we promote our support um is based on a financial tool where we identify technologies or tools or business models or approaches um which can disrupt the sector and have the potential to benefit all or main or at least a lot of players in the sector and and we support this the development of these solutions of these innovations financially and uh we are also hand holding in the in the development process and do a lot of promotional work in the adoption process and also additional technical developments if needed and at the next we also maintain a creative repository of high quality open source innovations and and we select them properly and and we curate them over time and to allow energy access companies to to go in one place and find the solution they need but open source and adopt it so their needs and we as a third part we do a lot of promotion for open innovation general in the sector it's not only our financial support ends up innovations but also other companies independently from our support do open innovation and do information sharing and technology sharing and there are other players doing open innovation and we believe there's still a lot of learning on all sides on the company side on the donor side on the public side and to really leverage the potential of open innovation and so just to give you a brief on on what we have done so far and you can generally put them in three sections software hardware business models even though the word business models might also be a concept or financial tool and so let me start from the top so software today we will talk later about the open pager token so I won't say too much about that and then we also finance the survey tool kit developed by devg which is a toolkit to allow to survey rural areas pre electrification so when you want to do an expression for the tool and open source tool to help you to do the survey then there's an air link developed by steam or solar which is in relay extension based on bluetooth to allow iot communication in remote areas where there's no 2g or 4g coverage battery management system for lithium ion batteries also yeah you see it's already hardware software because there's hardware piece but also software piece then cicada modules for wi-fi and also 3g communication which allow like to plug in on your already existing device and extend them to add in wi-fi communication or gsm communication further on an open smart meter which is also going more and more to the hardware part it's a physical ac electricity meter with iot communication for mainly ac minigrids and the steering initiative which is a software piece but it's mainly a model a business model and the financial tool which allows to monetize the renewable energy production of decentralized energy systems which was so far only possible for bigger utility scale or c and i scale energy systems but now also even a mini grid or possibly also solar home systems can monetize the renewable energy production on a certificate market and aggregate which is a business model which integrates electricity sales this agricultural preprocessing on on the local side to keep more of the value chain and yeah of the value generation on site and not in the urban areas or urban areas all that are projects we have funded and which are open source and openly available on our site and so yeah open paygo token let me say a few words about open paygo token to give you the introduction and what is so great about the open paygo token so in the past devices and custom and the device of customers we're often locked in into one open paygo provider platform because there were different token systems and paygo token systems which were in place and each provider had its own so this caused a lot of trouble and and like delays and additional costs for distributors which had like to integrate with when they integrate with one they had to decide where I want to integrate with another one because it's additional development work and manufacturers often had to have like stock of the same product just like integrated the different platforms and and it's all created like a lot of unnecessary costs to the industry and yeah there was a missing interoperability and so how it worked so I was often came up this one of the loan providers that we have the idea to make one open token an open token system which then can be integrated by everybody in the sector and then we quickly decided yeah we finance this project we saw the potential this can be disrupted we financed development it was developed in five months and just two months after completion the three main or three three of the main loan providers integrated with with each other and met each other interoperable so paygo ops, agent and gather and very quickly a lot of the manufacturers were automatically also integrated with all of these platforms so there was not one device which had to integrate with all of the planet integrated with one it was automatically integrated with all the other platforms and which say until today a significant amount of money to the whole industry so today there's an easily implementable paygo token system and how easy it is you will see just in a few minutes which is available and widely interoperable in the market already and Nexus still works on maintaining and helping maintaining also the developer allows of it still maintaining this platform and this project and we help and we are still promoting it that's also why you are here with us today and we show how great this token system is and how it can be beneficial for your system for your business and you you will learn actually an alive demo how to integrate it like really hands on so I don't want to waste too much of our time and leave the time to the real application of the paygo token to learn more about the options you have and how to integrate it to your system and yeah but let me say that open innovation in energy is a pathway to success we are convinced by it and that's why we are then access bring open innovation to energy access and that's why you are sitting today on this webinar and we'll now have the chance to listen to the live demo and I hand over to you for the presentation and I believe we all got enough information enough information from it now it's time we look into the open paygo token yeah but before starting just to recap the open paygo token is just a way to encode a value into a token on a server then entering the token on a device using the keypad to check if the token is valid then use that value accordingly so in this session before diving into the code we'll be talking about the different key components that are needed in order to use the open paygo token but also we'll talk about different modes that can be used while generating the token and then we'll see how we can set up those devices like the different parameters that are needed to set those components so in order to generate a token we need a server which can be any software provider or any custom product that any every manufacturer would like and this is where the token will be generated and then that token will be entered on a specific device and those are the main components that we need we need the server and we need the device and the device will have any keypad and then we'll decode the token and then it will use that value and while generating the token there are two different modes that can be used we have the set time and add time add time is used when you want to add time to the current value on the device let's say you have three days on the device and you add two days which means at the end of the day you will have five days left and set time is used when you want to set the time on the device to a specific time let's say we have three days and then you set time to one day that means at the end of the day you will only have one day left and in order to set up those components there are different parameters that are needed let's start talking specifically about the server we need the starting code we also need the key this is the key that is used to encode and decode the token so it's it's important to remember that while setting up the server the key should be encoded in exaggeration format so we'll see it also in the code there is the time divider which is the division factor that is used on the value this one comes in handy when you want to use like a value let's say you want to use a token for just a number of hours instead of the whole day you just use a number of hours and then we'll use the time divider there is the the secret digit mode and this one if it's set to one then the token will have a digit between one and four otherwise you'll have digit between zero and nine which means like this one is useful depending on the keypad used on the device if the the keypad has only four digits then you will use this one then on the server we keep also the count and this one is just a value that keeps on incrementing whenever a new token is generated on the server when you generate a new token the count keeps on incrementing same thing for the device but here let's see we need a serial number or this one is not really used during the token generation but yeah we know that it's important for even manufacturers to handle serial numbers for their devices we have the starting code as well we have the key which should be in exa decimal format we have the time divider as well and we have the secret digit mode and we have the count and there is also the test code this test code is like after setting up the device let's say you want to test it to test it for a couple of minutes for a couple of seconds that's all that's where this one will be used in every manufacturer we'll have their own way to implement this this use case so as we just talked about the parameters now I think it's time we see how we can use we can use them and how we how quickly we can generate the token using the openpego token so yeah the openpego token code is on github you can find it there and you can clone it you can also download it and then use it in your device and on the device and on the server and it has also some information that might be needed also it contains also documentations that will be that will be useful and in my case I've already downloaded the code as you can see I've already downloaded the code and I've also I assume that my device is ready and my server is ready so that I can go straight to see how we can generate the the token as I mentioned earlier it's better it's important to remember that the key should be encoded as hexadecimal so that it be sent as byte so probably in teams might store it you might want to share it as a string but then while setting it on the device or on the server it's better to encode it that's why you can see I did it as well now um let's try to run this code and see as we can see my device is up and running and my server is also up so um which means we can proceed and then we start the first the first process to generate um to generate the token so um let's let's go on the server in the create the a method to generate um to generate the token um we'll be giving it a value that we want to decode to to encode in the token and then um we'll pass also the mod as I mentioned earlier which can be either add time or set time and uh in order to decode to encode the token we'll use the encoder which uh which has the functionality to generate the token and then we use the method called generate standard token um this method uh needs the starting code so we pass the server starting code it needs the key which is the server key and uh it needs the value which means like the value that we want to encode into the token it's need the count which is the server count in order to keep in to increment the count on the server and uh it needs the mod so we pass also the mod that we'll be using and the restricted digit set to make sure that we generate token uh depending on the device for each device yeah and uh the generate standard token returns uh two different values we have the the count it returns the count so we need to update we need to update our server count and it returns also the token and uh let's also return our token that has been generated this uh this function will generate a token let's see if we can get it so we go on the server then we generate the token let's see if we pass um five as value then the mod um the open prego token code base has uh some shared values that uh will be useful once it comes to the mod and from there you can it's try to use the first one uh token type then we use the add time uh then let's print our token if you run the code you can see that our code our token is being generated so which means everything is good now um the remaining step is to decode to verify it on the device and then use uh use that value on the device so let's go on the device and write another method that we use to to decode let's say after the user has entered the value using the keypad and then you want to decode it on the device um let's say it's called token so um it will be receiving the the token itself okay and now um in order to decode the token we this is we'll need the decoder from the open prego token then uh get activation value count and type from token so um this function it needs uh the token and it's need the starting code so we pass off the device starting code then um we pass the key which is the device key and we pass the it's need also the last count which is the device last count and uh it's need the the so this is just set which is the device a few digit mod and uh the used uh use count um normally while configuring my device I created the separate a list that will be tracking all the used count and they used uh token so that in the future to make sure that if your token has already been used we don't use it anymore uh the decode decoding the token uh will be able to handle it so this that that that will be the use of this used count so we pass the use count there then uh okay yeah I think that's it so um the get activation value returns three different values we have the token value I mean the value that has been recorded in the token and it returns the token um token count and it returns the token type yeah and it returns the token type now um after decoding the token you need to check if it is valid so if the token is not valid or if the token is not valid the token value will be none so that means like if it's not there we just say that uh it's invalid and we can return felt and then every manufacturer will have their own way probably to prevent the user from entering uh invalid token over and over again and then you can handle it in this case then the next thing is if a token has already been used then the token value will be equal to minus two so if the token value is equal to minus two that mean like the token has already been used in the past so we can say it's an old token and then um um otherwise it means like everything is good so we can proceed and use the value as you want on the device for example in my use case I was encoding let's say five hours I'm coding days into the token so um let's try to use the value that we have on the device the first thing that we will do is to make sure that we are placing also the count on the device to make sure that the server and the device are synchronized so we give it the token count uh the second one is uh we will update the uh uh the used count to make sure that after using this token we don't use it anymore and to update the used count there is a function in the decoder that will help us to do that so that beta use count and what it means is just the past use count so we pass the device use count it's need the value which means like uh the value that we got from the token and it's need the new count which is the current count that we we got from the device from the token all right now um we have updated the count and the used count now let's try to use the token uh you know you know in my use case I will be setting um the expiration date on the device I will be setting the expiration date on the device depending on the number of days that have been used so um I'm going to to create just uh another method for that and here I will be passing the token value and and the and the mod to make sure that I handle the both cases correctly and um the first thing that you need to do is to get the the number of days in my because as I mentioned we are using the in my in my use case I'm using number of days and here we have the token value and remember to make sure that you are getting correct number of days this is where we'll use the the time divider uh to make sure that if uh I want if the time divider is two then we divide the value into that was encoded by two uh then here the next thing is uh to to use the token depending on both use cases uh let's start with the if it's set time so we also use the shared values um we get the token type and set time yeah so if it's set time then that means like I will just uh update the expiration date on my device to um to the current the current date then I I add the new number of days uh otherwise I mean we are adding then uh we say we just say expiration date is uh so we get the current one and we add we add this and uh sometimes the um expiration date might be already in the past so it's better to make sure that it is updated so that we have we have collected value that's why we we need to check if if it's already in the past we just set it to the current one yeah then uh this updates device status will update the device will update our device and we can use it to make sure that so we give it the token value and we give it the token type okay now uh one thing that uh for God to mention is while decoding the token you need to change its type to uh to integrate because when you when you generate a token it's returned it's being returned as a string so when you want to decode it you need to change it to numbers then you can decode it now in our test code uh we have our token here uh let's let's use it on the device and see what what will be the output so um let's also let's also uh get the status of our device and the server as well then um now um this is the initial status here we generate the token and here we decode it we're using it on the device and let's run the code again okay we are having a exception okay saying that the decode uh we didn't pass the type on the update okay yeah if i got to pass something uh on the update just count so we pass the token type that was used now uh we run the code again yeah as you can see um initially our expiration date was set to today uh the 15th and uh after decoding after decoding the token it is now set to the 20th which means like the token was used correctly and the value which was five days was also uh used was also decoded correctly correctly and the value was used to set to to to set up to be set on the on the device now we did an implementation to see if a token cannot be used let's see if it's it's working so let's just say device dot um decode let's try to decode this token twice and see if if that's implementation is working as expected yeah as you can see here at the end we have an old token which means uh you cannot reuse a token uh twice or more than once i mean because uh the token value is being returned uh this is uh the value is minus two and our code is working perfectly yeah this in short how quickly you can generate a token and decode it using the open bigger token without having to handle the code yourself like writing the the the the implementation yourself just by using the code that has been shared and if you want to learn more about how you can use it and how you can set up different things on the device in the code base there is a directory called simulators and there we have a device simulator which has many other advanced functionalities that you can also set up on your device same thing for the server it's also has some many advanced functionalities that you can also use on your um on your on your server just in the code base you can check you can check them it's also has some examples and it's also have some tests that you can check and um while implementing while implementing the open pago token if you need help you can just go to the open pago website and then in the documentation in the documentation section you just go to the outlaw some free help in there and access will reach out to you for help thank you everyone we just talked about the different components that can be used I mean the device and the server we just talked about the different mode that you can use while generating the the token but also we just saw how quick and easy it is to generate a token and decode it on the device thank you everyone thank you uh allah this was great and very interesting and insightful um and I bet I mean it would be necessary for for most of us if we want to implement to have a screen record but we have a screen record um of the whole webinar and and thank you for the very detailed way to structure it how uh companies could use it what other features and showing step by step how to do it in the code in fact and so what brings us to the Q&A uh there were already one or two questions which went through the chat but I invite all of you to post questions um you are free to post any like very technical questions on the coding which you just saw from allah on possibilities to use the open pago token experience with the open pago token um also on in access in general or on unreal um we are here to answer your question we have also the pleasure to have somebody from solos outfits uh here the developer of the open pago token if you might need his assistance in answering some questions um maybe let if there are no further questions so far um let me go to the first questions which were answered um from allah there are two questions I believe the first one is directed to us for me uh an access foundation um we have funded one um electricity meter it's what we have funded one ac meter it's a conventional ac meter as it's used in also utility grids um it has a keypad so uh pago enabled um it's not the open pago token so far because it's energy based and not time based um but we are working on this integration and yeah it's designed for single phase ac energy measurements um and this is the one open source electricity meter that we have funded you can also find it on our own page same as the open pago token there you will direct it to the github um and you find the hardware and software uh you need to build it and set it up by your own and now the next question from allah um for wiktron what is the biggest system you've worked with uh I'm not sure to whom this question is directed uh I guess what does meant is what is the biggest big trans systems where open pago systems or pago capitality have been integrated um there's something I'm not able to answer as we do not do the integration with sometimes assist in the adoption process but we don't do it by our own we have financed the open pago token um I am I don't know if Nicholas you are possibly aware of some of your members that have done this exercise if so you're you're happy to answer this question otherwise we will follow up on the question in the aftermath of this webinar thank you Vivian uh I don't have any one in our among star members that I know of that has done this integration like you've elaborated because most of them these are private companies that uh contract different service providers so at times you you don't uh you don't get to know that information that behind our information that they involved in so since we do not necessarily develop some of these systems or uh softwares we're not trivial to such information unless an individual company either any of the representatives on the call could disclose such information but uh would you not have that information at our site okay thank you Nicholas I just saw that cloud you from so now it's off with the developer of the open pago token and said in the chat but I also invited him on stage to possibly just quickly answer this question like directly yes uh from what I'm aware of Victron integrated it with in its I say it says 200 200 meaning 200 as input power and it's integrated in in this in this system so this is the the the knowledge I have about the this integration okay thank you um there this I think this answers the question quite like specifically um now the question is of how much of this process of the pago integration is free um so let me take this question first um your mic is off oh my mic went off um I'm sorry and so Steven your question on how much of this process is of the open pago integration is free and I mean the code is freely available and it's on github you can go there directly on github you can find it through so now it's off but you can find it through our page you can download it you can use the recording of this webinar to get some insights how to do it and they are also quite a big community around it which helps and helps help with a lot of troubles that people had it's well documented so far um you can also reach out to us um if you need additional help besides everything which is already available on the how-to and documentation on the github page developed by Solaris and this webinar for example um and the chats in the community you can find um and then if you need additional help as Alain showed in the very end of system presentation you can always contact us um and we can figure out there is no fixed number it will a bit depend on your background we obviously expect like that you have done the minimal effort on like looking what is freely available and where we can jump in to do the hand holding and provide some additional resources um but if you have a software development background or you have access to you should be able to do it mainly by your own but yeah there's also help available from our side and which we are happy to to provide um I hope this answers your question Steven just starting one thing here so we had many companies integrating this open pay go token and most of them they did it by themselves uh both in the server side so using Python and on the device side uh using well cc plus plus um some other companies maybe they needed help so we provided help on a consultant consultancy basis as well so paid by the mandate and we provided support to to help this company integrating their token into the device yeah thank you Claudio so yeah there's also Solaris always to help but yeah you have decided how much you can do by your own how much we as an axis can can provide as we help and how where you you need to allow us to come in or not this um yeah it depends on each company and their background and their and their know-how um on I have a question to you Ella and we we especially also have to say we did this webinar also with a third party developer who's actually not from the energy sector nor has ever worked with pay go systems or the open pay go and we specifically did that to show it's doable and and we yeah we asked him to do this presentation to just go on the page go on the github read the documentation download the code your software developers so this this is quite kind of a prerequisite to do it but then you should be able to set it up um but still I mean we are always looking into how we can do things better um is there any improvement that you could would suggest um like on the coding where you as a software developer are if I could and I've infinite time or so on I would improve this part on the documentation right there oh there is a thing that maybe should be explained better put it another way so yeah we are we want to improve it's an open source project ideas like in the community make the things better so do you have any of those recommendations maybe yeah um thank you Vivian so uh personally after reading the documentation first of all I was new to the pay as you go business model and everything so I got introduced to this thing by inaccess so after reading the documentation um and I started like using the code it was not like straight forward for me I had to go through the code base itself so that I can see how I can implement it and it was not that hard because there are tests like there are some functionalities you can just as a developer you can just go then look at the function say oh this is how it's working this is how it's done so that's was one thing that's here what can help me which means on the documentation side uh what I would recommend is to have a separate documentation mostly for developers on how they can set up let's say a device so now they can set up a server for example that thing of encoding the token in hexadecimal finding it was not easier like I had to look into the implementation see this is what they need then that's how I found it so having a separate documentation for developers that will be really helpful but otherwise just by looking at the code and if you are software developers most of the time you you will not be lost okay this is a great feedback um and thank you and as I said yeah we we always try to improve um yeah the open innovation that we have funded and I guess also Solars is also doing some improvements and okay there is a new question by Dorothea um which devices can easily be integrated to paygo in general um I will give it a first shot and then possibly invite others to also answer this question um basically you need some basic intelligence of the system to switch it on and off um but the idea is that any device like which is like electrically run which kind of palm but fridge in a tv solar home system um can be integrated with paygo I mean dependent on what the hardware is you need to add some additional hardware and some of you maybe just need to add a keypad um because the rest of the hardware is already inside um and for this it would take a bit more hardware modification to make them paygo enabled um but yeah besides that I believe that pretty much every electrically run device could be paygo integrated but I maybe leave it to Claudio or to Nicholas to maybe give some other insights on that now as you as you were saying Vivian uh it's uh as you say so any device that has an input method to enter token can be uh may pay as you go enable so can be a tv can be a fridge can be a solar home system mobile phones do and tablets we have some companies integrating open paygo token into their mobile phone and tablets so uh the mobile phone cannot be unlocked unless you you enter the correct password the correct token and so yes it pumps as you said so many appliances out there can be used uh under a pay as you go lease basis um there are certain specific minimum hardware requirements like having a microcontroller with an app memory uh switch to switch on and off the the power lines uh an input method that can be a keypad but also can be we have um integrated with companies using IR receiver so with um with a remote controller like in your tv or a bluetooth mode gsm activation based wi-fi so many different input methods can be used well of course the keypad is one of the cheapest and most used because you don't need to rely on on external connectivity or external uh modules let's say the keypad is integrated so you don't need anything else okay yeah thank you um so there were some more technical insights on on the technical hardware requirements you would need um so i have one more question through a line that i also have one to nikolas but let me first go to the one through a line when i would decide as an energy exit company to do that okay i want to use an integrated open paygo token in my system like the very first step i mean you showed the github and you showed our page but what does like the supposed to be the first document or the first thing you would suggest to read as and i asked this question particularly to you as you had to start from scratch and so do others so now that you have done it what would be maybe the first document or the first page you would suggest somebody to to look at okay um just by going to to the github to the github repository there are uh two two documents the first one is the general documentation and the second one is the example implementation the first the general implementation is good because it has um like uh many details on the open paygo token like it contains like its details it talks about many things in two details but then if you want to uh to see some other technical things you have to go into the example implementation because uh that's where they mesh although um it's uh uses the it uses the one built for c and c++ something like that but there you will find some uh some technical um examples and uh technical documentation that would be useful so keep it at yourself with the general documentation then you go to the to the example without forgetting reading both it's really important okay thank you ala i think this is a good hint for like adopter for the first steps to follow there's a new question from a legion sorry i'm sure i haven't pronounced my word but i tried um saying i'm new to this topic found it very interesting this is great so we did something interesting i'm happy about that and just want to know how secure is it um i believe there are like two ways to understand the question the one is security in terms of tampering so i have a paygo device um delivered to somewhere and how am i sure that it it is in tampered and just like overrun the the paygo um capability that i've integrated and the other one possibly like the software and data security uh one um i believe uh this year as anas also saying in the chat um that alan or claudio could enter i i believe that claudio uh maybe in the first try and then alan maybe from a outside software developer view you could give like your insight on security of the code and yeah would possibly be interesting uh yes uh sure then the token as alan was showing is encoded or encrypted uh and then decrypted in the device uh so to encrypt the the token you use a 32 bit a 32 digits uh key um in hexagresimal format the encryption method uh it's uh well as h24 so it's quite complex encryption method and the the entire encryption and decryption mechanism is being audited by an external security consultant you have all the documentation in github so you have the report from the security consultant and uh who has an extensive experience in cryptography and communication protocol and he says uh is approved so it's secure to be used and that's why also many companies well some companies they are starting to get open paygo certified so we have also a certification uh for the open paygo token integrated devices and some of the companies they are listed in our website they have the open paygo certificate certificate that they can display uh meaning that they are compatible with the technology and and they feel safe use thank you claudio i don't know alan is there anything to add from your side yeah so uh on my side uh as a developer you know like nothing is secure at the 100 percent but it's important for developers to remember that for example we talked about the key so you have to make sure that that key is secured like you can share it with anyone for example the project is open source so uh your device code should not be open so you should not push your key to github something like that so you have to make sure that uh it's secret it's not shared with anyone but also something else that i can suggest to developers is when you're setting up your device or the server uh you should be able to update that key later let's say um someone got access to the keys and then uh uh they will be able to generate different tokens so you should be able to have invalidate the old token and use the new token those are the two things that i can not sure it's come to security okay thank you alan this was helpful and i guess and i hope we answered Doris's question well she gave us a this one i guess this means yes and it's a shame we lost Nicholas already he said he had to leave sharp um not two minutes before i had a question to him but um this question i can also make to the ordinary um before doing this question i just want to um go on the pool so i'd like the pools like the one about have you software development in-house there's not too many so this may let's make the next question and if you would be interested in the software developers so how to set up open pager token there quite a few so as we said on our page you also find this unit i need to help an integration button click it and then you will be directed to inform to like request help from our side and we're more than happy to provide that and as i said it depends on how much help you need um and the last question is related to what we actually do we apply we fund open source innovation for energy access so the question you don't need to answer now but take it home is do you have any uh innovative ideas or which are sector building ideas which can be used then more than by your own company but sector right for other companies even your competitors but you believe that would be good to achieve universal exit to energy quicker and would have would like some money to fund it and you are open to make it open source and willing to make it open source as the open pager token is then check our page and apply for funding and yeah we are happy to evaluate your your ideas to hopefully and fast trick access to energy much faster than than we are doing so far because we won't meet the goal but we want to and so thank you you were here and now it's 10 oh yeah for the ones in eastern Africa it's 12 for the ones in Europe it's 10 and and for the others somewhere else in the world it's another time and thank you you joined um Nicolas is back but yes as we are um already run over the time I believe we should close but I would like thank you to Nicholas thank you to Claudio thank you to Alain is there any closing words you want to say Nicholas I'm not sure he's hearing me so then I will close it thank you for attending this webinar and see you soon in one of our next webinars and thank you for all people on stage today goodbye yeah goodbye thank you thank you bye bye