Hyperledger Foundation Hyperledger India Chapter, 10 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Blockchain Techfest 2020 - Part 2

Description

A virtual meetup hosted by the Hyperledger India Chapter covering a range of Hyperledger projects.

Data visualization is vital for knowing about what’s going on your blockchain network. We will present about what you can do with Hyperledger Explorer, its architectural overview and the plans of what the community is planning to do next. Hyperledger Caliper is a workload generator tool for the performance measurement of distributed ledger technologies. Caliper is scalable, flexible, and extensible. Scale out easily to match the performance of your backend system. Tune every little detail about interacting with the backend system to suit your needs and scenarios. Implement workloads with arbitrary content and rate to mimic your business use case. Extend Caliper with custom modules to integrate it with your infrastructure of choice. Join the Caliper session to learn how to do all these!

1. Hyperledger Fabric Production Deployment: Blockchain Automation Framework
Priyanka Vats & Sownak Roy
2. An introduction to Hyperledger Caliper - For users, and developers
Attila Klenik
3. Hyperledger Explorer Overview and Demo
Jeeva Sankarapandian & Atsushi Neki
4. Hyperledger: A Technology For Geeks Or A Product For The Rest Of Us?
Idowu Akinde

More about the event is at: https://www.meetup.com/Hyperledger-Bangalore/events/274315832/

----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #HyperledgerMeetups #Blockchain

A

Welcome back everybody to the second uh session of the uh blockchain tech fest, the festival will continue. uh This is what berun and the indian uh community- and we have the african chapter here as well. Today, I've put together and kamlish and others. um It was a great event. Last week and this week we've got even more uh contributors and maintainers uh from uh we've got something from hyperledger labs, um which you know which actually bath. We've heard a lot about. There's a lot of you know a lot of interest in bath.

A

We've had a few other events and a lot of interest there, caliper, which is a benchmarking tool explorer and, of course, we have uh fabric. So uh yet again, I think the message I'm gonna give to everybody is: you know I enjoy this. This is a great thank you for the community for pulling this this. Putting this together. Please do get involved. uh All these projects are looking for people to help in contribution.

A

uh This is all about developing this ecosystem together for all the benefit of everybody here, so please uh do get involved and uh once again welcome back and now I think, I'm just gonna hand over to you a run today to take this on. Thank you.

B

Thank you julian, and we welcome, will welcome the community across asia, pacific and europe for joining us today, good morning and good afternoon, good evening to you so up. First, in today's session we have saunak and priyanka joining us from accenture and then they're going to speak about blockchain automation framework, and this is one of the project which has been gaining traction within hyperledger labs, and um it's also like recently called out. Many people are describing that blockchain automation framework is defining the way we deploy a production grade.

B

Blockchain networks for for our use, cases so I'll hand it over to sauna and priyanka.

C

Thank you thanks. Aaron thanks julian welcome everyone again. uh I know it's uh mid afternoon uh mid. uh You know post lunch time for india and uh I hope we don't uh really bored you with a lot of details, but we keep the talk very relevant um and uh yeah. Please enjoy the session so I'll share my screen. Please let me know once you can see and we will get going.

C

Okay, okay, so uh the first thing that you know uh so this is the agenda and uh we will give you a labs intro, because the last time we spoke, we understood that a lot of the people who are active members in hyperledger uh community. Do they really do not understand?

C

What exactly is the concept of labs right, so we'll cover a little bit on? uh What does it mean that baff or blockchain automation framework is part of hyperlite labs? um You know what is the problem statement? Why did we really create uh such a product? Why did we really want to work on something like this, it's architecture and then how are we using it to consistently deploy production grade networks?

C

uh You know, I would say agnostic of the distributed ledger technology you're using so uh if I just choose the hyperledge umbrella, uh hyperledger fabric, indy or basu, so how does it use the same framework uh to deploy different kinds of dlt networks?

C

um The next part is, you know: how far have we progressed, but there is a lot more to do and how can you engage with us for that and q a and you know to get how to get involved.

C

So with that, um you know you can just uh scan this qr code if you're really interested with your phone, and it will take you to um the hyperledger labs detail link, but just to give you an introduction, the qualified projects that you see um they really require a lot of paperwork, uh technical steering, committees, review uh and a legal framework approval to become qualified projects.

C

So hyperledger came with this idea that why don't we introduce a labs where uh projects that are still a little early to go into and become a qualified project can actually start working their way to become a qualified project, and with that idea uh you know um the hyperledger labs has a lot of you know incubatory projects, if I can call them um being one of them.

C

So uh you know, uh I think we open sourced last year in 2019 around september october time frame, and uh it has been one year since we have uh been in labs. We have got a lot of guidance and hence you know we now strive to become a qualified project.

C

Okay, so um with that, just to uh you know show exactly where do we uh stand? uh This is a view of the hyperledger greenhouse the dlts, the libraries, the tools and on the right side. uh You know bottom, you see hyperloogen labs and that's where blockchain automation, framework.

C

Lies so again a qr code that will take you just to our. You know: github link um I'll just pause here for 10 seconds. If anybody really wants to see. While I talk on what exactly it is, if you have not heard about it before, please do that.

C

Okay! So now I'll just you know, tell you a little bit of story, so accenture really uh started working um on blockchain quite early. I would say way back in 2015-16 um even before that in our labs and then slowly. We had a lot of clients conversations and we then progressed to a stage in 2017-18 where we started doing pocs or implementations with the client.

C

Some of the common challenges that we saw was you know that we have done with poc. The client is really happy, but when we need to scale we have to redo the entire thing again, because there are a lot of architectural components that you know. We really don't uh think about, or we don't uh give a lot of attention to when we want to uh do a quick poc, but when we have to go and scale it to production. Those considerations make um a a solution.

C

You know of literally of no use um so, for example, security, how how our certificates are stored. How credentials are exchanged are some of the components that you know you might not be thinking about in poc, but in production it becomes very important.

C

um The second thing was: the network itself is the crux of blockchain or dlt technology, and it is, I mean, let's be frank, it's not easy right. uh The first trouble that we have seen developers talk about that. It's really complex how to deploy a network. There are a lot of dependencies.

C

uh This service has to be up or that service has to be up. uh The configuration has to be done properly, so these were some common. You know, murmurs that we used to hear from all our developers that we are spending a lot of time in in network deployment rather than our own chain code, development or application development.

C

So so, with that in mind, we thought why don't we create a bridge? uh You know which kinds of uh implements what we call as a distributed, ledger technology reference architecture, so it builds upon some principles and patterns. uh It should be designed for being production ready. So it's not something. You know that you would want to use. If you want to just showcase the power of blockchain, it's something that you you would need when you really want to build something production worthy.

C

uh It should support. You know multi-company uh or multi-organ organization concept, because we all by now know that blockchain or dlt is not a single player uh technology. It has to solve an ecosystem problem or multiple partners problem. uh So how do we really create a technology which would, by default support that kind of uh business?

C

You know um network? uh The next thing was: we also did not want it to be logged with a single kind of cloud provider or infrastructure. We wanted to keep it open. So if, if a particular client already has uh you know, is aws amazon shop or it's an is a microsoft shop and they really do not want to change their cloud uh infra. Then we we didn't want to force a single one.

C

Hence we have kept it infra, independent and the second thing is: it's obviously open source which you all by now know so so so that's the concept that we thought and with that what uh you know what we have built is uh is very simple. So there's a single file which we call as net. You know network.yaml file and all your network details.

C

um You know: what's the platform of your choice when I say platform is the it's a dlt platform, uh whether it's fabric, it's indie, it's bazoo or or the others, because we already, we have also implemented it for card card enterprise and quorum. So you specify the platform. So your application now becomes independent right. You can do a little bit of plug and play. um So you know you choose your platform, you choose your consensus, you choose the kind of cloud.

C

Infra environment details, your ports, your I'm, you know so all those details, um external dns, etc. They go in this single file and the framework um which uses some key components. So, for example, kubernetes is crux: um you know, shauna will be covering these uh in detail, but we used kubernetes because it it uh the managed eks on a cloud solves a lot of questions on high availability disaster recovery, which we really do not have to then design uh in a custom way, but those get um very deeply embedded in our architecture.

C

Hence uh you know kubernetes is the crux, um so it just takes that single file and brings up a network for you. That's it. So we don't call it uh one touch deployment, but we say it one step deployment, so we don't have a fancy ui, it's it's all through. You know command lines uh because we wanted to build it up for technical people for developers and uh architects. So there's there's no user interface.

C

You'll have to work on this configuration file as it stands now, uh but just using that one single file, we can bring up a network so a little bit on what is supported right now. um You know we had. uh We are on a point, six release right now, and uh um so we have our three chord enterprise, uh the version basu 1.4.4, the fabric version 2.0.

C

uh I think we we recently did a release to have 2.2 as well right.

C

D

2.2 is still in uh in a feature: it's a feature branch there. If someone.

A

D

To explore, they can do it, it's not merged to them. Okay, developer must.

C

Yeah so yeah I mean but yeah you can um see the code if you want uh 2.2 as well, so yeah, so at recorder version, 4.4, indie and quorum. So so that's the uh you know baff support matrix, which we have for each of these platforms.

C

uh Now a little bit um you know on uh when I say that it just takes a single file uh and and brings up a network. What are the components that we have used to to bring up the network right, so it uses ansible uh it uses it uses mainly.

C

You know the ansible playbooks, so we use it like an automation tool, uh not really like a configuration management uh software which, when you google to ansible you'll, see that it is mostly used as a configuration management system, but we are being we're using it primarily as an automation, tool right and it uses helm charts. So so we are using helm, which again is a package manager.

C

We are using kubernetes, for you know, orchestrating all the uh workloads and services we are using. Git tops and flux.

C

So one interesting thing here is that you know once you have deployed the network and if the network goes through any change, then um uh our network.cml uh is uh in the repository and uh you know get up get up flux, it's kind of uh binded to it, it's listening to it and if any change happens uh on in the network.yaml, it senses it and redeploys the network. Hence the the continuous deployment theme is very easily achieved using githubs and flux.

C

We are using hashicorp vault, but you know we have also implemented it for some clients that who did not really want a hashicorp vault, but they wanted, for example, a jerky vault. So with a little change you can, um I wouldn't say it's completely pluggable, but it's it's doable, so it's manageable to change the world and obviously, as uh I've mentioned, that it can be used on any cloud uh service.

C

So uh with that before I hand it over to shanak uh for a little bit of more detailing um thanks bianca.

D

Yeah, I think there is a question if my fabric peers, I'm answering live. So if I need my fabric peers to have users in indie, does it support this kind of multi-chain architecture?

D

The answer is, it is up to you to deploy fabric and deploy indie and create that uh multi-chain or the integration between that. What baff will do is give you that option to use the same tool to deploy your fabric and deploy your in the network.

D

Because again, bath is not a solution, it is a automation tool which will create, uh which will make your solutioning easier uh or the deployment of the of both any of the networks that we support easier.

D

Okay yeah, so as uh as we go back, go I mean if you go back, I just want to dwell on on that slide on the number of tools that we're using yeah. So we just to clarify uh that we are also using hashicorp vault, which is our secret storage certificate storage solution.

D

uh We have chosen hashicorp vault because again we want to be uh cloud agnostic, so we are not using any uh aws kms or as your key vault, which, which ties you to the uh cloud uh hashicorp vault has uh its own integration, it's more like how we are using kubernetes to achieve the cloud agnosticity, uh so hashicorp vault can be deployed on any cloud provider and you can integrate it with the say, kms or key vault uh on with the hashicorp vault, as well as the google uh cloud.

D

So that's how we have been received that and that's why we that's how we claim to be any cloud, including on-prem. uh Of course we in our day-to-day development we do not uh deploy on all the cloud platforms that are available because it is cost prohibitive.

D

uh We generally test on aws, but we have uh tested and have uh done projects on azure and google cloud as well right. Okay, so now going back going to the more on on the architect or not really the architecture, the how we have achieved this, how uh baff internally works is, of course we everything on bath is uh to be on on kubernetes, so hence all the applications.

