Hyperledger Foundation Meetups, 3 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Building Hyperledger Fabric Smart Contracts using Solidity and the EVM

Description

A virtual meetup run by Hyperledger Boston on November 3, 2022 featuring Jim Sullivan, Chief Technology Officer and Lead Instructor at The Blockchain Academy. This workshop covers the following topics:

* Hyperledger Fabric product architecture, including the EVM/Solidity components.
* Smart Contract Development demo
* Solidity Smart Contract Examples
* Why use the EVM for HyperLedger Fabric applications
* Use Remix for building Smart Contracts
* Solidity.
* Data types.
* Functions and Accessibility, i.e., public, private.
* Deployment Demonstration
* Distributed Application (DApp) demonstration
* Possible Next Steps.

To learn more about Hyperledger Fabric, feel free to check out their wiki and join the Fabric channels on Hyperledger's Discord server.

Fabric wiki: https://wiki.hyperledger.org/display/fabric/

Hyperledger's Discord server: https://chat.hyperledger.org/

----
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

Discord: https://discord.gg/rVCn4j7UFd
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 #Blockchain
License
Creative Commons Attribution license (reuse allowed)

A

Jim Sullivan today from the blockchain academy, is our presenter so welcome Jim and Ryan, uh who are going to be working with us today and leading the presentation before we get started. I do want to just take a minute to let you know that this is a hyperledger sponsored event and there's two things that are important about that one is we have an Anti-Trust policy, the Linux Foundation meetings involve participation by industry competitors and it's the intent of the Linux Foundation to conduct all of its activities in accordance with applicable, antitrust and competition laws.

A

So you know, please don't participate in any activities that are prohibited under any U.S or foreign antitrusting competition laws. If that's an issue, then please, uh you know, stop your attendance today at the meeting. The second thing is the hyper Electric Code of Conduct, which is very important to us as a community. So hyperledger is committed to creating a safe and welcoming Community for everyone. We treat each other with respect, professionalism, fairness and sensitivity for our differences and strengths at all times, so any uh feedback.

A

You know at the end of the presentation or questions or whatever. Please just be respectful of everyone else and be professional about it. That's all we ask and there's more in the hyperledger code of conduct and the Anti-Trust policy at the linuxfoundation.org.

A

So with that, let me uh stop my side of it and turn it over to Jim Sullivan. uh Who is our presenter today? Jim, you want to take it away. Okay,.

B

Great, so thanks so much Jim, Mason and again welcome everybody, a special thanks to uh David Boswell over the Linux Foundation, one of our Linux Foundation leads, and certainly a community lead, and uh thank you to uh my colleague, Ryan Williams, also for uh putting together all the documents uh that we will all take a look at afterwards and uh again. Thank you to Jim Mason for uh for being one of our session hosts, as well as running uh the the hyperledger uh communities and uh particularly the Boston uh hyperledger community, so again welcome everyone.

B

We're going to discuss uh the ethereum virtual machine running on hyperledger, so uh there's a lot to talk about as a lot of you uh know or will know we'll. uh So, let's, uh let's get started, please let me know if you can uh see my screen or if anyone can't see I am sharing right now um bear with me here. One second I do have to do the swap.

B

So uh what we'll talk about is we'll just refresh everybody's memory here of our hyperledger fabric architecture, including uh the ebm and the solidity components uh we'll look at a with some demos of some more contracts and some more contract. Examples on solidity. uh Why we use the evm for hyperledger fabric applications, we'll take a look at some of the tools, including remix.

B

This is the big one for building smart contracts and, again we'll see uh solidity running in remix, some data types and some functions we'll do a deployment demonstration we'll also take a look at the the Truffle Suite as well, uh because that's also supports uh hyperledger fabric EDM and we'll do a what we want to get to obviously is uh most likely our distributed application.

B

uh So we want to get our uh our hyperledger applications running as dapps or web at least web applications, possibly even mobile applications, and then uh we'll discuss some next steps, so I'm sure.

C

Everybody's familiar.

B

With the hyperledger architecture, we'll see a few examples of this running live, we have our client applications. We have our various peers or ordering peer, as you can see these between we have uh set up here. This is a private Network. It's running here in in this case at more than one Enterprise. So uh this is a.

B

um This is obviously a Consortium Network, and we can see here that both Enterprises have access to client apps and uh these all of these peers are in communication, the ordering peers guaranteeing uh that the guaranteeing transactions that are being stored in the ledgers at these various peers and these peers have several ledgers. Hence the name hyperledger fabric so, and we call those chat and not everyone. So not not. Everybody in this Consortium will have access, as we can see here. Some of these peers have channels that are not necessarily accessible to Enterprise.

B

A here, uh you're, probably quite familiar those of you that have worked with Hyper Ledger and when we install it. uh This is a typical install path.

B

So, under the hyperledger directory, we have our fabric samples and we are going to install a directory here with our evm chain code and then we're also going to update our uh one of our yaml files for Docker, with uh this volume here pointing us back to this evm chain code. So um look for this and I'll try to point this out during the uh presentation, but I'm sure a lot of you are familiar with this directory structure, and so why use the ethereum virtual machine for hyperledger fabric uh well uh for reuse?

B

Certainly so what you have developed for uh for any ebm applications, whether they are on ethereum or.

D

B

They are on Quorum or some other evm uh networks, some dlts. You can also now use them on hyperledger fabric so and there there also is commonality. So we want to preserve that commonality, so uh you can uh participate in the community, have a a common approach to creating our applications. Our DLT applications, our blockchain applications, but there's obviously a big Community already for the evm. There are multiple, multiple resources, as we can see right here right. There are already resources out there for uh the evm and hyperledger EDM. We can see here.

B

This is actually documentation on using a hyper Ledger, Fabric and the EDM. So we can see here just from these two different Enterprises here and uh there's certainly a lot more reasons, but those are those are some good ones.

B

uh What we want to get to ultimately is if we can. Hopefully you can see this I know. We will get a look at this, but this is here are uh our peers and our orderers here this is our hyperledger Network. um This is going to be running. Virtually uh first thing.

B

We'll do is uh we'll install the evm on hyperledger fabric, then we'll deploy the ebm smart contracts to hyperledger fabric and then we'll install node.js web 3, uh certainly a more friendly way to run the ebm, and that will ultimately we're not going to do it today. But that will ultimately bring us to uh running Daft in.

D

B

Of web applications, and maybe even mobile applications, uh not in uh that that would be the next step, but we'll go we'll actually run node and web3 from the uh hypoelectric command prompts or from the node command prompts. So for uh so we we can.

D

B

We'll deploy the evm on hyper electric fabric, we can see here our chain code running our uh we're instantiating, that that tune code, pvm chain code and if we go backwards here just for one second, this is what we want to get to. We want to get to that ebm CC running. So a lot of you may have a lot of questions already you're, like oh Jim, you're doing that evmc you've heard a lot about that.

B

Well, I promise you we will touch on the subject of the archive of that Repository and then part three is we are going to get uh we'll we'll? Have our we'll run our uh solidity contract, both natively from a hyperledger pier and then we're going to go back into node.js and we are going to uh run our smart contract from node.js and it's certainly a much more friendly approach?

B

Okay, so let's take a look. Everybody came here. Nobody came here to listen to me talked.

B

uh Bear with me here one second.

B

Okay, so uh hopefully everybody can see my command prompt here, so we're just running out of an Ubuntu image and okay. It looks like everyone can say it. So what I've done is I've cloned? You could, probably, hopefully you can see it up here- uh I've cloned the GitHub repository this. Is it right here, so we have our hyperledger Fabric, evm or chain code evm, and this is the repository of cloned I'm, sure we're all familiar with Git clone right, just uh essentially just run the command for the git clone and it installs right here.

B

So we have our hyper Ledger directory and we can see our fabric chain code right in there. So what? What we'll do? First is we'll start on the docker.

