Brazilian chapter meeting, so everyone is more than welcome. Marcos, see you. Hello, first of all, welcome for everyone that's joined our Hyperledger Brazilian chapter meetup right today. Before we begin, I'd like to talk a little bit about our code of conduct that we have at Hyperledger. First, we always advise everybody to treat each other with respect, no harassment, no discrimination, and so on. We are an open community, and that's important for us to have a good relationship together. And also we do have some anti-trust policy. If you want to know a little bit more, please go to the week for Hyperledger Foundation to know a little bit more about the anti-trust policy of Hyperledger. And some other information we are going to, after the presentation, if you'd like to ask some questions for our presenter today, please write down at the chat, here at the Zoom chat below. And I myself and Renato are going to pass to the presenters, so on. Welcome, everyone. Again, welcome, everyone. And I would like to introduce your speaker today. It's more than an honor to have here today. I'm sorry, I never learned how to say yours. It's a senior director of blockchain product management at Oracle and is responsible for blockchain technologies, strategy, and products. He helps to set the strategy for Oracle blockchain efforts and guide customer partners and partners around the world in applying blockchain technology to deliver key business outcomes. Marks, one more time. Thanks for your time. I'm really glad to have you today and the stage is yours. Sure. Thanks. Thanks for invitation, Renato, Marcus, David. Great to be with you and great to be at least virtually in Sao Paulo again. I had a chance to visit a few years ago and meet some of the folks involved with blockchain technologies back then. I hope to have a chance to, you know, come and visit soon again and perhaps do another, you know, live session face-to-face here. But today I'm going to be talking about enterprise decanization with Skype for Leisure Fabric, leveraging some of the new capabilities in Oracle blockchain platform. We have, just as to mention, been picked for two years running now on Forbes blockchain 50 list, which is really good news for us and for the project so that our customers and partners are building on our blockchain platform. So I just wanted to highlight that. What I will try to cover today and we'll go for sort of quickly, since I have a fair amount of material here, is a little bit of a novel view of blockchain decanization to sort of a set the stage for what we are seeing and where I believe we're going to see in a significant uptake. We implemented it as you know, Hyperledger Fabric does not have a built-in token mechanism. And so we have worked to implement one in the Oracle version as an application chain code essentially capability, but it's a little bit more interesting because we also created a local development tooling platform so that people that want to use tokens don't have to necessarily write a lot of code or, you know, be chain code development experts, and I'll show you that as well. Then we'll talk about customer examples and some use cases, leveraging decanization. And I'll show you a demo as well, that we have recently built and this is for a bank use case. And then, you know, we'll just close with some final thoughts on how we can help customers get started and, you know, Q&A as well. But if you do have questions, feel free to pause them and chat. I don't know whether or not on markets, if you see things there that I have not noticed, maybe, you know, you can interrupt me if necessary to, you know, ask if they're relevant questions or maybe we can, you know, depending on what they are, I might ask somebody to wait until we get to that section of the presentation. No problem. Right. All right. So let's get started, right. And I'll start with, you know, some basics here for those of you who may not be in the thick of things may not be familiar with what decanization really mean. We heard the term, right? But I kind of like to go back to the basics, right? What do we mean by tokenizing an asset? Well, what we mean is representing it in a blockchain ledger, often, though it doesn't have to be a blockchain ledger, but it plays itself describing, right, that includes things like attributes and rights and obligations, the rules that are associated with that asset, so that then you can leverage variety of, you know, systems applications to process any kind of state applications, right? So tokens go through some sort of a life cycle, depending on the type of a token, and you want to be able to have different systems help automate that life cycle by understanding those rules and attributes and rights and enforcing them. Obviously, a very simple case is, you know, buying and selling, you know, cryptocurrency, but there are many more complex uses of tokens. So tokens have the capability to really impact a lot of sort of process efficiencies in companies and also provide, you know, benefits like reduction in human errors and fraud reduction and so on. But they also can create new opportunities from a top line perspective and create sort of, you know, because they're based in a blockchain or distributed ledger, you have ability to support multi-party processes, which can be, you know, implemented to provide new capabilities and even new revenues and new business models. If you want to sort of get into the basics of tokenization that is great for us to report from last year and when the future disaster tokenization that I would recommend. So, you know, what is the benefits to companies, right, you know, if we are not talking about the centralized finance, and we're not talking about collectibles and NFTs and cryptocurrencies. What else can you do with tokens and why is it useful and of interest to enterprises. I mean Oracle, as you know, typically focused on enterprise kind of customers, right. So what we see in our conversations is that many customers are looking to use tokens to track digital assets or physical assets through a digital twin concept.  You can control the operations that various systems applications can perform in the asset based on its current state and, you know, the rules agreed and so on. You can of course do asset ownership transfer. Or write maybe not ownership but writes certain rights limited rights to an asset. You can write ownership history without intermediaries and you can and this is really cool. You can allow fractional ownership, which means that you can increase liquidity of the asset and have, you know, more people participating in it in some way. There is a study here from markets and markets pointing out that from 2020 $1.9 billion USD US dollar.  And of course you have new emerging networks like flow, for example, you know, polygon and so on supporting NFT marketplaces. There is, as I said, you know, a number of different enterprise use cases that we see one was fungible side and non fungible, and I'll go into this a little bit more later on. But, you know, all of us who really like Hyperledge Fabric, you know, really stuck because we don't have native token support. And that does not mean that you cannot run application chain code to emulate years 2020 or 2021. And many customers, many of our customers and partners have done that. And you essentially have common, you know, building blogs that people use. I mentioned here about tokenizing a funeral plot to facilitate as a resale. It's an asset right so of course it can be tokenized, and you can do more traceability you could all, you know, if you wanted to do fractional ownership and things like that. So we've been asked a question about different between fabric Oracle blockchain and IBM blockchain. So, you know, Hyperledge Fabric is obviously an open source project within the Linux Foundation, both Oracle and IBM takes it to the starting point and then provide a lot of enhancements and a lot of interesting capabilities on top of Hyperledge Fabric right and this Hyperledge Fabric. So, let's see. Now of course, most recently, we've been seeing a lot more about non fungible tokens. And we've been able to build this from one to one blockchains just, you know, looking at the different types of scenarios where NFTs can play, and from our own conversations right we talked to retailers who are essentially interested in this only channel experience right how they engage their customers, the consumers, and NFTs play a strong role there. Companies in entertainment and sports and media, they use and think of value of NFTs in fan engagement and monetization of that experience. When we talk to logistics customers, they're really excited about NFTs as a way to represent electronic bills of lading, which are negotiable documents meaning they get the ownership changes as a shipment goes through, you know, the freight forwarders to shippers in ascending port receiving port customs all of that. So, representing bill of lading in an NFT format provides some really cool capabilities. Companies in a products business who needs to trace them pharmaceuticals certified, you know, maybe components in aircraft parts and on and on and on. A lot of values there. Companies that rely on certifications or qualifications of the participants. You know, if you are required, because of the nature of the regulatory space you operate in to have specific individuals with specific certifications at the company level or individual level, representing those as NFTs and then tracking them provides a great deal of efficiencies. We talk to manufacturing companies who are using NFTs to represent the inventories, and then take that to a digital market for inventory financing right in some industries in some areas inventories represent a significant capital. And they want to have it financed rather than you know spend zone working capital on it. In the investment space and capital markets. We talk to companies who are interested in valuing what's called ESG investments, which is, you know, as a type of investments that are socially conscious that you have good governance policies, you know, ethical sourcing all of those kind of things, reducing environmental impact, CO2 emissions and all of that used to be called green bonds. But it's very difficult to track value and track achievements and milestones that the promise is built into those investments. And NFTs can help us that as well. So, you can see that you could do a lot more than just, you know, having really cute pictures was that you trade and pay and spend, you know, thousands of dollars on there is real business use cases here. Now, as other questions that we get asked often is, you know, you are using a permission blockchain, which is hyperledger fabric right. So, how does that play for NFTs well let's start looking at what's going on in the industry today. And a lot of concerns that people have about, you know, open marketplaces and public blockchains like Ethereum right. On the great slide I think protesting one Ethereum transaction is equivalent to driving a car for 500 miles or using one month of electricity for an EU resident. All right, protesting over 100,000 visa transactions. There's a lot of concerns about that. Right. And then there is also challenges around, you know, security issues and in a copycat is a lot of user complaints about security problems and fake NFTs. You know, performance issues like NFT gamers plugging polygon and in all kinds of things right. Then you have additional issues such as you know compliance security compliance ability to use fiat payments without requiring crypto wallets. Not everybody wants to or really want to spend the time to set up a crypto wallet. It may not be very easy for some people and just regular fiat payments would be easier. And privacy compliance like GDPR in Europe and other similar regulations. It's also an issue right with open marketplaces availability and SLAs, as well as integration with variety of internal systems if you need to be able to track your NFTs attract the financial aspects. So permissioned blockchain can really provide a lot of benefits. They could also interoperate with in a public blockchains. In fact, you could trade NFTs back and forth or exchange them or move them. But having permissioned blockchain as a core foundation area. I think that would be the very important starting point to solve those challenges. So what's Oracle's approach right. Our platform as I said, Hyperledger Fabric based. You can implement years it's 20 years is 721 and many have done this application chain code, but we wanted to create it as a more standardized capability out of the box building block. And so we use this development tools that's called blockchain upbuilder which is a local development platform to generate all the necessary chain code from a specification. Now what specification do we start with? Well, we decided to start with token taxonomy framework from IWA because it provides a great way to actually define a meta model for tokens with things like base type fungible, non fungible, different properties, the whole of fractional custom properties, behaviors, all of those things and you can then start with a definition, create classes, instances and so on using this hierarchy. And so we went ahead and use this in our blockchain upbuilder as a model where you have declarative spec. You can set parameters, you can set some values in that spec. And then we will automatically generate the code, the chain code methods necessary to support the entire life cycle. And we've released that last summer we actually announced that the Hyperledger Global Forum last June, almost a year ago, fungible token support. And I'll show some examples of people using it. We're now working on non fungible tokens based on the RC721 model. And that will be in fact coming out very shortly in about a month. If you're not familiar with CTF, it defines sort of this, you know, formula expression for how to map token properties, right? Starting with the base type, behaviors, groups of behaviors, property sets and so on. And, you know, you can see here different behaviors that can be associated with a token. And all of that allows you to fundamentally create a spec and then use that spec as a starting point. So how we implemented it is starting with our blockchain platform. So this is a quick overview of Oracle blockchain, like I said, based on fabric, preassembled with a lot of underlying components, container management, identity, event services, option data, so you don't have to think about it. It's all built in. You can go into our cloud very quickly provisioned it all. It has a lot of interoperability capabilities so we've started actually. I remember 2018, I believe, a conversation with the IBM team in Basel at the forced inaugural Hyperledge Global Forum, where Chris Ferri and I decided we really need to take this forza from interoperability perspective and created and kicked off the Fabric Interoperability Work Group, where we were able to then do testing with IBM, SAP, some of the other folks of nodes from different clouds and different vendors, the Fabric nodes all working together on a single network. So that interoperability has been verified, tested, and maintained going forward. We provide the ability to work closely with a variety of applications out there, right? Our customers are not starting from a blank sheet of paper necessarily. They have existing applications on premises in the cloud, Oracle, or third party. And we provide strong API gateway for STPI integration, event callback, mechanism, Fabric client as the case, as well as a lot of adapters for various systems, whether your P systems or, you know, many other systems that they might already run as a system of record. A lot of automated DevOps and tooling for management monitoring and of course is blockchain upbuilder, which is a local development platform. The first thing that we have done is that we have created what we call an enterprise addition, same product, same capability, but instead of running this in Oracle Cloud, you can run it on premises or in third party cloud. Most of our customers, however, do use Oracle Cloud, Oracle Cloud Infrastructure. We have a data center in Sao Paulo that supports us locally in Brazil, and I believe 13 other locations around the world. So it's available pretty much everywhere. The enterprise addition version for on-premises can run in VMware or virtual box environments and so on, and it's very similar to the cloud, feature parity with APIs and, you know, application portability and so on. So it can be used to support kind of hybrid environments. We've done a lot of engineering work, so it's not just taking Fabric and making it available, right? It's making it resilient and redundant with the application of high availability, all of the dependency integrations. Quick provisioning, zero downtime patching, identity, security and auditability enhancements, API gateway, management and development tooling, database integration as well, many, many things. I won't go into that in a lot of details, but if you are already using Oracle Cloud Infrastructure, you can find our blockchain platform in the OCI menu, which is this little thing that you click and you drop down to developer services, and then you can select blockchain platform from there, fill in a quick form, five minutes, and then we will provision for you all of the underlying resources that you need, infrastructure, all of the Fabric capabilities and nodes, like code spears, orders, Fabric CA for membership, chain code containers, et cetera, and then Oracle add-on components, right? It's all preassembled all in one place and then you can start using it. And you can go into our console, which is a web UI to be able to manage, administer, manage a chain code lifecycle, set all kinds of configuration settings here, and there is also REST APIs for all of this as well, including monitoring troubleshooting statistics and all the rest. So, you know, we said kind of this was all good for helping people to get to a production ready state very quickly, which we're kind of known for. But beyond that, we said, how do we help people with applications to start using blockchain effectively, platform needs solutions. So we went to our industry partners and have a lot of them build, pre-built vertical solutions across many different industries. And then we created this local development tooling, the blockchain outbuilder, that can automatically generate the chain code for you from local spec. And of course it could manage lifecycle deployment testing and all of that. It's built using, well, I'll get into that in a minute. But then we said, you know, we can extend it to support organizations as well as the local capability with fungible and unfungible tokens. So the tool is based on visual studio code extension, which is what you see here as a web UI. There's also command line versions that you can use. If you want to integrate it into CI CD automation and so on. It supports full development and test and deployment lifecycle. It has built in fabric configuration in it. So you can test locally. And then you can go ahead and deploy into our cloud instance or BP running in a cloud or on premises. And like I said, one of the key differences, I mean, you know, the kind of basic deployment lifecycle that's been done before, right? I mean, that's not revolutionary. What's really distinguishing is the ability to automate smart code genco generation from specifications, right? We generate and type script and go and all of the crowd methods, all of them, you know, query, create query update, delete and so on. So the way it works basically is you start with a spec file in JSON or YAML. Here's a sample of it. And then you generate and will scaffold the project will create a chain code. You can then extend it with custom method if you want to, if you need to. You can deploy and test locally in a small fabric configuration. You can run debuggers in VS code if you wanted to do a step by debugging. And then you can package and deploy it into a BP platform. And so that's a very simple and quick process. And it enables people that are not chain code savvy or not chain code development experts to build really cool things in a very short amount of time. So this was released a couple of years ago and we said, okay, you could do generic things with it, right? I mean, you want to track cars, parks, whatever, that's fine. But now people said, what about tokens? Well, we said why don't we create a sample token specification again, based on DTF. And we allow you to specify the relevant, you know, token type behavior parameters associated with those behaviors. And then custom properties, you can extend the token within custom method as well. And all of that is essentially done in a very simple spec. We provide one for you to start with, you can customize and tweak it, right? And then we'll go ahead and we'll generate the actual chain code. Well, what do we generate? We generate an SDK, which is a set of basic foundational capabilities necessary to support the DTF behaviors. And we provide the actual methods I'll show you in a minute. And on top of that, we generate a set of wrapper functions that manage the entire lifecycle and make it easy, including such things as role-based security, which is pretty important in enterprise applications. So SDK supports essentially functions that you can see here. Oops. My PowerPoint dynamic, sorry. Let me bring it up again here. Give me one second. I'm not sure what happened. Okay, let me get to the right slide. Here we go. All right. So we generate the basic functions and methods necessary to manage the different behaviors, right? And this is essentially provided, you know, as an SDK. And then we surround it with lifecycle methods, right? For lifecycle management. So we initialize the tokens, we manage accounts, create account and all of the queries. And then the actual, you know, regular operations like minting, transfer, as grow, born and so on. But because a great question was to integrate with stock and build a release by NGD. We don't currently, we looked at it and the things this might be helpful. But at the moment, we don't have this integration built in, but it might be something that we can develop over time. So you have those methods available. Now, we are with our API gateway, everything you deploy, all methods are automatically exposed as REST APIs. So you could start using this by simply making RESTful calls. Or you could develop more complex chain code methods using this underlying building blocks, right? And calls them from your chain code. Either way. This supports, you know, the basic lifecycle. What we've also done is integrated a sample into our console. We have the developer tools section. And then the samples, we included this Fiat money token sample. So that if you don't want to go through the upbuilder and the generation, you could get it right here. You could play with it, you could deploy it. And, you know, then it has actions that you could play with, right? You can interact with issuing tokens, transferring, burning all of those things. So, you know, that's basically built in, you know, to the product out of the box as a sample to start with. The other things that we have started doing is looking at, of course, with NFT support. And I mentioned we have everything we've done. Everything I've shown you works today for fungible tokens. And next month, we're releasing done fungible token as well. We have a number of customers across many industries, entertainment and retail and, you know, manufacturing and you name it. And so increasingly we see conversations happening about white labeled NFT marketplaces, right? So we talked earlier about why that's important and attractive. We have put together a reference architecture. And again, this is not yet published in OCI reference architecture center, but will be in about a week or so, two weeks. And it's a reference architecture that helps customers and partners to understand how to use the underlying infrastructure components to actually build a marketplace starting as a blockchain platform and now NFT support. Integrating with content management, because obviously if NFTs you're going to have typically some content, videos, images and other things. And there is a mechanism called OCI Webhook that enables the content management to integrate as a blockchain platform. You would need to build a marketplace UI, some kind of a front end for general operations, right? So you need a UX platform with a visual builder for that purpose. You could optionally integrate it with an e-commerce set of tools for payment gateway and all of that. And then you have an NFT marketplace basically. There is obviously a way of running just key components here as a blockchain platform, content management UX platform. And then you can add additional, more complete kind of capabilities including analytics, you know, mobile services, integration platform. So we have a starting architecture, reference architecture for this. You can integrate content management with Stogeo IPFS. Yes, we can. If you don't want to use our content management, you can certainly use IPFS. And you know, if you wanted to sort party content repositories, we can integrate as long as they have ability to make REST API calls as you, you know, upload content and, you know, assemble pieces and so on. Then we can integrate with them because everything here on the blockchain platform, all of that integration here is done through the RESTful APIs. So we have a number of partners that actually started already building solutions and leveraging these capabilities in various ways, companies like Zua, Ticket Core and Fishball and Stogeo. So, and you're going to see a couple examples of that as well coming up. If you are an ISV, if you're interested in building a solution, reach out, happy to have that conversation and help you get started. So let's talk a little bit about customer examples. As I said, over the last few years, we have seen interest in tokenization use cases across a number of different scenarios. I'll start with the most obvious, which is rewards programs. And with rewards programs, you can use fungible tokens. We have solutions that have been built by partners, such as loyalty programs, rewards in an agricultural supply chain, and rewards for contributing data from CNC factory machines, computer-operated factory machines, and then providing rewards for predictive maintenance kind of things. The other scenarios are digital currency, of course. So we're pretty active in CBDC space, talking with a number of central banks, as well as bank back, commercial bank, back digital currency. But also twins representing other assets. So in the product space, manufacturing space, we've used tokens to actually enable a certified supply chain tracking and royalty-accrual solution. In insurance back office, they have a lot of different silos that interact with brokers, with agents, with reinsurers companies. So there is an ecosystem. It's all about payments and flowing the money around. But because they're separate silos, blockchain ledger provides a single source of truth and ability to integrate all of them without having to the heavy point-to-point integration. And then we have non-fungible tokens, where we've seen interest in areas such as data marketplaces or our companies that have active sort of solutions around data marketplaces, IP rights and other things, ESG, auditability investing, consumer marketplaces for collectibles and videos and such, and other things. So I'll show you a few of those examples. The Castelon is a sports retailer, and they have implemented this a couple of years ago, starting in Eastern Europe. They had the loyalty system that would take 30 days to actually give you your loyalty points. So you would buy something in a store, and a month later, you get a statement saying you have some loyalty points. Of course, you forgot what you bought by then and what you're going to do with it. They wanted to change that to provide real-time capability.  You can go to a variety of partners they've signed up for lessons, club memberships, tickets to sports games and other things, and use those loyalty points immediately. So that was really great. And one of the big factors as well is multi-currency support because it's just in Europe, not everybody's in Euro, right? So they wanted to be able to do this and essentially use loyalty points for people buying in one country and then going to a game in a different country. I mean, there's football fans and such. Here are the different projects. This was about sustainable agriculture, a project that was supported by World Bank funding, implemented by Infosys, who is a big system integration partner of ours. It was about provenance. It was actually implemented in Indonesia for sustainable traceability of palm oil, palm tree farming, etc. And the oil mills funded the rewards program and there was a wallet implemented where farmers and groups of farmers, etc., all had access to the wallet, either as rewards points to be able to use it to buy stuff for the farm or convert it into actual fiscal payments, right? Fiat payments that could deposit that into the bank account. This is a different example where a company that is in textile space, they're responsible for fabrics that have some volcanic sand content in the fibers that allows them to keep constant body temperature. So they're using athletic sports, that kind of thing, right? But they don't manufacture anything.  And so tracking all of this as products and ingredient tokens on a blockchain, right? You ship the products, you have inventory of tokens, you consume them when you produce the next product in a chain and so on. So there's production and consumption of tokens happening here. Plus, everybody here pays royalties, which they used to get for spreadsheets once a month, a difficult process with a lot of arrows. Now they get this in real time as people actually record the royalty calculations that are automatically on blockchain, and then they can issue payments as well and we track the digital twin of the payment on chain as well here. We can drill down using our analytics integration into any particular product and see all of the ingredients. So a jacket here made out of different fabrics, particular fabric, what fibers, you know, what this master batch, et cetera, relationships with the companies and the Sankey diagram and all of that. This was an insurance case I mentioned earlier where there is different systems where the payments are flowing between brokers, between agents, between insurance company reinsure, and by using the ledgers, they can integrate all of that in one place. This is a more recent example that was implemented by a partner in Italy. In Italy, they have this tradition of creating Christmas trees using lights. This is the biggest Christmas tree in the world, apparently implemented, built on the stress seminal lake. I think it's a couple kilometers long, made out of lights and they have an event. And they sold tickets to that event because COVID-19 compliance and they wanted to maintain the maximum number of people at any time, real-time monitoring. So Ticketcoin has built, using our fungible token support, this ticketing system, right? And this was a great example of using tokens. And they're now expanding this to a variety of other sports events and other attendance kind of events that have live attendance monitoring in Italy. Here's another example in a transportation logistics space. There is a lot of issues. It's a very fragmented industry in freight and shipments and so on. And you have situations where there is a lot of payment disputes, a lot of administration costs, issues with temperature deviations. A lot of trucking companies, 90%, have six trucks of fuel. So there is a lot of consolidation, kind of matching demand and supplies. There is a lot of intermediaries involved. So we have been working with a company in Europe, which is a major industry player, and they are transforming this business, creating this transport management automation marketplace. And in that marketplace for freight services, they're charging for this consortium services using wallets and using the fungible tokens that are connected to payment gateways. And then using those tokens, they're basically able to do micropayment based monetization in this infrastructure. Here's an example of a bank on the Caribbean Islands. They fly a lot of US cash in every vehicle on the plane. And they wanted to do digital currency tied to USD money system. But basically combine banks and locally money providers in the digital currency network. And so we've actually created a demo for them. I'll show you this how this is done. We have essentially an issue, a bank issues a token to a user, and then the user will use it to pay for a hotel, right, using the token and then the hotel can exchange it back with the bank for fiat currency in the account in the bank account. So there is this utopian bank that sets up the system, bank managers and will issue the tokens, means them, transfer them to the user. The user has the ability to transfer tokens to the hotel, then the account receivable manager can burn tokens to cash out. Right, so let's run through this quickly. For Oracle blockchain platform that enables the developers to rapidly test and deploy the chain code for blockchain applications that can be deployed on Oracle blockchain platform or you can locally test using hyperlatch. AppBuilder supports multiple languages, type script and go programming, and there is a specific process that you need to. I'll skip through the intro just so we get a better, so you see here. Great token, bank coin tokens. So here are the assets, if you're for the bank coin demo, describing the metadata of the ammo file, looking at all the bank coin token asset, if you're looking at the anatomy, this type is called fungible token in this game. There are types of behaviors that can be defined for for this token based on the token taxonomy like transfer. So we talked about that, I wanted to show you there's also a merchant asset. The token has a specific lifecycle of methods that are automatically created, create, issue, update, transfer and burn. So these are the four methods of the token lifecycle be any custom business logic that needs to be generated. Such methods can be written at the bottom that can be written as custom methods in this case that initialize bank coin merchants and transfer bank coin. The blockchain app builder provides you with the simple mechanism to go and create the chain code by using the spec files. You, you can do this by clicking on the chain codes tab on the left hand side corner on the top by adding the button over there and defining the name of the defining. And this is the language that we want to generate the code in. And here is the spec file, which we created in the first step, like bank coin demo in this case, and enable the MVCC optimization and click on create in this case what you're trying to do, what you're seeing at the bottom is the output of code generation, as we speak so you can see the chain code is generated in Golang and you will see once it's completed, you're going to see the chain code that will be shown. Let me scroll over so you see some examples here. First one is the bank of the code model. There is merchant data structure. These two are the token, these two are the objects of data structures we are going to use the business logic like create, update, issue, burn, and transfer are defined in this control file that has been generated. Here are the custom methods that are generated with the signature to perform specific custom actions that are needed by the solution of the application. What we're going to do now is to write the logic to for this custom methods. So we're just copying and pasting the logic here. And so fundamentally what you're seeing here is this process using Godbuilder. Now we're going to go ahead and start deploying it. With the URL provided in your URL provided for this proxy. This is the remote URL that you're looking at and username has been defined as Bankhead for deploying the chain code and testing it. So we're saying this file to make sure that we get the right connection. You can see that the environment file is saved so that we are ready to do. This is, you know, pointing to our environment in Oracle cloud. And now we're deploying this. Initialize the token by giving a bank name. So let me skip that. This on our blockchain environment. So you can see that the chain code is deployed on the stable client channel. So once it's deployed, let me go to, okay, here's our blockchain console. And let me just go to where we have the PIN bank and spend it. The network defined. And we have the chain code here. And you see the ledger transactions here. This was just a deploy transaction. But now we're going to use REST APIs and Postman to actually set up, initialize and run the system. The API codes can perform transactions on our Oracle blockchain platform. Here is the URL that we're going to use for performing the API transactions. So, and here's the body of the transaction where we're going to initialize coin token. Let's go and perform an initialized token transaction. So you can see the kind of APIs here, right, that we can generate. You can see the token has been created with the name T1. So we're going to set up accounts. So if you create account here, add role, right. So for example, the bank account has a mentor role. Then we create account for retail user. Then we create the merchant, which is spending hotel. That's create account plus a few other functions in the custom chain code. They have a burner role. And then we can go ahead and perform actual transactions. You can see transaction history here for the token here. And we can show the actual history of all of the events. And then we can do basic transfer operations. Once I book the hotel, there's a $350, which I want to transfer to the hotel manager to book the hotel. You can see the $350 has been, the tokens have been issued to the hotel manager. Okay, let's go into the transaction, hotel manager transaction history and see the amount has been transferred. You can see that the credit is $350, $350 tokens. So we can do born and all of that. And that's what sort of it looks like on the ledger, right? But in the interest of time, I know we want to leave some room for questions here as well. So let me just wrap up here. One thing I wanted to mention, people ask some time, how can you exchange the tokens with other platforms and other ledgers? There is a protocol, hash-time locked atomic swap or hash-time locked contract, HDLC, that basically allows different ledgers to exchange tokens. We've actually demoed this before. I believe last September we had a hyper ledger event where we've demoed this with Ethereum, yes, it went to contract and now we've got money tokens. So that's a pretty straightforward process, right? Most of you are probably familiar, you can look it up, this Google HDLC. We also have integration work done with Quant, which provides this over ledger middleware that can interoperate with multiple ledgers. And we have seen also that the Hyperledger Cactus team released, I believe it was just a week or so ago, a one-to-zero version of Hyperledger Cactus, which is an integration middleware that supports connectors to multiple ledgers and so on. So we're going to be taking a serious look at that and see how we can integrate them into the platform and leverage it for cross-ledger integrations. An example of NFT-based deployments running currently or being tested. So I'm partnered basically with our partner Zuo here. I've talked earlier about many, many different use cases across an NFT space that we're beginning to see people adopting. And so just in closing, I'll mention that satellite tokenization projects can be done on Hyperledger Fabric. People sometimes shy away because we don't have native token support, but that should no longer be a barrier. Our capabilities and there is open source samples as well out there for how to do tokens on Hyperledger Fabric are out there. But I think with that builder, with low-code capabilities, we can significantly help accelerate that by providing this low-code approach with a TTF model out of the box, code generation and the local test environment and automated deployment all help to improve developer productivity a lot. And so, you know, if you wanted to try Oracle blockchain and see how easy we can make it, I would, you know, I'll skip that. I would just suggest that you go ahead and give it a try. I love this quote from Don Tapscott about future being something that it's to be achieved rather than to be predicted, right? So all of us have the tools and capabilities to do that. You can get a free trial on Oracle Cloud right there in Sao Paulo or 30 other cloud locations around the world. Oracle.com slash cloud slash free. It's that easy. And you can set up, I believe it's 30 days, $300 free credit. And you can go ahead and that's it. Start playing with it and you could use the samples that I mentioned. You will see when you provision as an instance in the developer tools on the samples that Fiat money token. So that would be great. All right. Thank you, Mark. Let's open to the question and answers. The first one, I believe that's important to be clarified. If you can do a short explaining the difference between hyper ledger fabric, Oracle blockchain and IBM blockchain. Yes. I already think address that earlier. Yeah. Hyper ledger fabric is a core open source components that all of us rely on and use to build specific products. And Oracle blockchain and IBM blockchain are two examples of taking hyper ledger fabric and then extending it to better serve with more comprehensive capabilities to our customers. In a comparison between Oracle and IBM I live for another time there are some most companies done a lot of excellent work in making blockchain easier to use faster, more reliable resilient and so on. And, you know, and interoperable right so you know if you wanted to mix the nodes from Oracle IBM or open source fabric you could do that in a single network. I mean, I would tend to think our blockchain is easier, simpler, we have tried to simplify and automate a lot of times that you'd find in other environments you have to do manually. Yeah, the second question. It's the about the builder. They are asking if the VS code is on marketplace and why are create and if it separated from the So, okay, the VS code extension is not yet on the VC marketplace. We do plan to get it there. There are some process involved, I guess, you know, Oracle has to go through certain steps and we are going to get that in place, but it's not there yet. As far as create an issue I think we're talking about create. When you create you actually initialize a token ecosystem right and that's the step necessary to set up the actual, you know, ecosystem initialize it. But then when you issues are just minting right so that you do, you know, based on the mineral, and you could, you know, you could use it multiple times. Yeah, I believe that the last one is if you can share this presentation to the audience. Yeah, reach out. So I think is a recording. Yeah, on the live on YouTube. Okay, so yeah, so we could certainly record that. If you're interested in learning more, please reach out through Renato and he can answer many of your questions you can connect with our team as well. If you want to try it out just, you know, go to Oracle.com slash cloud free trials and sign up in support region or any other. Yeah, I don't know if if someone else would like to do a question or not. I actually do. As usual. First of all, congratulations such incredible presentation. And such as incredible tool as well. This is very impressive to see all the other things that you can be can, it can do building chain code from from scratch. But I'd like to ask another question about the market. What do you think about the, can you access the risks of speculation at the token markets because you do have lots of things around NFTs and our ERC 20 tokens and so on. Do you think it can be a risk to the platform and to the technology as well.  And I think the answer is that in the public blockchain, which is really has no governance. It's not really, you know, no regulation, etc. There certainly could be speculation excesses and other kinds of risks. And that's why we recommend permission to blockchain for most of the customer use cases, where they have, if you will, a community of participants that's authorized, and they can define and implement their own governance policies to avoid those kinds of things. Right. You cannot really avoid it in a public blockchain environment, but in a permissioned enterprise blockchain, the governance of that is much more within the control of the organizations that are operating it, operating the nodes. And I think they have all the capabilities necessary to control, you know, any kind of risks associated with using the underlying blockchain technology. Great. Thank you. Okay, I suppose that's enough for today. I would like to thank you one more time for share your time. I'd like to thank you for everyone that joined with us, and especially those of us, amigos de Latino America. And I looking forward to have you again to share more about your, your work and everything that you're doing. Thank you. Yeah, thanks. Absolutely. We'll probably have something more to say on NFT support specifically, like I said, in the months or so, there will be stuff on our blog. You might want to visit blog. Yeah, and I suppose that everyone are invited to join us in Oracle Award in the October and the same to the Hyperledger, submitting September. Okay. Yeah. Thank you everyone. And next Monday, we have our next meeting of work on our chapter. 6 30 p.m. Everyone is invited to talk about the national stuffs of our chapter. Thank you again and to the next time. Okay, bye bye. Bye bye.