D

All the platforms, which is the dlt platforms, must have uh container support, so must have their proper docker images. Like I mean fabric, uh basu and indi. All of them are container native anyways like we. We run them always on containers. So that's what what's one very good thing about her lip ledger fabric all these tools, so we all have the images, the docker containers, basically fabric ordered and all that is all taken from official fabric releases. We don't uh rebuild them in any way and then our main uh code is is the ansible.

D

As as priyanka said, it is the automation, it's not really the configuration management, because ansible is not doing uh it's not deploying on the kubernetes cluster or on any machine. First of all, there is no uh is always deployed on a cluster, so it doesn't deploy. Of course, your cluster is running on some virtual machines, but ansible doesn't uh control them. So ansible is more of an automation, it's more of a templating tool.

D

That's how we have used it. So we and, as we see that ansible we have different playbooks and roles.

D

I think people who are familiar with ansible will understand that I mean playbooks are basically you know the stepwise, a sequence of steps that you will perform and then the roles are basically your functions which you call from playbooks. So these are the playbooks or roles we have like, which can install a chain code.

D

We can create certificates, we can create channels, we can create uh the we can join a channel orders or we can also do single cluster network or multiple cluster uh network and then on the then that creates uh the the I mean the helm. Charts also are also provided. So from baff point of view. The helm charts are also available open source.

D

uh Now we are trying to get like a helm repository uh so that you can use just the helm charts, but right now also you can you can take the helm, charts and use it in your own way. You don't have to use ansible uh to uh to deploy the network so also again our health charts. We all have this joint channel charts, update chain code, charts, creating of raft or tough quarter charts uh the member msp creation, then peer nodes or clis. All those charts are available. So what ansible does is when the developer?

D

The developer gives that one single configuration file and ansible is going to read the configuration file and create the helm value files, which will then be deployed onto kubernetes using flux. So flux gives us the continuous deployment, as priyanka said, so it will create the multiple uh all the all the deployments in a sequence as we are running uh running in so so. The first time you execute the playbook.

D

Of course it will wait for things to happen like it will wait for order to come up and then peers will come up and then the installation will happen and all that, but once your network is set up, uh then all you need to do if you want to change little bit of things like you just want to update the fabric peer image. So in that case you will only do a check in to the git ops, the git repo, with the updated helm, value file and.

C

D

Will be deployed.

D

Automatically, okay and next one or do we want to take some questions on fabric specifically.

C

So um one or two questions that were from karthikey uh I've answered but yeah, please, uh is whether two peers can be on two different cloud providers: yeah.

D

Yeah, definitely I mean it can be as long as you have uh see uh as I'll show you, the network ammo as well, so you can, all organizations actually can be deployed and we encourage people to deploy different organizations in different kubernetes clusters and different cloud providers. Yes,.

C

And the other one um I mean I'll answer this, maybe so yeah I I think we can go ahead and I'll answer these questions. uh Okay,.

D

C

D

Go to the next slide, please so.

C

D

Yeah, so that's on the indie side, I mean it is more or less same and I'll actually go into how to share my screen and show the network yaml. So it's clearer, uh so yeah so india again uh similar uh similar concept. uh The only thing is that uh the indie nodes cli, is key management.

D

The containers are built by us uh because we use the instructions from the in hyperledger in the documents to how to create those containers, ah because we again, as I said, bef, deploys everything on kubernetes and then then again we have the similar ansible roles and playbooks, which will do the id management, credential definition, creation, schema definition, crypto generation and and the actual node in the node setup and then single cluster, all multiple cluster.

D

uh The only complexity within these that it doesn't. It needs a static ips because indeed by design, doesn't work on on dns names, because dns names are going to change and it it's that's. How indie is designed right so uh all are for indie we need. When you deploy nd, you must have a few uh static ips uh in your account in your cloud account whatever and uh uh from the uh from the helm, charts uh yeah. We have the gen the key management group of charts.

D

Then we have the cluster management group of charts and also the organization where you can update the credential or add a did document and uh yeah. So the genesis file and all that and again nice is very simple, because genesis gets stored into our the vault as well. So if you want to share, of course, someone who has access to the hashicorp vault they can share because for indeed nodes to connect, you need to share the schemas and also all that information is easily available when we deploy in d.

C

So shanak one question: uh if you can answer live uh it's, how can we enable tls on pr node deployed on kubernetes.

D

All our peer nodes are tls enabled, uh so we we don't uh everything in daf, uh be it uh corda or korum, or or basu or or um or fabric, wherever the tls options are there. All of them are already tls enabled. So we we strictly enforce uh tls 1.2 as well. So that's one of the accenture policies. We cannot use 1.1, so all anything below 1.2 is is forbidden. So all the communication is 1.2 and the peer nodes uh in our network. When you create using maf, it is dls enabled by default.

C

So I don't know if uh that answers your question gauranga, because his question was: how can we enable tls so is there some something that I.

D

Mean it is already enabled, so if you check the code as well, it is always dls enabled and our chain codes as well are or when you install or deploy actually create a channel. It always uses the certificates.

C

Okay, so uh shanak at this point, do you want to go uh and uh just cover this for basu as well? Or do you want to actually.

D

Yeah yeah: okay, no yeah! Let's cover this for base. U then I'll go back and uh depending on the questions, uh maybe or the interest yeah, so basu is much more simpler, uh as I guess we'll share in the next and uh later that we need more contributors, especially for besu, uh because yeah so basu we have uh the the we have just used, one one uh uh ibft consensus as one and one orion as the private transaction manager.

D

uh So that's all we have and it's much simpler because visu or quorum by default is is not as complicated as as fabric or corda. So we we have the crypto generation, uh transaction managers and and again just to reiterate all transaction managers and everything is using tls.

D

uh There is no, even though they are deployed within the same uh same cluster and that yeah. So again we are not using. We have not integrated, say postgresql db or any uh any other db. We are still using the file system db for bsu, but the concept is similar. I mean that's how we have tried. So, basically, if, if you are working, if you are using baf uh for fabric and then tomorrow, you want to also try out beef sue, then it is very easy because the concepts are exactly the same.

D

So you don't have to learn a new new lang, new technology or something uh I mean you just have to learn. uh You have you know already how the ansible and the helm charts work right. So it's almost similar to how terraform operates uh so terraform is the same tool you use for both all the all other, all the supported cloud providers. But then, of course, you have to rewrite some code uh for different uh cloud providers, but you don't have to read that read and I mean re learn any new technology.

D

So that's the same concept. So, if you're using uh base, if you're going to use base 2 later it's it's all exactly the same configuration file, I mean, of course the value contents of the configuration file will be different as we'll see now, uh but but the concept is similar or the configurations that you put in them is is quite similar.

C

Thanks so we do not have any open q a, um but I think it will be good to take uh folks through network.yaml to um to okay, so I'll stop sharing them yeah. Let me.

D

C

So yeah, please feel free to uh ask any questions in the q a section.

D

Right, okay, hope you can see or is it too dark.

E

Yeah, it's fine.

D

Yeah, okay, yeah, so this is uh so this is uh we have uh many network cameras, as you can, if you some people folks have already gone to our uh code repository so I'll, show you how the repository is generally uh organized is on the main, uh baff repo. We have these platforms and inside platforms. We have all the platforms on. I mean all the supported platforms uh so under them uh on and there will be a fire folder called configuration which contains.

C

Yes, uh sorry to stop you, but there's a request to increase the font a bit.

D

C

If you can zoom it just see if a control plus works yeah, it does.

E

C

Yeah, I think this is good.

D

Okay, let me close this.

D

You don't need the yeah, uh so you have under configuration. You have samples and in samples you have different samples for uh all the play like the network, ammo samples, not the playbook samples and so I'll just go through this fabric raft sample again it's almost similar. You will have the network and and then uh that's where you type fabric and then the version.

D

uh We also support two zero zero but uh for uh I think, two zero zero had. We did not create the node, um the channel or the chain code life cycle, so it creates a few problems in our application, which is a supply chain application that is, that comes free with with the baf.

D

But that's why we are migrating directly to 2.2, so you'll see 2.2 here uh in soon, and then we have an environment section. So this is more for uh your for generally for developer environment, when you are running multiple uh tests in in the multiple environments in the same, but you will not always use this. If you are deploying it for production, uh it will be to say type production and then for pro we have proxy.

D

Now we only use h a proxy for uh fabric uh for everything else we use ambassador uh like like here, uh so this is in d, and this is vesu. uh Why we used amber aj proxy was for the tls uh pass through ssl pass through, uh because our as I said, our fabric network itself is tls enabled. uh So it was if we were using ambassador, the tls package were opened at ambassador and uh amazoner was. It was quite complicated to configure pass-through? I think they have done it now, but we have not.

D

We didn't have the time to upgrade the ambassador, so we continued with h.a proxy, which is very easy to do. Ssl pass through so all the uh aj proxy at the proxy. We don't open the package, it just passes through to the peers or the order, and the order opens the packets and hence this is not valid for just there for completion and we have the retry count and external dna. So again, these are your for the cluster.

D

So if your cluster is a bit slow, you can do because our uh when the playbook runs it waits for events to happen. So basically, it will wait for 20 times before the event to happen. If it does not happen within 20 times, of course, then there is something wrong and you can delete, I mean it fails. The playbook will fail. Then you have the docker section uh here again, it's more you don't generally need it if you're using all docker hub images.

D

But of course, if you have a private docker hub, docker repo, then this will be beneficial, because this is how we create the kubernetes secret to download images. Then you have the order section where you define the orders.

D

The order section is common, because all the um all the chant all the other peers non-order, where the peer organizations will need the certificates, because they are all tls uh to to connect to the order, and hence the order section is common, and then you can define channels here, and I saw there was a question of multiple channels. So, yes, you can define multiple channels in this section.

D

In this example, we have one channel and you have all the participating organizations of that channel and out of them organizations, uh only one will be creator and others who will be uh joiner or the creator organization will actually create the channel because we, as we know that the channel creation only needs to happen for one organization and then the genesis name as well. uh You can provide it here, okay and then then comes the organization part. So, as we said, we we uh create uh them.

D

I mean baf is designed for uh multi-party systems, so it has to. It is assumed that each uh there will be different people, different organizations, joining the consortium and joining the blockchain network, and hence we have different uh all these separate of separation. So no, no, except the order section and the channel sections.

D

Of course, where you have the common things right, like you know, you have to know the channel name that you are going to join and you you have to get the order or certificates the public certificates for the orders, but all other organizations are independent so which means that if I am the example that I am saying is that if you are running uh one organization in azure and another organization aws, so you will only have that organization in your network.

D

And so this first one is the order type of organization. So here these are common themes. I think you can go and read and like all them not draining on this one, but the important parts are the kubernetes and vault sections. So that's where you are specifying a different kubernetes cluster. You can, because each organization has their own k test section. So that means you can deploy on multiple kubernetes clusters from the same network.yaml.

D

If you have access to both the kubernetes clusters same as vault, each organization should have their own vault, so they would have a different wallet address and the world root token root tokens are uh generally a will and when you run the around the I mean this is a very operator uh node uh operator framework. So it's not for general. You know developers to run this, because you will only generally run it once when you are doing uh production test environment deployment right, uh but even then the wall root token as well.

D

As you know, the aws access keys and all may be visible in the logs. So we will always suggest that once you have deployed the com component, you should change the access key as well as change the root token, and then we have the github section. So this is where the git tops part, which is basically our operations via get get uh all all the new files that was created during the deployment process will be checked in in this.

D

This folder, uh whatever path you have given and it will be checked in in this git repository and then the services part yeah, so for orders you will have the ca service and then a consensus and then the actual order definition. So that's all the order organization has and then in in a this is another. This is a peer organization, so, in which case everything else is.

D