B

So let's go down I'm sure, you're again familiar with this with the basic Network.

C

Sorry, I'm gonna go down one.

B

B

And then we'll go down to our basic Network.

B

B

So let that start there'll be a few times where we have to watch things uh running, but uh I promise we'll we'll keep it to an absolute minimum.

B

Okay, great, so that's that's up and running now and now we want to go back to uh I'm sure you're familiar with the first Network, and we want to follow some. uh Some steps and I'll show you where those steps.

C

B

You will have access to all this information when we're done.

B

And let's clear this, so what we're going to do is we're going to follow the steps here in this repository under examples.

B

B

So now what we're going to do is uh we have all these steps in here so we'll go through we'll we'll update some uh we'll configure some volumes start our hyper Ledger Network go into our peers at some environmental variables. Then we will install our ebm chain code. We will instantiate it with a channel name.

B

Then we will invoke the the chain code again with the channel name. uh That will also give us a contract address. So there's there's a few little laborious items. We have to do like tests and contract address and channel name and all that um this is actually our smart contract. This is the byte code for our smart contract.

B

Then we'll invoke our smart contract with the contract address and the channel name and we'll run it natively and when we run it natively it's going to uh we're going to be using some hex data. um So you can see the hex data right here and the hash, uh but that's that's still important. We will uh go ahead and do that.

B

It's so important to do that, and then we will, after that we will uh scroll down here a little bit and we will use web3, we'll install web3 and node and run out of that with our Fab products and service.

B

So what we'll do here is we'll we'll edit our Docker compose file and we'll add that volume. So we have our Docker compose file right here.

B

B

And, depending on your.

C

B

Editor I'm just picking this editor, just because it's more of a friendly, editor and I don't want to make any typos or struggle with anything.

B

So uh down here under volumes, so under CLI volumes, so we actually passed CLI on here there. Here's the CLI that we show here in this documentation CLI volumes. This is where we want to add this volume and because this is really long, I have put this in a little document from me. So I can just do a quick copy paste. So forgive me if I'm copy pasting a lot but I just it's it's a smoother way to go for a presentation. You don't have to watch me type and type incorrectly.

B

Now it's important put some spaces in here. You may be tempted to tab, but don't tap. Okay, that looks good and what we'll do here is we'll save that and we'll exit that.

D

B

What I like to do, sometimes is cut it.

B

And just for a sanity check.

B

B

Here is our volume- that's added here, that's fantastic.

B

And I'm just catching up here in my documentation. Now we are going to run our hyperledger Network. So let's clear this and we're going to use the bring your first Network dot sh.

B

D

B

Have hyperledger installed on here.

B

So that is obviously a prerequisite. We will need the network installed and running uh and just bear with me here, while this double the network starts up, it takes about two minutes for it to start up.

B

So next, while that's running uh well, so this is where we bring the network up and next we will be uh going right into a pier and installing some environmental variables and the evm chain code.

B

I'm hoping this is clear for everyone to see. I I am on like a lot of you that are developers and we're software. Engineers I have managed to uh completely. uh Let's just say: I've uh I've stepped on my my main uh developer, laptop and I've had to switch to a different one. So I don't know I, guess it's opposing the environment. I'm sure many of you have opposed the environment. I did something to the uh the hypervisor and it just doesn't want to restart for me. So.

D

B

Of just wasting a lot of time with it I just moved to a different laptop.

B

It's a good thing about virtual images or if you can import them anywhere,.

B

So this you would do in really any instance, oh great, so our uh so we have our hyper Ledger Network up and running and we have our uh Genesis block and all that. So that's that's great. Let's clear this and now let's go into the docker.

D

D

B

Okay, so now we're we're in this pier and the next thing we're going to do is set some environmental variables.

B

So here we are in this is a document that that I'm, using and but I am following this documentation. So here we are in the pier and now we're going to set these environmental variables. So we have a configuration path right here. We have a pure address. You can see here uh we have some a local process ID and then we have a path to a certificate. So we want to set I mean it's important that we have all. That said.

B

So what I'm going to do is I already put this in here and it's all tedious typing, so we'll run this and set all.

C

B

Environmental variables, this way.

D

B

Okay, great so we have those set and what we are going to do next is. We are going to uh install the chain code on all the piers.

B

And I already have that right here. So we have our peer chain code installed.

B

And this takes yeah about maybe a minute or so. Oh okay, that came back already so stat is 200 degrees. That's what we want to say, then. What we want to do here is we want to now instantiate. So we've installed the chain code, but now we have to instantiate it and give it a channel name.

B

um So I gave it the channel.

D

B

My channel, which is probably overused, however, the uh there is later on in the documentation of my channel, is New. So just so, it's a little less confusing I have just chosen to follow what is in the documentation and I'll I'll. Try to point that out. So here we are now uh we'll get the instantiate command.

B

And we'll paste that in and I have already added my channel in here now, if you are using the these documents, obviously you've got to overwrite here, uh channel name with a channel name.

B

And this takes about another minute or so so this is instantiating.

B

And we're giving it our uh the chapter.

B

So this is installing the evm on all the tiers.

B

Okay, great that ran now now, uh let's uh very briefly, open another terminal and take a look at our ebm running.

B

So if we do Dr PS just from here, and so we can see all of our order well or we can see our peers, our order, P or zero tier one- a certificate Authority, the couchdb- and if we scroll up right here, we can see the evmcc right here and- and the name has wrapped you can see this name wrapped to the second line. So anything.

D

B

On the second line here at ebmcc, so we got it. We we have the ebm now running on our hyperledger fabric, Network, all right.

B

Now we want to now we're moving into part two here. We want to deploy the ebm smart contract on our hyperledger Network so before we do that, let's take a look at the Smart contract, we'll be working with and what's needed to deploy.

B

So if you are from now, this is remix I, don't know if uh hopefully you're familiar with remix. This.

D

B

Well, it's uh it's a solidity development environment, but it supports other development languages as well, not just the solidity, uh but we can see here. This is a very basic smart contract so but won't.

C

B

Matter with you on basic or whether you've run a more complex, smart contract, all the same steps we in our uh remix here and again, it's a remix, Dot ethereum.org.

B

uh We see here it's a community, it's free, it's a community based um uh IDE and it gives you it. Ships with a uh an environment, a back end, a runtime environment, a virtual environment, and it also gives you a very basic uh user interface, all which are good.

B

So we have a contract here, called simple storage and, if you're familiar with Java and how Java works, there's the Java virtual machine we're going to use the ethereum virtual machine, so our contract, simple storage, that's like the Java class, very similar to a Java class, although we don't have a main function here uh we see here we have an unsigned, integer called store data, and then we have a function to set store data and then a function to return store data. So it's pretty basic.

B

But when you see how we'll be running this, we kind of need a basic type of user interface. First thing: we're going to do is compile this so we're going to click on this compile solidity compiler button. Would they call this a module and we're going to click this button to compile the smart contract? Oh good, that compiled now what's important here well number one. The compiler version is important, but also this ABI and byte code. So the ABI stands for application, binary interface.

B

So if I click this button here from the compiler I can copy. Unfortunately, all I can do right now is copy this to foreign this text file, but, as you can see, the application binary interface is in Json format, and it's. This is what part of what uh or smart contract is compiling to when it runs on the ethereum virtual machine, so very similar in approach to the um again to the Java virtual machine. If you're particularly familiar with that and.

D

B

Item here is the byte code, so we're going to get the byte code and then we're going to copy that into this document as well, and let's just get a lot more, we'll just eliminate as well. So this is the byte code. We're interested in begins with 6080 or 6080 I'll point that out and if we scroll all the way over here at.

D

B

End, it ends in zero, zero, two nine. So this is the byte code for our for our contract for our smart contract.

B

