Hyperledger Foundation Hyperledger Global Forum 2021, 14 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hyperledger Cactus Project Updates - Shingo Fujimoto & Peter Somogyvari

Description

Hyperledger Cactus Project Updates - Shingo Fujimoto, Fujitsu Laboratories Ltd. & Peter Somogyvari, Accenture

Hyperledger CACTUS has started as a solution to interoperability that bridges the differences between various blockchain infrastructures, but in the future, we are trying to combine multiple ledgers to enable the construction of new distributed management services. In this session, we will look back on the history of the establishment of Hyperledger CACTUS PJ, share the current development status, and have an open discussion on future enhancements. We are planning to show a short demo at the end.

To learn more about Hyperledger, the open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments. Which serves as a neutral home for various distributed ledger frameworks including Hyperledger Fabric, Sawtooth, Indy, as well as tools like Hyperledger Caliper and libraries like Hyperledger Ursa click here: https://www.hyperledger.org/

Session Details & Slides (if available)- https://sched.co/j3ev
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/

----
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 #HyperledgerGlobalForum2021 #Blockchain

A

Hello, everyone, uh the welcome to the other session titled hyperasia cactus project update uh this uh session will be uh uh presented by the uh the co-author, uh the shingo fujimoto from the fujitsu and the peter samurai from the accenture.

A

So the uh that we are expecting to the 30 minutes, presentations and we'd like to reserve to the 10 minutes approximately for the question and answers uh there. So the please be prepared for your question and uh and comments so the uh the let's get started for the other. The sessions.

A

So as a introduction, so the uh the unfortunately the other the beta is not either on the stage yet. But uh the the other peter and I is- are the the core maintenance of the cactus project.

A

So the uh that we had over the the uh the two years, uh the we are collaborating to the developing to the uh the the captain's uh cactus uh from the beginnings.

A

So the uh that I myself is a I'm, a manager of the uh the physician laboratory of uh the data and security research laboratory in fujitsu and uh I'm the uh the working on the uh the blockchain technology in the uh the several years.

A

So the uh the peter will be also the other that he is a technical architect in uh center and uh here's the uh the arctic manager of the accenture and uh the is also maintained to the top of the uh the uh the hybridiza projects.

A

So the uh the the uh the the very first uh half will be. uh I will present to the uh the background of the project and the status and I later on. I will give the mic to the peter to uh to pre, uh to introduce to the uh the several uh the working examples and the future plans. That is uh the consistent structure of the today's sessions.

A

So the uh the the first of all I'd like to explain to you the uh some background of the other cactus, so the uh the well, the just imagine to the world the uh the shopping scenes in the towns and users want to buy the some of the shopping items from the shopping truck box.

A

uh That is a very easier uh to trust because they are in person, so the uh the with uh the both party uh can trust each other for the uh the payment and giving the items yeah so the at the same time in so the other. That was a other happening for the in real world.

A

However, the that is not easy, as in the other part of the world, so the uh for example, for the payment we needed, some sort of the virtual currency or a stable coin will be the use on the blockchain and that blockchain has a account for the iris or bob, and the also the shopping item need to be uh some sort of the management systems which uh keep the record of the ownership of the uh the tesla assets.

A

So the uh defender, uh the the trade between to the user recent shop block, will be made that mean to the uh the the coin, will be a transfer from the rs bulb one on the one ledger and another razor both will be transferring to the other ownership of the item to the rs.

A

So the the problem uh under these three use cases will be there is a no mechanism exists further at the synchronization between the blockchains, so the uh here's, the thing of the cactus comes, so the cocktails will be providing to the security mechanism to integrate to the blockchain security.

A

uh So I believe that peter has come the stage. uh How peter can you hear me.

B

Yes, I'm ready to take over my slide.

A

Okay, thank you, so the well, uh the the I just started to the fastest right. So the can you give yourself introduction as a shout.

B

Yes and apologies for being late, I'm peter modivari, I'm one of the maintainers of hyperledger cactus. I my day job is to work at uh as a technology, architect, accenture and part of that is me being the maintainer one of the maintainers of cactus and nice to meet you all.

A

So, thank you, babe, sir judy. I will give the uh the the mic for you for the uh the introduction introducing to the other use cases and future plans later, so the uh the the second slide showing to the uh the the role of the cactus in the high parisian greenhouse.

A