These parts are same the common parts, but on the services point of view, the peers, they are hosting a ca as well as just peers, and you can have multiple peers in it. So this example is a raft on so you can see. We have three draft orders and for for the peer uh we have uh you. Can you know we? We can do an anchor peer definition because, ideally at least one anchor peer should be there uh right, um but it can be more.

D

uh You can have multiple anchor peers in your uh organization as well. Do.

C

Have the cli option.

D

C

So sorry, in the interest of time, um do you yeah? I don't know if you want to just cover something.

D

Yeah, I think I'll just yeah cover that. So I mean again, these are all documented. I don't have to go through all of them, each of the time so uh just going through going showing the similarities, I mean because, as I saying that it is uh for indian basu also exactly same uh format, you have an environment and you can define extra ports that you want to use for in case of ambassador.

D

This one is valid if you want to deploy, because ambassador is acting as your general api gateway uh for the kubernetes cluster, so you may want to configure the ambassador with multiple other ports as well, which is possible and.

C

So somebody wants to see uh the running p shows running the terminal commands that consumes this yaml.

C

So site.yaml playbook uh consumes this uh whatsapp right.

D

uh Okay, so that I mean yeah, so that's how it is in I mean it's all documented. I don't know if that was a part of this demo, because we we haven't planned an actual uh running of a network in this uh today. So.

C

Watson and for everybody else um today, we just wanted to take you through the components, and uh you know uh how this has been architected uh there's another session coming up. I hope our own confirms on 21st november, where we plan to show you a 15-minute demo for each of these platforms. So, please, you know, look out for the announcement and if you really want to see how things you know how a network gets deployed, uh please uh you know log in on that particular day as well.

C

uh One more question is um for a multi-organization setup how each or gets connected to each other if they use their own separate cloud infra. Is there an any invitation process involved for bringing everyone on same network.

D

uh So uh no so you will have to uh so. Basically when multiple organizations are deployed on uh there is no invitation point. uh So you when you deploy, uh you will be just sharing uh you. They will have a public way to public endpoint to reach, which is which is defined by this external org suffix.

D

So all you are. If you are going to reach up here, you have to have the address of the pair, which will be something.org to ambassador.blockchaincloudpoc.com. This is just an example, uh and then you will have to use uh the actual uh name, the node name, which is defined by this subject, to reach that particular organization. So it's all via the public internet.

D

So so long as you know these the address and the name of the subject, uh you can reach each other.

C

Okay, so um yeah shauna. Do you want to now me to share the screen and.

D

Yeah and go go through the rest of the stuff.

C

Because there's a lot of questions already coming on, you know what is on the.

D

Same thing, yeah, yeah, yeah,.

C

Yeah sure, okay I'll share my screen again. uh So what we are pressing to presenting to you now will cover you know what we are supporting, what we have already built or implemented, and what we really need. Your help. You know a lot of community help um to you know, keep doing it with the same vigor. So let me go to the next one. Yes,.

C

D

Yeah sure so on um on the implementations that we have already done, which is on the on the left-hand side of your screen, we, we do have multi-cluster node deployment for fabric. We support 144 and 2.2.0, which is in the feature branch just remind you. Can I mean the feature? Branch is also public. You can get a pull from the feature branch. If you want to really use it, and then we have the multi-cluster setup supporting kafka for four one. Four, four and raft we.

C

D

Not tested, I mean we did test for two: zero, zero, the kafka one, but two point two is still. As I said, it's still in progress.

D

The credentials and certificate management are involved, and you know you can operate a creation of pr cli, as I show that you can enable cli in in when you create the peer, and you can choose that you not all your peers have a cli, you can have only one cli, then you can do. We can do addition of peers uh on an existing organization as well as addition of peer, a whole new organization to an existing network.

D

Of course, adding a whole new organization to an existing network is more, is more process intensive like it, the playbook will be quite big and all of those playbooks are there and the documentation is also available. You can add an order which is, of course, for raft.

D

You can add channels, you can remove an organization, so removal of organization is, I don't think it's live yet because it's uh in this sprint, as you know, we we run our in our backlog as a two-week sprint. We are, we do uh quite strict scrum, so it's two weeks print and but all the planning and everything is open. We have a planning on monday if you guys are interested to join like what are the things that are happening right now and we do have the integration with the supply chain application ref application.

D

uh So that's that's already there in the roadmap. We have this the multiple organization order that is not yet implemented. So these are the ones. On the left hand, side is where we need community help on and that's why we want your contributions. We have seen quite some contributions already and very encouraging.

D

So these are the ones that are open uh stories or open issues which anyone can take up. So you can do stuff, supporting standalone, couch tv images and then upgrading uh that one yeah, so one point four say eight or something so because we would like to maintain one point. Four point x and two point, two point x. uh So so, if someone goes doesn't it will be quite easy actually just to test that 1.4.8 works? Actually it's not.

D

I don't think there is any code change needed uh test and document of multi-chain code yeah, so multiple chain code deployment we have not tested yet because our application is very application. Specific so and our application only has one chain code and, of course, removal of channels or deactivation of channels. Those are the things that are not supported right now,.

C

And if I can add something here, we also want to know you know if you are working with clients or customers. What are they asking for right because we would want to develop what is being demanded? uh We would want to understand, uh get to hear from you, so so please connect. If you have something in mind, please request for a feature. um You know if you feel that we haven't built something which is required.

D

Yeah- and there is a question in case of adding a new or do you need- do we need access to their vault and control plan yeah. The answer is yes, because otherwise anyone can directly add uh organizing organization uh to uh to the to like that. So basically, when you add an organization you will have to, I have say, for example, take for exam any example of supply chain.

D

So I am a supplier and I want to join an existing uh network, so I'll have to host my own vault and I'll have to host my old kubernetes cluster on kubernetes cluster, and then I will request to the consensus that please provide me your certificates to join the orders and then, of course uh they they they will provide it, and then you will be able to join that uh channel or organization or consortium.

D

C

I think uh there were a few more of people asking about failover mechanisms, uh shana like, for example, what if the network or note goes down. So maybe if you want to address that live.

D

Yeah yeah sure, uh so a network goes down so net. All the failover uh again is uh to be managed by kubernetes, and that is why we are using kubernetes and we are not taking uh the uh what should I say, the the maintenance of of that. It's all that we should be done by kubernetes, because all the orders and the pods sorry the peers, are all kubernetes deployment. So if, if a node fails on your amazon e case, it is again one at one level up, we are using managed kubernetes.

D

We always encourage people to use, managed kubernetes, uh that that is the cloud providers headache to to actually set up uh bring up the if the whole kubernetes cluster is failed, but again uh the advantage that we provide, of course, is that all our code, uh all the configuration like the helm, value files and well as well as the charts, are stored in your get repository and if, if both amazon region is down and uh the whole github is down, so that is a super rare scenario, which means all our lives are in danger.

D

So so that is that will happen very rarely right. So you can actually spin up the whole thing again, but of course that data may be missing, because if your whole network is down so that's when you any any user who is doing it should do their own uh backup and restore strategies, because that will be again client dependent.

B

Okay, I have questions here. Is there any trick how many uh production grid deployed using the vf and uh another thing? uh How do you see the difference between the cello and the web.

D

Okay, so the first question on on production deployment- yeah there has been- uh there has been already production deployments uh in in the range of uh around four uh for baaf and more uh are already.

B

D

B

So, okay from accenture only or from the open source community.

D

So they are, I mean the ones from accenture. Only we know about. If there are things happening in open source, we don't know, I mean I would request.

B

D

Who is there listening if they're using it, please say.

F

That, yes, we are using.

D

It yeah, so we don't.

B

Know it's very important to be know the community, because is there any open source project? How many are in the in production and how people are using it.

C

So kamlesh, I would like to add something here: okay, so open sources is also sometimes a black box, uh the reason being say if our documentation is pretty much clear and somebody is using it and they haven't contacted us on rocket chat. We would definitely not know- and actually this has happened with us, so one of our clients, uh without naming them who were involved with us, not for blockchain, but some some other uh implementation.

C

They contacted the account team saying that hey we are using baf, which is built by you, and then they enquired and reached back to us. So you know they just went ahead and we got information quite late. So um hence the request from the community is that if you know please go ahead, try and use it. um You know, take the value out of it and and and let us know- um because we do have information only on what we have done and within accenture.

D

And that is where we encourage people to join our open planning, as well as open, pi demos, where you can say yeah. I am I'm using it in in xyz, client or even without naming the client I'm using it for our project, uh and we are trying to do this and that doesn't uh do this or because I have a problem so those kind of info. That is why we encourage people to join. Our community calls as well yeah.

C

So one question is: um we can handle multiple applications using buff. I think you're, meaning front-end applications right so shawna. It's plugging. I mean that is.

D

Yeah exactly so, that is how you design your uh your application right, because uh when, when you are using baf, as as I said, we say, we have already open sourced uh the supply chain, application ref application as well as we have for the indie. We have the implementation of the alice, alice and faber university. That example, uh which is the area which uses the aries components.

D

So you have a reference application on how we would like you to design your applications, but you can always go ahead and do it in lincoln in somewhere how some other format, but our application or baf asks the sample that provides is esup is the supply chain application which is microservice design, and it has separate api components and separate rest server or components, and all of them are with kept in my design with micro services principle.

D

So you, if you want to design an application which uses, because the application is not going to use baff as such, the application is going to use the fabric or the basu network that you have created, which is supported which, which is on on the fabric, uh support right. How you design your application.

C

So shrank we are almost on a time one last question from karthikey, which you can see right in the q: a if you would like to take that. Yes,.

D

So kubernetes cluster consists of peer order, couchdb, rs and psa separate right. So this is again how you design it. So I mean, of course, as I have shown you, the. I think there was a question on rocket chat as well. That can you do an order and peer organization, so right now out of the box. Bav doesn't support an order and we are in the same organization.

D

So ah organization can either be ordered and either bp.

D

ah So if, if it's an order organization, all the order components will be in the same cluster, and if it is a peer organization, all the peer components will be in in a different in a in the same cluster and they they can be different from each other, and as I mean, if people know about kubernetes concepts, we anyway create a name space for each of the organizations, so they are logical, even if you deploy all of them in the same cluster, they are logically in in different name spaces, uh so yeah.

D

So that's how it is I mean. Is that what you wanted to ask? Otherwise you can ask the question if it is not.

C

So shanaka, I think, we'll have to now give it back to yeah yeah. So I'll just uh you know once again, this is uh the screen. um I mean sorry. I think I'm.

C

Sorry, yes, so you know please come and collaborate. uh We we have a wiki page where you will find all the details, uh even the good first issues that you can pick to contribute. You can view our roadmap and please contact us on our rocket chat. So this will be shared to all the participants right. Arun welcome.

B

Yes, sprinkle we'll share out these ppt or any material which you are going to share us on our wikipedia page and we'll also send out a video communication link the recorded version of this session, and and thank you priyanka and shauna.

B

This was a great session today and for all the attendees we will have a continued version of blockchain automation, framework on 21st november and then priyanka thanks for that and priyanka has accepted our invite to join again on 21st, and then we will have a detailed version or maybe detailed demo of fabric shown on 21st november.

B

Again, once again, thank you, shanakan and priyanka.

C

B

So continuing our session for today up next we have a great session from attila who is a phd student at budapest university, and then he is going to present to us about hyperledger caliper cypolyzer caliper is but is a tool which we can use to benchmark our blockchain deployments or to you attila.

G

Thank you, aaron. I will share my screen now and hopefully you can see the full screen slides.

G

Yes, okay, thank you. So uh this presentation will be about a high-level introduction to the current version of hyperagile caliper, since the experience in the forums and channels that there is, there are still some general misunderstanding about uh caliper. So my name is attila clark and I will uh do this presentation. I'm a research assistant in the bureau, past university of technology and also a maintainer of caliper and along with containers, nick lincoln and david carson from ibm uk, so just to put caliper into scope.

G