And if we, when we run this and other things, solidity gives us- and you know we're here- to talk about tools as well. uh You can connect to solidity. You can connect I'm, sorry to hyper Ledger I'm running out of a DM, with a very crazy Network here, uh I'm just using the um the out of the box virtual environment here for remix, and you can see there's uh several, uh but you can also connect to an external HTTP provider. So it is possible to connect. But unfortunately, today, I can't do that.

B

The way I my environments have been behaving, but what we can do is deploy now this smart contract and when we come down here to this section that says, deployed smart contracts and.

D

B

Expand- and we can see here- the user interface, so we can see the set function has a button here and our get function has a button, and so we can set our stored data to.

D

B

An unsigned integer, so we can click the set and remix gives us some feedback there. So we can see that that was successful, and now we can click the get to return it. And then we can see it's one zero one, but we want to change it to.

B

B

And we could also do well. We know I've been.

D

B

A lot about the lottery, uh at least here in the U.S, so 777 that might be lucky and we can see here so pretty straightforward. uh The important things here are the byte code and the application binary interface, because that's how we're going to deploy our smart contract, we don't have to use these tools to deploy our smart contract.

B

So now, let's come come back over here and let's deploy our smart contract so again, I have this. This is a very long command here.

B

And we'll take a look at this.

B

And why don't we clear this.

B

So if we look closely in here, we can see that my channel is that uh you can also see the byte code for the smart contract, 66080 and all the way down here: zero, zero, two, nine! So right there. This is the the smart contract. So this is how we are invoking and uh deploying the the smart contract.

B

So again, if we go out here, we can see here. This is the invocation of the smart contract with the arguments you can scroll all the way over here, it's very very long and it ends up with a path to the certificate as well. So that's important.

C

B

Let's go ahead, and so that was successful, so uh but very important here notice, the payload that's returned from this invocation. This is the contract address and we're going to need this. This is not. Obviously, this is going to be different every time, so you never get away from your copy pasting.

B

And we're going to have to come down here to our contract, address overwrite right here and then let's say that once we do that we're going to have to update this item here to make sure that they all have the correct contract address.

B

If you want everything to run smoothly.

B

Okay, so the first item we're going to do now is we're going to validate uh we're going to query the channel and get the code that was up that was loaded as our uh smart contract. So we are going to run here. We're going to. We have to pass in. Obviously the channel name and the contract address. We've already done that at least in our text file, and then we should get back.

B

The uh the payload here what's returned is the byte code for the smart contract again beginning in 6080, going all the way back to zero zero, two Dot.

B

So again, this is the query of our channel.

D

B

So let's get our query.

B

Copy that foreign.

B

And great, so that's what we got back: six: zero, eight zero and zero zero two nine! Hopefully everybody can see that so we're we're getting back the byte code of our smart contract. So so far things are looking up.

B

So we and now we want to it, we.

D

B

To pass in so we want to uh invoke our uh smart contract and passing the channel. A smart contract need now. You can see here what we're using to set and get we're using the uh we're we're using this uh hex value of.

D

B

Looks like this if you're familiar with hex, which I'm sure a lot of you are right, you go a is uh 10. right it doesn't. We don't see what looks like 10 until 16 in the hex world, so we're we're going to pass this in. This will be 10 and also the set in order to call set the hash for set is uh right here, so it begins with six zero f. So that's what we'll be doing here and.

B

So let's get our okay, we've updated this command and which is some of the TV most tedious parts of this, and let's go ahead and clear this and then let's paste it here.

B

So what we're going to do is we're going to call our set and we're going to have this long set a and we and we have the smart contract address.

B

So that was successful. That's great! Now,.

C

B

We want to do again is we want to run the get so the hash function? Forget is right here, so we can see it right here um and obviously the channel name and the smart contract address so 64..

B

You can see it right here. 64. we've already put in our smart contract address into my channel.

B

So what we should get back here is that long date, this long data that ends in a.

B

And that's we got that great. So that's all good news now that we've pasted in all these, we can just do some manipulation. We can run another I. Just it's uh I just did the up key just to return our history and let's change here. We can do so. We can manipulate our hex data a little bit.

B

Let's end it with seven and run that so now we have a different set and then we can also uh so this is the chain code invoke and now, let's do the chain code query right on that contract address with the get and there there's the get right there. I know it doesn't look like yet, but there's a seven brought back and then let's go to our history. One more time.

B

And there's our uh let's put a three in there and run that great, that's successful. It's always good to see and then run our query there and that's brought back one other query we can run is our account, which will always be useful.

B

And what's clear here is this gets a little cluttery and what this is going to do is query our our account here.

D

B

My channel so that'll be our our account. So as far as the evm, that's our account. um Let's.

B

Add in one more number here.

B

Maybe we'll put five in there run that that's accessible.

B

And then we'll query that with the get that's right here and we get that back, so that's good, so that that gives us a lot right there. So we know that we know what to do. We know we can run smart contracts.

B

However, we have all these hashes. We have all these hex hex data and who the heck wants to use that, certainly not me. So what we can do is use node js and we can use web3 and what they have here for us is a a service.

B

This is the fab3 service which is going to run on Port 5000.

B

A

B

We navigate in here and we go to this file. We will have several environmental variables that we will set here. This is part of the actual. What we're going to want to build of this shortly and we're going to see the channel report name. So this is what we are.

B

um This is what our service our Fab three service, is going to connect to, so it is going to be our evm provider running on uh hyperledger fabric. So, if you're familiar with the ebm and um the you and node.js and web3, you need to indicate who your uh evm provider is. In our case, it's going to be this bad three service and I know you probably have some questions about the bad thread and I promise. We will get to that in the second hour of today's presentation,.

B

So, where we're going to go with this is okay, so anything else here nope we got all that so now we're going to go through. So we have this. We have to set up our Fab to create proxy a little housekeeping. We have to do before.

B

uh We, uh we use our Fab 3 proxy at least I have to do it is we have to set the go path and for whatever reason, I have this, but my maybe it's my permissions on my network I'm, not sure, but my permissions don't seem to be correct, so you'll notice there are a few imperfections. Everybody's network is going to have a few imperfections, I'll point that out. So, let's just exit out of here and clear this, so everybody take a brief. Like big brief breath, we got our we.

B

We have our uh EDM running here on hyperledger. So if you are a uh if you're an evm developer, a solidity developer, you also could say: hey I'm a hyperledger developer now, I know how to develop an hyperledger fabric. I know how to deploy my chain cut or I'm. Sorry, my ebm smart contracts on hyperledger fabric. Now we're we.

D

B

Running it natively so, and that was uh not that friendly of an environment but hey, you know we're able to do it so, which is a big thing.

B

So quickly, here and I've got to switch back to this network. Here, I've got to run.

B

So my permissions are not correct. Now you may not have this problem, but but this is the worker now that I have and all of us have that work Works around.

B

D

That command wrong.

B

Okay, so that looks like it ran correctly um and then let's just check our go path, so we have to Echo I've already set the go path, but we uh in in uh our document we actually included how to do that at least for this environment.

B

Okay, so there's my notepad.

B

Now we've got to navigate down to foreign.

B

Er chain code directory.

B

So we're going to be running out of here so first thing we have to do is again set these environmental variables.

B

So our environmental variables are going to be here or we're going to set a configuration path where we have the user, uh the um the Fab org and is our org name, the channel name notice. It says my channel are we're using our evm chain code deployed in our fabric, Network, here evmcc and we're going to be listening on our Fab proxy is going to be listening on Port 5000 and again, where does that all come from? Well, if we go again into Fab three.

B

B

Here is the the config that we saw the user, the Org, the channel, uh the.

C

B

And the port! So that's where that's what we're looking to do in this step so again, just to make things easier, we'll copy all these into the buffer.

B

And I'm in the right place.

B

And that looks like it's all set.

C

B