So the in the hyperasia project. We have several uh the the broken blockchain platforms in the at the same umbrella, this barrow fabric in the evolver and sawtooth.

A

So the uh I believe that those are the other, the the competing each other because of the uh there's, a no one fits all solution for the uh the digital asset management and at some sort of the uh the trail kind of the mechanism.

A

uh So the uh the sodium we want to uh we want to the cactus will be a collaborate with such a blockchain uh project, potentially, and also we need to be collaborate potentially whether uh the library prospective like aries and other uh the because of the those are providing to the useful, uh the right script, libraries and features uh the use of the blockchains.

A

So the uh the cactus is categorized in the warm the tools in the hybridge and we had a bone in the 2020 in the spring.

A

That was the 16th official project in the greenhouse, so the uh the the other recent update, uh the after the uh the almost one years from the our establishment of the cactus we announced to the blog post other. uh There is some sort of the interim achievement. uh The feature was version. 0.4 was released.

A

That was the first release of the source code for the public, uh so the uh that was improved from the uh the architecture uh from the beginnings, and now that we are uh some sort of the modularity was improved and uh we had a very uh the stable architecture now and the uh the the important part of the architecture will be a two. uh The first one will be a razer province uh that is consistent with verifier and validator, and the connector for the features.

A

The interworking, the blockchain dependent, so the the validator will be a node on the deployed on the other interworking bridges, and that will be uh uh the just providing some sort of the abstraction uh operation on the razer and monitoring and also the.

A

uh On the other hand, uh the the cactus will be integrated into the some, uh the the the cactus application, which will be consistent with the infrastructure part, uh which is named to the cactus node server, and we also have the very application specific logic name to the uh the business logic plugin, which might be uh other vendors specific.

A

So the other collaboration of the those two components, uh the cactus will be provided the various sort of the uh the application we can be provided.

A

So the basic concept of the cactus will be here are the the business logic. Programming will be interact with their at the validator server, uh the industry type of the communications.

A

The first communication type of the communication will be submitting to the transaction data, which was uh the supposed readers already signed, and that is a kind of bridging for the other. The difference of the uh the abstract, the difference of the product communication protocol and the business logic will be ascend to the those uh the abstracted uh the data uh through the uh the communication channels and because of that, uh submittance of the transaction data will be asynchronous manner. uh The the blockchain uh business logic will be also need to the monitoring for the other.

A

Those transaction is uh the the successfully accepted or not, and those are determined by the monitoring for the uh the blockchain data which was generated, and those notification will be also come through. The communication channel in the bi-directional manner and business project programming also the in occasionally need to the making security type of the uh the the uh the operations like uh getting to the balance or the current ownership of the asset.

A

So those kind of the mechanism will be uh some uh also provided other other asynchron asynchronous way. However, in the communication perspective that was integrated as asynchronous and that will be uh absorbed, differences.

A

So the other to foreign information, about the how that we can develop to the regia province for the specific regions. So the uh the in the center we will hang cactus node is uh could be running and we determine to the of which uh the blockchain razer technology will be uh the interworking.

A

And that time we will start to the uh building to the docker container, which name to the test net or one all-in-one container, will be provided as a tool and second step. We will implement it to the biodata server, which uh contained the uh the result-specific part of the operations like we needed the sending to the other transaction, so the other that we bear other.

A

The uh the validated server will uh the forward the those operations to the actual region protocol in other bridge and also the we also provided the testing mechanism, a testing framework uh that can be test further, those validator other parts and and finally, either. We will providing to the some of the uh the example application which can use to the validator other application.

A

So the uh those connectivity will be uh absorbed in the two way of the uh two choice, other one for the socket io and the one for the other. Another one will be open api and the either the the communication uh mechanism was chosen. uh The cactus make uh the business logic programming other example. Application can be absorbed, uh the minimize, the uh the uh the diff, the difference of the operations and the other protocols, so the other, as I mentioned in the uh the two pages before uh the cactus, was now the published other.

A

uh The public comment for the stage for their evaluation purposes, so those are contained to the, for example, applications, writer card trade, electric trade and supply chain management and renewal, energy trade. All those are very uh the well uh the interesting topics, so the uh those applications are using their actually for the uh the following, the other reject province.

A

Those are the the the uh that we are enhancing to the support uh before the version. One will be released uh that those plan will be uh presented by the uh the peter rader.

A