What's up everyone takedown here welcome back to another video today I'm going to be showing you guys how to factory reset your Xbox one I recently picked this Xbox one up for $80 because it could not connect to a TV and I got it to work so now I do have to factory reset it so to do this you're going to connect the controller to the Xbox one you're going to hit the Xbox button on the controller you're going to move over to the system settings and you're going to click on settings here you're going to hit a now on this screen here account you're going to go down to system you're going to hit a there's a problem with the controller that's why I'm uh it's jumping all over the place on here you're going to want to click console info and you're going to go down to reset console now here it's going to ask if you want to remove everything or keep my games and apps I'm factory resetting it so I'm going to select on reset and remove everything this will factory reset the console I'm going to hit go ahead and hit a and then you'll need to be online to remove home Xbox associations so I'm going to continue without connecting because I know it's not connected to that and it should be factory resetting here this may take a little while but that is how you factory reset your Xbox one let me see if it does come up on the screen here there it is powering back on it should be connecting back up to the tv shortly and just like that is preparing the console so when you're on the screen you don't want to turn it off like it does say there and you're going to let it to do its thing and then it will finally be factory reset once it is complete I hope you guys enjoyed this video see you guys in the next one please take care peace


Initially we called it Field of Dreams Pricing. So like price at low and the sales will come, right? Low margin, high volume. That's so great. Yeah, I mean we recognized that we couldn't compete. Like in order for us to have a healthy gross margin back then at such a small volume, we would have to sell our coffee for six or seven dollars. The initial price point at Whole Foods was 369 and it cost us like two bucks to make it. So we had a very thin gross margin. Today it cost us less than a dollar to make and the on-shelf price is 299. So we wanted it to be low and you'll see anywhere from like 299 to 399 is like where most bottle of coffee sit. So we wanted it to be right in the mix of it. So like even though we offer premium ingredients, we wanna be competitive with the mainstream guys.