We'll just double check that our go path, which is right up here, is returning, because that can be a big headache. If uh so, we'll just we'll Echo our fat, three config.

B

Okay, that looks good.

B

So now what we want to do is now we want to build our Fab 3 service.

B

So what we'll run a make on Fab three and build this binary.

B

So again, this might take a minute or so, if you don't have the permissions right, it's not going to work. If you don't have to go path right, it's not going to work in this case. You can see here that I. That was one of the items. It's not always it's not always obvious what the problems are, particularly when it's environments and um and permissions you don't always get the feedback from particularly a make. That's a lot of you know, okay, good, so that ran.

B

And what we can do here is see what it gave us, so we can do an LS on the binary or in the bin directory, and we say we have this fab3 executable.

B

So now, let's, let's run it.

B

Okay, great so now this is running it's running this service. So let's don't close this once this is up and running you got to let it let it run. Don't have to open up another terminal window.

C

B

We can actually see it from the browser, so we know it's running on Port 5000.

B

and again the Fab 3 is our evm provider. So we pass in 5000 there and we say: okay, great, so that's running right. There.

B

Okay, for hopefully, everyone can see that okay, so the next thing we have to do is we have to open up a new terminal window.

B

And hopefully this big enough for everyone to see.

B

And I'll just scroll.

D

B

Here, because now we're interacting with web3.

B

So we we have now our web 3 running. So what we're going to do now is install node.

B

In that right now right here, let me make sure I'm running out of the right place: nope I'm! Not so we got a seat down to foreign.

B

So let's install web 3.

B

Now we're we're recommending a certain version here. uh If you install the latest uh I believe I did install the latest as well. uh I didn't really have any issues with it, but now I have some issues here with uh and then we actually have to run a node session I'm having some issues on my network, my Network's a little slow, so it is re it does. uh There are a few times that we have to run run a command you'll.

B

You might notice it I'll point out, uh don't get discouraged if, when running or uh node application here, if it returns some errors or if it runs it into if it returns an endorser error, it's uh just that it's well it might. You might not have this, but I am having a little bit of uh of a slow Network, so I'm I'm uh up against that.

B

It's just uh come back here and let's require web 3.

B

for our application.

B

Great that runs, and now what we want to do is create this web three object and what we are going to do is create the object and the call web3 with our with where our uh evm service provider is listening. So that's what we're doing here, so our provider is listening onto our localhost 5000.

B

great. So here you get a lot of feedback when you use node, uh so we've got to do control, L, that'll, clear that node console and now we want to return our accounts and we want to set a default account now. I'll show you how this differs a little bit so here I have that account brought back now. If we look at the documentation here, uh you can set your default account to the first item. That's returned in accounts, but for me that's not working. So what I have to do is again.

B

This is uh I, don't know if you want to go to work around, but for me what I have to do is I have to copy this in.

B

And then I had to go up to the account that was returned here.

B

Maybe the data structure is not exactly the same I'm, not sure, and and then that works so notice, this hash feedback versus hex feedback that we get from uh from node.

B

uh Now, what we're going to do is we're going to go back to that ABI. So uh we have we're setting ABI to uh this. We're setting this value, simple storage, API, we're setting it to the texturing of the smart contract, API, so I think we looked at that right so that that's what we're going to do here. So this is how we're going to Floyd and so we're going to do the simple storage.

B

Again, there are tools that eliminate a lot of this, but we don't want to necessarily want. We want to go through this this process, and then you know, I will have a better feel for the tools and we'll add that, and if we look up here now, uh simple storage API is now set to our smart contract Abi and we'll do a control L there and the next thing we want to do is get our byte code, and this is our byte code is really long.

B

So it seems to work better from this browser here like um so. You definitely want to do some copying and paste thing out of here. So if I get it from.

D

B

Seems to be a little friendlier to work a little bit better.

B

So other than that that already came back so we can see here the 608 and the zero zero two nine we're six zero, eight zero. And so we can see that and.

D

B

What we want to do is we want to let's go back.

D

B

Now we have our simple storage ABI set. We have our byte code set. Now we want to set this simple storage object with the uh with the ABI, the simple storage API. So we want to create that object and uh set up our web3 to call this function with the simple storage API.

D

B

Got to get everything, obviously it's very unforgiving.

B

Okay, good, so that worked and like I said.

D

B

Have a I'm having.

D

B

Little uh problem with uh some slow response.

B

D

B

What we're going to do? Well, let's say what we're going to do first, uh now that we have that now we're going to set up this deployed contract object uh with the simple storage API from up here and we're going to create a new instance of it with the byte code in there.

B

So here's our our byte code, so we're going to deploy the contract and there's my little endorser issue that I've been having and sometimes just have to hang in there and it will run so there it is. It runs. So that is a problem you might not have Network seems to be a little slow now. What we want to do is we want to create this. Smart contract object. We're almost done.

B

We want to create this more contract object, uh calling uh this whole function here, simple storage at and then we're passing in our deployed contract hash. So here's deployed contract. You can see it here and.

D

See it here and.

B

We'll have this: my contract object that we can use to actually get a response and interact with our contract.

B

And again, I've already set all these up ahead of time.

B

So here it is my contract again the simple storage, the deployed contract- and this is important- this will return a contract of address, and this isn't always clear so we're going to have to at least while we're practicing this we're going to have to learn at this point to go up to where it says address here.

D

B

After transaction hash and we're going to have to get our smart contracted to rest, just like we did before now, obviously there are tools that can manage this. For us.

B

And we want to paste that in right here.

B

Save that- and we want to paste that in right here.

B

At least for this exercise or for this Workshop foreign okay, so we have our smart contract address and now we come back out here.

B

We we can actually set an hours more contract address and then we can actually start doing some setting and some getting so, let's set our smart contracted for us update our my contract object, which clear it is paste that in so there's our smart contract address.

B

Okay, that worked and we can see here. Let's do a control L we can actually go in and now we can start calling some sex and some gets let's type in my contract Dot and it's giving me the preview there. The set.

D

B

Let's do I, don't know it's a pretty good number, so.

D

A

B

Have we have some uh beat? We have our uh our our hash that the transaction was successful. Now we want to do the get so in a lot of times you might. We might want to set up.

C

B

Wait and if you look down here at this preview, you can see all of the items here that we're able to so we'll call it get like this right now we'll there are actually other functions available and again we have our little endorser issue. So let's try it one more time: okay, good! So that came back that time. Apologies for this, uh my network! Again, it's a little slow anytime! You see this endorser issue, you know it's uh just something that you have to Soldier on through.

B

So here's our our one, zero one, that's returned in the form of what it's calling a big number, but we don't want the big number. We want something, obviously, a lot more friendly, that we can return the value and then use to build uh a user interface like a web app or a mobile app. So we want to run the get, but we want to call the to number function on it.

B

And that will return it as 0.01, so one so set one zero one and now we're returning one zero. One.

D

B

If we wanna run that one more time do our set and we can do our 777- maybe that's lucky and give it a second.

B

Again, if you see this processing for endorser, it's just something you just have to solder on throw anyway the.

D

B

Was successful, there's our feedback, our hash feedback, which could be important right. We can always admit that to the blockchain uh log as well.

B

And then let's call the get.

B

And we see the 777 came back that time and.

D

B

Again, we don't want to see it as this big number, so we want to see it as.

B

A more friendly just the just the the data, just the counting number data brought back so we'll call the.

D

Two number.

B

Function on our get and we have our little endorser.

B

Sometimes you had a soldier on a little bit more.

D

B

There it is, it finally came back, so if we do our control, l, I'm, not sure, okay, sometimes you got a soldier on a little bit now. There obviously are going to be ways to manage uh issues like this. uh Just so, if we do get one, uh we can uh obviously uh work.

C

With it, handle.

B

The error and then just move on until we get harder, uh the the result that we want. So this is running the uh the evm here in a more friendly environment.