Caliper is a virtual generation generator tool which can target complex distributed systems and it's a performant measurement benchmarking tool. This is an important distinction, so caliper cannot deploy the artist. That's left for the previous presentation and the data analysts are not out of job yet so the caliper cannot perform the effective performance, analysis or evaluation. It just gives you the results of the virtual generation.

G

So that's, I think it's important to distinguish between these uh concerns. What caliper can do and can't do and won't do ever so. This presentation is built around the uh three main traits of caliper, which is its flexibility, scalability and extensibility, and in the upcoming minutes I will talk about these a little bit more.

G

So uh from a really really bird's-eye view. We have hype gadget caliper as a tool, uh and the system under test which is currently can be four types of blockchain platforms: hyperledger bazoo, ethereum networks, hyper azure fabric and fiscal bcos, and you will see a lot of boxes during this presentation. I don't want to go into too much detail, so you won't see too many texts. I just want you to focus on the architecture and components of caliper and their responsibility so from starting really far.

G

Caliper generates workloads towards the system under tests and measures, the responses, that's the main purpose of calliper and from now on, we'll just focus on caliper and leave out the assuts of this equation.

G

So, let's start with the flexibility of caliper at what we mean by it.

G

So as a tool, you give calipers some configurations and measurement artifacts, and this will generate a performance report uh regarding uh the given sqt and what you mean by flexibility is that you have numerous options to configure how caliper interacts with the backend system, how the benchmark is performed, how is structured, etc, etc.

G

So you have three main configuration options for caliper. One is a benchmark configuration not for configuration and the runtime configuration as you would guess. The network configuration describes the system under test. So where can you find its endpoints? uh Who are the participants? What kind of identities are present in the system like user or clients and calliper uses this information to basically connect to a network with arbitrary topology.

G

The other important piece is the benchmark configuration file which will describe the structure of your performance. Benchmarking, namely you can separate your benchmark into different rounds, for example, targeting different smart contracts or targeting the same smart contracts with different kinds of parameters or with different kind of at a different kind of rate for the runtime configuration.

G

I will ignore those you can find the detailed description about them in the documentation, but those can basically affect the runtime behavior of career, for example, performing some task or skipping some tasks or any other intricacies you might want to perform.

G

Since enterprise drts have a strong selling point when it comes to performance, the virtual generator side also has too much this kind of scalability and performability.

G

So caliper tackles scalability issues by using worker services to actually perform this round. So now we split the big blue box into two main component types: a caliper manager service and multiple caliper worker services, the manager service, orchestrates the workers and keeps a means of communication among these services. We will see the options for this soon and the workers are the exact services that actually communicate with the system under tests and send the specified requests.

G

Now the orchestration communication texts are just general descriptions of what is happening between those services, but there are several options to actually implement or configure this option number one is when the manager service automatically spawns child caliper worker services and communicates them through inter-processed communication. This is a kind of a sandbox mode. It's easy to use. You don't have to concern yourself. It's caliper workers, it just works out of the box. You got the manager service and everything else is handled to you. You see a dash line around the manager and worker services.

G

That means the host machine boundary. So when you spawn processes and using ipc, of course, every service we run in the same host, which can impact scalability a lot, a middle step towards the real scenario is when you switch in-depth as communication to some third-party communication method. Currently caliper supports an mqtt protocol, so you can use mqtt broker as a means of communication between the manager and the worker processes.

G

But in this scenario the caliper manager still handles the workers automatically. So we are still in the same host boundary as before.

G

And now the uh last deployment scenario, the rear deal, the scalability version of caliper, where the caliper manager don't manage the workers anymore. You start every service separately and manually and provide them uh common, mqtt brokers through which they can communicate this case, you can deploy your services. uh However, you want, you can scale out horizontally as far as your credit card can reach. So uh really, there is no uh limitation here.

G

When I say you have to manage the workers manually, that's a bit of a stretch, because a lot of container management platforms, like docker's form or kubernetes allows you to simply request a number of replicas from a service. You can say I want 100 caliber workers and it will be created for you, so there is no manual labor involved only just setting up the communication between the services, so this is the backbone for caliper scalability, the fully distributed scenario, communicating services through mqtt broker.

G

The other selling point for caliper is its extensibility and, let's see what we mean by this, so as we discussed, the workers are the actual heavy lifters of calipers. They perform the actual workflow generation towards the system under test and they are instructed by the manager to perform some tasks. So, let's dig into workers a little bit because that's where the magic or so called magic happens.

G

Let's suppose that the manager service says to worker that please execute now the first round with the given parameters and how it's actually done.

G

The worker logic is really simple: it's a main workload generation loop, you have a rate controller component and workload. Module component rate controller component is kind of a delay switch or simply by breaking a circuit break. If you are coming from digital uh circuit design, so then it's time for the next transaction or the last next request. The rate controller simply gives up its control and now it's time for the workload module to actually assemble the transaction and it repeats and repeats and repeats until some criteria is met.

G

For example, you submitted 100 transactions or some time-based criteria, so this is the backbone and the hot pass for the workload for the caliper workers rate control mechanism, that schedules the transactions and the workload module which is actually supplied by the user so by you, and this can be an any arbitrary module and whatever you can code in javascript. So there are no restrictions. Your only job is to when the time comes. So when you receive control in your module, uh fill out the parameters of a transaction and send it to the system under test.

G

Okay. But how do you send it to system under test? Do you have to anticipate for every kind of different platforms or how is it handled by caliper? Luckily, most of the details are hidden from your workload: module with a simple non-magical design pattern. The connector button, so virtual modules see an abstract interface of system under test through which they can easily submit a request or batch of requests and every other detail. Every communication and handle is handled by you, but you see them from you by caliper and the contributors implemented these uh suit connectors.

G

So when I say that caliper can support hyperledger, best ethereum fabric and cisco, I mean that there are four different connectors implemented in the caliper code base that can handle communication with these services and, as you will see, you can easily add your own if you want so, there is no magic involved, just a simple abstraction for your workload module.

G

I mentioned a lot of components here and all of those have some predefined implementations. Some configurable configurability points, but uh the first selling point of caliper is extensibility and that wouldn't be without allowing you to bring your own component to the uh dance.

G

I try to summarize the main extension points for caliper. There are the resource monitors which I didn't cover uh now, because it's not the main backbone of caliper, but basically those are the monitors that can uh look out for any anomalies or track the different data provided by specific sources.

G

For example, we can track the utilization, cpu utilization or other metrics of local processes or local or remote docker containers, or we can just pull such data from a general prometheus server and include the results in our report report or you can bring your own monitor because it's a plugable component. You can, for example, pull this data from your influx db server or whatever you want.

G

The other extension points are transaction monitors which reside inside the worker processes and they receive every kind of event about transactions, so a transaction was submitted. A transaction was finished with these results and you do whatever you want with these data. For example, if you have an internal transaction monitor that actually will compute the performance characteristics of the benchmark, we have a prometheus uh transaction monitor that will publish uh prometheus time serious data about the uh submitted executed, failed transactions and their timings.

G

We have a simple monitor that just drops the results as a log to the standard out to be collected by other pipelines, and you can create a simple transaction monitor to connect your favorite database backend or csv exporter or whatever you want.

G

There are many raid controllers.

G

Provided by caliper, I just listed the main ones: fixed rate, controller, linearly, increasing rate and a controller that tries to maintain the maximum rate without overloading the sut. So, as you can see, the complexity of these controllers can vary and, of course, this is a plugable component. Also so bring your own implementation and the heaviest components in caliper are the sut connectors.

G

We have four of them currently and we have a detailed documentation page about how to write your own connector to your own blockchain platform or any kind of platform. Really so don't hesitate to contribute your own platform to the caliper.

G

Ecosystem, I try to give you some high level overview about the caliper components without going into too much detail to distract you and but you can find everything detailed documented in the caliper documentation side. If you scan this qr code or you can navigate there from the github page and now I think I saw some q a notification pop-up. So I think I will start answering them.

G

Okay, so question: how how to get estimate on how many transactions of fabric supports.

G

As I mentioned,.

G

There is a maximum rate controller which uh tries to gradually increase the transaction rate of caliper until your sut can handle it. So using this eight controller, you can see that slowly the rate climbs up and it will stop at some point because it will detect that fabric, for example, is overloaded.

G

That way, you can kind of estimate the maximum rate fabric can handle, but of course this can depend on a lot of configuration options even in the fabric side. So currently we can't really do these configurations automatically automatically for you. So, for example, we can find the best configuration to reach the maximum throughput. That's still a task for uh designers and data analysts, but with this you can kind of figure out where the limits of the system are or if you use a linear lid controller.

G

You start increasing the rate continuously and at one point you will see your system break down or get overloaded, and then you found your limit.

G

I hope this answered a question, so you need to come up with your own strategies, but we provide some basic components on which you can build.

G

G

Support for multi-chain architecture, no, currently caliper can only interact with a single sut type during a single benchmark.

G

It depends on your scenario whether you can, whether you can, I don't know somehow circumvent this possible. You don't need to have uh in the accessing caliper anyhow, where you can put your in the access in the uh workload implementation which is kind of a hacky workaround, but it would work, but calliper currently supports a single suv per run.

G

Are there any more questions.

G

Or a lot of these are oh, these are the previous questions. Sorry, any more caliper related.

G

Questions, if not then uh head to the documentation site, if you are interested in the details or contact us in rocket chat and uh contributors or callipers channel, and especially, if you want to add your new platform to the caliper aperture, then definitely contact us and thank you for your attention.

B

Thanks artilla, um so there is one more question which is: if there is a demo possible.

G

Yeah, I deliberately didn't prepare the move for today. So live demos are kind of a ghost uh for presentations.

G

There is a detailed tutorial for caliper available from the documentation page, so you can head there, but in the upcoming next release or after that, we plan to do a detailed introduction presentation to caliper, since we left some major updates, then so that will also include the demo.

G

I didn't want to derail the high-level introduction with low-level codes, so I didn't prepare that for today, but documentation contains it. Awesome.

B

And thanks attila, this was a great session and attendees. Please feel free to ask all your questions and attila will be available with us to answer more questions, and you may also feel free to reach out to hyperledger caliper racketer channel as well. So all your questions will be answered there and then you could also join the contributors meeting, which happens, and you will find the details in hyperledger's public calendar of invite and thanks.

B

This was a great session and up next we have a talk on hyperledger explorers and to give a talk on hyperledger explorer. We have two of the maintainers with us at susie and and jiva and hand it over to them. What do you also.

F

F

Hey hello, everyone good morning, good afternoon, good evening, based on your location, so I hope everyone is safe and doing good. I'm jiva from dtcc, chennai and with me is from australia. Together we are going to introduce hyperledger explorer through a presentation.

F

We have been contributing to this project for the last two years.

F

We will have an interactive session at the end of the presentation when you can post your question and we will try our best to answer your questions.

F

So we are going to go through the following topics for this session: the overview of hyperledger explorer terminology. What are the common technologies we have used in that hybridized explorer? Then next features architecture overview, then deployment pattern. Finally, we will see the demo.

F

So hope everyone know hyperledger is a tool for visualizing the blockchain operation of the hyperledger fabric platform. So it's the first ever blockchain explorer for the you know, permission ledger, so it allows anyone to explore the distributor ledger being created by hyperledger members from the inside so but it does not compromise their privacy. So you know it's like a permission, but within the hyperledger member can you know access the ledger projects.

F

So let us now talk about the overview of hyperledger explorer. The hyperledger explorer was initially proposed by proposed by dtcc intel and ibm as a future to visualize the data which is getting stored on the lecture, so the proposal was approved by the tac technical steering committee in august 2016.

F

After that, the development of the tool was started in september 2016, with the many minor releases, the first major releases right, so version 1.0.0 was made in april 2020 in july 2020 we released version 1.1.0 with many improvements and migrated from the javascript to typescript.

F

Currently, hybridge explorers supports fabric and we are working on supporting like a euroha and other dlt platform, also hope it will next releases. It will release that one.

F