Safety is paramount in a manufacturing facility. There are a number of hazards there. We have automated machinery. We have presses that press coins at no 1250 tonnes of pressure. So no fingers, arms, hands, etc. Regardless of whether you're working within an office space or you're working on a production floor, there are different hazards within all areas. And if the work is injured, we take that quite seriously because it affects us all. I would say one of the major ones, which is commonplace, is manual handling. And we're constantly addressing those with engineering controls and also education and fitness type classes. No, four workers are in that particular field. In some areas there you have ear protection, hearing protection, eye protection, safety boots, high vis. Other areas require more sophisticated equipment. So other areas we have also AGVs, which are automated guided vehicles. They do have safety sensors that detect people in certain areas. We have signage and also induction processes for workers in that space. So we also have forklifts within those areas there. We have signage detailing the safety issues with forklifts. We do have regular breaks for our staff. We have exercise programs. We've also introduced new technology to mitigate some of those manual handling issues for staff. But also it's education and training. With regards to work health safety, it's continually improvement. We always have to look at other ways of doing things better, efficiently and more safely. And that's ongoing. With any organisation you have to keep on looking ahead and set the bar higher for both your workers and your organisation. October is National Safe Work Month. Visit the website to see how you can get involved. Safety is everyone's business and your knowledge and experiences are worth sharing.