So the further uh the I will explain to you the how the uh the cactus application work with the cactus in by step-by-step manner, using the first example unnamed card reader application. That is uh uh the the that is not the uh grading from the scratch. uh The you may know that you probably may know the uh the fabric. uh The hybrid fabric, has a uh the frame of application name to the fab curl, which manage uh the transport to the other, the ownership of the curve one to the others.

A

Either we used that application as a part of the other complex application, and also we used the uh the ethereum uh the private chain for the. Are they a simulator for the other stable coins? So the uh the the in that configurations, uh the that fabrica fabric will be interconnected to the cactus and the ethereum.

A

The network will be also connected to the cactus independently, so defend the artist as a user issuing to the uh the the trade that is assumed to the uh the one number, uh the the rental car for the uh the paid money, uh the so the uh that is agreement of the sub subs contract between the iris and bulk and bobo beer are the responsible to execute the services, but the other cactus will be intermediate for the security purposes.

A

So the friend cocktails received the request. The cactus will be uh help to issuing to the artist to the uh the sending money to beer are the cactus as a escrowed, so the uh the friend, the cactus, the determined detected that the money was safely deposited. uh The the cactus will be uh issuing to the second logic. To the uh the bob to the uh the hanako will be uh sorry, the other artists we were are they used to the uh the curve and, finally, the other, the this transferring uh the trans.

A

uh The the this service providing is uh the successfully uh the uh ended. uh The the the cactus will be executed to the uh the uh the deposit money to the transfer to the bulb as a successful case.

A

So the there is another uh the example like a electricity trade record uh that we also used view to the saltos application, uh the fitch name to the other, into integer values. So the uh that we assumed uh we assumed the integer value system will be a keeping record of the smart meter record.

A

Reading meta records will be kept recorded as a for the case of the uh let's say, the two kilometer watts will be generated from the solar powers uh that will be a charge further, uh the the the smart contract and will be ascended the money to the uh the gen other well, prosumer can be received to the uh the uh the the folder and 80 cent as a reward for the power generations.

A

So the uh the interesting point would be there isn't. No, uh the the uh uh the implicit invocation of the application was not happening in these use cases. Other example will be automatically executed by the smart contract ads.

A

The uh the smart contract, like application, will be uh executed, so the next slide will be uh presented by the peter. Can you continue the explanation either.

B

Yes, I'm going to share my screen just one.

B

B

Can you see my slides.

A

B

Great, thank you so single said. We also have a supply chain example, which features the most basic form of interoperability, that we know where you can uh present a consistent data view of different lectures in the application layer by having a backend that has the ability to talk to all the different lecturers where you're, storing data and our supply chain example demonstrates this ability. By being an end-to-end example uh containerized, where you get a front-end application that can track uh this made-up use case.

B

Where a bamboo horse occurs, then bookshelves are made out of that material. And then those bookshelves are then uh shipped and uh the interesting thing there is that all these three steps of the internet supply chain are tracked on a different ledger: the first one, basically the second one quorum and the.

B

Lastly, it's uh the shipments are on fabric and uh I'm not going to demo this right now, we're short on time, but if you're interested in an actual demo, uh there was a breakout session a couple days ago, so feel free to look that up as well.

B

And regarding our expected 1.0 features, we would like to add more support for traditional distributed, ledger technologies, and uh we really hope to showcase how the plugin architecture can enable this and how it can foster an open source community around the cactus project, where people come in and contribute their plug-ins either as connectors or other types of extensions, which leads me to my next point, which is that we also have a library of extension plugins such as atomic swaps via hdlc's, which are still in their infancy.

B

But we are getting there and uh and of course, we would like to have more examples: more uh stability in the code.

B

We need to nail down the api design for 1.0 and uh pass all the security checks, of course, which is uh very much in progress as we speak, and another thing I should mention is uh corda enterprise support. Of course, we do have corda as a supported lecture as of right now, but that's only been tested with the open source version. So that's why it's important to highlight quarter. Enterprise separately.

B

And uh the other important thing is that we take interrupt seriously, we're also talking to other projects, uh labs or or even just proposals within hyperledger about uh joining forces in some shape or form you know whatever uh it may be. However, we can work together and reuse each other's code.

B

It should be done in our opinion or uh creating a community, that's uh going in the same direction and uh it does not or not not, does not, but does as little duplicate work as possible, because uh at the end of the day, if you're all working on similar things, then the quality could be the overall quality could be improved if we are sharing some parts of the code. At least, we also have uh collaborations with hyperledger special interest groups such as the client action and accounting sig in the trade finance sig.