Hyperledger explorer was developed using the latest technologies such as react.js with the google material, ui, nodejs circuit, postgres, sql and azure pipeline, so hope everyone know, but I would like to say, like you know, react.js is the front-end framework for the client and node.js is the back-end framework for implementing the server-side component?

F

Websocket is used to push the information from the server to the client postgres used for store the information of blocks transactions and channels, so assure devops has been used to automate the bills and run the test for checking our code coverage.

F

So after we raise the pr right, so it automatically job will trigger that defined by the assure pipeline. So these are the technology we have used in hyperledger explorer.

F

Now, let's look into the keywords which are commonly used in the hyperledger explorer hope everyone know, but I would like to say before uh architecture view features. I would like to say we'll see the terminology based on that. You know we'll get the easily the data so channel. So what is channel channel? It's like you, know uh private of subnet, of communications between a two or more network members that is called channel so peer, each node is appear.

F

Like you know, a computer connected to the network that is called appear, then we are using the term as a transaction. So it's transaction! It's like you know. It's an invoke, invoke a result or instantiated the result that is submitted or ordering or validation and committing for the it's a transaction.

F

So what the transaction is we have created right, so its set of transaction is cryptographically linked to the you know, preceding the sub block, so that is they are calling us a blogs chain. Code chain code is like you know, so, whatever we are, writing our business logic right. We are using this called as a chain code. Our business logic will be there in the chain code.

F

uh The chain code will be written in of the supported language, either go or java.

F

It is like you know, installed or instantiated through the sdk or cli onto a network of hyperledger fabric peer nodes, it's enabling the interaction with the network, short branch. So these are the terminology we have used in hyperledger explorer.

F

So, let's look at the features. What are the features we have integrated in our hyperledger explorer, so this tool provides a you know, provides an user friendly web application for hyper ledger to view the query, blocks, transaction and associated data.

F

Also, we are displaying the network information of name status list of nodes, then chain code of transaction families. Like you know, we can view the transaction. We can invoke the transaction we can deploy or we can correlate the transaction so that features and that we have integrated in our hyperledger explorer, also any other relevant information also stored in our lecture.

F

So it can be. We have other future. It can be used to search the filter and transaction by date and range of channel dynamically, discover the new channels and switch data presentations of channels.

F

Also, we can get real time notification of new plugs. If anything is fabric, new transactions happen, it's automatically triggered to the hyperledger explorer. We can get the real-time notification. Also latestly. We have integrated the user management function, so it this this module right so allows you to create your user, manage the users of roles defined in the default security realm.

F

We must be logged in as a member of the administrator to add and delete the user. If you want to add the user, or if you want to delete the user user would be like you know, must be login as a administrator.

F

So now atusi will take over. Please.

F

B

We can see your screen at sushi.

B

uh I think you.

F

Are on mute yeah, we can't hear your dushy.

B

Maybe your mic is on mute.

G

B

Maybe do you need to.

B

No, maybe do you need to change the source of your mic.

B

And and all that in this we did test the feature just before the call maybe atushi is facing some issues. I will give couple of.

B

B

B

No, I'm probably will yes now. It is better. Okay,.

E

Sorry, uh okay, uh sorry for inconvenience, uh the next slide uh in the next several slides. I will give you our introduction about the architecture of explorer and.

E

And also, I will give you some deployment pattern of the explorer and give you the demonstration showing that how to deploy the fabric test network and public hyperactive explorer and in the end, I will also share our next development.

E

Plan: okay uh in this slide, uh I'm going to explain about an overview of the architecture.

E

As you can see, explorer has a typical three-tier architecture, consists of a front line and.

E

And server background and data background and in the front end layer, there is a react: redux single page application and this dr2.js application get access to this web api server to get data from underlying fabric network and in this server button layer there are two processes running in parallel and one is for providing a data x, api and the left hand side, the other for collecting blocked data from blockchain network and storing these data into database.

E

We call this process as a synchronizer process and, as you can see in this diagram web api server.

E

Basically does not access to the fabric network, it's always looking at the database and the database is basically updated by only by synchronizer process. The synchronizer process uh interacts with the fabric network and the hardware sdk for node.js and for this interaction and the admin administrator of the explorer application needs to specify and use the information.

E

One is the connection profile profile of fabric network and the other one is crypt artifact, which are generated when you started the fabric network, and these two materials are used for accessing fabric network through the sdk.

E

And synchronizer is a periodically watching fabric network to see if there is any change on the network through the service discovery function and once synchronizer gets new information such as a new blog data or new pure nodes, and so on.

E

The information is stored into postgres database and web api server basically used these records to showing for showing each graph on the dashboard.

E

And the synchronizer process does not only query to fabric network, sorry, but also the ship block event from public network when a new block data is generated on the network and this event is passed to the web api server through the inter process communication using message and ultimately it displayed on the dashboard vr web socket.

E

Now and the key takeaway from this right is.

E

The architecture is quite simple, so of course we know there are some complexity in our code base and we still have some called cleanup to be done, but I think most of the technology stack we are using in this project are quite popular and easy to use.

E

So I am, I believe that most of people can easily start small contribution in this.

F

Project one question: is it possible to add only the front end without replicating the data in the postgresql query, from our own tv.

E

F

So they have raised the qa. Is it possible to add only the front end without replicating the data in the postgres tv or query from our own tv.

E

E

Yeah sorry, I think possible to duplicate the front end without modifying any background, so yeah.

E

I yeah it's possible.

B

I think the question is to check if we can use any other database. If not postgres, can we use any other database with explorer.

E

uh At this moment you cannot use any other database, but yeah, that's the answer so far.

E

But we are using some abstraction layer for accessing a database, so with some code changes it should be possible. I believe.

E

B

That's okay, thanks.

E

And and in the next obvious ride, I will take an introduction of the deployment pattern for explorer.

E

And the first one is basic deployment for those who are using explorer first time in this deployment pattern. All related components are located on a single machine as a container and a native application.

E

But fabric network is running on the virtual network on the docker machine and explorer is running outside of the docker container as a native application.

E

So a explorer needs some host name: translation to communicate with fabric nodal endpoint.

E

This first name translation is automatically done by fabric sdk. If enable the option of this translation in the setting of the explorer.

E

In this case, all endpoints on the docker container are exposing port number to the to outside of docker machine like this.

E

So when you configure your connection profile for explorer, you need to specify an endpoint with a localhost and same port number like this.

E

And one more thing in this case in this deployment pattern, you need to install some software, such as, uh of course, node.js and also postgreat database in your host site.

E

In the contrast in the deployment pattern, 2, you don't need to install any software, because all components are running as a docker container.

E

Of course you need to docker machine to do this deployment, but I believe the docker has already been installed uh on the machine, because public network work is already running as a container and in this pattern all components are located within the same virtual network on the docker machine. So they can.

E

They can talk each other directly without any hostile name. Translation.

E

And what you need to do is two things. One uh in connection profile specify each endpoint is a host name which is buried within the token machine and also specify paths to crypt artifact with a valid path. Within the token machine.

E

And this pattern needs less effort to bring up explorer on your environment, but sometimes it requires requires user to understand about the docker.

E

The last one is, each component has been deployed in separated machine or vm or ports. If you are targeting a kubernetes cluster and you can separate web api and synchronize our process into different machines like this, and they were still using same explorer container image, but by overriding some run command for the image and configure changing configure. Now you can bring up a synchronizer process without web api server or.

E

Bring up only web api server without synchronizer process, and if you want to make reliability of a vbap cyber, much higher or workload on web api cyber distributed, then you can also deploy multiple instances in your environment.

E

Deploy multiple instance for web api server in your environment.

E

And that's all that's all my all major three type of deployment pattern for explorer.

E

uh Now, uh I'm going to share I'll, show you the demonstration to bring up hyperledger fabric test network and hyperactive explorer application.

E

uh This is same with deployment pattern. One that is a all component, are located within a single machine and explorer get run as a native application. Let's get started and.

E

Then okay, here no.

H

E

Sorry, the demo start with the cloning of fabric sample depository and once chrome gets done, you need to switch the code base into one version 2.1.1, and you also need to get hyperledger fabric binaries and required to generate crypt, artifact and control a chain code.

E

And you also need to get after finishing to download the binary.

E

You need to add the binary tool to your past environment and make sure that you can call the tool correctly and see the expected margin.

E

Now it's get all done to start.

E

To start net to test network by using script and test network, as you know, consists of two organization and one order which is in common between these organizations and once script finished. You see the three containers running and one is the order node here and the other two, a pr node for each organization and, as you can see, the peer is belonging a channel. In this case, my channel and after joining the channel deploy a chain code to the network like.

E

E

And after completing the deployment next need to define some environment variable for executing chain code, invocation yeah like this and now you can invoke the chain codes successfully here.

E

Now, that's all for the setup of fabric test network and.

E

Yep and the next few steps I will show how how to bring up hyperledger expo for the test network.

E

First clone the depository and next need install the node package dependency for each component, that is, web api server background and react.js.

E

E

And uh yeah now installing that, then she for the client side. That means front end and also only for the front end need for one more step for building the source code of j react.js.

E

E

In the next a few in the next step, we need to modify the sample file of connection profile for running a test network. The sample file located is here.

E

E

We can find here in this file. We can find some path to certificate or private key in here.

E

And we need to get these paths qualified to actual host cycle path, and this sample uh file is by default, prepared for this test network. So uh basically a you only need to change a few parts.

E

And after finishing to modify the connection profile and needs to set up database for explorer on postgraded sql database- and this is a last step required to run explorer and by using a script we provide, you can easily to do this.

E

Setup and once complete script database called fabric explorer is created in the postgresql database like this.

E

And now that's all.

E

Done then you can use start. You can start to explore with the ndp and script.

E

And navigate to localhost, with port number 8080 and robin you can log into the dashboard, which is a administrator credential defined in the uf connection profile. And then we could start explorer with the test network successfully and also you can view the each block, data and transaction. In the separate view.

E

E

And when generating a transaction continuously by using some command line to generating a continuous traffic in the prod.

E

E

Now you can see the notification in the dashboard and also you can see the real-time dashboard updated.

E

Yep and okay, that's all for the demonstration.

E

And at the final part of this introduction from my side, I will share our next development plan.

E

While we keep up with the regis fabric platform and resolving detected issues, we also trying to introduce new features. At the same time.

E

Currently, we are planning implementation of the following two major interesting feature by working together with the new contributors. First, one is newly adding more information and metrics on explorer.

E

In the current prompt, we are going to show the endorsement policy of each chain code to make user easily easier to understand their their network, and it will support the endorsement policy for the chain code, definition, label and private data correction level, and also we try to add metrics.

E

Of each node on fabric network to the dashboard, and we are going to use the metrics exposed from each peer via promises, protocol and the other one. The other major feature is.

E

Raising up the explorer as a next level data query platform.

E

In the current explorer, as you can see a little bit in the demo section, it provides provides the raw data rather than human, readable data for each block and transaction.

E

So this plan includes a tracking feature for historical operation of any specific asset or state, and also automatic schema analyzing feature of a payload in each transaction.

E

By introducing this kind of feature, we are expecting that this feature will provide you a deeper data, insight and more flexible query and yeah.

E

We believe it's, it will be fantastic contribution to the community and we are looking forward to pushing this plan to the release in months later, and that's all my part and in the end and we'd like to appreciate so much to the great contributors and this fantastic proposal and, of course, I'd like to say thank you all for joining this session, and if you are interested with this plan, please always we are welcoming your contribution and please reach out, ask our explorer community.

E

Okay, I will head back to jiva.

F

Yeah, thank you otoshi for that fantastic demo, I'm sure. Now everyone now has a better understanding of hyperledger explorer and many of you may be thinking. How could you help you to contribute right if it would be a great if all you were able to contribute towards the hyperledger explorer project? Okay, so you can contribute by reporting issues, features, request, documentation, update and code development.

F

This is how you can get involved, so you can subscribe and join our mailing list. If you are the first time user, then you will be asked to create a linux foundation id and join the explorer chat with us to start the conversation whatever. If you are facing any issue or if you willing to contribute this explorer, so you can contact us in the racket channel.