We have a really good demonstration of this last night. Anyone that wasn't there, there's going to be a repeat performance time. Where is it, Rick? Do you know the name of the place? Well, wherever he goes, I'm going to drink here. BBC, BBC. I've made a few things, so if anyone's ever used Ice Cube, which is an idea of recurrence library before Easy Translate, there are the whole things that I've made. I'm sure you can find other things that I've made also. And I work at Patch in New York, so just a quick shout-out for my employer, who I said I would, and I came all the way from New York. If you live in New York, or want to live in New York, and you're a Ruby developer, come find me. We do really interesting things. We're able to freely contribute to open source as ourselves. Which is really cool, and that's a nice benefit, which I know a lot of you have, but a lot of you also don't. So the plan for today. First, we're going to talk about do what. So we're going to talk about what do I mean when I say splitting your app. Then we're going to talk about why you would want to do that. Then we're going to talk about how you can make it happen. And then we're going to talk about when the best time to make a shift like the one I'm about to describe should be taken to your plan. Where's that little iPad thing? There's plenty of time. Do I have time? So I'm actually talking about a few things when I talk about splitting your app. It might not be apparent, but the first thing I'm talking about is services. So I'm talking about taking your app and breaking into multiple pieces so that you can hopefully get the benefits that are tied to services that we'll talk about in a second. But the second thing that I'm also talking about is APIs. So as we're splitting the app into pieces, there's no reason that the pieces that we split off can't serve as APIs themselves. And this API might be a public-facing API or it might be just something again around internally or to other parts of your business. But there's no reason that when we break off into a service we can't have a nice API to work with. So why do you care? The correlation between scaling and splitting your app is very, very high. Just imagine trying to lift something, right? And it's very tightly coupled and it goes really big at Ross. You try to lift it up and try to make it bigger. But it's so heavy and it's so cumbersome because it's this huge piece. A lot of times it's valuable. We see this like who, everyone in this room probably, has multiple database machines. It may be a single application. Right? So splitting your app at that level, we also have to be thinking about splitting our app at the application level. So taking the model side of our application or the controller side of our application and finding ways to scale that separate of the rest. This is not something to really think about until it becomes a problem. And it recently did at Patch when we went from 30 counts to 850 counts in three months. So the amount of users that we had just blew up when we did that. So this is the age of innocence. This is the first thing that you do when you want to expose some kind of an API or have some kind of service, maybe even just JavaScript on your own application calling back. You just add response to your controller and you respond to different things. You respond to JSON, you respond to XML. You start doing this in a whole bunch of different places. And respond to is very innocent in the sense that every time you respond to you're coupling that controller action and the data that it's going to give back. And if it needs to change independently of your application, you can't do that. Also, your editing these response blocks kind of just where they're needed and if it's not maintainable. So the next thing you do is just the age of denial.  And you make other controllers. They do the same thing as your normal controllers. But they only are there to respond to API requests. So they only do response to it. Or maybe you decide to use something great. Then relief comes. When you decide that you're going to take the logic in your API and split it out to a separate application. At this point, things were getting too big. So you said, hell, if I just make a new application, that'll be super fast. Maybe your relief has collapsed. So if it's built in Sinatra, or it's built in Grape, I had to put that image in there because that's the coolest thing about Sinatra. That image was awesome. So how can we do this? How can we avoid duplicating logic, which is the problem with making that new application, is that if you have all of this logic on your model layer, all of this logic inside your controllers, you end up copying all that logic forward into the API layer. Then, if a business rule changes, you need to change it in two places instead of one. If you write less code, it does more, which should just be when it makes sense and when it's still readable, should be the goal that we strive for all the time. And how can we not all build the same thing? Meaning everyone in this room not all build the same thing. So I'm going to describe a couple of tools that I've been working on, and that we've been using in patch with a lot of success. So the first one is called Flexible API. The second one is called Flexible API Server. And the third one is called Constructor RB. So, first I'm going to talk about Flexible API. So you include Flexible API into a model. And by doing that, you get a method of two hash. So two hash does the same thing that you would get out of something like attributes. And it doesn't seem very useful. It's just like this, and it's really not because it's just attributes, right? So, what we realized really quickly was that there are multiple people that wanted the same data from us. They wanted it slightly different, in slightly different formats. And they wanted to make the requests in slightly different ways. So for example, we recently did an integration with the Huffington Post. And Huffington Post, on their page, they wanted to make a request and they wanted to basically say, give me the most popular story but at the same time, we're building a mobile app. It's going to be out at the end of March. And mobile apps are also using the exact same API. And when they call about a story that allowed long, they want a list of the publications around that allowed long also. But it doesn't make sense to have to give that back to all the users that are calling in from Huffington Post. So we invented this idea of request levels. So request levels basically say, what are the things at this request level that they care about?  These can either be methods or these can be actual fields that just calls to be the model instance. And when we call it to hash, we're able to pass in a symbol which represents the request level at which we want the hash back. So this hash doesn't have ID in it because the request level doesn't have ID in it. Request levels can also have notifications. So you can make notifications and pass a block that basically says, for this request level, I want to do something special. And I don't want to make a new method for it because it's something small. It's just a notification. You can use this to return the time along with things, or do you see the things like this? And then the hash contains the notification also. I think it's really interesting because you can also do includes. So you can say, this request level includes this association with optional scoping. So you can say, the most recent articles can be included inside of every publication that you give back to the user. The request level can have an include that gives the most recent articles. And you can actually do the include there at a certain request level. So when you call to hash with this nothing request level, you get a nested hash back which has a person inside of it.  It's just a hash builder, right? It's just a really fancy way, just a nice DSL for building hashes of any given model. When it gets really interesting, it's here, so find hash and find all hash. And the reason that this is really interesting is that when the model hasn't been loaded yet, in the instance of the model hasn't been loaded yet, find hash will actually do a select when it goes to get the record. So it's only going to pull back the actual fields that are inside the request level. And find all hash will actually preload all the associations forward. So you get to stop worrying about whether or not you stop having to write all of these includes and you start just worrying about what's going to be returned to the user. So then there's a partner for it. It's flexible API server. And the idea behind flexible API servers that we want to be able to quickly roll out an API that's entirely usable and whether it works is like this. So flexible API server is a small center server that sits on top of a group of models that include flexible API and it gives you paths like this so you can get things, get things by ID or get things by ID with a certain relation. And these return in either JSON format or XFL format depending on your accept header by default it's JSON. And it will return at the request level that the user is associated with.  You also get count only equals true which will just return a count instead of returning the records. You also get all of these. So click things to update an object with all of the data and click rems to create a new object or to create a new object through a relation for as many as as many years. So let your mind wander and this also does other things like deletes. I didn't work on this slide because it's scary but I'll say it out loud.  Also at the base of the entire thing since this is sitting on top of the database and it knows exactly what it's doing we're able to provide documentation that's built on the fly that just details what's inside of individual request levels on individual models. Also since it's in the database we can provide example URLs that actually point to resources that the user could access. So the way that we can do that we do slash things we do think.find whatever the scope is and then just do .first and use that inside of the example. So it's not pretty but better documentation. You can also put optical look-out files alongside it that describe what individual fields are for the user. So you'd say people.id is a certain thing or name is a certain thing. So then construct.rb is this way to get back a list of all of the things. This is something that you would use in the other half of your application to interact with the API for Ruby. And the way that it's typically used is like this. This is the way that we use it in our application. So instead of inheriting imagine your application being two pieces where one piece is kind of the front end back end and the other piece is the back end back end. So back end back end deals with the data that's where the API would be running and the front end back end deals with handling the controller actions and making calls back across the API. So this is a way to inherit inheriting from active record base and inherit from construct base and when you make calls the DSL mimics active record DSL. So when you make calls they're actually happening across the API boundary but they look like they're happening locally. So what we were able to do at this is a few models in our application that we were able to completely swap out with absolutely no changes to our code and our application is making calls across the API boundary using construct. The other cool thing about construct is that it's just an construct RV. So we also have construct.js and we also have construct.jective.c. So our application developers on the iPhone are writing calls in construct.jective.c. So when we add new API calls they don't need to write new code to parse the JSON or figure out how to deal with it and they can just use it. You also get things like reload so you can reload at a certain request level. So in patch what we ended up doing is we made a completely separate app that runs this and we use construct.rb to set our application and slowly are moving things to the services model using construct.rb in our application. We also use git sub-modules. The way that we use git sub-modules is we actually sub-module our existing app inside of the API and then what we do is we load the entire model and vendor layer so we have access to everything that was in our existing models and our API can use all the business logic and when something changes it automatically changes in our API we don't have to rewrite or maintain two applications at the same time. We just maintain the API layer. Currently, and this is actually in production right now our mobile developers are using this so we have an iPhone and Android platform that are both using this. We have external consumers external inside of AOL and also external to the world and also we have certain places where the JavaScript on our site since the API and the application are sharing a cookie the JavaScript on our site is actually making calls to the API instead of our application and this is all happening right now, but so a couple of issues that you might write into is something like this one is rate limiting so what we ended up doing with rate limiting is we used billware to handle the problem because it's just rat, right so basically if you make too many requests in a certain period of time you just throttle we also, I think our ops team actually added rate limiting and apache because we were not passenger why we need both authentication is another issue so the idea with authentication with flexible API is that users are tied to request levels and everything that they do is tied to what can this user see and what can they update and that's all contained inside of a request level so when a user views slash things and they are of a certain type they have the default request level that will be associated with them and it also enforces itself on posts and puts so if they try to update attributes that aren't inside of their request level they have access to so wrapping up this is just wrapping up I think that I mean obviously there's value in splitting your application but I think that finding ways finding ways to deal with the least pain that are still somewhat elegant is really valuable and I think that that's that's what we've done and I'm excited to hear any questions or feedback that anyone has on any of this thank you yeah so the other thing that we do the question was what if you want to limit access to certain types of record and not just the fields inside of the records so what we do for that is actually you can inherit flexible API server and extend it so when we go to extend it that's where we want to enforce additional logic, additional essentially controller logic like what you said we have a method called pass it allows us to say like do this thing and then pass and it will pass up into flexible API server so that's how we handle that this is just to give some background a little bit more background on flexible API and flexible API server it started actually as a separate project it started off kind of internally it started building this thing and we realized that it had value outside so what you're seeing now is I guess the result of also running empty issues like what you said and trying to find ways to fix them and there's going to be a lot more work on this and especially the authentication layer I'm also speaking at RailsConf on a similar topic so hopefully between now and then we'll get to somewhere where it's more usable Can you repeat what you said about the submodules I missed part of that one? Yeah so that pass we use we use git submodules and the idea there is that the submodule are existing application inside of the API so the idea is that when the API starts we load just the model, lib and vendor layers and all of the initializers inside of our application so we have access to all the models that are really existing and then we just go through and we define request levels on the models that exist you mean aside from submodules so it's started out really naively by just copying things over trying to get more of the API working and you quickly realize that's just completely not maintainable another thing that we did early on was we used the path to our application but that's assuming that you have your application checked out alongside and I just think submodules and it's a great use case for submodules versioning your API or something like that yeah so that's a really good point versioning is definitely important and I think that the the adverbs take great cakes with just the version command adding a namespace to the entire thing which would really work actually it might be valuable to consider instead of some option because it's closer other questions so the question is would I run multiple copies of the app to maintain multiple versions at the same time so it's a good question and the way that this the API the reason that we started doing this is I asked both the site citiesbest.com I built the entire back end the cities best not rails unfortunately but the cool thing about cities best it's not a very pretty site the cool thing about cities best is that everything on the page is driven by an API that sits alongside cities best so all of the calls that you're seeing are actually being made behind the scenes too a separate API that makes the same kind of model that we're using here and what we ended up doing there was we would we'd use routes to namespace all of the actions and then you already test the entire time so when you make a new one you initially defensive the completely different version or not but a lot of times you're just doing incremental updates in that case what you can do is point two versions kind of at the same code and then as they do a verge move them off I'm not sure if that's the best approach but data validation the server or the client and then also error propagation or any marshaling errors back up to the client and then retaining that across the platform that's a great question so the question is how am I handling error cases especially validations right so what I do for validations right now if you try to put or post something and it's not valid the validation happens inside the model layer back and back and so the API side so they're just active record validations and what you'll get if you do a post that contains invalidated you get a 422 back with an errors hash so this is the exact errors hash off of the diagram that you're trying to create any other questions are they even responsible for working on different parts of the application in that light? yeah so the question is people working on multiple parts of the application they're just confusion we're just things breaking in general so we're lucky enough as we go to we have really good test coverage on the stuff that we are writing so the API as we're building it and this is another benefit is that if you split out the model layer of your application into an API like this you can essentially unit test the API like you're testing it's like an integration test to do that we're maintaining a test coverage but we have run into issues definitely where people didn't realize that a request level already existed for a certain purpose and ended up recreating it so I think that it's hard to avoid duplication and you need to be watching out for that questions very briefly touched on how you created the API for your IOS calls did you generate that code, objective C code oh ok so the same way that there is this construct base constructor rb for Ruby we have a very similar one constructor for objective C that does the exact what? how does that exactly query the API itself so the way that this works you say set type name people, actually that line is not needed but because of all this just singularized underscore lower case so when you're making calls across this it looks like an active record but it's actually making calls completely across the API boundary and it even works for nesting things like if you were to do person.things it's going to make the call slash person slash id slash things and then it will unwrap the entire result and instantiating the thing object so it uses method missing and dynamically is generating methods as they're used on these so it's kind of introspecting on the format built by the API and it actually the API if you're using it with constructor this is kind of a detail that I glossed over like I said but returns other information about associations that you wouldn't be able to figure out so it'll say like this articles array that I'm giving you is an array of articles and like this recent underscore articles is an array of articles so that construct can pull it back and decide what kind of object to instantiate for every factor that it sees. How do you specify where it's looking for the API if you're running them on different servers or maybe even if you're running two different two different servers how would you do that? I guess currently we're construct-rb as to handle models that exist on separate APIs although that's a really good use case because you might want to fragment you might want to load only a piece of your application that does a certain thing so like if you have a gem that maybe takes up a lot of memory or is like this huge burden and it's only needed in a piece of your application you can completely separate that so we don't have an answer for that like the answer the fix that I would say seems pretty straightforward but we do have an answer for it it's telling you where the API is and it just happens inside of an initializer on the front end of your back end so the controller side of your application basically just says construct-base. there's like a I don't remember the exact name to say where the server is cool, thanks for having me and talk to you later