B

Let's do our control, l.

D

D

B

We got it back here anyway, uh so this is a more friendly environment and the next steps would be to uh have within node.js my water install a web browser, so we would use the node.js browser.

B

And we would use the web 3 JS. Why not right?

B

We would use web3js to uh to essentially call our smartphone track using the API to call our smart contract from behind the scenes and then return that back and essentially build a web page with it. So that's that's where we're going to, and that will be in look look for look for a class or a workshop on that in q1 of next year so watch out for that we will be uh obviously taking you to the next step.

B

But again we are very, very close here to running or smart contract where uh out of node.js and web3. In fact, we are and again if we are solidity developers. Now we are hyper Ledger developers, because we.

D

B

Obviously, go into our smart contract and then take it to the next step, especially using web3. We can call more functions and we can build more applications uh to return back to a client interface with using the ebm for hyperledger. So that's that's really. The great thing is the big thing. The big takeaway here is um we I. If we are already, if we're familiar with solidity, we can uh also be hyperledger developers and again, a prerequisite here is what is was to install uh the um hyperledger fabric.

B

uh We do have all of the uh the steps as well and that can be in a a future presentation or a future Workshop if anyone's uh looks to uh install the just the basic uh install on hyperledger fabric.

B

So what I'm going to do right now is I'm just going to switch and we're going to look at some other tools that are available to the community I'm, not going anywhere, but we're going to look at some other community tools that we can take advantage of to build our smart contracts and also our distributed applications on hyper Electric. So just bear with me here: I've got to stop my sharing.

B

And hopefully oh.

B

B

B

Okay, am I, muted, no, okay, oh I, think I know the problem.

A

How about now, okay,.

B

Okay, that should yeah that should solve the problem. Okay,.

B

Okay, so uh hopefully I'm back with with everyone, um so we can take a look here at can. Is there any? Can everyone hear me yes, you're, coming through fine now, everyone here see me try to.

A

B

Me a thumbs up or something: okay, yeah.

A

Can you hear us.

B

Okay, we can uh so right here we have our. uh We have our truffle suite and if we scroll down here, we can see, uh uh we can see very clearly that we have uh hyper Ledger fabric as uh supported by the Truffle Suite and truffle's a good Tool. uh It's uh the it's an open source tool, I believe so anyway, uh there is a vendor for it, though.

B

The vendor is consensus, I believe at least the current vendor, and if we navigate in here to hyperledger fabric work with the hyperledger fabric, evm we can see. Maybe I can make this a little bit bigger.

B

uh Well, we can see here our Local Host, our Port 5000 right, our Fab three right here. So it is this. Is this approach using our Fab? 3 service is still uh the uh the way to go. At least this? No, no vendors! No no solution providers have dropped this yet and we'll we'll discuss the fact that the uh the current approach that we just looked at is currently archived. We will talk about that.

B

um And and some nuts and some next steps, so this is a good. uh This is a really good way to go.

B

And let's just uh go back to our presentation briefly and show you what we're going to discuss um for the next hour.

B

So again, we have uh we'll be we'll, take a look at some tool Suites. So we have here truffle, which is a great uh tool suite for uh developing um hyperledger evm applications.

B

We we've already looked at remix and we've talked about the way we can develop smart contracts using remix in a a very lightweight uh approach, getting our ABI and our byte code.

B

Now, if we use tools like truffle that takes away some of that overhead of the ABI and the bytecode Truffle gives us tools that manage that for us, but it's it's good for us to get a little bit of work with it, because that comes up quite a bit and we also have a book so take a look for our book for programming and solidity. It's available on Amazon, um so you know developing a solidity smart contracts um and uh give it a book review.

B

If you like it- and we can see oh boy look at this tonight- the Eagles are on so I've got to uh gotta, make sure I'm uh we're all wrapped up by that time.

B

uh One of the things truffle will give us is a project, so we do we run uh truffle init and it gives us a project and one of the items that we'll get from this. It will have our contracts directory we'll have a bill directory when we compile, because we can compile, deploy and build and we can connect. Obviously, you saw right the connection here: the port 5000 and the localhost so uh fabric type evm.

B

So we can uh run that build and that deployment to our hyper Ledger environment you've got to obviously have the network up and uh going uh the correct way. Have it configured the correct way, or else you get stuck doing it kind of the hard way like we just did it, and then we get the source folder, which stores, JavaScript and HTML uh to use the web3 smart contract AP uh API, so this truffle uh Dash config. That is where that that this is the Truffle uh Dash config right here.

B

So that has so it gives us all of that and we can deploy right here. So it's pretty straightforward. We get some feedback and then we're able to run out of the console so the Truffle con. This is what we want to do. First, that leads to validate that everything is working uh as uh as uh we had hoped- and this is very very similar to what we just did on um with directly on hyperledger fabric.

B

So we'll take a brief look at this and then the smart contracts eight uh API. So this is something that we have so with web3 this this happens to be a web. Three uh we're actually uh instantiating our provider, so here's our provider just like we just saw you- can see it right here and then we're actually calling our smart contract so uh we're calling our smart contract returning it back to this JavaScript and then using that data to build our web page. We can build a web page similar to this.

B

uh We can see here. This is actually a voting dap uh again, we'll need just uh the dependency for this. One is really just the uh the web server the application server, and uh but we can see that how we could progress and use that on our uh have that already installed in hyperledger fabric, because we've installed node on hyperledger fabric, you saw it. uh We installed web3 on hyperledger fabric, so the very next step is taking advantage of the job the web 3 JavaScript or it could even be react.js.

B

If you're a react.js fan, you can even use that and are setting up the web application server which, as everybody knows, comes with node.js. Let's take a look at another quick uh demo here.

B

And just bear with me here one second, so what we want to do here is we have a smart contract. Let's take a look at the Smart contract here. This is going to be called tally and very s uh in a way. This is uh not not that much different from the smart contract. We looked at actually in hyper Ledger fabric, uh we're going to compile it and again we have the ABI and the byte code.

B

We don't have to worry about it here, because truffle is going to manage all that for us, but let's uh deploy it here now notice we have our contract tally and it's in a file called tally, Sol uh similar uh to other uh object-oriented languages. You can uh develop all of these contracts in one file and so just be careful make sure you are when you're running and deploying make sure you have the right one selected.

B

We don't have that problem right now, because we just have one contract one file, but if we had another contract in there that that would matter and when you use reusable libraries like open Zeppelin that matters so be careful of that. So we just deployed- and again we have our user interface, that we get for free, very basic user interface uh so uh or we initialized our count here to zero.

B

So if we click get count, we're going to get zero back, then we have an increase here and that Inc that send that increases the counter and emits that to the log to the blockchain log and then we we, then we decrease, and then we so we can see here we decrease. So we reduce the count by one and then we have the the get count to return. So we can click here on increase and get the count, and it's one you can hit increase two times, get the count.

B

Now it's three and we can say, decrease and get the count. It's two so pretty straightforward, but that's what we are going to do now. We, uh we I, have already copied my our contract in here. So what we want to do is run.

B

And this is a lot better than some of the now I always pass a reset in here, because uh there are sometimes you could have truffles a little funny, sometimes with contracts of the same name. So I always use reset just to make sure it overwrites and that's one of the items here so good so that that ran and we deployed to our environment.

B

And now again we want to use the Truffle console.

C

B

So this will be a part of what of what we have to do. So we just want to just go in here and just make sure everything's running uh as we expect.

B

So one of the items we can do is we can, and these are all ways to manage the API, the calling of the API so we're going to create a new instance of our deployed contract. You can see tally is our deployed contract notice, the await and all that that could be a solution for some of those errors that we saw before, and we can actually then bring back this new instance because now there's lots of data, because new instance has now been instantiated as a new tally. Contract.

B

