Sign Massachusetts Banking IOU Simple

Industry sign banking massachusetts iou simple

so today we're going to take you through our managed quarter service on collido this is a very apt title build a quarter business network in minutes not months so so end to end we're going to start from scratch and should take roughly 15 to 17 minutes to stand up all the components and actually instantiate and drive our core depth so pretty appropriate title have a few slides to go through and then we'll dive right into it so at a very high level there's kind of three tenets that encapsulate collido built for modern business networks so we're completely industry use case agnostic we're providing the componentry the runtime the course services and these are extensible to financial services supply chain healthcare pharmaceuticals retail entertainment you name it you can build and solve any use case or solution on the platform number two radically simple you'll notice this throughout the user interface but behind the scenes there's also a very simple clean rest api for every action that we're performing at an administrative level uh or at a programmatic or at a service level and then the third really important uh built for the enterprise so you get these high levels of you know high availability disaster recovery auto scaling best of breed public key infrastructure and key management you get these out of the box on collido and even on our free starter tiers you're going to get these high levels of availability in dr as well so our approach really is is to flatten the curve try to make it as streamlined and as quick as possible to transition from wrapping your head around this technology at an early poc stage transitioning to a pilot to prove out you know the viability of your solution in your use case and then ultimately to get into production you don't have to bother yourselves with maintaining the network with operating and standing up all of the core components um the really hard technical things uh collider does all that on your behalf so you can focus your attention on the things that really matter which are the business logic and then a nice interface for your end users and your customers one thing that's become abundantly clear to us over the last 18 to 24 to 36 months as we've worked with a really really extensive array of clients and built out these production solutions is that you know the blockchain the smart contracts the consensus algorithm the nodes uh it's really really important right that's our ledger that's our trust anchor but it's it's a kind of a drop in the bucket in terms of the overall application stack and we see blockchain as being maybe only five to ten to fifteen percent uh in a lot of these solutions and there's a lot of things that you need to build into your solution you need to answer questions around data you need to have you know different transactional components for public and private transactions and the ability for your application to reliably consume events you need rich integration tiers to your existing legacy systems and your back office processes and then you need easy buttons around the application layer restful interfaces and digital asset constructs so within our ethereum ecosystem in collido we've provided these all as first class citizens directly embedded into the platform and moving forward you're going to start seeing a lot of these become available inside of corda as well this is just a quick snapshot of a few of the clients that we have running in production on the platform so gives you a taste of you know really how extensive and how diverse the ecosystem is and then lastly just a few snapshots on what you get when we say enterprise grade so iso 27k1 certification really really high caliber secure key management techniques enterprise identity constructs with pki and x509 certificates um h-a-d-r you know business continuity with reliable snapshot backups and then just best of breed open source clients as well i'm not going to go ad nauseam on these but i think it's worth mentioning that you truly do have enterprise out of the box regardless of what plan you're on in collido so that's it for the slides one more piece of housekeeping this is recorded you'll receive an email with the recording of this demo but we've been doing these for about eight months now as well uh we've done these um you know for corda but we've done a lot of them for sort of the ethereum door inside of collido so if you are interested and you know any of those i guess ancillary services that i touched on or actually want to see some turnkey applications and real world demos uh encourage you to go to you know just the collido youtube page and you have a curated list of all of the videos that have been done in the past uh jim did one on upgradable contracts a few weeks ago for example okay so without further ado let's go ahead and hop into it and everything that i'm going to do uh in this demo every single person in attendance is going to be able to do this as well so i'm going to use the out of the box free starter plan on collido and what i'm really going to do is just go you know step by step through the corda quick start guide inside of our documentation so this is a rather lengthy piece of documentation because there are a few steps involved but i just want to mention that every single person in attendance is going to be able to repeat these steps that i'm taking you through okay so into the product need to log in so again this is just a free starter account that i've created and our first call to action is to create our consortium or create our business network so i'm just going to call one make one called testnet i could actually upload some some pros or some rhetoric or legalese for the mission statement i'm going to forego that and now i want to choose one of the available cloud providers and underlying regions in collido and you see that we give you a choice of four regions across aws all across the globe and then two regions on microsoft azure and what we're essentially doing here is we're whitelisting this cloud provider and whitelisting that underlying region for the containers to be hosted in that data center so since we're on the east coast of the states i'm going to go with aws in columbus ohio and since i'm on the free starter plan i can't truly make this a multi-cloud or hybrid multi-region network so we're sticking with one cloud provider in one region so here's the name space for my business network and now i'm going to click on this governance tab here and i'm going to use the memberships option so one really nice construct that we've built into collido is the ability to easily mock out what you want your network to look like when you get into production right creating a facsimile of that future production network and so what you can do is you can mock out you know the participation using what we call memberships and so you could pretend to have multiple banks multiple financial institutions insurance carriers health care systems etc since i have named my organization alpha i'll just create another one called bravo organization and what we're going to do in the quarter demo is we're going to do a very very simple vanilla iou transaction between alpha organization and their node and then bravo organization as the borrower of an asset when you do get to the point where you've hardened your application and you know the topology of what you want your network to look like you can start decentralizing it so you can use this invite organization option to actually extend invitations and allow autonomous control of resources from external organizations inside of the network okay so here's the namespace the business network two memberships and now we want to create our blockchain we want to create what we call an environment and collido nomenclature so we see that we have two doors to go through we're going through the corridor today so click corda click next and now we want to create a name for this environment for this blockchain namespace so i'll just call this sandbox and inside of collido we've built this you know sort of in tandem with classic devops pipelines so inside of your business network you could have you know a sandbox dev environment you could have a pre-prod or a uat environment and then ultimately you can have a production environment we make it very very easy to promote and progress your code and your application logic through these environments without having throwaway work so i'm going to go with cloud only since i'm on the free starter plan that's my only option on other plans we do offer multi-region multi-cloud and even support for running these these containers these runtimes these nodes in a private cloud or in your own on-premise data center so if that's something that's of interest please reach out to us and we can discuss that in more detail take you through the steps and the requirements there okay so i'm going to go with corda os and we're going to go with a manage notary service here so click finish and here's the name space for our environment this is just the the firewall namespace and now we want to bring it to life by creating a couple quarter nodes so i'm going to create a node for each of our memberships that i have so create n1 for our alpha organization this will be the issuer of the iou transaction uh we're going to skip this step here but this is um you know sort of emblematic or representative of a lot of the integrations and synergies we provide you with your existing cloud resources backups log streams private traffic etc and then i'm just going to go with a small node again on our higher tiered plans based on the performance you need and based on the horizontal scale of your application we have different t-shirt sizes that support those requirements so we'll go ahead and click finish and then i'll do that same step and i'll create a node for our borrower in the demo node number two bound to the bravo organization next next and click finish and these guys will take probably 45 to 50 seconds to fully initialize and join the network and then transition to a started phase and you can always have full line of sight sort of on the status of your resources just by clicking the dashboard tab beneath blockchain here so while these guys are coming to life i'll draw your attention to another construct that we have and this is really nice for network operators or system administrators that want to have that full expansive line of sight into all the entities and all the organizations that are operating on the network so we have this address book here and you can view all of the memberships inside of the network and these would include of course external organizations if you were to properly decentralize your network and extend an invitation so we see here that we have our system monitor this is going to act as our notary and then we have our two organizations both bound to my root organization alpha organization so you can click on this view the membership details see the run times associated with it nothing terribly exciting here we just have a node for each uh each membership and we can see the status there as well so the address book is a it's a very useful utility um becomes even more useful you know as the network grows and as the network decentralizes so we'll hop back down to our dashboard tab see that we've made good progress here node 1 node 2 and the system monitor have all started up and one important thing that we need to do here before we take actions of restarting or re-initializing our node is we need to let these nodes properly and fully initialize essentially what we're looking for is we're looking for a notification in the logs that the node is running in its p2p messaging loop that it's fully synchronized and that the p2p communication that those threads are active and that they're happy and one of the steps that we do need to do is we need to upload some of our business logic our core dapps and then we need to restart the nodes so that they can load those core depths so anyway we'll come back to that in a second so our next step right here is to add a core gap and all we're going to do here is we're going to upload our iou contract and our iou flow and then we'll promote those into the active runtime of the node we'll restart the node and we'll let the node properly load those so first thing we're going to do here is we're going to create what we call contract project so this is just a wrapper or a namespace for underlying core dapps for our for our java code or in ethereum this would be for our solidity code as well so i'm going to create a contract project called iou and this is a useful construct because it gives the entire business network this full collective shared line of sight into exactly what business logic they're executing exactly what their apps are talking to so first thing we're going to do is we're going to go ahead and grab the we're we're gonna grab the contract file let me just move this zoom bar it always gets in the way um and these are available um all of these assets our rpc client that's gonna drive our application uh and then those those uh core jar files those are available in our public-facing github library which i'll pull up here in a second so first we want the contract jar grab that click finish and then we want to go ahead and grab the flow jar as well so as that guy is loading in there i'll draw your attention to the collido quartus samples gallery so this is the first thing that's referenced in the documentation and like i said this lets you build the rpc client that's going to sort of drive our transaction calls and it's going to provide you with that source code the jar files that we need to actually execute the application okay so now what we want to do is just add that flow file to the iou project that we created so again we'll go back here record a demo library glydo court of samples and now we'll go into the flow folder so go into build go into libs and there's the flow jar right there and we'll go ahead and click finish and now what we need to make sure is before we promote these into the active bucket of the node into the run time into the core container we need to make sure our node is in its p2p messaging loop so we'll go ahead and click the logs and we see that this guy is good no core dapps have been loaded and it's running the p2p messaging loop so let's check on node number two as well do our due diligence with this guy so no core daps and also running the p2p messaging loop okay so now we're going to use this core dat management tab and we see what we have is we have our contract jar and our flow jar hanging out in the staging bucket of the node so what we're going to do is we're going to promote these and then we're going to restart the runtime so it can successfully load those core depths so we'll promote promote and now we'll restart and we need to do the exact same thing to node number 2 as well node number two is gonna take part in this iou transaction it's gonna acknowledge that it's the borrower of a hundred um arbitrary units that we've configured in the source code so we'll go to core debt management for node number two and we'll promote both of those as well and we'll restart this runtime so as these guys are restarting what we can do is we can go ahead and provision the other components that we're going to need in this application namely what we need is we need a way to access the tcp port for for the quarter to node we're going to need to create what we call a collido bridge or a collido tunnel or service and this is going to allow our rpc client to ultimately have requests proxied into the corda node and resolve at that tcp layer there's not a public-facing rpc endpoint that we can access so we're going to use a service that we've created called a collido bridging technology and this is the same service this is the same technology that we actually use with our collido private stack orchestration that i mentioned at the beginning the ability to fully manage you know your own runtime infrastructure in an on-premise data center or in a private private cloud of your choice it's going to use this collider bridging technology as a forward and reverse proxy to communicate with managed services on collido and then ha e those you know p2p communications come back as well so we will go ahead and you can do this one of two ways now within the context of a node you can go ahead and click this create network bridge option or if you go back to sort of the the blockchain menu here we have an absent integration section and you can click on the dashboard and you can go ahead and create you can create a service from the security tab excuse me within the apps and integrations what we're going to do is we're going to be sending our transactions directly to node number one so what i need to do is i need to create this private stack bridge that has the same membership i need to bind it to the same membership as node number one so to make this easier or to not screw up what i'll do is i'll just create it through the context of node number one so that i don't even have to pick that membership okay so we'll go down to alpha name of the deployment what we're really doing is we're collect connecting a local bridge to a collido managed bridge and ultimately then into the quarter node so i'm just going to name this nick's laptop because that's really what i'm connecting through that's the proxy that's sending calls back into collido so we'll click finish and this is a collido managed service so this is going to require application credentials you know basic auth in order to securely connect to this endpoint here so this guy will take 30 or 45 seconds to fully provision and while he's coming up let's go ahead and check on our nodes and see if they've fully initialized here so we'll go back to our dashboard we'll click on node number one we see that the private stack bridge is still provisioning let's click on our logs and we see that it's loaded two core depths and it is running the p2p messaging loop here so node number one is happy and node number two is likely happy as well so also loaded the core dapps and running the p2p messaging loop so that's fantastic we'll come back here and we'll just wait a few seconds for this private stack bridge to fully initialize and now we're going to go ahead and make use of this connect network bridge button here so again this is just like any service or any node on collido it's protected with boundary security so we need to create these strongly generated security credentials that we call app credentials in order to have that secure tls connection so i'm just going to call these alpha123 since that's the membership and kaleida is going to give us a screen showing all of those details and all the endpoints that we care about username password embedded basic offstring or base64 encoded off header right here what we want is we want a json configuration object that we're going to be able to use with our locally running version of the bridge so that it can securely connect back to collido this is going to teach our local service about the core endpoints it's going to teach us about this server right here this collido private stack or private bridge server and it's going to teach it about the basic tcp ports that we need to send these these calls to here so i'm going to go and click this download config button and this is just going to be a pretty simple um json blob here with all of those endpoints i just alluded to so here's our client this is what we'll be running locally uh here's the server that we're trying to talk to this is the collido bridge hosted the hosted one on collido there's the username and the password and here's all the port mappings that we have here what we're really concerned with is we're concerned with the port mapping to note number one over tcp so this is what we will enumerate inside of our application here okay so this is u 0 v c saying that for my own memory and then the the local component the executable the binary that you want to run like i said it's just a it's a symmetric mirror of the service that's running on collido so you can go and click this download network bridge button this will take you to a library you can just grab the appropriate binary for your operating system here i'm running on a mac for for context here so okay so what we have here this is the collido the local executable that i have running on my machine so first what we need to do is we need to create an environment variable that's going to tell our local executable our local bridge about that configuration file that we just downloaded so we're going to call this tunneler config and we're going to give it the path to where we grab that i think it was u0v i hope okay it was okay and now we can just go ahead and kick off this bridge so this is now securely connecting back to the collido hosted bridge and when we send application calls they'll get routed through this local bridge into the collider hosted bridge and ultimately into our quarter node okay so we've done that heavy lifting the last thing we need to do is we need to create um some usernames and some passwords for authentication uh for our application to connect back to the chorded node so we'll do that in the context of the alpha membership or node number one as well so we'll go down here to the user management option go ahead and create a user we're going to call this guy user number one i'm going to give him an arbitrary role called transactor and then i'm going to just create my own password you can also let collido handle the entropy for you here on the password either way so we've created user number one we see an error message that's got a role called transactor but that role hasn't been defined so let's just go ahead and create that role transactor and i'm just going to give it super admin root permissions there so user1 with an associated password that i created this is where we're going to pass alongside our application here okay so the last step i think we've done all the heavy lifting we've uploaded our core dabs into the nodes we've created our kaleido hosted network bridge we're running our local bridge with that proper configuration and then the last thing we want to do is we want to just drive the application here so this is the rpc client that we got inside of that public github library so it's just an rpc client executable and grab the h-flag to see the available methods what we're going to be using here is we're going to be using the u the url pointing to localhost 4031. uh we're going to be using the username the password and then we're going to enumerate um a method inside of our inside of our flow the issue method so clear that again so we have some space so we'll say issue dash u is local host four zero zero three one dash n is user one and let me move the zoom thing again uh and dash p is password one i made a real strong password okay so we should see some activity happening over here um this is routing the request into node number one so if we actually go and look at our nodes right here we'll see that this right here 5tq is actually the id of node number one and what it's prompting us for over here is to enumerate the id of node number two our borrower in this scenario so let's go back into the collider console and let's make sure that we have these strings properly identified so 5tq we expect that to be node number one and then we wanna look up node number two so here's node number one five tq and now we wanna switch to node number two and we see that its id is lmk so now we just need to choose the integer that corresponds to lmk which is number one in this scenario so this is going to complete the entire iou flow about i don't know 20 to 25 seconds for each of the nodes to you know sign that acknowledgement send it to the notary and then the notary return it to each node and they can store it in their private state vault so 23 to 24 seconds would be my guess for all of these hops to fully complete and once they've completed we'll have a transaction hash will have an id that we can use to do a more involved query if we want so here's the id of the transaction so we can go ahead and copy this onto the clipboard and then we can just call a query so again rpc instead of issue we're going to go query um we're going localhost again we're going through the same route to node number one user one password one and then i to identify the hash there i think i got that right yep so that request came through and then we'll just see a cleaner list out of who the lender was who the borrower was who the notary was in this scenario right here so looked up the transaction by the hash we see the notary the common name and the ids and we see the value that we used in this flow and then we see the lender and the lender id and the borrower and the borrower id as well so how do we do so i think we did that in about 20 minutes so again all i did was i went step by step through this documentation the court a quick start guide again every single person can sign up for an account on collido don't even have to put in a credit card you can use our free starter plan or you can use our team plan and you can experiment with this court of functionality and or with the ethereum functionality as well so i see that there's maybe one question in the chat so maria i'll give this one to jim if jim's on um can we integrate tableau as an api in the application yeah hey thanks nick that's that's a great demo um not very familiar with tableau i'm going to assume that's a software as a service platform that gives you api to certain um aspects of enterprise application development just like twilio i assume the question is can we call apis from our decentralized applications so typically this decentralized applications involving a blockchain has at least two parts uh conceptually uh the part that runs on the blockchain layer uh in the decentralized mode nodes and then the rest of them are just regular um enterprise application back-ends and front-ends you can definitely call any apis in the in the typical enterprise back-end code and front end but decentralized applications running on the blockchain typically do not allow you to call external apis this is by design because blockchain logic needs to be deterministic so that whenever they are run on any nodes sitting anywhere in the world they always turn out the the same output given the same input so by design you're typically restricted on the things you can do in calling an external api is not one of the things that you're allowed to do in that layer of the architecture so if you have a need to um to consult a external data source as part of processing your transactions you need to not pull data from inside but send data from the outside and usually that involves a architectural component called oracles which is a name for a component that can fulfill these requirements and then send data in into the blockchain layer on demand so if you're interested in learning about oracle's uh there's an article you can find on our blog site that talks about chain link chain link is one of the more well-known oracles designed by a company called chain link so you can read about this and see how this particular oracle works under the cover and that is just one example of using external apis with a blockchain application thanks jim um looks like there's a couple others uh in the q a from flavio first one around the the database that the quarter nodes are using i think it's h2 but i'll leave these ones um with you to give more details on that yeah yeah yeah that's absolutely right uh nick um the built-in database we have uh today running on the note which is based on corda os the open source ver edition of corda the built-in database is h2 so if you have a need for more um [Music] types of database to be supported like postgres for example then talk come and talk to us we're still we're still in the process of onboarding corda enterprise version which will bring you the support for other relational databases like postgres sql and it's really easy to contact us uh once you've are in the collateral console click on that um question mark in the lower left corner and you can uh open the ticket and our support team will be very responsible to help you through this thanks jim yeah so i'll take the second question um yeah i did um flavio i did a very um benevolent dictator centralized flow in in this quarter example i'll give the same responses jim just just reach out to us offline so we can learn more about your project and your use case and your requirements and we can absolutely discuss and look at options to run this in a more decentralized way similar to how the ethereum networks are run on our business and our enterprise tiers as well so what i will do thanks for the the questions guys those are those are super useful um yeah so like jim said uh just use that question mark you can reach out to us if it's of a technical nature um just use the appropriate tag here if it's a sales inquiry just go ahead and use that tag as well and this gets routed to myself and the broader team what i'll also do is i'll put some email addresses into the chat here for folks to to reach out as well so you can always contact us at support collido.i o you can reach us at sales collido dot io and you can reach me directly just at nick.gaski collido.io so choose choose any of those routes if you want to get in touch with us okay another question in the chat as well any protocol to support interoperability of different blockchain platforms oh good one i'll i'll leave that with with jim um i guess i guess as you could see um you know we we do support multi-protocol we have um a theory enterprise ethereum and we have corda on the platform um within the ethereum bucket um we also have geth and we have um baisu and korum um soon to be just under the banner of quorum but maybe jim you can you can speak about um potential down the road interoperability options yeah sure um so interoperability is a pretty wide topic um generally that means uh getting transactions that are happening in one blockchain to be to be consulted on when a another transaction is happening on a different chain and have the two separate chains be uh be able to validate and verify transactions mutually it's a i said it's a very wide topic because solutions for interoperability is a wide range of architecture choices you can have a centralized component that's coordinating the transactions on both chains listening to events and then making sure when one transaction happens in one the corresponding transaction happens in the other uh so obviously this uh kind of breaks the decentralized nature of the blockchain themselves because now you're relying on a centralized component to do the critical coordination there are other techniques where you can do the transaction validation on the blockchain code themselves using smart contract it's more uh it's more complex to accomplish a more decentralized solution for interop and there are many other ways to achieve interrupt not sure this attendee do whether you have a particular need and scenario in mind uh clyde clyde today had supports ethereum variations plus corda we do plan to support other popular enterprise blockchain protocols down the road and interoperability is something that we have been working on in the background as well because eventually our customers will have a need for this as they onboard more and more consortiums that tend to across different protocols so if you like to discuss more details feel free to contact us often great thanks jim okay so i think that's it for the chat and the q a um thanks everyone for those uh those great questions uh also thanks for taking some time out of your day to attend this and to see how corda works on collido i'll reiterate that it is free to create an account and to go through the same steps that i just did and you can always contact us using the features that we showed or using any of those email addresses as well so this is recorded you'll receive this recording and you can view any of the past recordings on corda and or ethereum on our youtube page and stay tuned for announcements on future topics on upcoming tuesdays so thanks again hope everyone stays safe and healthy and have a great remainder of your tuesday