Just a disclaimer, this video is not really intended for those of you who are suffering from depression or any other type of mental illness. I am fully aware that you just cannot get up and choose your happiness. It doesn't work that way. If that was the case, there wouldn't be any type of depression, right? But I do pray for those of you who are suffering and I also pray that you will seek help, get the comfort and support that you need. Look, I am so unprepared for this. This is something that was just last minute that I felt like it was on my heart. I'm being obedient, you guys. It's one of my things that I really am aiming for this year is whenever I feel a little whispering over here and we know what that is, a little nudge to do something, I'm doing it and I'm doing it as soon as I can because the late response is still disobedient because now you're twanging on whether or not, whether or not I should do it. So anyway, what's going through jotting down my ideas for my series that I am coming up presenting for you guys this year. The purpose series is coming in March. Like I have all my ideas down. While I was working on the woman to woman idea, I mean, I came up with a good eight to 10 different video ideas for that particular series and towards the end, you know, I'm like, great, I'm almost done, got everything down and then all of a sudden I get, you know, the notion of happiness, happiness, happiness, don't wait, don't wait to be happy. So I'm like, okay, great, let me write this down. This could be an idea for my series, either purpose or woman to woman because it kind of goes in between both, I think. And sure enough, I got a little nudge, little nudge. So I'm just gonna come on real quick because I feel like this is somewhat, since there's this is an urgency, I feel like to get this out there. I feel like this is for a couple of you guys actually. And it's not just one person, a couple of you guys need to hear this. So when it comes to happiness in general, don't get it twisted. This year, I'm all about walking into my purpose and finding my purpose, but I am happy. Walking into and finding my purpose is not gonna secure my happiness. One thing that we need to get out the way right now is that, yes, happiness is a mindset, a mindset, excuse me, but it's an awareness of a mindset in the now. All too often you have people who think that once I find that husband, once I get that job, once I make more money, once I, let's break it down to little level. Once I clean up my house, once I get these kids out to school, I'm gonna be happy. You cannot go throughout life with that type of mindset. I'm gonna tell you two stories in the midst of all this. You have to learn to be happy in the now, present and happy right now. Tomorrow is not guaranteed. You guys, last year, and I looked this up because I wanted to see how many people died. Nearly three million people died. And if you made it today, you better be grateful and be happy right now in the now. I mean, there are people who are literally dying as I'm recording this video. And you worried about being happy when you get that job. Hell, when you get paid, look, I praise the Heavenly Father every day when I wake up and breathe life. Now, yes, every now and then, I'm gonna have my bad days. You guys know I have anxiety. I have, you know, I'm not always, I'm not always in a good mood, hell. But I have learned to not have this notion of when I get this, when I become this, is when I'm gonna be happy. I have learned to find joy in the simplest of things and to humble myself and be happy right now. So two quick stories I'm gonna tell you, excuse me, because I just wanted to get that out of the way and I think that's gonna be for someone. And I'm gonna share a scripture here at the bottom in James. Two stories. A personal story and just one that happened with my husband. So the personal story, let's get that out of the way. So when I had JB and you guys, I had no help. No help. First time mom, my mother was here for two weeks and then she shipped off to Texas. My husband worked second shift in the hospital and it was literally me with a newborn baby, two weeks fresh smelling like angels and fairy dust. I was overwhelmed for like a bit of worse. None of the, I know that there are those of you who are currently going through that, who have gone through that, you've experienced that, you get it. I was having problems adjusting. It was really bad, I wasn't sleeping, I wasn't eating, I was breastfeeding. He needed to eat, but that was draining me. That was draining me, draining me. My baby wasn't, JB was not sleeping. He was like, forget your sleep. I'm not sleeping either. So I'm around eight months old. I think he was around eight months old. I was sitting on the bed and I think I've told this story before in one of my rocking sessions. We would do like 15, 20 minute rocking sessions. My back was hurting. I had on a shirt that had spit up. It was baby food on it. My hair was matted up. Just a hot mess. I was hungry and had forgot I was hungry. And I think I had started crying. I started crying. And then I looked down at my baby because oh, this is what I had. I told myself, I said, I cannot wait for you to sleep through the night so that I could finally get some peace. Peace goes in hands with happiness. So a certain degree in my opinion. So I could finally get some peace and be a little happy. Please sleep through the night so I can get some peace and be happy. But then a little whisper said, you have life. You suffered a loss and was told that you could possibly not have children. You're looking at America. I don't know those you probably don't know. I had a miscarriage like literally four months before I had JB, before I got pregnant, excuse me, with JB. Of course, you're supposed to wait at least six months. That didn't happen, girl. So I got pregnant. I was going through pain and I had suffered a miscarriage. So I was double high risk that couldn't figure out where the pain was coming from. Thank God that went away, of course, into 12 weeks into the pregnancy. But my point is, is that I was not supposed to have my baby.  Saying that, you know, I'm sorry, I'm keeping it real. I can't wait for you to sleep through the night so I can finally get some peace to be happy with. I need to be happy that I have a healthy eight month old. But so from then on, I'm telling y'all, I have learned to be happy in the now and to appreciate what I have right now. And then, cause I don't have to have any of this. And you don't either. Second story real quick. My husband worked with a woman who, I don't know how long he worked with her, but she was a nice woman, extrovert, social butterfly at the hospital. She was literally a couple of either weeks or days before her retirement. So she was trying to get everything ready, working, working, working. And pretty my husband, that's all she was talking about. I can't wait till I retire. I'm gonna go do this, do this, do that, do this.  That woman did not make it home. She went home and on her way home, she got hit by a bus.  And again, he emphasized that that's all she talked about was retiring and being able, you know, to finally have time for herself. But he said that she was working like crazy hours. She was working double shifts for extra money, I guess. She was doing all of this. So yes, you guys, that's another thing too. Don't get caught up in, don't get caught up in work and forget to live. I've heard that before, I've heard that before. Don't get caught up in the day to day stuff and forget to actually live. Do not get caught up in that, y'all. Let me tell you something. I've also learned to not get caught up in worldly stuff and not waste my time. Not wasting any more time, not doing any of that. But yes, I wanted to get this, I want to record this real quick. I know it's all over the place, but I feel like one of you, some of you needed to hear this. Not one, some of you help us need to hear this. That don't wait to be happy. Find the smallest things to be happy now. And I get it, y'all. Some days, let me tell you something. When you suffer with pain or multiple stuff, overall I'm healthy, but I have my issues, girl. So every now and then, not every now and then, I could go weeks with something that's going on. You know, I'm either, I'm sick, JV sick. And I'm like, I don't even know when the last time I felt normal.  I have a roof over my head. Just the simplest thing, y'all.  So anyway, let me wrap it up. Be present in the now, be happy in the now, be grateful for what you have because you, frankly, you don't have to have it. You're living here on borrowed time as it is. We really all are here on borrowed time. But yeah, you guys, I felt like I needed to get that out there. God bless y'all. Take care. Bye.


