Countersign on Explorer Made Easy

Countersign on explorer

[Music] we're joined by the agora team and i think i'll just leave it up to you all lo'laan will have books trickle in but we can just get started right now with an introduction to you all to a goreck why someone might want to use a goreck and how to get started take : and I have to say Luigi's Mass with thee with the reality glasses on it that's the best mask I've seen so far so hello I'm ding treble actually I'm going to show some presentations I will show some shell scripts I will throw some browser pages and take you on a tour of what we have for you at the hackathon here and what you have to be able to build with first as if I can find my powerpoint window here there we go let me share my screen oh you have to yeah you have to enable screen sharing for me okay we'll do on one sec need you a co-host you should be able to share now let me know if you can alright yes a giant red thing so gorg was founded by folks who've been working in distributed systems and smart contracts for a lot of years I worked on the first production smart contract in 1989 Mark Miller who's also on the line here wrote the agora consistence papers in 1988 which were really the first big articulation of software agents creating and participating in market so we've been doing this for a while and that certainly predates blockchain and the basic idea of a smart contract a lot of people think they haven't encountered one before but it's that it's a contract like arrangement executing in source code executing in software where the software the execution of the code is enforcing the terms of the contract it's enforcing the payments enforcing the rights transfer those sorts of things and what's important is nothing about this says blockchain it's about enabling cooperation where the orchestration of it is happening in software and so services like eBay and PayPal and venmo and uber and lyft and all of those things have a trusted third party in the middle executing software that is orchestrating the cooperation of multiple parties and that's a huge valuable thing to do and and so it's something where lots and lots of people millions of people on the planet have experienced the upwards of a trillion dollars in market cap of actual smart contracts but blockchain revolutionizes that in an important way right blockchain brings multiple computers voting to agree on data and order of events and computation and what happened so we get a whole nother level of integrity and so whether that agreement is a Bitcoin Bitcoin is implementing a particular smart contract which is payments and there's proof of work to cause the agreement among all these different unknown miners or whether it's ten Derman coordinating the state validators in a cosmos system those are all different smart contracts I just lost the meeting control someone just asked a question in chat oh sorry that was that was me okay great break in if you need to okay and so but this is but but but but what what blockchains bring is they allow us to eliminate that trusted in trusted third party of you know ebay or the stock exchange or air or Airbnb or whatever it is so what is AG work building AG work is you know all of our ideas of doing smart contracts evolved in a world pre blockchain where it was network communication cryptographic communication between individual machines right exactly like you see on these these other these other services you know these these currently centralized services well IBC is the destroys a ssin of doing that kind of distributed coordination between chains were a chain as we talked about a chain is just a machine built out of agreement of all those computers using proof of work or tender mint or what-have-you we're and now we can have those individual machines that are chains communicating with each other so you have different kinds of machines we have public chains we've got consortium chains we've got individual machines which are just your servers now or an application running on your wallet and and so forth and on top of that we layer this model of computation with distributed communication between these different chains or between services between these different machines or between services what we call that's running on those machines and that communication mechanism is ibc that's where the vision of what we've been doing for several years came together with the ideas for how to do a cross chain coordination and matching each other's state machines and proof of work and and all the different like client behavior between chains into what we call the inter blockchain communication protocol or IBC and much of this hackathon is about stitching together and connecting different chains using IBC I'm talk about layers above that and we're mostly going to focus on layers above that and how they let us realize these different layers so let me go ahead and sin and head straight up the stack and and then we'll come back to actual code so above these layers of simple execution you know machine level instruction sets and all that sort of stuff what a great built is an environment that that captures that and makes it available to programmers in JavaScript JavaScript is the number one programming language on the planet 80% of the programmers in the world understand it that's something like 18 or 20 million programmers depending on who you believe and from our perspective in order to have smart contracts and decentralized web and all of these ideas and visions of what we want to be able to do to increase the level of cooperation to enable high integrity computing to orchestrate workflows across countries and so forth we have to have something that millions of programs for program to and so we so Markham for Markham for starters and then the rest of us coming along afterwards join the JavaScript and or just community and he's been driving into JavaScript the elements needed to be able to build a secure orchestration layer here so we have JavaScript where JavaScript promises if you're familiar with that idea it's in it's in browsers it's in node it's in reactants and everybody's user interface components it's a way that all these programmers are able to to build a synchronous systems we've extended it where one contract here one program here can have a promise for a payment a promise for a remote service a promise for a concert ticket whatever it is that's implemented in a contract either in another contract on the same chain or over the underlying communication protocols of IBC and and and and application protocols on top of it you can have a promise for an object on a remote chain and it can send asynchronous messages to those promises on the remote chain and get a promise for the result and I'll show you some of that and I'll show you some of how easy it is to program with that but that's it the javascript layer in the same way that yeah people could build user interfaces directly in JavaScript but they can do much fancier things building user interfaces in react or angular or view we have the equivalent of that for smart contracts and many of the challenges and most of our challenges are now at that next level up is build something using our smart contract framework so you can have components at the contract level like swaps and covered calls and opt other kinds of derivatives and and concert tickets and order books all those things that people will be able to then reuse to put together a fancier and fancier applications when JavaScript first came out like I said experts could do a few nice interactive things in the webpages right because now they could program finally some stuff on webpages but nowadays amateurs can come in with a couple of you know through a couple of prototype lessons and they can do much better stuff then those experts could do fifteen or twenty years ago simply because they have a framework of tools to work from and they've got components that were built by experts and incorporated in you know smart scrolling banners and photographic renderings and an embedded age you know an embedded HD high definition TV component all those kinds of things I think just put them together using a nice layout engine and and and deploy something really fancy our our goal is to provide that same kind of environment for you where you're either building components for other people to use or using components a lot of people are built to put them together to solve your problems okay so where do we go from here so weird so the framework I'm going to say a little bit more about it and then I will dive into it and I want what at some of whatever touch on is eating and dean real quick so cap TP and ERT what are those ah thank you yes so so IBC is split into two layers and there's a bunch of presentation about about IBC but the two layers are what we call the Tau which is transport authentication and ordering and that's the low-level goo that is implemented once by the people building that infrastructure twice for three times but it's but it's in the same way that all of the mechanics of making TCP work and making IP work is done by experts in the US and you and me as application developers we just open a connection and send packets the hackathon people are unlikely to be making edits to that exactly exactly that they will be relying on and and they will be using and above that they will build application protocols and it's good might be an application protocol to share like like bands did exactly this they had their protocol already for being able to talk about Oracle data their layering that on top of IBC so now as an application protocol you can ask for for band Oracle data over IBC to the band chain all right one of our challenges is for people to define a new application protocol and then do something interesting with take a proof of location on a location chain bring that over IBC and have a application to resell concert tickets that you can only do if you can prove you are not within a mile of the concert venue or whatever it is and refreshing then come back in this case cap TP is an application level protocol for IBC that we use for stitching together these machines at this high level to be able to send messages and get responses between these different JavaScript engines button that's the question that makes sense cool so Taylor did you want to read it up um sure is from Rick Tabaco this does decay allow interoperability with cosmos and polka dot chains and is there a template for developing plugin according to existing adapted with cosmos and dot like write a plug slash adaptor for years and also speaking of years there's a great plan and anything with records in contracts okay too many questions answer all the ones we're gonna need we're gonna need to spread those out of work certainly so agaric at this layer we are built on top of cosmos in the current version we are as you can see quite platform agnostic because we want to just layer across IBC and we use the consensus algorithm underneath but we are well integrated with cosmos and deploying our tests netizen acts as a Cosmo zone and when will be participating in the cosmos game of zones with our chain so we're well integrated with cosmos and we work with them very closely we've also worked closely with polkadot folks and we do expect in the future to port the system across there it will certainly interoperate with polka dot and all the other IBC all the other systems out there as they start to integrate IBC and there are projects integrating IBC with a variety of different chains and substrates and and and and and consensus engines and so we definitely are excited to do that to get to the world of millions of programmers building on this our belief is there won't be one winning chain there will be a whole lot of winning chains all winning more because they're connecting with each other and leveraging each other's own and and things built with IBC aren't necessarily built on cosmos correct yeah so it was very much a chain neutral chain independent protocol specification the current first implementation was done as a cosmos module and we're leveraging that but but we'll be building one in IBC there are people already working on doing that in substrate etc there's some one of the informal systems which is an ICF spin-out research lab for doing Interop they're building a rust engine that is designed to go into other people's rest chains and has nothing to do with cosmos in general so so so IBC is absolutely intended as as entirely ecosystem agnostic and trying to enable stitching them all together Thanksgiving and then cap TP is a protocol as I said it is a app protocol from the IBC point of view or either will be it's not currently implemented that way that'll be happening next but but that will run across the IBC rails to be able to do these remote messages between chains so I can invoke a javascript object on another chain ER TP i'll say a little bit more about in a few minutes but that is part of the JavaScript framework so cap DP is a data layer on top of tcp/ip just like you know HTTP is on top of tcp/ip sorry Kappa P is on IDC er TP is an object API just like react gives you an object API and let's pull out the other parts of that question I'd like to come back to some of it will be answered here and I want to make sure that we don't lose too much time oh I didn't I didn't dive into this quite so quite so quickly but so I'm going to talk about our our smart contract framework and then we'll look at some of the code in exists in most of the existing ecosystems right your user experience is I send money to a random number this is a snapshot of meta masks actually produced by Dan Finley so it's not like you know we work with very closely but it really is meta masks and what you're doing there at the end of the day what's the problem is you're sending money to my good friend 0 X 5 5 e 2 dot right and it's not just meta master this is the loonie wallet same thing right that's on cosmos same thing on everybody's wallet it's also for applications this is the well-known eunice wah and indeed I'm going to go through all this lovely user interface and then I'm going to send money to the random number and hope that something happens right that's not a great user experience that's not something I'm ever willing to explain to my friends and family right it's just did you talk about so oh um so what do we do instead and I move my picture of the I moved my picture that I wanted to show you next so I will jump ahead to it there we go I will show this picture and then come back um so our wallet expiry are system is all about offers instead of my throwing money at a number I make an offer through the system the contract will find out about the offer and the offer it has a quid pro quo I will give you three thousand moolah in exchange for two hundred samolians or I will give you two e in exchange for that that fancy concert ticket or you know or whatever it is and I Marmite I will give you digital access to this painting and exchange for you know a rental agreement on your condo right so it doesn't necessarily involve money these are all just digital assets that I can treat uniformly in an offer kind of framework and so what happens there is then the wallet is now instead of being in terms of sending money it's in terms of offers where I've got rejected offers to pay something for something else or I've got offers that I can confirm and and and that's my interaction instead of approving send money to a number it's approving do the following trick and so having now done that I will race backwards because they've dragged out of the position there we go so we have offers anyway so in building an application in building a smart contract you'll be building the contract the deploys in the Zoe frame and with the N and in that scenario if a seller was auctioning a concert ticket they would there would be the running auction the seller would offer that concert ticket for at least X moolah so his offer is I will give you the concert ticket if you give me one and that's the offer he is placing to the auction all of the bidders would do the opposite they would say I will pay at most this much money in exchange for a concert ticket and then and all of those offers will be presented to the to the contract and the concert ticket will go okay I'm going to go and and as those offers come in they come in with a proposal saying I'm willing to do X for Y and they come in with the money right they come in with the asset that is required so in the sellers case that offer comes with the concert eight in the buyer in the bidders case that offer comes with the moolah and then the Zoe framework underneath s shows that and so it's escrowed by the infrastructure on behalf of the the clients and the contract never ever gets direct access to those assets as a result it just knows that it has those offers right and now that it knows it's got a bunch of bids it's got a seller I can figure out which what the match is at that point it executes and doesn't what we call a reallocation that says okay you're the top bidder I'm going to give you the concert ticket you're the end you're you're the seller I'm going to give you the money from the top bidder and Zoe enforces that that reallocation only succeeds if everybody's offer constraints are satisfied and so it will only exceed if you know if the concert ticket seller is reallocated at least X moolah it will only succeed if the bidder that is B whose money is being taken away is given a concert ticket and it also only succeed if of course currency is conserved but that's required now the important thing is what happens to all of the other people is is when when Zoe completes all those contracts yeah the winning bidder gets a concert ticket and thereafter their offer was satisfied but all of the losers get a refund and nothing that the auction contract can do can cause it to get the money from the losers other than having another concert ticket to provide them in exchange right and so what that means is that that they get what we call offer safety where for the clients they either get their desired payout or they get a refund regardless of the behavior or misbehavior or bugs or what-have-you in the contract no code in the contract can cause this to not follow Zoe is enforcing it on the contract as part of the framework and that simplifies the contract and it simplifies clients and it generally increases the overall safety and composability of these components so is that is that basically like you create an open like a sign to offer and then they have to like counter sign and perform it wherever it's needed somehow like how do i much simpler than that i'll be showing you and then to the contract you get to you get assurance that all the assets rescued and you can from the description from the proposal you can figure out which of the two things I'm going to complete and then it has assurance by Zoe that the money will be eventually delivered on completion right and that allows you to handle and all of this allows simple coordination among clients and contracts while the underlying structure absorbs asynchronous transfer of money across chains it absorbs if it's not clearing and settlement or various other things all of that happens behind the scenes in the asynchronous communication about about moving these digital assets around okay you saw this before the final thing is we mentioned the RTP the electronic writes Transfer Protocol that was that object protocol that lets us talk about all these things and I'm just gonna mention the key elements of and then we'll get into the code where there are purses that are like accounts they are the holders of digital assets so I can have a purse that contains a currency quatloos or a purse that contains concert tickets a payment lets me transfer those so I can withdraw from a purse a payment Simonian purse a payment in samolians in order to send you a mint is the thing that would have created that in the first place and so there will be use cases in our in our in our challenges where you're creating your own currency or you're creating a new NFT a new non fungible token scenario where you instantiate a mint and then you just mint for example the currency is theater tickets and you mint non fungible tokens for each of the seats and now you have a purse that contains a non bundle token for a seat and you can withdraw seats and send it in a payment of concert tickets to your friend or sell it in an auction or at any and then finally there are issuers which are the things that let you both set up those new currencies and verify that a particular asset is of those currencies and there's plenty of tutorials and material about ER QP and in detail I'm just giving you the quick overview of it again all of these are tied together with what we call brands and amounts I will I will not spend too much time on brands but amounts are just the formal thing that say it's not 37 it's 37 quat moves or 37 samolians and napkin no end and a payment of samolians can only be deposited in a Somalian purse and so they're of the same brand right that god I've got payments that are Somalian brand ok so now I'm going to jump and this is another picture of the IBC ecosystem but I'm gonna jump from here - - the code if I can get over here before I do that are there any questions yes what I would like okay go ahead where can we find the example of swap AB that you showed apart from unit slope I pointed to our Docs but these are something that you can show yes so we're gonna start by going here this is the getting started page and this is you know you can go to AG or you can you can start from agaric and get to our documentation but the Bitcoin site has the directions to the getting started page and this is really you know the beginning of the world where where our if we go to unders OE it has all of the contracts and so you can look at the description of auto swap you can look at the strict the description of the simple atomic swap contract you can look at description descriptions of various different contracts that we have built over time a key thing is these are examples of reusable components reusable smart contract components so it's great to have a swap but it turns out the swap is used in the covered call where the exercise of the covered call is going to do a swap of you know so I don't know people are familiar with the covered call it's if I've got a a a a well I'll use a concert ticket again if I've got a digital concert ticket that's worth $100 you're not sure you want it but you're gonna find out you would like to pay me five dollars in order to have the right to buy the concert ticket for a hundred dollars from me sometime between now and Wednesday that would be a covered call it's covered because that covered call has the actual concert ticket inside it I have to put it in there so I no longer have the concert ticket it's now wrapped up in a smart contract and then I sell you the smart contract which is the covered call that you can now and I sell it to you for five bucks and now you have the ability to call exercise on it and if so you would do a swap uz which internally had uses the swap contract in order to get the actual concert ticket in exchange for another hundred dollars right and so that's a composition of two smart contracts that we talked about a lot when both of those examples are here let me go to my so the in the cross train hackathon so if you haven't seen it already and and Tatjana will bring all these links together into the recording of this video and they're all available to you but you can get to them all from the getting started site or from the git coin hackathon but here are our prizes we talk here about build a reusable smart contract and in that in that in that list were just work several examples which then they list under here you know were several examples of those smart contracts and similarly in that list if I go to our github and go to a gorrik SDK and somewhere under here I'll be saying directly the link but I find it just easier to say why is it scroll like that to say cover call and there it is so if I go to the government all there's an entire contract directory that has all of the different smart contracts here and as people build new components we will add them to the litany here and or and eventually we'll be making a place to be able to get at them elsewhere in normal JavaScript but this prize right here is build another one of those building it into an application and show it off okay as long as I'm on these these prizes that's this one the first one our biggest prize is do that for a stable point smart contract now that's just another reusable smart contract but it's one that might internally use an order book or my internal you know CDP is a subcontractor duck it's not various pieces building a stable coin is a hard problem so that's this one special fancy reusable that we called out that a few people will be able to tackle to build that particular reusable smart contract if you do other pieces that are reusable then you might have you might be eligible for more than one of these prizes but the big one down here that I was just talking about is usable smart - how much time do I have one thirty yard so I'm going to do a quick little stint here this is you know under the guide under the the refreshness okay under here we have the the the agora gap guide and this is a walkthrough of an entire very simple DAP that is the one you will install if you go through the getting started in sprout right so starting from here if you went to starting a project and each time you've been starting a new project you'll do a gorrik and knit you know my contract agora in its stable coin of work and it whatever and that will pull this simple toy encouragement dap which is like hello world only its nitrogen right so i'm going to take you on a quick tour of that in order to show the structure of an application if i go over to one of my command windows here i have a few of them i have i am in that directory where i pulled it down and let me go ahead and pop up a development environment with that all right let me not pop up a development environment to it I'll bring it up the old-fashioned way just one sec okay and in this view I have I have the hierarchy generated by do by grabbing the DAP encouragement application from our github site or by calling the agora can it step in our in our in our instructions okay and what I'm going to do is show you the structure of it so first let me you know I ran this in this case I ran I don't know if you can is this is the code readable here I ran I pulled down the encouragement gap I did the install and what I'm gonna go over here is I'm going to go to this window down in the lower right here I can find the window in the lower right and I'm gonna say agaric start - fast reset and what that's going to do is that's gonna start up the Agora chain locally and a server that is that is basically acting as my application server right so it's my web app server so what's the structure of an application an application has three parts to it if you're deploying a new in this case the encouragement body you're applying a eunice WAP clone or whatever it is is there's the contract running on the chain there's the web application the application server running on a server in the cloud or some set of servers in the cloud and there's the UI that goes to the to the user and so here this this system is launching book okay and so it's launching that server and I can now start up my application by going to localhost colon 8080 nope that's my wallet or sorry I will go to all of us so that you show you that in a moment one of the worst three thousand oh sorry Dean that server is that is that basically a node that has the ability to posts to each relevant blockchain and that is correct right right you know you know you know in our diagram it is it is the equivalent of pop here it is the equivalent of this solo machine that is set up to talk to a chain awesome okay okay so nothing happened here oh nothing happened here because I launched a vanilla chain right I didn't do anything so there's nothing running there I haven't launched a local application I haven't launched a chain or whatever but my vanilla chain has my wallet with a couple of budgets and no other applications wait I'm actually Dean this is actually kind of interesting forgive me if I'm wrong about this but so you're you're deploying something to this solo chain or whatever and through IBC you're then posting to the Agora chain huh not yet so it's only not yet because I BJ IBC just came alive two weeks ago it will be through IBC IBC is designed to cover that face um but right now it is it is cap key P running on crappy little TLS socket okay um no it's not CLS it's actually a IBC precursor that helped come up with the speck of IBC but it hasn't been my great thanks okay so um so first off I have not launched the UI so let me go and launch the UI so that's up here I am in you can see I'm in the UI directory if you can know if you can tell that right there so I'm going to go ahead and do yarn start in this directory and that will launch the UI server that is just the the thing that is listening on that port if I now go to that and again nothing's happening cuz I've launched the UI server but I haven't put my app on the on the system so let me finally do the two things that I've said the two really important things which is deploy my contract and deploy my application so the deploy my contract that's going to connect to my server and then it is indeed over the moral equivalent of IBC going to send source code um and [Music] there we go I didn't break things it has now deployed the contract so it's so it uploaded the Conda source code of my contract up to the chain and in order to see what that is what it uploaded is I go to contract J s and this is the entire source code of my contract and I will do I will come right back to this and run it but first I want you to see what I'm doing so it's easy to explain and then finally and so I will do the same thing which is I uploaded the contract I'm also going to deploy my API service which will basically do the equivalent of push my application up into the cloud to run that solo machine that will talk to the contract and now that's up and running and so finally I can go back to my browser I've got it I've got the website running and I did something horrible to myself oh I know what I did all right I did the the unforgivable act of a [Music] last-minute change so find that see what I'm gonna do is I'm gonna go get check out how do you do it up arrow head to get the last version all right who's got the the get command for getting up quiz yeah yeah all right now now let's try that again I'm gonna go ahead and deploy my contract where do you if that's what they change and deploy my [Music] yep nalchi of his works well that's a bomb oh I broke it there let's try that again where we go I did too early I mean I've actually had a good thing I just did okay so now I've got my trivial did my trivial encouragement app which is just like hello world only only I can say you know hey I'm feeling down because I'm all isolated here so I'm gonna go ahead and say you know please encourage me and it says I'm doing great I don't know if you can see my tiny little browser little thing there it's just saying I'm doing great so you know yay me right and if I do it again well I get another one I'm still doing great and and it updated in behind the scenes what the count of these things were okay that's just a simple app that has nothing you know it's running in my solo app and it's going actually going off to the chain and doing this thing so let's take it away and then I can do it through the browser through the browser but let's take a quick look at what's going on okay so fundamentally a contract and this contract is entirely within inside of this inside of this file is that large enough for people to read or am R&I yeah we can read it actually okay good um and so a smart contract for Zoey is constructed a it's a module in JavaScript standard JavaScript one function the make contract function that is a function of a single argument zcf the internal Zoe contract facet you know it's the way that it interacts with Zoe and what it's going to return if I jump down to the bottom of this file is a single object that has an invitation to participate in this contract and an object API that that will be provided by people who accept the invitation okay and and kate can jump in if i'm misspeaking here because this is a checks out one thing right okay and so so what this all with this what this application is doing is it's a little bit fancy it's got the it let me see where man they're gonna make comma so I've got my two messages the basic message you're doing great and the premium message which is which which I clearly did not earn cuz I only got the ordering gray and there is there is in this in this structure and I'm not gonna walk through all the details of this I have what's called a hook the hook is the function that will be called when an offer is made on a corresponding invitation so an invitation is exactly hey here's a place where you can submit an offer where you're gonna say you know I will give you five bucks if you can if you encourage me which is you know my simple therapy app or the one which is just a friend I'll give you your about to kill encourage me right and so what will happen is this is that offer will go in the assets will be asteroid bye-bye so II and this offer handle will be invoked in this particular case it's doing some fancy thing to figure out if there's a tip and various other stuff which I didn't show you but in general in the simple case what happens is is that it simply returns the amount it returns an amount which is here we go this first example hook is when I get called with an offer just return that the invite handle was redeemed and that's the starting thing where the guy who's sending all this up the application server is going to get the offer for the Uni it's going to get an offer from the from the contract to say here's the offer to start this contract start it all up be able to get lots of offers on behalf of these users so I'm a and I realize I jumped ahead here and I'm going into a part of this app that I don't want to go into let me just focus on the wiring of it which is I returned an offer to participate in the contract and the object that that that will be the outcome of that offer when when it's accepted and that will allow the service that is running in the cloud to be able to provide encouragement stew parks I'm going to jump to that service so this is the contract that is inside this contract directory here when I built this application when when I initialize this application using the aguar can it it gave me three directories it gave me the three pieces that I wanted it gave me the contract directory that has the contract in it under source and a deploy script for deploying the contract it gave me the API directory which is where I get my website my web application and it gave me a UI direct and so if I go to the place where I did these deploys you can see that it gave me those three directories it gave me the contract directory the API directory and the UI directory and if I look at the tree now here I'm installed so I might see a big never mind I won't install it on the fly I might see under API it's got a deploy script and a source directory that has my cloud service or my cloud application so if I go into there in here I've got the API I've got the API directory I've got the source directory and it's got my handler my handler office so in my web service I have a handler the entirety of that web service is in some sense sitting on this API handler here there's a bit more goo to put it together but fundamentally when I get a WebSocket connecting to me I might do a little bit of stuff when it closes so I'm just keeping track of all of the connections and when I get a message on that I get a message of the form hey from the UI get me an encouragement and here it comes back with the operation which is get the free encouragement from my application okay and so what my user interface is doing is it's a react UI or a simple web UI that's making this API call that goes to the web application submitting a JSON blob that has a type field that says encouragement and what's coming back as the answer is here's the encouragement this is code that is in my application never mind I will not try and figure out what it's doing there this code here is code in the contract where I showed you that contract here that has a get free encouragement operation here what's happening is my application when a webs when a message comes in from the browser on WebSocket it turns around and calls over the network from the solo machine from the application service it's calling over the network to the chain to the contract on the chain and say hey give me my free encouragement right and so the the the the once you get your contract set up the wiring have having these people talk to each other is very straightforward it's you know this is using a JavaScript standard that we talked about on our site a standards track proposal into the into the JavaScript Standards Committee for doing asynchronous messaging on top of standard JavaScript promises and so public API here looks like a promise for the that API I said and I invoke an asynchronous message and I immediately get back a promise for the result of that encouragement so a promise for the hey you're doing great and I return them in this infrastructure here this is a standard WebSocket II kind of thing by returning that hey you know the result of that it's just the string hey you're doing great and that goes to my UI just a no rush but just a quick time check it we have 15 minutes left so if we want to leave like maybe last 5 4 open questions that might be for diving do deep into the code that it's not this is awesome this too so people can dive in if they get stolen yes and then I then and and you know there are other recorded presentations that dive into detail of how the contract works I just wanted to show a little bit of it ok so now let me go to a much simpler contract and start there and I'm gonna do that where someone asked about this on the github site um oh sorry one more thing so in the UI thing of course in the UI is where the UI code is that that has the behavior for you know add an event listener on the button that with click and when I say click I'm just going to send over the API a record of the forum hey get me an encouragement right it's exactly as simple as you could imagine with the hey get me an encouragement huh I finally got the chat window yay part of the problem was I had no chat so so this is doing the API call in whatever UI framework way you want to use back to whatever API framework you want to use in this case it's raw JavaScript we've had simple react ones we've had people build things using material UI we've had you know and so so whatever you know this is going over WebSockets but it works over posts this is all standard ap standard UI framework from here but talking these very simple things where when the answer comes back it then puts it into the into the into the okay all right now let me go to the another application here unless people want to stop and dig more into this I will look at No so I will take five minutes but I'm not gonna Deadwood so there is a branch and the reason I brought up the the the the the the encouragement application is partly because it is an indent application that is the one that is presented when you do a gorkon it so it is how you will throw out a skeleton that includes all of the deploy scripts and all of the pieces of UI the web app and the fur and the contract but there's also a branch called the dibc birdee ibc example branch that shows how to get dibc integrated in and so there's the comment part and and and what's happening here is in the deploy script it just says hey give this guy an IBC connection as well and now the contract deploys with an IBC connection so that when the contract wakes up now this is all just a pull request against that branch you actually look at this death in addition to getting all the other stuff that it gets in order to be able to network communication it gets the IBC port out of the route of the the contracts record for the instance so zc z CF remember is the zoe contract interface it's pulling out the description of that contract and grabbing the IC IBC port out of it so that's just one of the things that gets authorized with and then then in the behavior when it's getting all set up yeah does all of its wiring to the WebSockets but all it had to do is using our JavaScript API for IBC so this is now going back to yeah there's all sorts of crazy stuff to make IBC work under the covers but from a DAT point of view from a programming point of view all this has to do is added listener on the IBC port I got is authorization just like you might add a socket listener or or a observer and JavaScript and that has an unaccepted that will be invoked every time someone connects to you so now this dat this encouragement bot suddenly is listening on an IBC port on you know on the chain so I could connect from another chain right so it's listening for that and when that connection is opened it's going to send over that connection this message and it just goes out as packets over the IBC connection and when it receives a message back its first gonna check if it's open assuming it's open then it'll turn around and send a message which is the V which is the wherever it is the message IBC it here it is which is which the first time out is the premium message and that's how I would get the premium message is you gotta go override to see to get it right and so I would get the bring me a message of wow you're awesome I've never seen such a thing right and and then it'll change that message back to basics only the first guy to connect gets the premium message to reward them for their efforts of getting connected over IBC and this is what it takes to do dynamic IVC in the system and so what I what I would be able to do in order to run it I'm not going to press my luck too much but it is basically get check out of that branch dibc - encouragement and remember I've already deployed my chain my application here I think you missed a C in there Oh actually I yes I often misspelled these things this was the change they did before okay and so if I do that and move it back because that was the bad thing all right so that hack I just had to do because I I misbehaved earlier now I will just go through the deploy script again and deploy that contract I've updated the contract deploy the contract and and then deploy my my application and it's deployed so the important thing about this deployment and you know and and and the application is still there is still there and working except I may have mucked with the good with the deployment script or with the configuration but the employment the important thing is at no time did my finger leaves my fingers leave my hand and at no time did I restart the chain right this application is now newly deployed updated the contract on chain of this encouragement protocol that the chain was deployed never knowing the existence of and that's what the dynamic part of dynamic IBC is that we'll be running our test net and or we'll be running a AAA game of zones test net and you'll be able to build new contracts and deploy them you'll be able to fix them update them redeploy them again and when you redeploy them it's a new instance so you so it doesn't have all automatically migrated state or anything like that but it still now then gets the poor gets access to it you can now reconnect to it load up things from the old instance that sort of thing and so that ability to iterate and deploy stuff after the fact on a chain is what the dynamic part of the IBC is about and it's and several of the challenges two of the challenges for this hackathon are to use that to build a new app protocol connect between chains deploy an application and make it interesting across chains or simply stitch together multiple chains three chains where you're buying and selling assets implemented on one chain in a contract on the goreck for to a contract on another chain awesome I'm curious if anyone has questions you can at any time in the hackathon go to the Explorer and hit chat and go and chat directly with the team on the company Agora channel but and you can even post in the town square with questions that you have and folks can contribute but I'm curious if anyone has any questions directly for the team right now synchronously we also have a key base oh yeah that's right yeah you can interact directly on key base and that's in the prize description the details there I'll also just paste something that was just sent to me by Rick tobacco oh yeah and I also wrote down all the questions which have been asked during this live stream so I will publish them with answers it's what kind of like 2d record of everything yeah sorry that's the question again did you yeah there were a few here so early on Rick tobacco headset as a results of the escrow not being optional and abstracting away the asynchronicity that something like a flash loan would become impossible is that right I won't say impossible but it certainly in this in this scenario is deliberate yep wrinkles so Rick asked the majority the questions here and I others can pop into is there a documentation for how to actually test your smart contract component write unit tests for it and everything before submitting on get coin I can I can answer that question um so we're working on documentation specifically if you're setting up the debugging but if you do have one of if you have add app locally that you're working on you can run yarn tests and that will run some unit tests that we've created for you but are in let me look up the directory should be in contract test test contract Jas so that will get you started at least mm-hmm yes we we have lots of automation tests for our system there are some amount of that in the in the example demos there's also quite a bit of it breaching the contract director each of those contracts have have tests we use tape it's very straightforward to add your own tests and a handset over time and we strongly encourage that as one of the ways to demonstrate that it all works I can I can probably answer this question from Rick to if I try to combine the DI see with the CDP challenge with the cosmos IBC challenge which bounty do I submit work for I would recommend Rick you just submit work for all those and point to the exact same code yep absolutely the one the one non-overlapping thing we have is that the CDP challenge and the reusable component challenge are different you might make a reusable component that is not a CDP reuse it in the CDP and that would be fine but the CDP itself as as the much higher single bound any last questions synchronously or does anyone want to share kind of their in progress projects that they're working on and and what they're hoping to build and maybe any requests for help feel free to pop in a chat I can undo some one really likes Dean's start yeah I finally got the chat window working I apologized that it I somehow managed to make it go away before and couldn't get it back so yes you can ask questions on a git coin chat there is a goreck chat and I think there is a chat created for every new project started that correct silence that's correct yeah but you can always hit up the key base as well which is yeah so I wanted to our all day get coin chat so whatever question gets us there I can always introduce you to our G key based chats and just pass on all the technical questions we are we are mostly on Pacific time but we have a one or two people that are on other time zones and may be able to answer questions outside of that we will have office hours and if people need more specific diving industry areas we will certainly be happy to yeah we we scheduled those office hours so everyone should have those invites as well on their calendar sorry I blew you guys left with so many invites working subscription preferences but for now just want to make sure you didn't miss anything it was another question from Rick is there a way to demo interaction with a cosmos chain like between the unis WAP example in Thor chain maybe in a separate session um so yes I actually went through that last night and was trying to figure decide whether or not to include it it's a good thing I didn't because literally my machine had to reboot seven minutes before they started so that was but but we will be putting that together and we will at least do a video record and get that up the the the the relayer demo the jack runs you can now do the relayer demo with you know with the board chains and that dap thing the demo that we walked through last night was using a route using the relay ur command set on the Kosmos chain to request an encouragement over the wire to get it from the running javascript contract so all of that stuff is has has is is working in various ways and we'll get demos of that that up over the course of this week sweet boy I don't want to be conscious of time so we can close out by the end but thank you all for your questions in chat thank you so much the Agora team for spending the time to go through and especially dean for jumping through the code we've mentioned you can ask any follow-up questions on the various chat channels and hope everyone enjoys working on these projects thanks everyone thank you all thank you [Music]