 So, hey everyone, I am Amit and this is my final presentation for this mentorship season. This is my introduction. The project that we were working upon was global scouting of distributed ledger technology of blockchain educational opportunities. I am Amit and I also had a fellow mentee with me, also a friend, Zhenming Yang. He was unfortunately got into a car accident and could not complete the whole internship for the second half. So, these are my credentials. I am from India. Zhenming was from Taiwan. We both have Alfonso Gauval as our mentor, has been extremely helpful, he has huge support in completing this project. So, let's talk about the project first. So what we are trying to do is create a community of people who are actually interested in learning about blockchain and D&D in general. We expect to create some sorts of tools which will help people in order to learn faster and overall decrease the whole barrier to entry for the blockchain community. We expect to create a knowledge graph and a taxonomy as a tool. People will be able to learn from these tools and help curate them. So, as you learn, you find out new resources and you will be able to add to this taxonomy as well as knowledge graph. We are currently using Neo4j database to host our knowledge graph database. We are also creating a website using Next.js. It's a React-based trainbook to enable everyone who is trying to interact with the knowledge graph to be able to interact with the knowledge graph without needing to know about Cypher query language and stuff like that. We have also created crawlers using Python and Coly like inside Golang. That was done in the first half of the mentorship period where Zhenming was also there. Zhenming worked on Cypher and Python and I tried to create a Coly and Golang crawler. We would use them to crawl data and data from the websites that permit it. We are trying to currently make efforts towards creating a thriving community for people who are willing to learn more about distributed lecture technology as well as blockchain and also people who are willing to teach others what they have already discovered. The objectives of this project were five core activities. First of them was taxonomy for educational opportunities. It's a list of basically educational opportunities. We would have questionnaires for meetups, special interest groups and working groups. We would also have a web crawler that would be helpful in scraping and crawling websites which are considered as learning resources. Then we have Q-ratorship, which means people should be able to add and interact with the database that will be creating or the taxonomy that will be creating. And also at the end of it, we like to have a knowledge graph of the taxonomy. The idea of knowledge graph was actually suggested by Zhenming in the start of the internship. So the project derivatives, the ones with the green tick are the ones that have been done and the ones with the circle are the ones that are still left. This was because Zhenming was not there for the second half and I had to take all of the responsibilities, so I volunteered for it, but we are still on schedule right now. So right now we have a simple but a strong representative version of the directory and we have a taxonomy of educational opportunities specific to the DLT. We also have a small but geographically extended community of people who are willing to contribute to the knowledge graph. We are working on creating a basic set of tools to support collaboration which will be hosted on a website. The website will basically contain a knowledge graph and the taxonomy and the interactive features that would be implemented inside the website. I'm working on also creating a final report and a series of blog covering the process that I went through within these three months. A half of it is done and some of it is still remaining. So I'd count that as still to be finished. And in the first half we created web crawlers to help people find opportunities faster. So project execution and accomplishments. I think I basically covered that in this side but we have posted a knowledge graph on the Neo4j Aura. What is Neo4j Aura? It's a cloud distribution for hosting the Neo4j database. We have created a visualization for knowledge graph that will help people to interact with it. They have also created a taxonomy which details everything that is contained within the database in a neat manner and in a neat format so that computers who will be scraping our website will be able to access all of that information programmatically. We have also conducted questionnaires asking people about their opinions and if they would be willing to contribute to this project. And we also gave a meetup talk, the hyperlogist and then the meetup talk about this project. I and my mentor, both of us were able to get that done. So this is a, okay, so these are the deliverables. I will now share the stuff that we have accomplished through the mentorship period. This is the survey. This was actually translated in 11 different languages with the help of translators within the hyperlogic community. But a big shout out to everyone who did support us to get this done. It was very, I'm very thankful for everyone who helped me translate this. This was in 11 different languages. These are the insights from those questionnaires. And the biggest insight here is that people mostly prefer platforms, third party platforms like Code Academy or Dapp University. And 20% of people prefer YouTube as a learning resource. This helps us to, in future, we'll be able to more specifically target these websites and YouTube to grow our knowledge graph and grow our taxonomy. This was the first version of knowledge graph that Zhenming was able to create. Later on, I used that to create a bigger knowledge graph in the second half of the internship period. And right now, this is the version that we have. This is the visualization that will be hosted on the website. This is a development sample right now. I'm still working on it. A bit of features are still to be implemented. This is an interactivity feature where a person will be able to prune and navigate the knowledge graph to his choice. For example, let us say, after this internship period, I'd be willing to search for jobs. So this would help me look for what kind of jobs are available in the blockchain community. This is a taxonomy visualization sample. It's very big and it's not really readable. So I'll just skip this. This is the front page for the website that we have. This is also a development sample. I have not deployed the website yet. I'll get to why I haven't deployed it right now in the later period. So these are recommendations for future work. Curatorship projects, basically adding more data to the knowledge graph and curating the existing data that is already present inside the knowledge graph. Adding badges and token systems to gamify the process of adding resources. So this was something that Alfonso and I discussed upon during the internship period and we decided that it would be a better thing to put this as a future project, a future implementation that we could work upon after the internship period. Improving documentation, we can improve the documentation for the project website. I have implemented some level of documentation, but it's very crude and I won't be able to basically flush it out with all the details I can. So obviously there will be some room for improvement and documentation. Add better search and filter support inside the website for knowledge graph and browsing the axonomy. And even in terms of accessibility, I think we'll be able to do much better. One thing that I'd like to personally say is that we should migrate to TypeScript, but I have not had the time to do that because there are several benefits for migrating to TypeScript and this is something that could be a project in future. There are also accessibility improvements and internationalization support for the website because the blockchain community is widespread and throughout the world people should be able to access the website in different languages. They should be able to basically interact the website in a more versatile manner. We should also look into schema.org and their formats. This is something that Alfonso was kind enough to tell me about. He said they should be able to stick to this format, but I'm not sure if we can do that within this internship period. So that could be a future project or a future improvement. These are the project output and results. These are basically links. There's a disclaimer. I'm still in the process of completing the code for the website. I have not pushed it yet and pushed it as in like pushed my commits to the GitHub. The final deliverable for this website I was thinking would be between the 26th and 30th of August. This delay in schedule is because of the unplanned and unfortunate incident with my friend and fellow mentee Chenming. I did say I will take all of his responsibilities and deliverables and then plan ahead and we are still on track. But it's just that the plan that I had made was between 26th and 30th. So the insights gained. First thing that I'd like to say, which I encountered in the development phase was things will break and things will break very fast. Everything that can go wrong will go wrong. So there's needs to be a specific mentality to follow that things will break and you have to face them. Second insight was that availability of the resource is not the same as accessibility of that shared resource. A lot of learning material is available online, but it's this show is a need to be more accessible in terms of availability. Like it should be more accessible to more people. If a person cannot discover that resource, it's not very useful. The third insight was that open source is much more about the community and communication within the community than just about writing code. This was something that I learned during this mentorship period. Earlier, I just used to think that it's just code, but I was proven wrong. Fourth insight is that opinionated libraries and frameworks are not bad. They are just designed to solve very specific and niche problems. Once you understand why that library was created, for example, Neo4j, you start to vibe with why they handled things the way they have done it. And the learning curve for every project that you take should also be factored in when you're choosing your text stack. This was something that was brought up in the last meetup for Denvo. And I tried to think of ways that can do with the barrier for entry for developers when they are trying to contribute to this project. Yeah. So that's about it. A big thank you to everyone who has been supportive and everyone who has been in touch with me. And in general, this whole community is very nice to be a part of. If you have any questions, I'll be ready to take questions right now. But apart from that, my presentation is done. Thank you, Amit. Yeah. So, you know, this is a very ambitious project. You know, initially we had two mentees work on this. Unfortunately, there was, you know, medical emergency and the other mentee had to withdraw. So I'm really happy and appreciative of you taking on the additional responsibilities and looks like you've accomplished a lot. So I'll give a chance to your mentor, Alfonso, to chime in here. Thank you, Min. And thank you, Amit. Yes, it is very ambitious, but it's something that is absolutely needed. We all want to learn in an easier, better way what DLT and blockchain is about. And that's an area that the Learning Materials and Development Working Group has been quite active within the Hyperledge community. And this project was presented for the mentorship program to look outside of the Hyperledge community. So once we have acknowledged our ambition, fate jumped in. And I appreciate, Min, you, that we got two mentees. We wouldn't be able to do anything if we only had Shen Ming because he had his unfortunate cortex. And I want to thank Amit for taking the responsibilities of all the rest. And yes, we are still without the website. And I'm biting my nails, as I said yesterday at the other meeting. I'm biting my nails because I want to have that. And all of us, that website as soon as possible. Because once we start playing with the tools, then we'll see their advantage. No, the taxonomy is very clear. The knowledge graph is very useful. And the idea that this is the beginning of a long journey. It's very, very convenient for our community. Yeah, I definitely want to add on to the completion of your time in the mentorship program, really, is just the beginning of your journey in the Hyperledge community. So I hope you will stick around and we look forward to, sounds like you're going to be doing some write-ups and maybe a blog post. And it sounds like the elementary is able to connect you with our marketing team. So I look forward to reading more about your experience and outputs. Sure, thank you. In terms of, okay, can I say one thing? Yeah, sure. Right now in terms of development, there's one big security issue that is stopping me from deploying the website. Otherwise I would have gone ahead and done that. The only problem is that the database credentials are being stored as static. And if I don't store them as static, they basically stop the website from functioning. And that's a big problem. I cannot release my credentials, but the website won't work if I don't release them. So I'm trying to work on that issue right now. And that's the only reason why I have not deployed it. That's it. Thank you.