B

The climate action and accounting sig has a carbon accounting tool that we are exploring with them, how we could add a cactus connector plugging in there to help them out with certain uh views that they're having right now with the lecture communication and uh the completely breaking news there is that we are also talking about coming out with a use case that combines trade, finance and climate action, but that is uh that is so new that it is literally just an email thread uh for now that started up uh this week.

B

So I cannot say much more about that. Just yet.

B

The release plan is, we would like to start with a release candidate in autumn. The month is uh we don't know which month it's going to be yet, but uh definitely this fall.

B

And then, after that, once we are satisfied through the release candidate, that we are ready for the actual release 1.0, then we will make that happen and in the meantime, as in bitmain right now and the full, we also plan on issuing uh bi-weekly minor releases uh with any new features. Any interface changes as we go along.

B

So if you'd like to keep up with the development of cactus, then definitely check out the releases as they come every two weeks.

B

And I will conclude there just one more thing I wanted to mention is that there's a link to our wiki page, where there's a link to our calendar, where you can find daily pair pro that we run every day in the morning hours of pacific time.

B

So if you wanted to try out cactus and something's, not working or maybe you just had a quick question- feel free to join in there and ask us, because that session is just there specifically for community members to be able to hop in and ask something and get an answer right away.

B

And with that said, I will open it up to you. Q. A thank you very much.

A

Thank you peter, so the uh I believe to the uh the the people in the floor cannot speak up. So the can you type in the question uh on the qa at windows. If you have any questions comments.

B

Yes, we we do have a few questions as of right now,.

A

B

Yes, you just uh have to click on the q, a tab instead of the chat, tab.

A

Yeah, I could not see there any update study. Can you read up to the some questions? Yes,.

B

I'll do it. uh We only have a few minutes, so mohan asked who or which party would run the cactus infrastructure and how will transaction costs be charged to the parties involved? Technically, it sounds good.

B

Can you okay you'd like to, but let's go ahead and answer it.

A

Yeah go ahead. You first, okay,.

B

So the idea is that companies who would join together to form a consortium could all run a node, but if you want to, you can run your own node just by yourself. There's flexibility in that. So the answer, the short answer is, it depends, and then uh transaction charges would still be paid by the person or the application interacting with the cactus apis themselves.

B

Cactus does not uh introduce a sort of a tollbooth. We want to stay away from that. In that sense, the usage of cactus is free. There's no additional sort of transaction payment infrastructure introduced uh on top of what the ledgers do themselves whatsoever.

B

Second question: thanks for the presentation uh this is from craig: how would you classify the production releases or readiness of the hyperledger cactus project eg for integrating hyperledger fabric and cornmeal, and you expect 1.0?

B

Oh, I think uh tennis.

A

Yeah, we do not have any uh the judgment further, any uh the prospective, however, to the uh that, we think that we will recep to the uh the certain risk of the expected future uh as a part of the ladies brand. So the friend of the release brown is safely uh produced and there is a no bag, and that is a kind of the prospective of the. We are ready to go for the release, candidates and the that is all the common in the hyperledger project.

A

That is my understanding.

B

And the last question is from guzman, which guarantees cactus provides to assure receiver blockchain. The information passed, the consensus protocol from the origin, blockchain.

A

Yeah, I believe that is uh well the in the uh that we can you back to the stride of the architecture, uh the we are uh they're providing to the validator other other trust point. So the validator will be your previous right. I guess sucky the validator will be the determined to the other finalities.

A

Even the original result itself does not provide such a things, so the uh the validator and the cactus node will be also having a thrust relationship between so the that was named to the consortium mechanism right. So the uh the the that is a mechanism that you are asking. I guess so. The other.

B

A

The basically the cactus, who does not provide the general uh well the wide range of the trust, but we will providing to the uh the user to user uh contract, will be providing to the level of the uh the assurance or service grades. So that is our assumption in the use of the cactus, so the other even the same pair of the measure. uh There is a multiple uh the cactus node can be deployed for the third purposes, to differentiate it to the surface level or qualities.

B

Yes and unfortunately, this is all we have time for we have to finish on time. So thank you all for joining and have a great conference.

A

Thank you very much for the participating and we are expecting to the many people to join us for the exciting project to be achieved. The great goal. Thank you very much and have a good day. Bye.

B

Thank you, bye.