It could be, I'm not saying it's going to be, the beginning of this integration of the European Union or the Eurozone, you know, at some point the future of the Scots might decide to go for another referendum and maybe the breakup of the United Kingdom. Then the Catalans in Spain might say me too, and that might lead to a breakup of Spain. Some of the Nordic members of the European Union might say without the UK, the European Union is mostly the Eurozone, so what's in for me, Sweden, Denmark and so on. And as we know, there are lots of economic and political fragilities within the Eurozone. There is austerity and reform fatigue in the periphery. There is bailout fatigue in the core. There's a rise of extremist populist parties of the extreme right and extreme left, both in the periphery. There'll be a huge amount of uncertainty and the Europeans will have to figure out whether they want to go towards more integration of Europe and more integration of the Eurozone, even if the voters are becoming increasingly skeptical about giving power to Brussels in the centre, or whether there'll be more variable geometry and less autonomy of nations within Europe and the Eurozone, but then having less of an integration that might be needed to have a complete monetary union. So I think this set of economic and political uncertainty is going to bear on economic growth. They're going to bear down on financial asset prices. They're going to create a significant amount of uncertainty. I don't expect a global recession or another global financial crisis. I think that the shock that comes from Brexit is significant, but not of the same size and magnitude as the one we had in 2007, 2008 and 2009. However, I would say it's a major significant financial shock as the reaction of the markets on Friday suggested. It creates a whole bunch of economic, financial, political and also geopolitical uncertainties.


