 So everyone, thank you for joining this virtual hyperledger meetup today. I'm excited about the topic here. Just one second. I am dropping the YouTube link in the chat. So I'd like to introduce Satya Argella, Arjana Arige and Ajin Suni from Infosys. They are going to be speaking today about Blockchain Explorer. This is a lab that is creating a Blockchain Network monitoring utility. This is based on code from Hyperledger Explorer, a project that many people in the community were using. And so I'm very glad and excited that the development of this is continuing because I think there's going to be a lot of people who are interested in what's happening and to hear what's the latest, what's the plan and how they can get involved and how they can use it. So with that, if you do have any questions about anything that's going to be discussed today, again, we welcome your questions. Please feel free to type in the Zoom chat or to raise your hand and then we are happy to take your questions. With that, let me hand it off. So Satya, please take it away. Yeah, thanks a lot. Yeah. Hey, good morning. Good morning and good evening. So today we'll be covering about the Blockchain Explorer, so which we build on top of Hyperledger Explorer code. Okay. So basically, first of all, thank you for taking time and joining the session. So I am Satya, Senior Technology Architect from Infosys, Blockchain Service Line. So I have Archana and Ajin along with me. So we'll also be talking about Blockchain Explorer. So Blockchain Explorer project now currently part of Hyperledger labs. Okay. And Infosys started contributing to Explorer project on top of the earlier Hyperledger Explorer code base from last year, actually. And this year, we submitted two proposals. One for Explorer feature enrichment and other one for enhancing UI, which are part of mentorship program. Okay. Archana, next slide. So for today, we'll be going with the below agenda. Basically, we'll talk about monitoring and its importance before deep diving into Blockchain Explorer. And then we'll have introduction to Blockchain Explorer, where we'll be talking about the key characteristics of Blockchain Explorer, what all features we have. And then we'll talk about Blockchain Explorer architecture view, where we'll cover all the components of the Explorer and how it will be integrated with the fabric network. And also the application flow, how the flow happens from ledger to a database and from database to this one on the UI side. And we'll be talking about the new features implemented on top of the earlier Hyperledger Explorer code base. And then we'll have application walkthrough and the demo, the configuration of it has been done. And we'll do some live transactions and see how it gets synced with the network. Then we'll talk about the issue status, like what are the issues we closed and how many issues are currently open. Then we'll talk about the current ongoing activities that will part of the feature scope. And then the floor will be open for questions and any suggestions, basically suggestions. We are looking for the features which you would like to have on the Blockchain Explorer. So that is one thing. Yeah. Yeah, Archana, next slide. Yeah. So before we deep dive into Blockchain Explorer, basically I will cover quickly about the monitoring and its importance. So identifying and mitigating suspicious behavior should be the first job for any Blockchain teams. So although Blockchain technology is designed to provide secure transactions with an immutable record, so there are still several ways that network security and policy violations still may occur. Okay. So enterprise chains are getting hacked. So endpoints and nodes within the network remain vulnerable. So there are some events or activities which require frequent monitoring. Otherwise, many may which will impact the overall network health. Okay. So these events may happen due to the deployed infrastructure, code, network, et cetera, or due to any other external factors as well. So some of the suspicious behaviors alerts, maybe like we can see on this slide, increases in failed transactions. If you see a lot of transactions keep failing and changes to access controls and permissions, we need to check whether it has happened as per the business requirement or any suspicious activities happening and multiple failed login attempts and unauthorized newses and performance degradation, overall network performance degradation, CPU degradation rate, and sudden spikes or drops in the transaction volume. And the transaction times that fall outside of the normal business hours. So usually they will be having some business hours beyond that if some any transactions happen. So we need to keep an eye on those things. And also the proactive or precautionary monitoring of events is required with respect to the transaction volume and the contract usage, what are the contracts, smart contracts written, how those have been used, and the validation speeds, and the overall chain health. And we need to have real time transaction view and the locks and alerts and the real time we need to monitor those things. Next slide actually. So all of these monitoring activities, whatever we check now, so this can be broadly categorized into the below five categories, like basically identify and mitigate suspicious behavior and receive real time alerts for any critical issues. Suppose if any node is down, if it's not a transaction not happening, and the transactions are keeping piled up. So all those things we need to have real time monitoring. And also analyze blockchain data and events. So it may be not be easy to analyze the data because the blockchain data which are having most of the hashing and all happening. So we need to have proper data and events to have the proper audit and create and access auditable records. So where we'll be creating the auditable records so that during any audit time it will be easy for any auditor to check what is the type of transactions, whether any privacy issues happen and all the things, it can be easy to do that. And the final thing is ensure the security and health of the blockchain. So hence for any application or project, it is required to have the continuous monitoring of DLT network health and processing exceptions on any node. For example, any errors in the smart contract code and any other issues with current elect with respect to communication between the nodes and the security monitoring for usual and unexpected behavior. The same way network monitoring for unknown network traffic and the performance degradation monitoring. These are the things which we need to have the monitoring enabled for all those things. Next slide actually. So with this we'll define what is blockchain explorer and what are the key characteristics on this. So blockchain explorer, it's a simple, powerful, easy to use, well maintained open source utility to browse activity on the underlying blockchain network. So it is a user-friendly web application tool for visualizing blockchain operations of the hyperledger fabric platform to view our query blocks and transactions associated with the data. And then the network information, like we'll have the network and node names and list of nodes, the status of this and the chain codes and transaction families as well as any other relevant information stored in the ledger. It provides the transparent view of the activity on the network and users can easily identify troubleshoot, quickly troubleshoot and resolve the issues with the explorer. And explorer attempts to provide an easy visualization by using graphs, charts and pictures and templates in addition to the usual search and monitoring facility. And it has a rich user interface developed using latest technologies such as ReactJS, Google Material UI and WebSourced WebSockets. This tool is primarily designed for developers, editors and administrators who need to track and examine the behavior and the operation of the blockchain network. So, and it also has API support where blockchain explorer provides APIs that allows developer to integrate the explorer with other blockchain applications. So, the key features of blockchain explorer includes the module that can listen and query a hyperledger fabric network and this is the utility that can get the latest status, blocks and networks and the chain codes. And we can use the blocks and the transactions. And it also has a feature like blocks and transactions, metrics by hours and minutes, search and filter blocks and transactions by date range and also with the channels. And dynamically discover new channels and switch data representation by channels. So, if you have multiple channels, we can switch the channels so that we can have the data related to that channel and get real-time notification of any new blocks. So, whenever you create any new transaction or block size, it will be notified on the dashboard of the blockchain explorers. So, there are two options to get started with explorer. The first option will be using core base where we need to have the prerequisites will be like NodeJS and PostJR SQL need to be installed and we need to have JQ installed. And the Linux-based operating system will sometimes like Mac OS and Ubuntu will work. And if you want to run any end-to-end testing, we need to have the goal length to be installed. And other option we are using the Docker. Basically, we need to have Docker and Docker composed as a prerequisites to start with the second option. So, with this, I'll stop here and hand over to Ajin to cover about the application architecture and the application flow. Okay. Yeah. Thank you all, Ajin. Please. Thanks, Sethi. Good morning. Good afternoon. I am Ajin S and working as an associate consultant at Infosys. Well, I'm sure that most of the people in this meeting might have attended the previous meetups and be familiar with the high-plug fabric blockchain explorer architecture and its designs. Even though I'm briefly explaining the blockchain explorer architecture and designs for the people who are not part of the previous meetups and who are new to the high-plug fabric blockchain explorer project. In this slide, we will discuss about the high-level architecture of a blockchain explorer. The blockchain explorer project consists of main three parts and they are the underlying high-plug fabric network, the explorer backend and the presentation layer. As we know, the need of blockchain explorer is to pull the network information and show it to the end user. So primarily, we need a high-plug fabric network which is up and running in background. And at the top, we have the presentation layer, the UI. The user interface is a single-page application that is built with ReactJS. And at the middle layer, we have the explorer backend packed with different services like REST API, database service, metric service, sync service, fabric SDK and the database. The high-plug fabric SDK allows applications to interact with the fabric blockchain network. Similarly, we have the fabric SDK in blockchain explorer so that it can interact with the fabric blockchain network and bring up the network information. In blockchain explorer, we'll create a common connection profile for a peer and with that peer, we will initialize the fabric client and cooperate the network data. Within the fabric client, we'll make use of the discovery service to get the peer information on the network. Next, we have the sync service. And it is the core part of the blockchain explorer. Sync service helps to sync the data between the network and the database in the explorer. Sync service periodically fetch data from the ledger and network and update the database also. We also have the fabric even listener added with the service which enables updating the database whenever the network has some updates, like whenever new transition is being created, the sync service able to fetch the data and update to our off-chain database. Next, we also have the metric services to show the metrics like ledger height, blocks by minute, blocks by hour, transition by minute, transition by hour, etc. Next is the database service comes up with credit operations to update the DB. When the blockchain explorer application is started, we will fetch and store the ledger data and network information into explorer database so that we can reduce the amount of time required to fetch the data from the ledger. And the database we used here is the postgres database. And we also have Rusty APIs which is used to serve data to UI and the middle layer is built with TypeScript. On to the next slide. In this slide, we'll have an application explaining how data is moved over to explorer application. As I said in the previous slide about architecture, explorer has three layers. The network, the explorer backend and the UI. Here we can see a running fabric network. In the explorer, we have a synchronizer or the sync service. When the application starts, the sync service will fetch the data and store the data to the database available. Once we load the initial network information and we are ready to share the rest, we are ready to share this data to the end user via UI. We have our UI which is connected to the Rusty APIs and gets the data from the database. And this is how normally the data flows in the blockchain explorer. And to the next to the floor diagram, we can see a table. And this table is mentioning about the latest supporting version of fabric, explorer and not JS. As of now, blockchain explorer can support fabric versions from version 1.4 to 2.3. Apparently, we're also trying to make explorer compatible with the latest fabric versions. Those changes and testings are going on. Then the explorer version currently, we have this version 1.18 and we will be releasing soon version 2.0 in the next weeks with the new features added. And also the minimal supporting version for not JS is version 12.13.1 to 16.4.1. And to the next slide, yes. In this slide, we have the new features implemented for the new release of blockchain explorer. As you can see a list of items over there. And first one is the display of health status of peer. In the current blockchain explorer, we can see the number of peers and orderers in the network. But what happens if one of the peer is down? As an end user, the user is not aware of the peer status, even though the user is monitoring the current blockchain explorer. But with this feature, we will show the health status of all peers and orders in the network, whether it is alive or not, whether it is up or running or not. And we have a new feature called search by block ID and transaction ID or block range. If you have visited the Etherscan application of Ethereum, you can see these options there, like search with block ID, transaction ID, hash and all. But this feature was missing in our explorer. So we also bought the same feature where we can search with block ID, transaction ID, and also we can get blocks information in a block range. Like if I want to get one to 10 block info, I can specify the start and end block number so that I can get the block data within a block range. And here we also change the client-side pagination to a server-side pagination. If you remember the Transactions and Blocks tab in the current explorer, the explorer is loading all the transaction and blocks data to the client-side and pagination was performed from the client-side. But now it is totally moved to the server-side pagination, hence improved the performance as well. Next feature is like chain code metadata, like display of chain code metadata. This is a new feature in Explorer where we'll show the chain code information. In Explorer, we have a chain code tab where we'll show the chain code information like name, version and deployed channel, etc. There, we added a new feature to see the metadata of a chain code. This metadata will show the information like basic info, components and schemas. Info means like the chain code specific names and components specifies like what are the functions available in a chain code. And schema suppressants that are structured that are types that have been used in a chain code. So basically we can see like, you know, the outline structure of a chain code with the help of this feature. Next important feature we added is Helm charts for Explorer and the DB. With this new feature, Explorer is packed as a Helm chart and ready for container deployments to Kubernetes cluster. We also have a, we also have added as a new feature like moving images from Docker Hub to GitHub Container Registry. So currently Explorer Docker images are available with Docker Hub and soon we'll be moving those images to GitHub Container Registry. And finally we have the Perch Explorer DB data based upon block count or duration. So, but this feature still is in progress and will be released as a patch release soon after one of the current release. As I said in the architecture, we have our sync service in the Explorer backend where the sync service will fetch all the ledger data and network information and store into the Explorer database. So what if the case, there is a huge data in the ledger loading this large data into database, fetching this data from the database also makes Explorer very slow. As an alternative to this problem, we will store only the latest data into the database based upon the block count or time duration. Means we will store only the latest specified number of blocks for past seven days data like that. If I would give an example like, if I have thousands of records, like thousands of blocks, like 10,000 blocks I have in my ledger and if I try to load everything the 10,000 records to the same database, it might make the performance very low. So what we'll do like, we will fetch only the latest thousand blocks or the blocks which have been created past seven days, something like, we'll take as a configurable and we'll load such amount of blocks to our option database. So this is a, this is configurable based upon our user choice. So whether user can decide whether it can be taken from by the block count or the time. And that's all about the new features we have developed. And next we'll have a demo on the new features. Archana will take over the session. Thank you. Thanks, Arjun. Morning, good afternoon, good evening everyone with respect to their time zones. My name is Archana and I currently work as a consultant here at Infosys. Without any further delay, let's start with our presentation. So before we get into application demo, let's once visit the official GitHub page of Blockchain Explorer. So this is the official GitHub page of Blockchain Explorer. Let me scroll down. So here it is an update saying, Explorer now can be used with Hyperledger Iroha as well. Okay, some time back Arjun speaking about the release notes as well, he has covered. And Satya was also talking about how do we start and for a replication. It can be done in two ways. One is using Docker. These are the prerequisites. One important thing to note over the Explorer containers and fabric containers should reside in the same Docker network. And second important thing is the volume properly mapped. All right. So you can start the container services using these commands. Arjun, hello, we are not able to hear you. Yeah, now we can hear you. Yeah, we'll ask you for the past one minute. For the past, wait it like shall I move on to the application demo? I'm so sorry. So earlier I was talking like bringing the Explorer application using the code base. So we have well defined steps and instructions have been provided here. One can easily set up the Explorer application using the documentation. Can you please share the screen? Arjun, I think he loves the screen. Can you able to see my screen? Yeah, yeah, visible now. You can please go on. Yeah. So I was talking about like how do we bring up the Explorer application using the code base? So we have well defined steps and instructions that have been provided here. One can easily set up the Explorer application using the documentation. One can also refer the link before below for more detail on each configuration. All right. Let me also show you the official documentation of Hyperledger Explorer. You can visit this link where we can get the official documentation of Explorer. Okay. All right. Let's start our demo. So I have already the fabric network up and running. This is basically the test network from the fabric samples. I have two organizations. Each organization contributing one peer each and an orderer. Okay. This is what all about the fabric network. Then we'll start our blockchain Explorer application. I'm starting the blockchain Explorer application using code base. I've already cloned the Git repository and set up the DB and install the required modules. Let us start the application. Okay. This is how the sign in page looks like. We can have as many networks defined in the configuration file. As of now I have defined only one network. Let me log into the application using the credentials. Explorer admin is a username. Explorer admin PWA is the password. Let us sign into the application. All right. This is how the dashboard looks like. Let's take a glance of each tab and navigate to each one for more details. So the dashboard page looks like this. Network page where we get information about the peers orderers and their ledger height. Blogs and transaction. We would get the information about the blogs and transaction. Similarly, chain codes where we would get the information about the chain codes deployed and channels, the number of channels that are available with respect to this particular network. We do have the number of channels. This is one of the most important key characteristics of Explorer. That is Explorer discovers the new channels and switch data representation by channels. We do have a bell icon where we would get the real-time notification of blogs. Let's move on to the dashboard now. So if we can see here, there are 27 blocks, 28 transactions, two nodes and one chain code. We can move to the right-hand side. Here we can see the metrics. The metrics are like blocks per hour, blocks per minute, transaction per hour and transaction per minute. Here we can see date time and the number of transactions at that particular moment. We do have also a chart indicating the transactions by each organization. When we move to the left-hand side, we would get the latest three blocks data that is block 24, 25 and 26 to which channel it belongs to data hash and the number of transactions into this particular block. Let's click over this and see what happens. If we see here, this is a block-related information to which channel it belongs to the block number, at what time it got created and the number of transactions in this particular block and block hash, data hash and pre-hash. This is what all the block information we would get. Now let's discuss about the new features or we can go through the new features one by one that is search by transaction hash. Let's take the transaction from here and input over here and see what happens. A model would be open where we can get the transaction details. We will discuss about this transaction details in detail in the transactions tab. All right. What if if I try to give a transaction hash which is invalid or not found? Let's see what happens. It says me that transaction is not found. Okay. Now we'll switch to block number. Let me give some invalid block number and see what happens. Let me input the same thing. So it says me, please enter valid transaction hash or block number. Let me give the block number which is not found something like 30 and see what happens. It says me that block is not found. So let's try for a success case where we have a block number. Similar model would be open where we would get the block details. This is what all about the search by transaction hash and the block number. Now let's discuss one of the most interesting feature that is display health status of peers and auditors. If you see, we will get the peer names and order the names over here and the status of it. The green indicates these particular nodes are online. So we make one of the node down and see what happens. Let's drop this peer and see what happens. Our syncing happens. It will take some time to reflect the status over here. Oh, I'm so sorry. I think I have stopped the couch TV. Let me restart it. Yeah, as you can see the status over here. Now the peer has gone down and the status has been reflecting over here. It is red and the status been depicted as offline. Let me bring the peer back again. It will take some time again to come into online status. So this is what all about the health status of peers that we have implemented. Next, let's move on to the network tab. So if we see here, we have the peer names request URL and what type of peer or order it is MSP ID and the ledger height. Since this peer has gone down we would not able to fetch the status. Once it is up, we would the status would be reflected over here. As you can see, it has come up and the status has been reflected over here. Now let's move on to blocks tab. So here we can filter the data based on date range. We can also apply filter on the organizations. Let me select filter. Let me select some date. Let me filter the data. So this is all the data that is available within this date range. So some time back, Ajin was saying that earlier in pagination was handled from UR. Now it is managed from back in. All right. So we would get the block number, channel name, number of transactions, data hash, block hash and all this information in the blocks tab. Let us click over here and see what happens. So our model would be open and this is what the information we would get about the block. And similarly, if we click on transaction, the same transaction model would be open where we would be getting the information with respect to transaction. We can also apply filter. Let's apply filter on organization one and C. So as we can see, we have this much data available when we apply a filter on this. And this is again new feature that is searched by block range. The range has been prepopulated over here. We can select number of blocks as 10 here. And let me input start block and end block here and see what happens. Zero to nine. So we would get the information zero to nine blocks of data. If I try to search from nine to nine, what it happens? So it gives me block number nine data. What if I've tried to search from block number 11 to nine? So it says me two blocks should be less than or equal to from lock. So this is what all about the block style. Next, we'll move on to transactions. So similar to your blocks, the same information we would also get on transactions. We do have a filter on date range. Let me select the date and search. So this is what all the data that is available within this date range. We can also apply filter over here. This is what all the transactions by organization to. So let me open this transaction model and we'll discuss. So here we would get the transaction ID, whether this particular transaction is valid or invalid. We do also have payload proposal hash, the creator MSP, who are the endorses to which chain code it belongs to. What type of transaction this is at what time it got created and the reads and the writes. Let's expand and see. So this is what the information we would get on read set. All right. Then we expand the writes and see. So this is what the right set that we are able to see here. So this is what all about the transaction model. Next, let's move on to chain codes. So here we could able to see the number of chain codes installed deployed as part of this particular channel. So we have a chain code named basic of version one and version two available and the transaction count. And the new feature that we would like to discuss over here is display metadata of chain code. This is basically, say for example, if a user likes to see what all the functions that are available as part of his contract and what it returns and the number of arguments that's been passed to that particular function. So he can have a quick V over here that is the display metadata of chain code. This is a hyperlink even over here when we click on this a model would be opened where we have three layers in four contracts and components. So if we expand here we would have the transactions. This is what the name of the functions that has been defined over the smart contract. So we have eight functions defined over here. Let me expand and show. So this is the name that is called asset exists. And these are the input parameters. And this is the return type of this particular function. Let's expand this one and see. So this is the name of the function get all assets. It returns an array and the reference has been provided here. So this reference has been referred to schema. So components schemas at asset components schemas and this is the asset. So this is what all about the displaying metadata of chain code. All right. Now let's move on to channels. So in the channels tab we would get the number of channels that are available with respect to this particular network. So in this network we have two channels channel two and my channel B number of blogs and transactions with respect to this particular channels. And one more thing we need to check is like we need to see whether real time syncing of data is happening or not. Let's post or invoke a transaction and see what happens. So in this particular channel we have 27 blogs and 28 transactions. So when we invoke this transaction it has to get incremented by one. Let's do that. So if you can if you can observe here earlier it was 28. Now it has been increased to 28 and 29 blocks. We also got a notification. Saying block 27 added to channel. All right. One more thing also I would like to show that these multiple transactions in a block. So if we observe this block we have multiple transactions and even we can click on this and check the transaction details. All right. This is with respect to one channel. We do have a user management where we can add users as well who can access this application. Then we'll switch to other channel. So similar to my channel be the other channel the same information that is available as part of this particular channel we could be over here. So this is what all about the application demo and any doubts or shall I move continue further. All right. Next let's take some time understanding about the issues that have been identified and their status. So these are some of the issues which are closed and some of the issues we are still open. So some of the closed issues we have listed over here is like test cases failing explorer docker image build failed empty org is being displayed while fetching the list of orgs and so on. This is some of the open issues like ledger height and peer status is not updating with respect to multiple channels. So while we are testing explorer application with Fabric version 2.4.7 we observed that the ledger height which was in the networks tab with respect to other channel was not updating properly. Okay. So we almost have fixed this issue and we are testing it. So let's see. Let's pick one of this issue and see how this how sorry how this is like created documented and resolved. We copy this and go to the issues. So there if we see we have listed only few issues but if we can see here there are 19 open and 30 closed. So if you can see here this is an issue this is a PR. Let me create open this. So this is how we are documenting over here when we try testing the explorer with Fabric version 2.4.7 what we have observed was the first transaction which is of conflict type doesn't have any creator MSP. So when while we are trying to fetch the list of organizations we were getting an empty organization. So that is what we have given a screenshot over here and we have explained we have like documented what it expected to happen and how can it can be reproduced. Let me also show you the PR for this and how we have resolved it. So this is a PR. Then we have given this particular PR resolves this particular issue and it's been reviewed by Aditya and it's a minor query change that we have done in order to fix this issue. And thus we have resolved and merged to the main branch. So this is how we are creating issues and resolving so. So this is what all about the issues status and their creation. Let's move on to future scope. So these were some of the items that were outlined during our weekly status calls. The first one was like research on metrics and bring a possible metric features. So we were referring to this documentation. So we have Prometheus metrics. We were thinking we could pick any of the feature from here and bring this particular feature and integrate with our blockchain Explorer application. So that is first line item. And second thing is like we would like to make this Explorer application compatible with all the latest release versions of fabric. Third one is like similar to Etherscan. We would like to have our Explorer application in terms of robust UI design. And the fourth one is like user management. We would like to really remodulate the user management thus by avoiding the administration key dependency. We do have a reference link over here. Let me go through that. So we have listed all the light items over here in this project plan. This is actually the mentorship project plan. So if anyone has time they can go through it. Milestones and all these things we have mentioned over here. So this is what all about from my side. And we are open for questions and suggestions. We do also have Discord channel Blockchain Explorer. One can visit over there if you're facing any issues. And even if you're facing any issues you can raise them directly in the issue section of Hyperledger Explorer. We will try to answer from over here. Any questions in the chat window? No, there is only one question like whether this is open source or not. So I replayed for that. So we're waiting for questions. Yeah, still we can use 2.4.7 with 118 actually. Yeah, we can use that. We'll be releasing the next version maybe in a couple of weeks. So currently we have Fabric and Iroha only. So other things still we are not looking into that. So basically once these two things are done maybe it will be like we were also planning for a uniform dashboard. So where it will support for all other platforms also. But currently work has not started on that. Only Fabric and Iroha we are supporting. No, these are not funded by Infosys in. It's just we are contributing as part of the open source. So we are contributing for this open source community. That's it. But it still is part of Hyperledger labs only. Whatever the Explorer code we have earlier, we started doing the changes on top of that one. Aaron, do you want to answer anything on the funding? So some questions are there. How can we get funding on this? Right, so none of the projects are like funded, right? So the funding or the contribution from each company is the time that they spend. The developers from each company they spend and open source activity itself. That's how it works. And apart from that, if you're asking specifically about the mentorship project, as there are like a couple of mentorship programs which are based on Explorer this year, and those are paid for by the mentorship program guidelines. So that's how the mentorship program works. And that's a Linux Foundation mentorship program. I also see another question on support for RBAC is planned or not. So yes, I am integration and support for RBAC is one of the features that will be picked up very soon. It's in plan to be taken up by the mentee who is contributing. If you are willing to get started on that, we welcome you to join the bi-weekly calls of the project and then all these features can be discussed in detail in those meetings. Hi, I'd like to ask a question. Can you hear me? Yeah, yes, I type in the channels on the chat. I'm glad to see that Infosys is adding code to the Explorer, but we just switched from Explorer to Hyperledge Fabric Operator. So I'm trying to understand what is the difference from a long-term perspective support by the technical steering committee? I'll probably take that answer. So for detailed analysis of what each project provides in terms of features, it's documented elsewhere and we can look through it and share it across to audience of this meetup. So Operations Console main purpose is on the Operations side, which is to deal with deploying the fabric components and then maintaining the fabric blockchain network. And however, the Explorer's main goal is to give visibility into what's happening in the blockchain network. And I do understand that Operations Console does also have certain capabilities where you can see what's the latest block information on each peer notes, just a way of how these work is different. And Explorer is purely focused on the operations, then the operations in terms of observability and then knowing what's happening on the blockchain across the network. So yeah, these are the problem statements that Explorer solves. So you could consider this to be equivalent to some of the other projects that you might have seen in open source or in public blockchain ecosystem, which allows you to explore through different blocks and know the contents of those blocks, know what transactions went into those. So that's the kind of problem statement that Explorer solves. Yeah, the Hyperledger Fabric Operator also shows the blocks and the content of the blocks. It also shows the private data collection, which I don't think Explorer can expose today. I could be wrong, but I like the Explorer UI because you can do a lot of query. There's no doubt you folks are doing a great job. I'm just wondering, because we just switched from Explorer to Hyperledger Fabric Operator, so I was wondering about the long-term view, long-term support. If we have to switch back, we will do so. But I'm just wondering, what is Hyperledger Foundation? Is it something that the user has to determine? I mean, we'll do that. If you don't know the answer, that's okay. This is open forum. I'm just bringing this up. Well, I can jump in and help answer that, Arun. In terms of the long-term support and the direction, and if that's something that you're interested in, the way open source works is if you're using a project or code and it's relevant for you and it's important to you, the way to make sure that it evolves in the direction that you want and the reason to make sure that it stays active is to contribute. So, as we've been sharing on this meetup, you're welcome to get involved. Join the calls, join the Discord channel. You can help move it forward. You can help make it into what you want. So we definitely welcome your contributions and the more people who contribute, yeah. Right. I understand that. I think I share a link in the chat. It says that Explore was end of life, May of last year, by the TSC. So there must be a reason by the TSC to make that decision. Oh, I see. I see what you're question. Well, yeah. Okay. I see. Well, the reason was the previous maintainers for the Explorer project left and they went to the TSC and told them that, like, hey, we had, you know, their priorities changed. They shifted. They were no longer available. And so nobody at the time was available to keep the project going forward. So if there's no projects with, if there's a project with no maintainers, the TSC will move it to archive. And the reason for that is we don't want to communicate to people who are looking at the hyperledger community that a project is active if it's not. But there were a lot, I think this is a great story of how open source works. There were a lot of people who were using Explore and as soon as they found out that the previous maintainers were no longer able to maintain it, they stepped up and took the code forward. So I think it's a really great example of, again, if you care about something and are using something, if you want to get involved, you can evolve it. So it's not, you know, the TSC is happy to see the lab evolve and thrive and grow. And so, you know. Right. David, I understand that this is all in good spirit. I'm just pointing out if the direction is hyperledger fiber operator, don't you think that the resources should be directly to that way, rather than I understand it's the availability of the maintainer? I'm just pointing out because we just switched from Explore to hyperledger fiber operator. No, I hear what you're saying. Yeah. But again, I think it's the way the open source works. It's not the TSC or the hyperledger staff to determine the direction. It's really the people in the community. You know, an open source community does what people in that community choose to do. Right. So if people in the community choose to use one project over another, that's what happens. Right. So again, it's really up to you and other people on this call, you know, how to move forward. And if you want to collaborate with operator, if there's, you know, an overlap between some of the functionality, you could always do that collaboration and potentially, you know, merge the similar efforts. Right. I mean, it's again, it's whatever the community chooses to do is what happens. Okay. Thank you. I don't know, Rune. I mean, as somebody on the TSC, sorry, I didn't mean to jump in, but I don't, if you have anything to add to that, please. Right. So I think you've covered it well, right? So the POC's roles wouldn't come in terms of how each project maintainers decide to go. However, from a POC standpoint, we try our best efforts to unify efforts if similar efforts are going on across. And when it comes to operations, console, and then the explorer itself, the way I see it is operations console, eventually we'll start can have integration in it for Explorer, right? That's how I see it. It's not a competitor project. It's rather a complimenting project. So operations console has its own logic for fetching blocks data and showing the transactions data right now. I know those are API based and eventually the operations console can have an integration where it can have Explorer as part of it. So it's a compliment than a competition. And this is like the technical view of how these projects should be seen. So operations console has the deployment-related things in it, whereas Explorer is purely on the observability stack. So it's a compliment, not a competition. Yeah. So there are reasons why you might use both. If I'm understanding correctly. That's correct. And eventually the explorer is being planned so that we have unified experience for all the different blockchains. And hopefully we right now are getting started with that effort. We need more contributors. I saw some questions on the Basu as well. I think this is the great point. If there are people, enough people interested in the Basu work, it's definitely time for us to get started and let's collaborate and join the calls for Explorer and get started on that. So Mahesh, we saw the question. I think there may be some complications in the way how private data can be seen from the explorers. It may depend on the node that the current explorer is connected to. So when you saw the demo, most of the components that you saw, like they were showing the nodes for online or offline and then showing the current block height across them. And these are all possible through the metrics that we could collect across the network. And if it is private data, then yes, that can be integrated. But then we need to have those provisions saying that this private data is as seen by this particular node in the network. And of course, it's not possible for Explorer to go and see what's possible to see from other nodes who we are not connected to. So that's definitely something we could explore in terms of how the feature can benefit. So there is a participant on this call. So this is related to the Explorer features and then the new UX user experience itself and what features we would like to see in it. So Deepika, who is on the call, is going to work on those things. So deepika is going to work on those things. So deepika, who is on the call, is going to work on those things. And we are going to send a survey soon. David will talk more about how the survey is sent. Please share all these inputs so that all of this can be considered. Thank you, Arun. Yeah, that would be happy to participate in providing some feedback. We see some real need for it because in a consortium, imagine being able to give every person in the consortium an Explorer that they'll be able to see their private data along with the generic non-private blockchain data. So it can be like a very nice tool which really improves adoption. Right now we struggle with why would a partner run a node kind of a question, right? So I think that's where the question is from. But thank you for that. Deepika, probably this is the right time if you want to jump in and talk about the work that you would do and then the survey that you're going to send. Thank you, Arun. So hi, everyone. I'm myself Deepika. I'm currently a mentee for Hyperledger Aresai project. So David will be sending you a form for our Experience Research Survey. So where you can give your pain points, what all the features you feel you are missing from the Explorer project. And you can mention how the usability is now and how you see you can improve it. So if anyone has any feedbacks you can give now, you can give it in our chat. Thank you. Great. And look for your email for that. After later today or tomorrow, I will send an email out to everyone who registered for this meetup and I'll also include links to the repo, the meeting invite, the Discord channel slides if they're available and other resources. Are there any other questions anybody has? Well, if not, thank you for joining. And again, this is just one opportunity to talk about Blockchain Explorer. If you would like to talk more about this, there's always, as we were saying, the Discord channel, the regular calls, and we hope to continue the conversation with you. If you're interested in what's going on, please do show up and we're happy to talk with you more. We're happy to, you know, collaborate with you and we look forward to talking to you in the future. So thank you for joining today. Thank you, everyone. Thank you all. Thanks for that. Thanks, everyone.