And the address you can see the address you can get lots of information brought back here and control. L is the uh the way to clear the console and we can bring back the address of of the contract as well. So we saw that address was in there, but we can actually call address on new instance.

B

And that brings back our smart contract address and then we can start in calling our functions, so we don't have to work. We don't have to work with any of that hash, uh counting or anything like that that hash data here, because we're running directly within node and web3. But we want this. We want to set a con. We want to set a constant result, zero and we want to call get count on this new on the tele contract. We call the tele contract new instance.

B

Maybe there's a better name for it, but again we can call res 0 or result zero, and we can see. Oh okay, there's our zero okay. Now we have that very right, big number. It was big number on hyperledger fabric here, which is called BN for big number. But, as you can imagine right, we just do the two number which we have to do with the API, and then we get our zero back.

B

um So let's call our now we're not obviously getting those those errors like we got before, uh but we can also call our our increase on our new contract.

B

So here is now we'll call this result, one because it is always going to return something, so our constant Result One tally. You know we probably should have named it tally or something like that, but we're calling increase on that on the contract which we set to so we know we're at zero.

B

So and again we should be able to do res one and somewhere in here.

B

But this is the result of the transaction.

B

And then we have to run on res one. We have to return, get cap or run get cap, so we have to do constant.

B

Whereas one equals- and this will wait.

B

And it looks right to me yeah, so a little bit of a typo in there. Oh res one has already been declared. That's right, so we've got to make it res two.

B

Okay, good and again we can bring back data on res 2.

B

and we can see it as a big number and we can see the one in there and what we can do here is call again. The two number function.

B

And luckily we're not crashing into those little errors we had before and we can call let's try uh increase one more time so increase this time, we'll make it res 3.. Hopefully that hasn't been used before and great and then we'll call get count on res3.

B

And here it is get count, but we have to use. We can't use res2. We have to use Res three.

B

Oh, we have to use res four.

B

Okay and again our res four, it should be that now we're up to two and again two number, and we see that now the two is returned and we can even try the decrease.

B

And this time we'll go with uh we'll go with a completely different, constant.

B

We'll call it deck as in decrease on new instance and we'll do our get count.

B

And our res six and we can see we're back down to one and.

B

Two number there, so that's how we this is how we interact uh with the smart contract using truffle. uh We saw also uh remix. uh So these are a lot of the tools that we can use to develop our smart contracts and for uh for hyper uh for hyperledger fabric I'll. Just clear that out we'll exit out of here.

B

B

And we'll get to this in one second, so let's go back to our presentation.

B

So this is what we want to install on hyperledger fabric and there actually is a GitHub repository out here and if we take a look at this, we'll take a look at an example of this, uh so we have our evm chain code, our fab3 proxy right, our fabric Network, and our decentralized application out here, uh which will enable just a contract for uh for in this case for voting, um and uh so, but you can actually download this if you want to experiment with it or read about it. This is uh this.

B

Github repository has been working and it has a little bit about uh this application. Again. All of the the documentation in the community is all out there around the Fab three approach which uh we we will talk about. We can start to talk about uh right now, but before we do that, let's take a quick look at how we would do this uh with uh with hyperledger fabric, oh I'm. Well, let's one thing that we need to do is: let's just make sure we're in this case. In this example, we need metamask.

B

Metamask appears to be up and running. Okay, that's good.

B

And the way that we we run, this application m mpm run Dev and what that'll do is it'll start the light server.

B

And we'll just open up a new tab.

B

And we see oh okay, one one item that we have to do is we have to go back here.

B

And we have to run truffle.

B

B

B

Because I was doing a little experimenting before and now we should be able to.

B

Run again here.

B

Get this updated up. Okay,.

B

Okay, now now we have it and we can in this election here we can vote and metamask is called on by the API here. We'll just confirm that transaction and we'll see here that Ryan Williams has one vote for the coolest kid uh this. This smart contract is also running in solidity. So if we go here to election, we can see here that if we deploy or compile and then deploy just delete that one.

B

We can interact with the contract. So here are here are the candidates that were listed back on the web page. We can vote for our candidate candidate number, one which happens to be Ryan. uh We can return the candidates names here. You can see here and you can cast the vote now. If we try to vote again there is uh there we we require that they haven't voted before. So. If we try to vote again, we returns an error. So that's, uh but we got.

B

We actually set up the the DAP to just not allow a user interface. Here we just see the one vote and that's it so that that is very similar to the IBM solution here that that they give us.

B

And want so one item, uh so all of this are tools that that will be that are available will be available, obviously are available for hyper Ledger Fabric and uh look in q1 for uh more information on that some some training on that as well.

B

Some workshops we do see now the evm chain code that we have been working with is currently archived so um and there's some concern about that. uh At least I was a little bit surprised by that uh you can take a look at it. uh I did contact the community, the hyperledger community, and currently there is no replacement. uh The evm is not packaged natively with at least this version of hyperledger fabric. However, though uh it still can be used, we just used it and it is still obviously the the choice of the community right.

B

We see here from Simba chain the steps that we just went through right using the Fab three uh does it. It does doesn't say Fab three in here, but if we look through this documentation, you will see the Fab three, uh the rest of the uh very similar to what we did. The Fab three installation- and we already talked about truffle, suite and other products as well, uh using the Fab three uh Service uh for the evm for uh for hyper Ledger. So we will be uh like it says here, the blockchain academy.

B

We will be working with the community to figure out uh what the steps are, uh but for right now this is this uh product. The um the Fab three approach is, you can still complete all the same steps I think you saw I was able to still clone the uh the Fab three uh repository and obviously we were able to instantiate run it. uh So it's all still there uh to use we'll have to as a community going into next year, figure out the status of the um of this repository I'm. Sure.

B

If there is a replacement it'll, be something very, very similar right. Why would we start from scratch? Okay, uh all right, I, don't know where this came from. Who put this slide in here? I, don't know who did that?

B

Okay, uh we'll.

A

Investigate anyway,.

B

So uh So, currently for next steps, uh like we said there is, there, is uh look for uh future workshops. uh This is a QR code that you can use to register to get uh the materials that we use today uh have that even access to the virtual machine that I used snapshotted and everything.

B

So if we register we can get the document that uh that we use so scan the QR code, uh we will have a Hands-On Workshop coming up in December and uh January and we will be like I said it will be Hands-On with virtual desktops snapshot and everything. So, even if you run into trouble manage to get yourself wrapped around the axle which we all do, we will have Snapchat there is our. There are snapshots for you to move forward uh so again uh scan the QR code.

B

Here is the link that's associated with the QR code and also uh just want to thank everybody for their time. We will be uh opening up to questions uh shortly and we want to thank the Linux Foundation again thank David Boswell, uh my colleague Ryan Williams, uh for all that was done here for setting up this Community page and also thank uh Jim Mason for uh for being our session host. So maybe I'll temporarily. Kick it back to Jim, Mason and.

A

B

Can take some questions or have a discussion or talk about some next steps or anything anybody knows about.

C

The status of the.

B

Evm on hyperledger fabric.

A

Hi Jim, can you hear me? Okay am I coming through.

A

C

I hear you Jim, okay,.

A

Great, uh so I don't know that Jim can but um yeah. So the good news is. We have some questions. Jim. If you can answer those in our chat. uh If you look in the chat, we've got four of them right.

B

Now, uh let's see, could we okay some questions here that are in the chat, I'll, just look, what's in the chat and again Jim, Mason or David, Boswell or Ryan feel free to take yourself off of mute and speak up.

C

B

Runs on every node on the hyperledger network. uh The well uh I can tell you this the one when we instantiated we did uh that we instantiated to all of the peers correct. So we did do that so that service uh runs on all of the peers on the network and could we run the the fabric evm on a production environment. uh Sure I mean I think what you're going to have to right, you're going to have to have it running on that runtime.

B