Good morning everyone and welcome. This is Melissa Arma with the Stock Squish reviewing here Amazon Really nice option. I caught on this yesterday and actually you know, I mean you could have even said that I called it late, but busy office week for the room and looking at things when I can but when I saw it despite the fact that it rallied into The afternoon I still said wow, this is lower. So I called the 1300 puts yesterday It was around the afternoon period for Amazon expiring April 16th April 6th. I'm sorry Because I wanted to do out a full week at minimum least Based on the holiday coming up this week didn't want to do anything with an expiration date obviously of today But Amazon is lower. So this is already up Really really nice call and I don't know how many people did it on the letter because a lot of people saw that rally Probably in the afternoon in the tail didn't even matter stock up down today is lower It's taken a hit and this doesn't change the trend of Amazon Amazon is still strong still one of the strongest things in the market That's true, but it's not moving higher right now. It's not a buy right now. When is it a buy again? I don't know. I'll see it when I see it. I can't predict when something's gonna turn around and change Direction right now. It's falling and that's what you play. So the bottom line is Amazon is lower Really nice option call running a special for Easter only through Saturday only through Saturday March 31st for the next golden gap class if you sign up You receive the options that are free to the end of 2018 and also the trading room free to the end of 2018 to get all My calls long shorts everything But very interesting here to be calling puts is options trades because most of the ones have been calling this year have been calls and This baby is a put and it's working and it's up and it looks like it could be a biggie So congratulations to everyone that did do it and Have a great weekend everyone email me at Melissa the stocks wish comm if you want to sign up for the Easter special for the Golden Gap class Expiring Saturday. Have a great day everyone