Hello everyone and welcome to the next episode of the cryptocurrencies’ project analysis in which we will talk about the AION project. I hope you’ll enjoy this video. The AION product, of course, aims at being a highly scalable and efficient platform that serves to create decentralized applications and would be in direct competition with projects such as ETHEREUM, EOS, NEO. Let’s see what this particular project has to offer in comparison to its’ competition. The project is on the market for almost two years, and, what makes it interesting is the fact that the development team managed to provide us with the product within these two years. In comparison to Nexus that is being created for few years now and it is still in the ongoing development phase. That is definitely a plus for the AION project. Let’s go to the Code Progress tab. Nevertheless the project is a complete product, as we can see on the repository, the development team is still active. On the graph we can only see the commits but it is still a proof that some work is being done in this project. There are 49 people on the GitHub site, 311 stars given to this project from the GitHub users. Now let’s go to the repository website. AION network – GitHub’s organization, 36 repositories as of now, 4 of them pinned, hence, 4 most important repositories in terms of organization. The main project that we are going to talk about is the implementation of this protocol in JAVA. We also have a twin brother, that is the implementation in Rust. What’s more, this project is written in JAVA, that is one of the most popular programic language responsible for back-end side of projects. Back-end side, that is, all the logic on the server side, on which the application is running. That is where all of the main calculations take place. It is not the element of the software that is visible or clickable for us. It is an element that is responsible for calculations, and logics of the project on the servers’ side. That is the side that we are not able to see but that’s responsible for the realization of the direct goals of the given project. Hence, the choice is absolutely good. It certainly won’t be a problem to find the developers. Also, there won’t be a problem with outsourcing in the form of an external software house. So it’s definitely a good choice when it comes to this type of project. ‘Issues’ Tab. Here, there is an interesting and logical information: 40 open issues, 270 closed issues. It is a ‘logical’ information because many of the issues is marked with the ‘Enhancement’ label. It is logical because when we have a complete product, the users or even the clients report enhancement propositions for a given context, a given functionality of the project. This kind of report is further analyzed by the team and if the project architect or the project manager considers the enhancement as worth implementing, the issue is created and labeled accordingly, and the development team can start its’ realization, thereby enhancing the project and meeting the customers’ expectations. ‘Pull requests’ tab: here we have 3 open requests, 2 of which don’t contribute much to the functionality of the project, they are connected to the docker, hence, connected more to the delivery of the product, its’ publication on the production server. The end user of the given 2 pull requests will not feel the difference they will make. 1 pull request connected with database refactoring, that is definitely a bigger issue. We can see that, for now, only one step out of six has been implemented. So, that probably is the main point of the development team’s work. We can see that it has been created 13 hours ago. ‘Projects’ tab. There is nothing interesting here. ‘Wiki’ tab. Here we have a really nice, extended documentation. We have to remember that the project is, as of now, targeted at software houses that need to test how it works when it comes to creating the new application, decentralized projects. Only they will be able to come up with the propositions of particular projects for particular organizations, and the sales team will probably take care of that. ‘Security’ tab. Unfortunately, it will be a minus from me to this project because I couldn’t find any reported errors’ policy nor vulnerability management. So, I think that when it comes to the maturity of this completed product, the organization reponsible for it should take to this matter, because JAVA language is prone to vulnerabilities and errors due to its’ popularity, and so are the projects based on this language. I can support this statement with the fact that in the ‘Release’ tab there are almost 50 published versions, and some of them are marked as ‘security fix’, so a fix connected to the security. As we can se that this kind of errors occur and it means that some kind of vulnerabilities policy should be implemented. ‘Release’, as we can see, is also published pretty systematically. So it looks nice. ‘Insights’ tab. Let’s pick a period of 1 month. 20 merged pull requests – that is a lot for a 1 month period. 1 pull requests a weekday on average which means that the development team works very efficiently. The freshly published version 0411, marked 4 days ago, connected with a security fix. The next version will be probably be connected with the database refactoring pull request. It is planned to be the 042 version. Here is where I would expect the next release in which this pull request will be merged, added to the source code. Now we can see the main page of the project. We can see how the project aims to meet the expectations of the developers, because at this stage they would be the ones who can spot the ease of app development decentralized on this platform. As I’ve mentioned before, the platform is written in JAVA. The lanugage used for the creation of smart contracts is, in this case, Solidity, which we already know from the Ethereum project. So, in my opinion, it is also a plus of this project as we can use our abilities and our contacts connected to the development team, and transfer our projects from Ethereum to AION if we’ll consider it appropriate. If we consider Ethereum as not sufficient for our business expectations and that we would prefer the AION’s infrastructure. Here we have some interesting graphs but the problem is that we have no data. Here we should have some links but the links don’t work, hence, the graphs have no meaning form me, as we don’t know what are these numbers and where do they come from. We can’t find any confirmation of these pretty graphs, but it is known that there must be some marketing even in this kind of technological project. When it comes to the road map, in my opinion, there is a problem with its’ time frame, at least the one that I’m looking at. There is also a problem with the accounting of this project. We have the information that it should be completed in 12 months but we have no specifics here. We can only see what is completed according to the authors and what is still in progress. So I think that this road map can be enhanced. What’s interesting, when it comes to the development process, the team uses Agile, that is the most popular development methodology. This is definitely a plus of this project. We don’t have the problem that we faced with Cardano project, where we had the simultaneously created phases that are hard to comprehend and find some solid data. AION also offers rewarding the users in different fields like research, current bounties, I’ve opened this page to find something connected with the security policy. Unfortunately, there is nothing here. The ‘Bounties’ programs are widely used by different platforms, and cryptocurrencies projects. Let’s go to the website ‘Stack overflow’. AION project targeted at the developers. Of course, it already has a Tag on Stack Overflow. As of now, there 14 questions asked. I can see that most of them are already answered. So we can see that the social media specialists are working and trying to help the users of the platform. Of course it is a typical development project so the analysis on the nmp service’s side. Here after entering and searching the exemplary library of this project, we can see a lot of projects connected to this one, 27 exactly. AION JAVA, in short api. Let’s take a look at the first one. Let’s notice that it is a beta version of this library, released about a month ago. It already has 12 depedent projects, so on the nmp webiste that is dedicated to managing the development libraries, there already are 12 projects that depend on this library. I think this is a really interesting result. The average download number, so the potential adoption in the developers’ environment, is, as of now, 36. So we can see that there is some interest. People are successively using this project. Here we can also go through some other libraries of this organization What’s interesting, we can also find here some projects generated by the community which eases the integration of this web. It was created by an external developer about 10 days ago. Out of curiosity, let’s click on it. There are 42 downloads which is a lot for this kind of project. We can definitely say that this project is prospering well. It is also prepared to be used for other projects. CryptoMiso portal. As of now, the AION project takes the 37th place by the commits. It is completely authoritative. I try to emphasize that in my videos. I think it is an interesting ending and summary of the whole project. Thank you all for watching this video about the AION project. That is all for today. I think it’s an interesting topic. In this kind of projects dedicated to smart contracts and decentralized apps, it is extremely important how many projects are already built using this structure. because there are different problems that can occur in this product. Let’s take notice that everyone picks the Ethereum’s scalability and vulnerabilities’ erros apart, but let’s also notice that there are a lot of projects based on this one and, as of now, we don’t know if the projects like AION or Neo or Eos won’t have this kind of problems, when the use of their infrastructure will be as popular. I think that is all for today, thank you. Bye!