So whatever that run time is so if you have a cloud and I'm not trying to sell you on cloud in any way, but if you have a cloud, obviously you can spin up multiple instances template multiple instances. Oh I may not be hearing you. Oh okay, apologies! Let me let me change up here. I may not be hearing you, um so let me uh switch over to a different computer.

B

Bear with me I'm having all these environmental issues here.

B

Okay, I think: can someone speak up.

A

Yeah hi Jen. Can you hear me now.

B

Oh I think I know the problem. Can someone speak up now? Hi.

A

Jim, can you hear.

B

Me yeah I can hear you now: apologies, okay,.

A

Great thanks all right, so if you want to go back to your questions, that would be great. Okay,.

B

uh Bear with me here one second: uh let me just get back here into Zoom.

A

Oh and there's a question here: I think you answered the one on the fabricate VM in production, I think the there's one that came in on the bottom, which is really sort of I, think out of scope, but it says: are there Cloud Solutions you could suggest which is more of an open-ended thing. I think.

B

uh Right now, uh aaws well I'm, not aware that the what you would do is you'd spin up a hyperledger instance on AWS. Interestingly enough Amazon web services seems to be the leader as far temporarily as far as hyperledger fabric I'm sure IBM wants to get there on the IBM Cloud.

B

You can open up a free account uh on on the IBM cloud like because it's IBM it's much more difficult than it is with uh with AWS or Azure or anything else uh for whatever reason, but you can eventually get a free account on there uh and you can run a hyper Ledger instance on the IBM Cloud, as you can on AWS.

B

You'd have to go through the same steps, though, to install the evm on there unless AWS has within the last couple of days, provided that and I think uh maybe AWS would would be a little distant right now because of the archive for the Fab three being I. Guess you could say officially up in the air.

A

Yeah yeah I will say it on the cloud. Side Gym um I've run uh fabric production applications on a couple of different clouds, including IBM Cloud, AWS and Azure um I've had uh in the past, been running in production. On all three of those environments and I know, a friend of mine ran Google Cloud, fine, one of the bigger things when you.

D

A

Cloud, though, is obviously the clouds are I'll call it proprietary and different from each other. um You're right about the IBM account setup taking much longer than it should. The reverse of it was when we ran in production on the fabric side, because IBM in a sense, uh I'll call it IBM. Blockchain is a fabric implementation on the IBM Cloud. It was actually easier on the setup for what it's worth than AWS is but um you're right that the majority of my knowledge anyway, the applications are running over on AWS one.

A

Other major consideration, though, is if you're either like where we are now, on my end, we're trying to deal with cross-network issues. So it's not about you know all of us being in one fabric Network.

A

It's now about the fact that we're in a fabric, Network and I've got two or three other networks that we have to in a sense work with uh real time and to do that, one of the things um we're uh I I haven't done it, but a friend of mine did earlier actually wrote the book for fabric on how to install it in kubernetes and so there's a fabric tutorial out there in the fabric, samples that actually looks at setting up fabric under kubernetes, which at least gives you also a better portability across clouds and we're.

A

Looking at the idea on the interoperability side of these networks, now trying to figure that out and one of all the things you can do invoking apis and all kinds of things sharing private files via ipfs. Whatever else you want to do, the one thing that's coming out clear on this Cloud integration side is the problem of integrated workflows. So we have it's not just that. I have multiple separate networks. It's the fact that in my organization, when I do something in my organization, Jim's organization has to react to that.

A

So not only do we have to connect across these clouds and be able to interoperate, but the bigger thing is honestly being able to enable what I call event workflow processing across networks, which is really something. That's not what I call well addressed, but at least kubernetes provides a platform along with some other. What I call utilities you'll need to start to address something like that, but that whole thing about Cloud deployment and interoperability is a big big deal. So I agree.

B

uh Yeah, so somebody asked me that or I was in a I got dragged into a discussion on that with a potential client and they were uh interested in running uh hyperledger fabric on kubernetes, but I was just like well. If you can run it on Docker, you can run it on kubernetes right, because doctor is one of the container Solutions I didn't really, but whatever uh they didn't seem to. um They wanted some yeah. They didn't seem to think that it was going to be that uh that straightforward, but it's.

A

uh Well, so the good news is IBM at least documented. It um two different ways. So first, um a friend of mine Chris, actually wrote the original book on how to do that. He actually put um fabric on a completely different Cloud I, think it was Blue Ocean or whatever it was, or fast, Comet some other cloud provider and then uh from there built it on kubernetes sort of from the ground up.

A

But then there's a fabric tutorial under the samples, the fabric samples, um a late this one on the asset transfer that actually specifically talks to the sacrament kubernetes.

D

A

Which is easier for you to test I would argue.

B

Okay, great yeah, so I I would look for as soon as we get this settled, which you know as a community. We certainly should, uh as far as running the evm uh one of those Cloud providers, probably AWS, knowing how slow I used to work for IBM so um I have some experience there right. Ibm tools are always more expensive than other. It's competitors more difficult than its competitors, uh but I guess the support right is always there 24 hours 365..

B

But anyway, uh you would expect that at least IBM the IBM Cloud to have something competitive with AWS, which we'll probably say I I, can't uh I, I, think they'll. Finally, wake up and you know, devote some resources there.

A

Yeah I'd say you're right on the IBM side. There's two differences, I say: AWS. You're right has the largest share of the market right now for sure, especially in the fabric space, and then the reverse of it. As I said, if you look at IBM, Cloud, there's only two things that sort of make a case there. One is, if I already have other IBM assets, I integrate to then maybe IBM Cloud office advantages there. They have all these Cloud packs that are pre-built Integrations and the third.

A

The only other point and I can't speak to the validity of this yet is IBM is trying to with openshift uh leverage kubernetes to become what I call a more Cloud, independent, so yeah.

A

um So that's that's something that I'll call it I haven't experienced, but that's the strategy that they're trying to implement for what it's worth yeah. That makes sense so anyway, that's that's! All I can contribute on that. Okay,.

B

Great any other questions out there from the community I see a lot popping up. How should we answer some of these.

A

I guess the amount of customization ec2 instances uh over others microservices can be handled separately, um but um let's see yeah I'm, not sure yeah. We don't somebody made a comment about the customization in ec2 instances.

A

um You know I, don't know what they're comparing that to is my problem. I can't comment meaningfully on that uh thing and then there's another one down here. A link on the Linux CVM may I know which evm client is built into fabric evm. Can we run Basu evm as fabric evm? Well.

B

A

B

Using basically, though, no I was not using bass, so bass was a little bit different right than what I was using I.

A

Was using it and that's actually a huge difference to be aware of because Basu is fine in itself, but what's I'll call it more interesting. I'll say is what Jim did today to me, because it says I'm just saying: I've got a fabric: Network I can in a sense, take solidity contracts and put them on my favorite network and run them directly, which actually seem to be really well done.

B

Mm-Hmm yeah, so that so that was a very what we did was a variation of burrow hyperledger Borough, which, as everyone sees is now, is currently archived. Who knows right if, if that will be the, uh if how long that will be for or if it'll become active again or just become a different product right, we all know sometimes I'm part of a bigger product. uh So but it's not the same thing as base, so Basu is what they call well.

B

Basu is almost like a standalone right that uh it's considered an ethereum client, not a uh doesn't.

A

Run yeah, and so the thing with Basu is I. Guess if you look at ethereum, mainnet is a public internet period, a public network, I should say, and so yes, you can run over there, but the thing with Basu. You could also set up ethereum on a private Network right and that's where basically, with its permissioning, also can operate in that model, so I'm working with a company now that is actually been running, Basu on a private ethereum network, with the idea that it's not the main net for what it's worth.

B