F

We also have a bi-weekly contributors meeting occurring every thursday at 4 pm ist time zone. So you we always welcome your welcome you to contribute this project.

F

So these are the links for your reference, uh a link for link to the documentation site. So you can refer this link, then a link to the code repository you can. We have given. I know brief the readme so based on that you will to set up yours locally so based on the link, you can follow that and links to the docker hub, where you can find the image for the deployment so use this link for the reference.

F

Thank you so much now, let's have an any. If you have any questions, so we can clarify that. So thank you. So much for.

B

Thank you very much jiva and let's see it was a great presentation on hyperledger's um explorer so um up next we have a talk coming up from idobu on hype on blockchain right, whether our use case is suitable for suitable to use blockchain, or should we not go for it and how do we decide the life cycle and over to you, you know on the next topic.

B

And it always joining us from in africa.

H

Yes, thank you very much.

H

Can you hear me.

B

Yes, we hear you all.

H

Right, thank you very much. um It's a pleasure to be here. um I've heard a lot of technical um conversations here today. You know from the blockchain automation framework, which I think is absolutely genius uh uh in this, in the sense that it um that it eliminates many of the frustrations and headaches of people trying to um deploy production networks. Okay, uh all the way to caliper.

H

You know a tool for measuring workloads measuring uh essentially an instrumentation and uh efficiency or a metrics uh measurements tool for your for your network uh and then, lastly, the explorer which finally gives us a visual interface to uh interact with and consume the information that has been emitted out of the network second by second, as it keeps on uh operating as it keeps on running.

H

um I've often said that um the future of blockchain adoption is business. Blockchain and you'll see me, and you see that in a few slides to come and then further, the future of blockchain adoption has to will depend largely on the development of abstractions abstraction frameworks. You know um so these three things that we've mentioned today are tools. You know just using that word loosely that help us well human beings to better interact with the highly technical uh information and based foundational.

H

uh You know software or applications that are called blockchain frameworks, so essentially the value of these sessions today and mine that I'm about to start is to help us see how there is value in creating a bridge between that technical base of knowledge. That is a blockchain and interfaces uh tools, abstractions that enable human beings to interact with all of that technology.

H

The best analogy sometimes may be to use something like a car right, because uh uh uh I think that the word dashboard, the most popular use of the word dashboard, is with cars. Okay, so uh probably the most familiar example that everybody will be able to connect with is to think about a car when you think about it. Your dashboard actually in your car, essentially abstracts away all of the complexity of the engine that is driving that vehicle that is, enabling that vehicle to work.

H

So uh uh that's essentially what uh are the points I'm trying to make so uh without, but for much further due our agenda will cover a bit of rudimentary discussions about the foundations of what are blockchains just to set up the stage just to set up the context. So we'll talk about uh what blockchain is. We spend a bit of time talking about why blockchain, because I get the question every day by in in person in charts on linkedin in so many communities, this thing called blockchain.

H

In fact, I remember someone asking me a few days ago relating to the to the current ongoing u.s elections that if blockchains and elections are so revolutionary, why are they not using it in the u.s, and I have to explain that you know some of those decisions are not technical decisions. They are political and business decisions.

H

So um so so we'll talk about those those those human aspects of uh business, blockchain or rather blockchain adoption, okay, so there's why blockchain and then there's why block business blockchain uh now hyperledger as a business as a family of business, blockchain tools and frameworks? What's their vision, what are their goals and what is the market traction? What is the traction? What's the industry saying? How is the industry reacting to hyper layer if it is a hype, if it's type, why is the industry appearing to pick up?

H

I apologize um tools and frameworks at such a high rate. You know- and you see all those things, so we will we'll take a focus, look at uh hyperledger frameworks as well as the uses, and they will give a call to action if you want to get involved, there's a number of things to do so, um of course, these are foundational things. uh um Blockchains typically include the the the ledgers, as well as the smart contracts that run on those glitches will come we'll come to definitions of those things.

H

What's a blockchain at the end of the day, a blockchain is a database right because, when you think about it, a blockchain is an iteration is an improvement. Is an optimization of the traditional ledger. Are our traditional relational databases essentially are ledgers that help us to track information in either transactional format, if you're thinking about ef codes or relational database format or or any other format at the end of the day, a database is a record-keeping system. Right. uh Blockchains are also record-keeping systems, but they have certain characteristics.

H

Certain attributes, certain properties about them that help them be more useful in certain scenarios. So let me quickly run to why why why blockchains? Why distributed ledgers? And you see three major three major considerations? Okay, uh can you see my screen by now? I should be presenting actually apologies for that.

H

Okay, all right! Thank you all right. um um Can you see the presentation.

H

Yes, we see all right. um So what are the concentrations for business? Blockchain? Okay, one blockchains were not designed for individual use. Blockchains were not designed. A blockchain is not a it's. Not a sheet of paper right um blockchains were designed for community use, so you need in theory in principle. You need at least two participants if possible. You know you know more so uh blockchains were designed by definition for communities and ecosystems. Okay, going further.

H

Is there a community of people where they periodically and habitually debates the authenticity of the records of the records of information? Is there a community or an ecosystem where the players in that particular um space constantly have reasons to doubt and or distrust the claims made by other other players? Those are prime candidates for blockchain, okay, so dx are particularly useful in situations where members of a community are mutually and naturally mutually distrustful of one another. Take the use case, the classic use case of banks, okay, banks, all over the world, not just in nigeria.

H

Just in africa, all over the world usually compete with one another head-to-head red ocean style. You know, you know, you know deploying a lot of gorilla tactics against one another, if you, if you, if you envision some kind of product or service or innovation, where you will require those naturally mutually distrusting competitors to work together and or collaborate in order to get value from this new product or innovation that you're bringing on board, then a blockchain is a likely candidate.

H

Is, is electric candidate for for that kind of innovation? Again, one critical aspect of blockchains is what you call the immutable part of the immutability of its ledger. What that means is the third consideration is whenever you want to whenever you are considering a blockchain, it's also important to consider the question: what is the impact of a possible loss of history?

H

What's the impact of a possible loss of, or loss or erasure or tamper of historical data in this particular scenario so take? For instance, um people's bank records, people's financial transaction records, people's employment records, people's immigration records people's um medical histories, okay across different medical service providers, you pharmacies, hospitals and the like.

H

What is the potential impact that, if patients a would step into hospital a1 today, it would there's a significant probability that patient a cannot cannot access his medical histories from hospital b, c and d?

H

That already sounds like a chaotic situation right, because what if there is a medication or a diagnosis that the medic that the doctor needs to provide? That depends on understanding the history, therefore, systems where it is vitally important that the historical log of transactions remains sacrosanct for the for eternity for the for as long as possible. Right, if it's absolutely important for that kind of integrity of the historical lord, then you want to consider blockchains.

H

Okay again, they were designed to provide a near zero probability of term and that near zero assurance of integrity of the lord is provided by. You know uh uh the mathematical, the branch of mathematics called cryptography. You know- and you know that's a bit technical and, like I promised, go technical I'll I'll, be the bridge between the keys and the and the and the users all right. So um so those are the three typical considerations for considering blockchains okay um going further um again.

H

This point just says: it's vitally important to know that your copy of the ledger is identical to others in the network. So uh an additional consideration is at any point in time. If you take the medical service example that I just mentioned, for instance, if, if you are considering going to hospital a or hospital b, you need to have the assurance at the back of your mind before you set out of your house, that, regardless of hospital that you're stepping into your private and valid authentic medical histories, will be equally available for access.

H

When you authorize that access across you know whatever number of medical service providers, if you cannot guarantee that, then that already tells you that there's a broken quote-unquote society or ecosystem of healthcare providers, and then you start to think which of them will give me access which of them cannot guarantee me access. That's already cuts out down what, if the one that cannot guarantee your access, is the one that provides a better service or better service within your budget. You know, so those are some of the considerations.

H

So it's vitally important to be sure that everybody on the network maintains the same copy or the same authentic version of the informational transaction, as the case may be all right. So um this is an example scenario that is very, very popular and it's just a an abstraction or just an elaboration of what I just mentioned about the medical scenario. So everyone in your room takes a book and someone is calling out numbers, okay or calling out instructions, and everyone is writing those things down.

H

Okay, that's number two, and then um there is a request that two people should call out the numbers that they have. Okay.

H

At the same time, uh of course, because there is a there is a there's already a competition because they are doing it at the same time, there needs to be a referee or an umpire or a process to determine who to listen to because they are competing for the same time. That process is slightly technical and it's called a consensus algorithm. We won't go into that, because this technical stuff is for the geeks, like you know, uh but essentially just uh on an overview.

H

That is what a consensus algorithm does it's essentially an umpire or a referee that determines who who's ver who's, whose claim, at least in the in in the present time is, is, is honored okay and when all the parties in the in the mix in this, in that particular room, agree on the the version of information that is being uh proposed. Then everybody records that new version in their private ledgers and then going forward into the future.

H

You can be assured that everybody has the same version of the same information, all right, smart contracts again, um the word smart contracts coming from the private blockchain section of the blockchain space, the blockchain companies and I'll talk about the dichotomy or the differences between private blockchains and public blockchains. Shortly uh coming from the private blockchain space, essentially where the cryptocurrencies have largely played.

H

There's a lot of talk. You know a lot of people who are looking for alternative investments. I've been hearing people talking a lot about smart contracts and the context with which people mention that sometimes has been slightly perplexed. Because, I wonder, are you sure you really understand what smart contract is, but you know, regardless of whatever it means to different people. It just sounds like another buzzword to sell or justify you know, cryptocurrencies a smart contract.

H

A smart contract is nothing other than a set of instructions that are run when a set of conditions that are executed or followed when a set of conditions are fulfilled. That's essentially what a smart contract is. Okay, so um that's actually what a smart contract is. The definition here says the code, which is source code or computer program or code snippets. That is wrong whenever the setting conditions are fulfilled on a blockchain, you see a very interesting example uh shopping.

H

Now this example talks about a talks about a farmer based in sacramento california, who buys an insurance agreement that protects him or her from uh from extreme weather conditions. Obviously, the farmer had envisaged that oh should there be a situation sometime in the future, where the weather conditions are not favorable. To me, I'd like to insure myself against those conditions ahead of time, fair enough, the insurer right, the insurance company thought okay, I'll calculate the risk, the probability of extreme weather conditions happening.

H

I've done my mathematics and it looks like weather conditions happen once in 300 years. Okay. I will therefore ensure you, because my mathematics tells me that I am likely not to be liable in not more than once in 300 years, just just theoretical scenarios, and then they went ahead and documented that policy and said if, for any reason, dear farmer, you experience a steady um record of a hundred degrees temperature for a hundred consecutive days, then we'll reimburse you with a hundred thousand us dollars of of range of of of insurance.

H

Okay, uh that's the agreement. Okay, um the current state of the insurance industry and I mean any innovator that is listening. This is an opportunity for you to start a startup. You know uh the question of the insurance industry is that right now, insurance claims are processed manually, even though there was a prior agreement of the conditions that should trigger the release of the insured sum automatically.

H

After every event, insurers typically habitually continue to review those conditions again right and you wonder, what's going on, was there not a prior agreement?

H

Is there no way with all of the technology in the world today to code some kind of algorithm that automatically you know carries out the terms of the contract based on the conditions that have been fulfilled? Okay and that's and that's the value here- that's that's the gap. Okay, so with a smart contract in place sitting on any type of blockchain fabric saw to basu any of the any of the typical uh frameworks. Okay, um you want to write a script. Theoretically write a script called a smart contract again.

H

uh I I explained earlier that a smart contract is is a set of instructions that are automatically carried out or executed when certain conditions are fulfilled. Now the farmer has demonstrated that the conditions have been fulfilled.

H