Okay, good anything so yeah, they're they're, it's not swappable, it's not considered to be uh one. One is not the other. So Basu is uh right, correct it's it's its own Standalone product right. What we did today was actually run the ethereum virtual machine on hyperledger fabric instead of the go right that supports the solidity smart contracts, uh as opposed to running in your your golang uh chain. Well, I should say yeah chain code.

A

Yeah excellent, actually, the other thing you pointed which was really good about what you just did today for me is it doesn't get enough press when I go to another platform. I can pick any platform I want, but for the most part, I'm pretty much stuck on the contract language. What's really nice about fabric, is you showed us in a sense um that I can run in other languages, so I can not only do I using what you did today with solidity.

A

There's a contract language but I can also create contracts in node.js Java or go as well. Well,.

B

Right, yeah, exactly and a lot of networks are adopting the evm right we see near also runs the evm tazos Corda even has support for the evm, even though that's a I guess a competitor to hyperledger fabric in a lot of ways.

A

Yeah, it is because I run for it as well and you're right, but the evm stuff over there isn't where I guess that's in beta or whatever, because most of what we're running is really uh kotlin contracts over there. You.

B

Know for what it's worth, because that's the native right, that's the negative one right! It's it's fine! If everybody has their native way to go, that's great, but in order to really open it up to the community, uh evm is I. Guess you could say the low-hanging fruit uh for building up the community, and it's already got support out there. uh Like it or not. You know.

B

um um uh Consensus is a big, influential member of the community and uh they're able to uh Drive market share, and uh you know we all know it's a uh it's. It's a very compelling product. It's a great product. It's got the support there, the community there a lot of resources there already.

A

Yeah and your point on the fact that uh a lot of what I call the public networks run, evm compatible for sure it's a separate, it's not the main net, it's a separate network, of course, but the advantage there is. You, then, have lots of choices so, like you said near and you've got polygon and a bunch of others that are right.

D

A

A sense ebm networks, if you will, even though it's not mainnet, it's not ethereum,.

B

There's more contract language is, is solidity, so there's a lot that are grabbing it just because it's just to grab the community yeah excellent.

A

All right so I don't see a lot of new things uh coming in chat, but I certainly appreciate this session Jim. It has been fantastic and I would say um you know, for those of us that need to go to the next step. I would certainly look at your AWS book I'm going to guess the AWS book you have is only available as a Kindle format. It doesn't support PDF or.

B

No, you can, you can get. uh Let me just move back here a little bit. uh You can get it in Kindle form.

A

Or physical I can't get it in ePub or PDF forms. My problem, oh.

B

uh Pdf I believe you can is Ryan on uh Ryan. We can support PDFs I believe um it looks like you can get right here. It's just the! uh So, if you can, if you buy it in Kindle, right, isn't PDF an option. um I don't know.

A

It's just me and Jeff Bezos having an argument until the end of time over the fact that they don't support, PDF or ePub only Kindle format, which.

D

A

It actually it's hurting authors, because I wind up there's another company that actually produces um registered PDFs, which is something that uh Amazon could easily do, but they choose not to they're trying to force you into Kindle and so, um but the registered PDF said you know, we buy I'll, call hundreds of books over and that other publisher manning.com, because they offer that format. And it's a challenge because for those of us that have what I call better technology for PDFs than Kindle, you don't have that option with Amazon. Unfortunately,.

B

We had a really hard time with the formatting. In fact, if we still get some feedback that the formatting is still not great, uh we even hired somebody from upwork to go on there and help with the formatting, and he it took him two weeks to do it.

A

The bigger thing for me is the technology is so different with PDF I couldn't begin to tell you the 29 things that I can't do with the Kindle, and so it's her. It hurts the it hurts the authors and it hurts the community badly, that we don't have more formats and just can't go over there. But.

B

A

There's nothing you can do about that, but anyway the book I'm sure is worth getting period, regardless of what the format is.

B

A

To move forward on.

B

And uh get a book review now we had a question here: uh are the? Can we expect the recording in the slides, Jim, Mason I believe right? You should have.

A

All that I will be sending out tonight's Thursday it'll, be probably by tomorrow morning. You should look to see the link it's going to have the uh recording the entire session recording will be over on YouTube and we will have whatever the slide deck as I received. That'll also be a link from the YouTube uh location as well. Yeah.

C

If you send me that text I can send it out to everyone who registered yep.

A

Absolutely thank you David. That's awesome.

B

And we have a, we have a question here: are smart contracts tied to one specific blockchain I'm gonna say that well a lot of a lot of the networks. A lot of the blockchain or DLT networks are have their native uh uh or their native programming environments.

B

However, a lot are also adopting uh the ethereum virtual machine as I uh I don't want to I, don't want to use the word bridge, but as a way of uh opening up to more community members and just like we said the reuse, the resources there's so much out there that are available. That you know it's hard to say. A community is going to devote itself to the native language of say a near uh or um an algorand.

A

Where yeah those right, those, unfortunately, are not going to be well received and they haven't been even on their own networks honestly. So as a result, you're right. The fact that you have ebm support in many of these um public chains is really a big big deal. uh It's it's actually. Why that whole Community has grown so well, because you can easily build and develop Solutions, so you get a few customized ones on those other chains, but for the most part you're right. It's always solidity. That's the default on those other public chains.

B

Yeah- and we have a question here- about gas fees. uh Well, if you're running on hyper Ledger fabric, you might get some data just because it's part of the ethereum virtual machine on gas fees, but it can be just nothing right because uh we don't have on a private blockchain. Typically, there aren't uh the transaction costs are absorbed by the Enterprise or by the Consortium. So uh right might see the gas fee on there and you might be able to use it. Maybe for your Consortium members, it might be able to make use of it.

B

A

Good point: I've never tried it, but you're right when you set this up and run it the gas fees. Unless you do something with it or basically ignore there are no gases, and then the reverse of it is I'd, say you run into gas fees on ethereum, but one of the things and there's other choices out there, but there's a bunch of public networks that are faster in ethereum and have much lower gas fee. So I recently had experience on polygon and the gas fees were really low.

A

So running I just saw a thing the other day somebody else was running a D5 security trade and the cost on polygon was like two cents, a trade kind of a thing. It was very, very cheap.

B

Oh yeah, that's the big thing that they're offering right over ethereum I mean ethereum was the first right, so you can obviously make improvements on that. That's what that's! What we're saying! Yep.

A

Cool anything else anyone has before we close, if not Jim. This has been excellent, uh really a tremendous job on your end and the team's end, and you know, obviously, we want to get everything out to the community on the recording and the handouts as well, and certainly I think the book would be a great next step for a lot of people to take a look.

B

At yeah, a lot were, like I said you can register here, get the documents we will be putting on a workshop in December and another one in January. If you want to get some Hands-On, you can imagine that whatever the um whatever the I guess, you could say replacement. Is that the word we're going to use. It will be very very similar to what we did, because it's working right and it's already been adopted by solution providers.

B

So we as a community Jim, Mason David, obviously are going to be active in uh getting all that information out to uh to the members of the community on what our next the steps are or what product we use for uh evm on hyperledger fabric.

A

Right: okay! Well, thank you again, everybody for attending and can't thank Gemini for uh the great session you did today was tremendous. Oh.

B

Good I'm glad I'm glad everyone enjoyed it. The World Series.

A

D

Don't know where.

A

B

Came from that's.

A

Right somehow, don't forget, don't worry about it. Jim I'm sure we're tracking that, on the.

C

Blockchain so we'll figure out what happened right.

B

In Philadelphia, so um so we have the Eagles tonight playing in Houston, uh ironically enough and the Houston Astros are up.

C

Here, oh that's funny: yeah cool.

A

C

Thanks Jim Mason for hosting and thanks Jim Sullivan for running that and yeah uh thanks everyone for joining. Thank.

D

A

B

Thank you. Thanks for all you do.

C

David Boswell talk.

B

To everyone soon, thank you thanks all yeah. Thank you.