There's no reason why the insurer should doubt the claim of the farmer and again we are saying in this case: if there is such doubt and we build a blockchain solution to address this particular use case, then it should be automatic that the farmer, the insurer, should be able to automatically disperse, given that the system also has a way of, of course, verifying that the claims are true. Our accuracy 100 uh accurate. If that is the case, then automatically um disburse the funds.

H

Okay, a similar example to this is what is what is what recently happened in my home country in nigeria, we recently experienced a wave of protests, okay, which got a bit violent, especially in lagos, nigeria, where you, um a number of private residents, experienced damage to their private properties, some people shop owners. Some people are retail business owners, some people they're private cars. You know they just park them in their offices, not in necessarily hazardous or dangerous places, but those cars are those assets were vandalized.

H

I know about a few of them that just got to learn after this incident that the insurance policies they have taken out, even though comprehensive were not covered, or rather did not cover this particular case, because there is some loss there. That says it doesn't cover ios and other civil disturbances and stuff like that. Okay, so, theoretically, let's say that it was covered.

H

I think that certain insuring insurance companies will still look for opportunities to dispute the claims on a case-by-case basis, and I think that this is a perfect opportunity for a blockchain solution right which would automatically verify that the conditions, the list of checklist conditions have all passed and automatically this person responds to the claimants. You know so, um essentially that's the concept of a smart contract. I hate, I have the term smart contract being um explained in all sorts of contexts, and you know many times I really don't understand. What's going on.

H

uh This is the authoritative definition and application of a smart contract all right. The second myth I'd like to debunk is that blockchain is not cryptocurrency. Okay, um blockchain, rather is the foundation. If you think about a house, if you think about building a house, blockchain is the foundation and the cryptocurrency is the house. So um what that means is that uh there are many types of things or rather, let me use another example. Blockchain is the operating system right.

H

We all have laptops, we will have mobiles and device mobile devices and stuff think about blockchain as the operating system and cryptocurrency has just one app that has been developed for and on top and operates and runs on top of that operating system. What that means is that, for all intents and purposes, there are many other types of applications that can be built, deployed, operated and run on again.

H

The operating system that blockchain is so cryptocurrency just happened to get a lot of public attention because it was the first publicly propagated the first publicly renowned instance or application of blockchain as a general technology. Okay, but cryptocurrency is by no means equal to blockchain. If anything at all, cryptocurrency would be one member of the family of possible blockchain applications, and you will see in the following slides how people have deployed blockchain creatively to help integration, identity, management, finance, uh cross-border remittances, all sorts of scenarios.

H

You know so uh just to prove the point that blockchain is not equal to cryptocurrency. All right. uh We've covered that um now. Let's talk about business, business, blockchains um and the word business blockchains you know implies that the term business business blockchains implies that there is a category of blockchains that are not optimized for business.

H

Essentially again, if you think about the history of how we got to where we are today, blockchains started the first blockchain, the first public blockchain, the first problem publicly known blockchain was a cryptocurrency, the bitcoin, the most popular one, bitcoin, okay, and so many times when people speak today they still speak about blockchain in the context of bitcoin. However, over the years people have studied the characteristics, the parameters, the attributes of that particular.

H

Instance, the bitcoin and the cryptocurrency family and they've seen that there are certain attributes that we like okay, that could be useful in other scenarios and there are certain other attributes. That may not be useful in this scenario, so we saw a gradual evolution of the blockchain landscape from purely permissionless public blockchains to something called private blockchains, which are closed ecosystems, unlike the public, open ecosystems of of cryptocurrency, and then nowadays we have something called a hybrid okay which is somewhere in between you know, middle of the road solution.

H

uh What what that has meant is that when people find like, I said earlier, when people find situations where those three conditions- one a community ecosystem, two mutual distrust and three a need to have a an authoritative, sacrosanct immutable tracker log of transactions.

H

What has happened is that people have discovered that it is not all the time that it is useful to make all of the information publicly available. So take a medical health records system, for instance right in any city of the world where you're living.

H

It is easy to imagine that it should be easy for you, as a patient, who wants to walk into any hospital to have access to your or rather to grant access to your personal medical records to the attending physician or medical professional.

H

um If you think about it, if there was no way to protect your privacy, even though it was on the privacy of your medical records right, even though it was on a blockchain of participating medical institutions and organizations, you know carrying out medical operations. uh Sorry, medical! You know medical and medical related operations um is that does that therefore mean that blockchain cannot be useful to us, because before business blockchains came about the only types of blockchains where blockchains, where all of the information is publicly available, anybody can join.

H

Anybody can contribute anybody can create a node anybody. Can you know you know, set up a node and join the network, but in this instance now, should anybody, technically speaking, claim to be a hospital and join that network that contains your private medical histories? Without some kind of scrutiny, I don't think so, and there and and and and there comes- and there lies the point- I'm trying to make- that there are certain scenarios in our everyday lives.

H

Talk about medical histories, talk about finance, talk about uh identities across borders, our visa, our immigration histories and stuff, like that, there are certain scenarios in our in our modern societies and our modern lives. Where is it useful to have the the benefits of a blockchain, because it gives you an immutable history, but it is also useful to have some degree of censorship and or scrutiny to a to a to a minimal degree, not not 100 censorship.

H

That goes back to the days of centralized uh uh database systems, but something that helps us validate that the players in this particular space are people that are validated and verified to be authentic players. Imagine that it's the image that we built a medical systems, blockchain that connects pharmacies, hospitals, hmos insurance, insurance, health insurance providers and and all the other players in that space, and we made it open to anybody to join.

H

It means that over time we will have authentic as well as unauthentic hospitals, authentic, as well as authentic pharmacies and and and and so on and so forth. So that's the that's. That's the point that is being made here for business blockchains, so business blockchains came out of the valley, realization that they asked they are closed systems that need to be operated as closed systems. We want to leverage certain advantages of blockchain and early adopter industries over the financial services supply chain and healthcare. Financial services were all well familiar with that.

H

You know uh we need the banks to work together. You need to be able to carry your identity from bank to bank all over the world. Today it sounds like a no-brainer, but all over the world today, not just in arizona just in africa. Whenever you want to open a new bank account with any particular bank or financial services provider, you need to do something called kyc. You need to start to create your own profile afresh with that new bank.

H

Despite the fact that you have a 20 year, he banking history with bank b, you know, and that's and that jason- and that just sounds like like, like a no-brainer. Of course, there are a few you see in the in the in the coming slides that there are a few innovators that have started to address this particular problem. You know, but uh that's supply chain supply chain. One of the biggest challenges with supply chain is provenance.

H

The the the assurance that the good that you are looking at at the retail level at the at the retail end of the chain uh that started from either the manufacturer or the raw materials producer or supplier is actually what was claimed to have been sent.

H

So people have come up also with innovative creative approaches to introduce a degree of assurance into that process that allows people to trust the movement or the journey of goods all the way from sometimes from the manufacturer, to the retail shelf, or sometimes all the way from the raw materials raw materials are processing. You know, plants or factory all the way through the manufacturer, through all the all the nodes.

H

All the steps in the chain that go to the final retail shop and, if you think about supply chain, there's food supply chain, there's farmers of pharmaceutical supply chain, there's diamonds and mineral supply chain. It's a really really big industry and blockchain has really proven to be useful in that. In those regard, healthcare as well I've I mean I've been using healthcare all morning, so uh the value is clear.

H

All right! um Blockchain now I have been asking a question: my linkedin posts, you know, uh which is to say, and that question is what really really is the hype around blockchain right? It's really just hype, or is it really some kind of revolutionary technology? um The the answer to that is blockchain has been compared.

H

You know has been seen as a parallel to the in the introduction of blockchain in recent times. You know in the last five six five seven years, five ten years has been seen to be a a close, parallel or very very similar to the introduction of the early web back in the days back in the back in the early 90s, and what that what that means is that we all are living in 2020. Today we are, we, we all are familiar with the current version, the 2020 version of the world wide web.

H

If we, if we didn't, make it to 2020 and we were arriving, you know you know if we had asked ourselves in 1995 that can you imagine that this would be possible or the world would be so interwoven into global human society by the year 2020?

H

Do you think that any of us would believe that ultimate reality or that other fictional statement most likely? Many of us would not believe it, and that's the that's. That's that's the that's a similar scenario to how blockchain is a lot of people are saying.

H

How can you say that blockchain can be so groundbreaking so revolutionary that it will be the new business communication protocol you'll be the name it will be the standard for business or protocols and communications and transforms essentially, essentially the same questions were asked of the anywhere you know, but look at what the the internet and the web have done to to to to to modern human societies and modern human life.

H

So um of course it's a long journey, so um some of us may be familiar with what somebody's been familiar with what is called the hype cycle. So, of course there will be some along this 20 to 50 year journey of food maturity. There will be some periods of rapid adoption. There will be other troughs right.

H

uh uh You know along that journey, but overall, if you take the overall journey, we will discover that blockchain has come to state and, as we've seen as we're going to see with many of the use cases that in the coming slides, blockchain is here to add value to so so many more sectors, and it can only continue to increase in adoption all right so hyperledger right.

H

So so uh our conversation is slightly um dovetailing or narrowing or streamlining getting more streamlined. We started with the dlts distributed technologies and blockchains generally, we filtered out that parish, permissionless and or public blockchains aka cryptocurrencies, the most popular of which is bitcoin, were useful in that era. In that early era of blockchains, when all that was needed was to create an open network where everybody can join, everybody can be an equal participant.

H

What we've done was what's happened nowadays. Is that with uh there's now the introduction and hyperledger sits in this category of a new category of blockchain businesses or blockchain products or blockchain systems where people are players rather are unequal in their participation in that space? Because, if you think about the again, let's use the healthcare or the medical services example, every every participant in that player is not an equal participant.

H

The the place of a patient is not equal to the place of a of a doctor or a physician or a nurse, and it's not equal to the place of a pharmacist or a pharmacy and so on and so forth. So uh uh those are the constitutions now among many business, blockchain families or frameworks, or uh you know, families if I can use that word. Hyperledger is one of them, uh and this is where I will comment my own personal comments.

H

Hyperledger is my personal favorite, because it is that particular framework that gives you the shortest time to get up and running with a practical usable proof of concept. So you have. I mentioned a few startup ideas. You have a startup idea to solve the insurance claims management problem right.

H

You can be up and running in 24 to 48 hours if you come and take one of the many production status, production uh ready, high polisher frameworks, unlike other business blockchain frameworks that are not yet that mature, so hyperledger offers the entire community around the world the opportunity to quickly two things. One majority of framework and you've seen the depth of technical experiences that many of the earlier speakers have demonstrated maturity of the framework in terms of technical depth, as well as the speed of quick um deployment to quick, demonstrative proof of concept.

H

So you have a new supply chain um concept or idea for your particular use case, your country or your continent, your region, and you think, oh, my god. How am I going to get a blockchain expert to help me? Do this coming over to hyperledger? I will help you stop a quick poc in in in in in 24-48 hours, and you have something that validates your concept. You can use that poc to to to secure partnerships, raise funds and they can start to.

H

You know, um come back and do a proper build for for the for the system. So that's where I but hyperledger, as as a particular organization comes comes now, it's a consortium. I will go over all of that too much uh because I just want to the vision again. The 50-year plus vision is to change the way business is conducted and and turn the way transactions are excluded across industries all right.

H

uh What's the current momentum, hyperledger currently despite being just four years old, is currently has 16 projects in the in the you see a diagram shortly that puts everything in visual formats uh out out of out of the 16 projects. Five of them are, production are currently in production at production level. So um one of those five is hyperledger fabric.

H

That's the one you've heard everybody mention everybody that's presented today and I presented last year at least mentioned fabric, in addition to others to to other frameworks, so apparently guys the most much much excuse me because it is the most advanced. It was the first framework to be developed, and it has the most uh community support. So hyperledger is currently at, I think, 2.2.1, but at least you know, that's a 2.0 production release there. If there are a few others that are chasing hyperledger hot on his heels, uh sawtooth, there's bassoon, there's bro.

H

Fourth, one now, and they are all also in production. They are not in beta, they are not in alpha, they are in production, so they are also useful in production environment. Some of them are tailored towards specific industries like we know that, indeed, thank you. Indy has been particularly designed for identity management framework. So in a country like nigeria, my country where we are still significantly challenged with identity management problems, hyperledger, indeed, is a no-brainer for us. uh Apparently just sawtooth is a no-brainer for anybody that wants to go into the supply chain.

H

Industry, you know, fabric is more generic and it can do just as well. You know on any of those any of those situations, the training and certification parts there, uh as at this time last year, I think we had only one or two training and certification courses uh relating to hyperledger. This is uh as of right now we have nine uh and they are available on the website. Hyperledger.Com uh 16, active working community groups and special interest groups.

H

Sig stands for special interest, so special interest groups are things like the trade finance special interest group where they think about all the problems and around the global trade finance industry and how to bring business blockchains, especially hyperledger, into that space, 170 bucks worldwide and so on. So far um uh these are. Thank you. This is the dragon that I was talking about earlier, so we have uh distributed ledgers so in this in this in this.

H

If, if we think of hyperledger again, like I said as a family of frameworks and tools- okay, a community of business, blockchain expertise and tools to use to deploy that expertise, then there's some major categories or some major buckets right. It's a distributed! Ledger category of pockets where you have like a like we said uh fabric is a poster child he's a favorite child of the family. uh There's business borough, there's indie ira has sort of these are the ledgers. So these are the main frameworks that operators will interact with on a normal.

H

These are the frameworks that will be deployed by each member of the of the specific network member, whether it's a medical services network, a healthcare network or it's a financial services. That's always a supply chain network. Then there are libraries which are like, which are like foundational, reusable plug-and-play modules that are utilized by all these distributed: ledgers, okay, so think about. uh Well, it's a it's a common concept to technical people to software engineers and architects.

H

But you know when you have reusable modules, so we found people have found when they were building this particular different, distributed ledgers. That fabric has certain common modules and functionality that indie era and sawtooth also have. Why not abstract it out? Why not pull it out and create a reusable package for it, so that, whenever fabric needs, it can call it whenever indy needs it, indy can call it whenever brewer needs a broken, and that's what the library section is.

H

The two sections are like has just been explained by the by the by by the wonderful lady and gentlemen that presented on calipan explorer are tools that help you manage your instance or your deployment. So you have a production deployment of fabric, for instance, explorer helps you visualize. The health parameters is it. You know, you know what are the? How many nodes do you have?

H

What is the status of which is the opposite down just in a visual format, rather than having to go through this typical command line, uh slightly less unfriendly uh format and so on and so forth? So that's what that is. um We can pick them in in focus. Hyperledger like you can see, the starter is active.

H

The code base is passing. We're currently at 2.2, uh stylus and important to know fabric is growing in such popularity has grown in such popularity. That fabric is available as an offering because it's open source and it's free it's available as an offering on all of the listed cloud listed cloud providers. Aws uh google cloud, microsoft, azure tencent by do oracle, sap, ibm huawei, alibaba cloud is here. I know that they do have it. You know.

H

So there are quite a number of cloud providers that have a working available instance for anybody to just go and you know: try their hands out, deploy a product, deploy a test network or a pilot, a concept network and and can take it from there. Sawtooth is also growing in popularity in the specific design for identity management applications borrowed designed specifically for the ethereum virtual machine. So it's something like a bridge between hyperledger family and the ethereum family, which bitcoin and other public permissionless frameworks are funding.

H

uh Business blockchain, eurohaha bc, and these are the libraries that I mentioned earlier, and these are the tools all right so more important. uh The focus of my presentation is not on the technicals, but only use cases and which is what we're about to describe so um excuse me. uh So industry use cases uh cross-border payments right, um there's this collaboration by anz, bmb, melon, swift, the popular swift right and wells fargo.

H

Essentially, if you think about it right now, if my brother in chicago wants to send money to me or want to send money, so I'm in lagos, nigeria, my brother in chicago, wants to send money to me. I want to send money to my cousin in london. um I need to worry about a lot of things. I need to think about. What's the current exchange rate, I need to think about uh what days are these specific uh conversion windows open and all sorts of complexities?

H

uh You know some people have come together to try and fix those market, frictions, smoothing those market frictions by providing a solution that can uh smoothen the process of transferring money across international borders. Reducing the time and money spent in the process reduce the transaction.

E

H

And reduce the time of delivery right health care records. I've spoken about that quite a lot and people are creating. You know um healthcare networks, especially around jurisdictions. So I know that in the united states, for instance, there's a national health insurance scheme that connects many providers together.

H

That's that's already a natural blockchain ecosystem, just waiting for somebody to deploy it. um If you come to nigeria, for instance, we also have something similar. It's called any uh called hmos, uh where we have some kind of system like that. So it's you know it's a natural, no brainer to do that uh interstate medical license. This is specific to the u.s seafood supply chain traceability. So I mentioned earlier when I was talking about supply chains that uh it's possible to track uh things. Many things along the journey.

H

In this particular case, some people have attached iot sensors. So this is a combination of blockchain and iot2 imaging technologies in to try and um improve the visibility right of fish. So if you are in europe somewhere in europe, say paris or somewhere, where you are ethically you, where you are conscious about the ethics of how that fish that was just served on your plate arrived on your plate, then you can download. You know uh uh some kind of apps. You know where someone can provide you with traceability.

H

Of that similar things have been done for coffee. uh Similar things have been done for uh many other products, jerry products, I've seen something for dairy products. uh You know. Are you gonna contact the high college? uh There's a there's, a hyper, agile use case library on the website? Ipad.Org, and uh you know you can see many of these use cases in diamond supply chain. Again. uh You know anybody that is, you know. Just scantily familiar with the process of the demo supply chain knows that he needs some kind of innovation.

H

In fact, many innovations you know blockchain inclusive, so that's also mentioned and then digital identity. So we mentioned this. I also know that uh one of our one of our hyperledger coordinators uh in kenya, mr eddie cargo, has a digital identity product. I think it's called quili. uh That's that also leverages hindi, hyperledger indie. I believe uh he he built that on indy and worked, you know so, but that's really for investment or deployment real estate transactions. You know as well, music and media rights.

H

I'm particularly passionate about this, uh because I have interest in something uh that is that's going in this direction, and you know that's just it. If you think about it, how do you establish that someone's claim on a particular piece of music property is valid or invaluable right now the process involves uh combing through unbelievably huge amounts of audiophiles audio histories over the past 60 years, and then sometimes those laws are different for jurisdiction, so laws may be strong music and intellectual property. Strong rights will be strong in the u.s.

H

They may not be strong in lagos, nigeria. They may not be strong in in in in bangladesh. You know or somewhere like that. So so uh you know that's basically, innovation right. uh That's that green assets, management as well, letters of credits, uh food trust, similar to the fish fish supply chain and digital trade as well.

H

So those are the global use cases um and you know there are a few others, but I'll just run through them because we're we're fast spent for time, but I guess I think that I've answered the major non-technical questions around one is hyperledger just hype right, hyperledger has progressed beyond it's. It is not hyped. Okay. I think I've answered that two.

H

um How exactly is it useful for everyday life? So so so so so, if you step into the hyperledger community, you may be, you will be lost. You know in the sea of technical jargon that is being mentioned, but just relax. uh The there are people like us who can help you bridge between the techies and the and the non-techies, and we can help you see the value, the business value of what you need to uh deploy, so so that you know there are so many things.

H

This presentation will also be available uh uh through mr aaron. The convener of this uh conference they'll be available after the conference, so you can review them and uh you can review the slides and take away what you need. Just you know uh explorer was just mentioned. These are some of the these are some of the projects that are still in the hyperledger labs, which is our experimentation, quote-unquote incubator for new upcoming projects.

H

So every each of the current um hyperledger projects that is current, that is currently in production status, was was at once at one time in the in the labs because it was being incubated and then, after some time he passed the checklist to graduate it to a full status, full-blown project status- and you know these guys hopefully will also graduate out of the labs into the mainstream sometime in the near future.

H

A lot of blockchain showcases, like I said many of the world leading organizations, are members of the hyperledger organization from ibm to oracle, to jp morgan to hitachi. You know you see some of them on the screen already.

H

Thank you very much, and that is my slide last point, um because, just as an offshoot of the increasing adoption of hyper ledger, as we've seen across many industries across many use cases, just as an offshoot of that increased adoption, the natural consequence is that job openings that require high quality expertise are, you know everywhere. Okay, so that presents opportunities for anyone that you know you would would like to cash in on this. To get yourself certified, uh uh there's a link at the bottom of the screen.

H

That shows you where you can access training, materials and certification, information and there's also something called the hyperledger store. Tech study circle, which is a meet up that meets weekly to review uh knowledge and examination preparation material. So, if you're interested in becoming a hyperlink, you're professional- and you want some kind of certification, there's a hyperledger certified fabric administrator, there's a fabricator certified software administrator, and then there are all of these training courses that are available on the hyperledger website. Slash resources like streaming, where you can access that information, and that's me.

H

Thank you very much.

H

B

So there are actually two questions. Would you like to take them up on the q.

F

B

Portal, so it's the first question asked in the use case which you shared on insurance was there's a production one or it's still a proposition.

H

Okay, so so that particular one in uh sorry, two two scenarios- one is a use case- that is, that is in proof of concept in sacramento, california, and then I shared a is a fictional scenario that is still that is closer home to me and and possibly africans, because what just happened in lagos uh a few weeks ago, so the one in sacramento california, is proof of concept.

H

The one with the farmer, the the farmer and the extreme weather conditions.

B

And there is one more question: what are.

C

B

Thoughts on using time series database versus blockchain do you think blockchain can reach a point where rate of transactions are comparable to popular databases?

B

It's basically asking around the scalability aspect. Problem.

H

Well, I think that with modern with the state of modern technology architecture, it's kind of a no-brainer that skill is no longer a problem and I'll explain because pretty much every application, uh I could hazard, he gets and say 90 plus of applications. Just to guess you know, just off top of my head of application of modern applications are built on the cloud.

H

What that means is where traditionally scale was a problem, because it meant that you needed to procure additional physical resources either in terms of memory, hard, hard drive, space ram or some other type of you know, network capacity. Nowadays, you don't really worry about those technical, physical, technical constitutions anymore. You outsource those things to the cloud so.

H

The the potential to scale any application to unlimited levels, automatically hyperledger, auto blockchains, automatically inherits that ability by also if they are implemented on the cloud. So if your use case does not prohibit you from implementing it on the cloud, because that, because I understand that there are certain use cases, some of them regulatory that will prevent certain people from uploading settings or hosting certain information on the cloud, then I think that using the cloud would be a way to ensure or assure that going into the future the application itself never scales.

H

That's the that's the high level generic answer to that question. In terms of specifics, I don't think so. I think that, depending on the efficiency of the specific business logic that is implemented, remember we mentioned that smart contracts are the implementation of business logic in individual networks, uh depending on the specific um excuse me, depending on the specific.

H

Business logic, depending on the specific algorithms that are built to handle the business logic uh it should be, it should be easy to optimize those algorithms for skill. Thank you very much.

B

Thank you, though, um thank you for thank you for the presentation and with this we come to end of today's session and for all the attendees next week we won't be having a session, so this is a week of festival for in in india, so happy deepali to everyone in advance.

B

We hope to celebrate techfest the coming week, which is on 21st november.

B

So once you celebrate the festival, let's join back and let's celebrate the technology festival again on 21st, we on 21st we'll be having a continued session on blockchain automation framework with a demo, and then we will have a session on mini fabric, that's a tool which we can use to set up a network on our machine and quickly set it up test out things, write chain code and and do all that kind of things, and, along with that, we'll also have a topic on identity.

B

How do we write a client, for example? How do I use hyperledger aries and build a solution for identity use case, and we hope to welcome you and seeing you on 21st november. Thank you all.

B

Yeah. Thank you all.