One visual asset news. My name is Robert. Today I want to talk to you about is just a quick update about what's going on with world mobile token. And if you haven't heard me talk about this before, this is one of those crypto projects that has a real use case. This is a world mobile token scan link in the description. You can find this for yourself. And this gives data internet usage to the unconnected right now in Tanzania and Zanzibar in Africa. And it looks like the total network consumption over the last day or so is 1.71 terabytes. Now, that's not an enormous amount in first world countries.  So what I want to do is talk to Mickey Watkins. He's the CEO of world mobile and him and his team here. They have over 100 plus years of telecommunications and mobile phone experience just to see why they're doing this and just to give the updates. To talk about the why, it's very simple. And that is that in the entire world, we've got around 7.5 billion people, give or take. And right now, we've got about 3 billion people that are unconnected and are just in areas that just do not have the internet whatsoever. And if we keep doing it the old way, it's going to take us to 2050. So what world mobile did was this. They go, we're going to make this very simple. Instead of putting in those enormous cell phone towers for telecommunications and data, which costs millions of millions of dollars, which of course, they'll never be able to recoup because in those different areas that are unconnected are usually poorer. We're going to put in these. They're very small, very simple. And it's called an air node. And that's what's going to give these people access. So once this goes into the areas where people actually live and are unconnected, once this is already set up, the person that is living in these areas will go to their local shop. They will buy a card that will give them access to the world mobile token app. Once they have access to that and they paid for it, now they're going to download the world mobile token app because they have finally have access. That's going to give them a digital ID. And they're going to have access to these different apps, talk, text, financial service apps, which will give them access to the global economy, which is pretty big. But the question that is, well, why don't they just keep using cash or whatever their local currency is, instead of using Cardano for access to the network? It's because of this. The infrastructure to have telecommunications is not just just some magical wireless app. You have to have some type of infrastructure that keeps the data that puts the data out. And the only way to do that is through a sharing economy. And the best way to do that is in a decentralized manner, usually through earth nodes. And of course, we have our air node right here. And we talked about right in this picture right here.  And what this does is it gives them access to authentication, identity, of course, the blockchain, engine node communication and all the data that you need to store to run the actual business itself.  So I actually have skin in the game. And then lastly, I will just say that there is, of course, we have these air nodes, but if you want a super air node, we can have one of these things called aero stats, these are the ones that are delivering the huge payload, they rise up in the air about 1000 feet, and they give a coverage around 50 feet. So if you need a large area to be covered, and you don't have any cell phone towers whatsoever, this would be the way to go. So without further ado, let's break in and talk to Mickey Watkins, the CEO of World Mobile, and see what he has to say about the updates. All right, so everybody, what I want to do is like we talked about in the intro, just bring up Mickey Watkins just to ask some basic questions. Mickey, thanks for coming back. I think this is like the third or fourth time you're on the show. I'm a regular and I love it. Thanks for having me on again.  So I got three big questions for you. So first of all, what's the status of these earth node operators on the I attest net? I know there's a lot of questions going on there and people want to know. So it's a good thing you're here, we can talk about it. The second one is, what's happening with branching out to other countries? It's great that we're starting in Africa and Tanzania and you got everything worked up. But I mean, we got three billion people to help service. So how are things going with that? And then lastly, what are some of the things you're most excited about and not excited about for this year? Like what's hindering progress, that type of thing. So those are the three questions. Let's start with the first one. What's the status because I am an earth node operator. Mickey, as you know, I'm getting a little restless. So tell me what's going on here. Okay. The community is also very eager to jump on. I believe that tomorrow we, during our AMA, which you'll move invited to come to. And so as everybody else listening here, there will be an announcement from Antonio on the next onboarding process for earth node operators. But we're looking to get everybody on to test net really rapidly. Okay. As rapidly as we possibly can. Sounds good. So is it like a time frame we're looking at or just kind of like, Hey, we're going for this. Let's see what happens. It should start next week. I believe the first punches of people to come on, and then it won't stop until everybody's on. It will be phased because we learn a lot of information as we bring, as we bring people online. But it'll be quite rapidly phased as well. Perfect. Way too much longer. Okay. I'm okay with that. So you're telling me that there's doing me no earth node left behind. That's what it sounds like. No earth node will be left behind. They're operator. Okay. I'll take it. So that will answer that question. I think people will be a little pleased. At least moving the right direction. That's the big thing. But this was a question that's, uh, well, we had talked beforehand and you would said about branching off in other countries, most of the United States. So let's talk about that. How'd that happen? What's the timeline and why are we going this route? 2022 was really about fine-tuning the share in economy, making sure that we had the right equipment, testing. We tested maybe 30 or 40 different manufacturers of air nodes and different components that we put together and exploration, exploration for where world mobile could go where it wants to go. And where we wanted it was a massive road show as well as deploying and getting the Zanzibar network live and building the connections for the next couple of years. So we're very privileged to have many countries that would like us to come in and provide the the aerostat solution on this side and the on the ground network as well. But we've got to be focused. We've got to be focused because in order for the business plan to work to build one of the biggest mobile networks, we're going to have to come together. And to come together, we're going to have to make sure that the the air nodes that operate the network, the operation air node that is actually a core of the business where we reduce the capex load on any telco and allow us to grow very fast. And the OPEC side or the people that are looking after the the air nodes and operating them has to work. So in Zanzibar it's working. We do have paying subscribers on the network and WMT scan will soon be updated to to show everybody that and that's a very exciting moment for us as well. Now we've seen it working in Zanzibar. There's a few strategic countries that we want to go into first, not just because we want to jump straight to B2C, but also because there's wholesale models that can that can really grow the world mobile network super fast by bringing in revenue into the network that then the sharing economy is able to to share. And that's that's the whole model behind what we're doing, right? We're connecting the unconnected because we believe that everybody has the right to to connect to the internet, but also believe that the big MNO is also believing that's a right. They just don't know how to do it. Our model is something different and moving into other countries, moving into Asia, moving into North America and moving into other parts of the African continent is very exciting and 2023 is about cementing, making sure that we stick to our roadmap and hopefully over exceed the expectations of the community and the people that are inside this sharing economy. So USA is very exciting, but so is the Asian country and the African countries that we're operating as well. Right. Got. I mean, yeah, no, it's it's it's super exciting. I will just tell you, so when I heard about the USA, I was like, well, first of all, how hard is it to compete to get into the US market? Because I mean, we've got here, I mean, here in the US and here in Puerto Rico, we mean, you've got you've got the T-mobiles, you've got the AT&T's, you got the horizons and everything else that's out there. So like, how hard is it to competing? It's so hard. Like, I don't know why anybody would compete. It's completely oversaturated. But whilst it's oversaturated, that's in the connected areas in the underserved areas where the Swiss whole Swiss cheese problem exists. And in the rural areas where there's absolutely no coverage, then there's it's not competition. Our radios, our antennas, our equipment, our infrastructure can really go further than never before than anybody else has. And the model is really exciting. So we're not competing, competing at all. We know we're complimenting and actually just providing cellular coverage where underserved areas don't have the right amount of coverage they should have or none at all. Right. Yeah, I've got a place. So I have a sports facility on the outskirts of El Paso, Texas, El Paso County. And it's kind of spotty out there. So I can see that would be one of those areas that potentially could be serviced. I could see that that happened. You're going to be a nano donor and an operator by the sounds of it. Yeah. So apparently it's going to look something like this, right? Like we talked about going to have one of these just put out maybe a little bit more of a structure and then have people use these things for telecommunications and mobile service. That's what it sounds like to me. Yeah, it's going to look like that with a few more heads on it as well. We're going to put it up there and it's going to it's going to do exactly what it's meant to do. And then you can see how if you put enough of these in areas where there is underserved areas and people will seamlessly connect as they pass through on their phone, roaming customers and your own customers, it's it can quickly rack up adoption. Yeah, I think it'd be the big one with the roaming, especially if people have had the roaming service on. Okay. So it makes a lot of sense, especially under serve areas and of course the Asian countries. I mean, there's a lot of different places that have no service from what I understand. So I guess that will lead me to my last one. I mean, we already talked about the countries, but what are you excited about now moving in 2023? You guys done a lot of work over the last couple of years. And I think we did our first video at least a year and a half ago. So now we're already at this point where we have a working product. But what are the things that are hindering you? And what are you more excited about moving forward in 2023 and 2024? Bothering me is the is the era start, but this is just time. It's everything that we are meant to have done. We've done and I'm looking very much forward to launching that baby and seeing it fly or float. Very excited about the mobile application. We've got some really surprised features there for the community and for the wider crypto crypto environment. And I'm super, super excited of where we're going to be in June or July when the antenna, the final model is out there and we can put that up on the era start. And we've actually got the beginning of the end of the dynamic network because we'll have some nodes laid down strategically in order to function with the era start and coordinate from the ground. And we'll be able to show something that nobody's ever done before that's actually massively useful to the connecting the unconnected. And not only show it, we're not looking particularly to sell this product. We're looking to utilize it and build this network from it. So it's super exciting. And then whatever else 2023 has in store for us, we're trying to stay super focused. We've got a very big team now. We learned a lot from 2022 and we're looking forward to taking that forward. This is the year of the era start. This is the year of main net. This is the year where the sharing economy actually starts to bring revenue into the network. This is where the rubber meets the road or the telecommunications meets the phones. Okay, Mickey, sounds like a good time. So look, everybody who's watching the video, there's a link in the description. You can find out World Mobile Token, World Mobile Team and everything else that's with it. Mickey, thanks again for stopping by the show. Always good to have you. We'll bring you back when all the new stuff that's coming in. Thank you very much, Rob. See you soon.


Hi everyone, Joe for jaskiescasecreates.com doing a quick little team random for Prism football team all five box picker team number one and with break credit in here as well So we just sold 14 spots. Everyone's guaranteed something for your 14 spots. Everyone's gonna get something But a random something we're just randomizing names So the name on top will get the dolphins the name on the bottom will get the New York football Giants The second name down will get three hundred dollars in break credit. That's pretty nice So big thanks to these folks here for getting into it Let's roll it. So we're just right again just randomizing names Not that list not the other list of teams and break credit just your names. So good luck eight times four and a four hard eight one two three four five six seven And good luck faith and final time after eight. We've got a couple Roberts on top So there you go Robert Kanos with the dolphins Robert Briggs with the three hundred dollars of break credit I'm gonna email that to you Robert Briggs Check your spam folder if you don't see it in your email do it right after this video Ryan with the Packers Matthew with the Cowboys Michael with the Raiders got my Raiders Jack He got the Broncos Nicholas with the Niners Robert Briggs with the Lions Adam with the Jags Nicholas with the Cardinals Adam with the Seahawks Eddie with the Jets Ramon with the Saints and Rick Serrano with the Giants There you have it for the people one teams We're gonna put little rooftops next to your name so you know you won that in a team random I'm Joe for jazby's case breaks calm. We'll see you for the break


Thank you very much, and welcome all of you to the White House here. And let me say a special welcome to your chairman, Ambassador Joe Rogers. I just told him I was going to blame him and say he made me late coming here, but I won't. And to Pat Barrett, who did an outstanding job heading up your youth initiative program. Two hundred years ago this month, we all know a small group of men met in a room in Philadelphia to draft a new order for the ages. For the two centuries since then, the constitution they drafted has been the enduring guide for what they called the great experiment, and Lincoln called the last best hope of earth, the United States of America. The heart of that experiment, the living soul of that hope was and is the simple proposition that the people should control the government and not the other way around. I delight when I meet with young people in schools and tell them how many constitutions I have read of other countries, and how much they are like ours in many ways, except for that one difference. Their constitutions are documents in which the government tells the people what they can do, and ours is a document that says the people are telling the government what it can do. Let's keep it that way. You, the supporters of Vote America, are in the forefront of helping to keep that experiment a success and to keep that hope alive. Without the right to vote, there's no American experiment. Everything that's great in our nation arises out of that broad right, just as the majestic Rockies rise out of the vast great plains.  Too many have said, well, I'm busy on election day, or my vote doesn't count much anyway, or I'm going to be away, and it's too complicated to get an absentee ballot, and the result has been that fewer and fewer people have shown up at the polls. It was quite a shock to me when that first in many, many decades, that first democratic election occurred in El Salvador, and with the guerrillas, the communist guerrillas, threatened to kill the people on their way to the polls, and a woman stood there, wounded by rifle fire, and refused to leave the line until she had voted. And there were other stories similar to that, and I think about 83 percent of the people wound up voting. We haven't had that high a percentage vote in this country, where all they have to do is just walk down to the polling place and get it over with. And we've got to change that. Incidentally, let me say that Will Rogers, the great kind of country philosopher that he was, Will Rogers once said, the people in public office are no better and no worse than the people who sent them there. But they're all better than the people who didn't vote at all. So let me pause here and say that I've noticed over the years that many of those who find reason to complain most loudly about the state of our nation, no matter whether Republicans or Democrats are in office, they turn out to be the people who don't find time to vote. They remind me a little bit of a man who was on a roof with the floodwaters all around him, and a boat came by and offered to take him off, and he said, no, I've placed my faith in the Lord, and he'll take care of me. And a little time later with the water much higher along came a motorboat, and they offered to take him again the same answer, no, he placed his faith in the Lord. And finally a helicopter dropped a line, and he wouldn't touch that. And he was swept away and drowned, and he got to heaven, and he said, I don't understand, I placed my faith in the Lord. And here I am dead and in heaven, and a voice from above said, I sent two boats in a helicopter. Well, when it comes to deciding our nation's future, the Lord has sent us each boats in a helicopter our right to vote. Six years ago, Joe Rogers decided that there'd been enough talk about declining boat or turnout. It was time for action, and like a modern Paul Revere, he decided it was time to sound the alarm. Just as Paul Revere carried his message to every middle-sex village and farm, Joe and all of you in Vote America are carrying your call throughout the land. You aren't shouting from horseback, of course, you've got a faster, more modern means, television and radio, and you're producing shorts for movie houses to show, distributing bumper stickers and posters and sending out direct mail appeals. But however much the medium has changed since Paul Revere's time, the message is still the same, that it's time to stand for freedom. American voters may not have to face musket fire, but when we vote, we're standing for the same things the Minutemen stood for, the same things Americans have fought and died for throughout our history. We're helping to keep our country free, to keep our government one of, by and for the people. I especially like the fact that you're focusing your efforts on four groups, Americans who in particular should vote, but too often don't. One of those groups is young people. No one has a greater stake in the future of our nation than do our young people. We have their entire adult lives stretching out before them. Yet young people are the least likely of our citizens to show up at the polls, and you're helping to change that, helping to get them to register and vote. Another group is new citizens. Many immigrants have come here because they yearn to live in freedom. Many are here because freedom has made America a land of opportunity for all. But often getting registered is a baffling process for these new citizens. You'll be helping them with advertisements and announcements in publications that immigrants in particular read, and with spots on radio and TV stations that large numbers of immigrants listen to. Then there are our men and women in uniform. In the last two elections, you've helped the members of our armed forces and their families vote through absentee ballots. I can't think of any prouder service you can perform than assisting those who are on the front lines of freedom to take part in our democratic process. And finally, you're launching a campaign to reach Americans who can't make it to the voting booth on election day. And I appreciate this because Nancy and I are often in that boat. Like many Americans, we're often away from home on election day, so we use absentee ballots. You'll be getting the word out about absentee ballots to business travelers as well as the handicapped and students. You'll be helping these voters learn about how to get a ballot, and then you'll be urging them to fill it out and send it in. Everyone in America owes each of you a vote of thanks for all you're doing. As I said, you're helping us all preserve, protect and defend our liberties. Before I leave, I thought I'd tell you one last story. These days, a lot of things remind me of stories. I particularly like to collect those that I can be sure that people in the Soviet Union tell one another in private when the authorities aren't around. And I make sure that I can check them out, that they are truly stories from behind the Iron Curtain. They show how the people there feel about their system, in which, of course, they can't vote freely and in which only approved candidates can run for office. This one's about Comrade Ivan from Leningrad. He was a member of the Communist Party, and after many years of service, he was at last trusted enough to be sent on business out of the country. First to Eastern Europe and then to the West. And every place he stopped, he did what he would do. He sent a postcard home. So after a few days, the first card arrived in Leningrad. And it said, best regards from Free Poland, Ivan. Free Poland, that's how the Soviets refer to the nations of Eastern Europe. Free Poland, Free Czechoslovakia and so on. Week later, the next card arrived. Best regards from Free Hungary, Ivan. A few days later, best regards from Free Bulgaria, Ivan. Then a week passed, and then two weeks, and finally another card. It said, best regards from France, Free Ivan. All of you are helping to keep America free, and I thank you for what you're doing.  I just yesterday got a new Soviet story, and I just have to share it with you. Well, it seems that they put out an edict, too much speeding. And the police were to give tickets to anyone that has caught speeding in the Soviet Union, including those vast government limousines, no matter how high up and how ranking the individual.  He was needed to the Kremlin. He was late, and he liked to drive anyway. And he told his driver, you get in the back seat, I'll drive. And down the road, he went breaking all the speed limits. Two motorcycle policemen, and one of them caught him, caught up with him, came back to the first policeman in a little while, and the other one said, did you give him a ticket? And he said, no. Well, he said, why not? Oh, he said, he was somebody very important. But he said, there's supposed to be no exceptions. Everybody, no matter who was supposed to get it. He said, who was so important? Well, he said, I couldn't recognize him, but he had Gorbachev for a driver. And now I'm going down to the blue room there so that I could meet each one of you individually, and we can shake hands and say hello. So I'll go down to the blue room.


Okay, we are live. We'll just start, David. Oh, yeah, I can't, sorry, Igor. I thought you were gonna kick it off and I'd say a few words. Thank you for organizing this event Igor. And thank you to everybody for joining. These meetups are intended as a way for you to learn more about what's going on in the hyperledged community and to ask questions and then make connections with other people. And hopefully, you know, you'll find out something that's interesting for you. And as an open source project, if you do see anything that's interesting, you can get involved. You know, this meetup is just one event, but we have a lot going on in the hyperledged community. There are other calls, you know, other ways for you to engage. So if you are interested in what you hear, we would love for you to, you know, get involved in the community. So I can drop a couple of links to where you may go if you are interested in learning more. But with that, I'd like to hand it off to Igor to announce the speakers and we'll listen to what they have to share. Yeah. Hello, everyone. I would like to introduce Danny and Yov from IBM Research. Now we'll talk about hyperledged Orion, which is, which is the Orion is a standard database with the blocking properties that provides the temper evidence, provenance, data, lineage, autistic, city, non-reprediction and multi-seq capabilities with standard data model and transactional API. So Danny and who is a manager of the Blockchain Technology Platform at IBM Research and Yov, who is a research staff member in the same company, they will tell us more about hyperledged Orion. Please feel free, ask a question at the end of the presentation and enjoy, enjoy this time. Okay, so hello everyone and thanks for the invitation to the Hyperledged Labs event. It's a real pleasure to meet with you today. In our talk today, Yov and I will present you our centralized trust blockchain database technology named Orion developed by IBM Research that was recently accepted to the Hyperledged Labs community. I hope that by the end of this session, even those who are less familiar with centralized blockchain approach will understand how this technology can play a key role in building trust in your business ecosystems. So let's start with the short background. As you probably know, trust is crucial to the growth and success of business ecosystems. According to the study by Boston Consultant Group, trust was indicated as approximate factor in the failure of more than half of unsuccessful ecosystem and matter a great deal of success in more than 70% of the successful ones. However, it's important to understand that business ecosystem vary in their topology and the intrinsic level of trust between participants and therefore has different trust requirements. From the topological perspective, the ecosystem can be divided into centralized ecosystem with at least one party highly or partially trusted by all participants and decentralized low trust ecosystem with no single trust party. In highly trusted ecosystem, it may be enough to ensure independent, consistent and crash tolerant recording of the data. While in limited trust environments, we may also want to verify the correctness of the recorded data, ensuring authenticity and providing temporary evidence and data lineage. Finally, in low trust environments, we may need to control the transaction execution by supporting multi-party approvals, parallel execution of smart growth drugs and even reaching a consensus in presence of malicious parties. There are three major types of technology that can help to close the trust gap in business ecosystem. First of all, the classical database with the basic recording features usually sufficient for proper operation of highly trusted centralized ecosystems. While blockchain databases that extend classical database capability with proofs and controls are the best choice for limited or low trust centralized ecosystems. Finally, decentralized ledger technology that usually provide a full stack of trust features should be used in low trust decentralized environments. It's important to emphasize that support of advanced trust feature usually result in higher complexity and may impact the performance and increase the operational cost of the entire solution. So why and when should you consider using blockchain database technologies? Look, most of the business ecosystem today and probably your systems as well operate under centralized trust assumption which means that there is at least one trusted party like cloud provider, government organization or some big player while the other participants doesn't have to trust each other. For example, organization usually trust the cloud provider not to block their clients intentionally from accessing services although they can easily do so. However, having a trusted party doesn't mean that the other participant should blindly trust it. And as our experience shows there is still plenty room for further improvement of trust in centralized ecosystem. For example, participant can benefit from having transparency into data lifecycle and the ability to prove the integrity and consistency of data which is very important to streamline the auditing process especially in highly regulated environments. Ensuring authenticity of data is crucial to prevent potential authorship disputes in the multi-party interactions. Finally, even trusted parties often want to restrict the power of their privileged user to prevent mistakes and fraud. Well-known classical databases that are widely used today in centralized ecosystem do not provide out-of-the-box capabilities needed to guarantee and prove the required trust features while the use of decentralized blockchain technologies for centralized systems is usually highly inefficient and doesn't justify the increased cost and complexity. Hyperlegiororians combines classical database with blockchain properties specifically targeting centralized ecosystem. Such blockchain database technologies according to Alibaba can reduce the deployment cost by at least 75% compared to decentralized blockchains. And according to Gartner we'll replace most of the permission blockchain users. By 2025, the addressable market of such ledger database is expected to reach 2.2 billion dollars. Now, let's better understand what Orion is. First, Orion provides a trust layer on top of standard database with the blockchain features like authenticity and non-repudiation that can be used to prove that the data was received exactly as it was sent by the source preserving ownership disputes. It's also provide temper evidence which is the ability to detect changes to the protected objects even if done by privileged user. In addition, it enables provenance and data lineage which includes recording of all transactions of the data along the way. Finally, we provide a multi-seq mechanism to improve transactions only when signed by several designated parties which is very important to ensure trusted multi-party interactions. And all that comes with the classical database capability such as queries, resilience and scale, standard key value JSON store and transactional APIs to ensure that the set of read write operations are executed as an atomic transaction preserving consistency and data integrity. At the high level, Orion is implemented as a cryptography based layer on top of classical database. That is with a highly secure and replicated distributed database with temper proof immutable legend. It also enables history queries to extract information and proofs of integrity using GraphGP based provenance engine and provide read write key level access control to support privacy and multi-seq capabilities. You are welcome to join our open source community and contribute further advanced our technology and the following things should help you to get started. Now to better understand the applicability of Orion, I would like to share with you some of the key use cases that we have encountered in our work and provide the references to a few public projects that we can share. So in addition to the auditability use cases which is highly available in the regulated industries, there is a set of unique scenarios across different domains that Orion can help with. For example, the multi-seq capability can be used to automate many business contracting processes and easily support notary services. Orion can help to ensure authenticity and protect the integrity of the evidence collected through the insurance claims process. It can significantly simplify the management of lives and certificates, educational records, property ownership rights for government organization. It can be used to securely digitize the COVID vaccination status which is extremely important these days. And of course to trustfully reflect the provenance of goods and compliance to maintenance requirements in supply chains. Orion can be applicable in financial sector to support central by digital currencies and securities and can even be used as an off-chain store for the decentralized ledger ecosystem to preserve the financial data integrity across the hybrid environment. In less regulated environments like entertainment, for example, Orion can be used for media tokenization and even for a trusted reputation management. After a detailed examination, it was decided to use hyper ledger Orion as a blockchain platform in three EU projects. C4 IoT to build an IoT cybersecurity framework, Copa Europe to build a media trading platform and I4Q project to support smart manufacturing. Now I will let Yov to take you through the more technical part and demonstrate the ease of use of the hyper ledger Orion. So thank you and Yov, the stage is yours. Thank you, Danny. Let me share my screen. Let us take a look at the main components of Orion. The Orion database users have to be onboarded by an admin. Onboarding means adding the user's identifier and the certificate to the user's registry orion as well as setting the user's privileges. Users sign every request, both transactions and queries, which is used to implement authentication and authorization as well as non-repudiation. The state database is composed of multiple named database tables. And each of those is a key value store. Each row in a database table contains a key, which is a string, a value, which can be binary or a JSON document. A version, which is monotonically increasing on every right and is used for concurrency control. And finally, an access control list or ACL, which is used for fine grained access control. Multiple database tables are useful in order to manage user access, as well as in order to define custom indexes according to the schema of the JSON documents in them. The data in every transaction that mutates the state DB is also stored in a graph database. The provenance store holds the history of key value pairs, as well as the relations to users and transactions. This provides an easy way to query and retrieve historical data and explore the complete data lineage. The component that gives Orion its blockchain properties is a set of append-only authenticated data structures. Orion uses a hash chain augmented with a skip list, a hash skip list, in order to bind blocks together, a mercury for the transactions within each block, and the Patricia Mercury on the states, like Ethereum. These data structures allow Orion to provide succinct proofs of two aspects, the existence of a transaction in the ledger and the existence of a state at a specific ledger time. In Orion, as in a hyperledger fabric, transactions are batched into blocks and the blocks are signed by the server. The server also signs every response to a client request. The combination of these features provides immutability and temper evidence and allows Orion to serve as a trust anchor to establish trust between users. So far, I describe the single-note perspective of Orion. However, Orion is based on a cluster of servers, which relies on raft consensus for replication. Clients can connect to the database via REST API or using an SDK. So far, we have fully implemented a Go SDK and we plan on providing SDKs in other languages too. The administrator can connect via REST or use the SDK as well. The admin set of APIs allows the administrator to manage users, database tables, the cluster configuration, and certificate authority information. Let us now take a brief look at the programming model using the Go SDK. Our main goal was to maintain the simplicity of the key-value store. Every database session starts with creating a database instance, which loads the connection details of the cluster. A specific user will then create a user session using his credentials, that is his private key and certificate. The session serves as the starting point for transactions. We support two categories of transactions. Admin transactions and user transactions. They all look roughly the same way. Database management transactions are used to create, delete, and query the existence of a database table. User management transactions are used to add, update, delete, and get the credentials of users. Cluster configuration transactions are used to add or remove cluster nodes, manage the parameters of consensus, etc. Admin transactions can be executed by admin users only, and are recorded in the ledger like any other transaction. This makes admin actions and config changes traceable, just like any other piece of data. Data transactions are what concerns most users. Here we support multi-key, multi-database transactions. A transaction starts by creating a transaction object, data tx in the figure to the right. That object can be used to create, read, update, and delete multiple keys for multiple database tables, all in the context of a single transaction. When the user finishes manipulating the data, it calls commit, which creates a transaction envelope that captures all the reads and the writes on the data, signs it with the user's key, and submits it to the server. Transactions provide the ACID properties and are serializable. As I've said earlier, each key value pair has a version. The transaction object records the read set, where each read is a key and the version, and the write set, where each write is a key and the new value. Each key value pair is accompanied with an ACL. Readers is a set of users that have read access, whereas writers is a set of users that have both read and write access. As I've already mentioned, users sign each transaction. The transaction will be valid if and only if the signer has read and or write access to the keys involved in the transaction. In addition, we have a flag called sign policy for write, which determines how many writers need to sign in order for a transaction to be valid. Any means that any user from the writer's set is enough, whereas all means that all the users of that set must sign. The addition of a key-level ACL and the write policy provides fine-grained access control and opens up a lot of possibilities. For example, setting just readers and no writers creates a read-only immutable key value. Setting two writers with policy any means that either Alice or Bob, for example, can write the key value. And setting two writers with policy all means that both Alice and Bob are required to sign the transaction in order to make it valid. All this while granting read access to a third user, Charlie. The last example is an instance of a multi-signature transaction, which is extremely useful in some business flows, as we'll show in a few minutes. The values in a database table can be JSON documents, and if so, it is possible to define an index on their fields and execute range queries. Orion supports the JSON queries index in a format very much like CouchDB. So the learning curve should be easy to manage for people familiar with it. The last set of APIs exposes the provenance information Orion maintains. It allows you to answer questions like, what is the evolution of the values of this key? Or which users have read or written this key during a transaction? Or even which keys were read or written by this specific user. And this is just a partial list. Now, let's demonstrate some of these features using a simple example on a car registry. In this example, an imaginary department of motor vehicles runs the registry that keeps track of all the cars in the country and their ownership. This is, of course, an oversimplified scenario for ease of presentation. The first role in this scenario is that of a DMV officer which approves transactions that bring new cars into the system, what is sometimes called minting transactions. The DMV officer also approves transactions that transfer ownership between the users. The second role is that of a car dealer which submits mint requests to introduce a new car into the system while becoming its owner. The car dealer later sells the car to a new owner transferring ownership to her. The third role is that of regular car owners which can transfer ownership between each other in the process of buying and selling. Note that we assume that the DMV is required to be part of every such transaction by law. There is another role here, that of the service provider, database as a service, for example, but we will not address each role in this example. The car minting procedure goes as following. First, the dealer executes a mint request transaction inserting a mint request record with the required information. The record which identifies the dealer and the car is accompanied with an ACL which allows only the dealer to write to that record and allows the DMV to read it. Next, the DMV reads the mint request record, inspects it, and compares it to the actual car and then insert a new car record into the database. The car record is again accompanied with an ACL but this time it lists both the owner and the DMV as writers, and requires that every change in that record be accompanied by the signatures of both. Let's take a look at the code of one of these transactions. This is the mint request transaction. The data transaction is started from a user session, in this case the dealer user. It then prepares the record, verifies that the record does not exist already in the DB, and then writes the data with the put method. The commit method then packs the transactions read and write set into an envelope, signs it, and submits it to the server. The result of the commit is a transaction receipt signed by the server. The user can then save the transaction envelope and transaction receipt to his local storage as evidence of the transaction execution. As you can see, it's very simple to understand and very intuitive for database developers. The transaction receipt is basically the block header of the block in which the transaction was committed and the index of the transaction within the debt block. You can also see that the header contains the hashers for the hash keep list, the Merkle tree, and the Merkle Patricia tree. In the next step, the current owner, the dealer, sells the car to Alice, the buyer. The transfer of ownership is implemented as a multi-signature transaction. First, the car owner prepares the transaction, just like we saw earlier. It reads the car record, which is captured in the reset. It then changes the owner to Alice and changes the ACL to Alice and DMV. It then adds Alice to a field in the transaction called must sign users, which allows the initiator of a transaction to require additional user signatures. He then signs the transaction, but instead of submitting it to the server, he sends it to Alice. Alice, the buyer, will inspect the transaction content. For example, checking that she is indeed the new owner and then add her signature. She will then send the double sign transaction to the DMV. The DMV will again inspect the transaction and validate the details, the new ownership, the new ACL, and the signatures. The DMV may also run provenance queries or add custom logic, such as checking that the owner, buyer, or car are not on some blacklist. The DMV officer will then add her signature to the transaction and submit it to Orion. The Orion server deems the transaction valid, only if it is correctly signed by all three parties. The owner and the DMV are required because of the current record ACL, and the buyer is required because it is specified in the must sign user set. I will not show the code for this transaction. Instead, I will refer you to a self-service demo with detailed instructions in our Go SDK repo. The example cars package allows you to deploy an Orion server and run car registry transactions, as I just demonstrated. After the completion of the ownership transfer transaction, the Orion server will contain this virtual dependency graph between transactions and records. The transaction, the transactions, which are signed by the users, are producing records via the right set and in turn are consuming records via the read set. The provenance API I had shown earlier allows the user to easily traverse this graph and extract insight on its evolution. Now let's assume that Alice wants to sell the car to Bob. However, Bob is suspicious. He asks Alice for a proof of ownership. As I mentioned earlier, after commit, the users may save the transaction evidence, which is the transaction receipt and the transaction envelope. Alice, or the DMV for that matter, can give the evidence of the ownership transfer transaction to Bob. Bob can inspect the transaction content, and then with the evidence, Bob will ask the Orion server for a proof of the transaction's existence in the legend. The server will reply with the hashes of the skip list path and the hashes of the market repath. Bob can then verify these proofs locally. The complexity of getting and validating the proofs is all hidden by the SDK, and the developer generally does not have to go into these implementation details. However, let's dive a little deeper and see, how does Bob verify the proofs? Well, he simply verifies the hashes of the has skip list path from the last block to the blocking question and from the blocking question to the Genesis block, the first block in the legend. Note that the size of these proofs is logarithmic with the number of blocks. Next, he recomputes the Mercury root from the respective hashes that were given to him by the server. And again, the SDK has utility methods to help the user do all that. In a similar manner, Bob can use the transaction evidence and ask the server for a proof that the states in it in our case the car record that the states are still valid with respect to the latest block. The server uses the Merkel patriciatry to construct the proof. And again, Bob can use utility methods in the SDK to verify the proof. The transaction and state existing proofs achieve two goals. First, they allow Alice and Bob to establish trust between them by using Orion as a trust anchor. Second, they allow users of Orion to detect tempering in the blockchain database by periodically requesting proofs of existence to pass transactions and states that they know should exist. For further details, please take a look at our online documentation. To summarize this presentation, Orion is a database with blockchain properties. As a database, it has a standard data model, transactional APIs, queries, resilience, and scale. The blockchain properties, it provides our temper evidence, provenance and data lineage, authenticity and non-repudiation, existing proofs for a transaction and a state, as well as multi-signature transactions. This concludes our presentation. Thank you for listening. And now we'll open the stage for questions. Thank you very much. Thank you very much, Dani and Joff. That was a great presentation. Any question, please? You can turn on your microphone or you can ask a question in the chat. Also on YouTube, feel free to ask a question. No, I have a question. So Orion, it's on GitHub. It's available. So it's open source, right? So it's a standalone node. You cannot understand the loan on premise or does it connect to some online services? It's a standalone node. Actually, it's a standalone cluster. And that's it. It's self-contained cluster database. And in GitHub, we have two repositories, one for the server and one for the SDK. And in the SDK, we have extensive examples and the demo is there also. And basically you have a SDK for Go and REST APIs, right? Right. The cluster API, the server API is REST and the Go SDK rides on top of the REST API. That's correct. Thank you. Great. Thank you. We've got two questions on chat. Can you please share again the link, for example, to the demo for Cardio. Please put it on the chat. And the next question was, Rohan, can you give an example of application in supply chain space? You mentioned supply chain application in a previous slide. Sorry. Can you repeat what types of examples? The question is in the chat. I'm just trying to find it. Of course, supply chain. Okay. So in supply chain, it usually may be very important to have a provenance of goods through the supply chain. So in classical supply chains, there may be interaction between multiple parties, starting from manufacturing through the delivery companies, through retailers, all sellers, and at the end also potential even customers who own the goods and may in some cases even need to maintain them. So all the information that can be related to a specific asset can be recorded within the Orion database and keeping all these records in a secure and signed manner with all the capabilities to get the provenance of ownership and the state where it was, when it was maintained and so on, enables and provides full visibility into the entire lifecycle of the asset. So in supply chain is one of the classical examples for the use of blockchain capabilities and in the environments where we have a strong central party or a trusted provider like cloud provider in infrastructure company, we can definitely use and leverage Orion as a blockchain solution for that. Thank you. Danny, would you like me to read questions or you can check on the chat? Yeah. Is there a use case for punks? No example. You know, the performance question. Joao, do you want to take the answer on the performance one? Yeah, the performance, we are still in the early stages of, you know, productizing the silver. So we haven't done rigorous performance tuning, but from early testing, we can say that performance is better than blockchain, like fabric, naturally. But it will undoubtedly be lower than traditional databases. But I don't want to commit to numbers. I can say that the ballpark number is 10,000 transactions per second. At this early stage. And we still have a lot of work to do on performance tuning and improvements. So that's with respect to performance. Yeah, I see question on the bank or regulated space. So, look, as we said, the financial sector is one of the sectors that usually leverage or one of the, you know, pioneers in trying various types of blockchain technologies. And, you know, if we are talking, for example, about central bond digital currency, so different countries take different approach for central bond digital currency. So in some cases, they are going and trying some decentralized approaches for that. And some countries goes with centralized approaches. So we believe that for those who, you know, want to go with a centralized approach, Orion can be definitely something that they can leverage. And of course, in these specific situations, it can provide better performance alternative solution. But again, as you have mentioned, you know, you pay for additional features. So if it's compared to classical databases, yes, without all these trust features. So we will, you know, have a lower performance, but compared to the centralized blockchain technologies, that, you know, Orion can be the best fit in, if we are talking about centralized solutions. And also it can be, you know, in the regulators, just like the DMV example. Again, if you have a regulator, which is usually a highly trusted participant, not fully trusted, but maybe highly trusted participant in the ecosystem. So I also believe that in these kind of scenarios, use of Orion could be beneficial for these environments. There is another question. Is there a use case available for telcos, DSPS for blockchain hyperledger? For telcos. For telcos. So I'm just thinking loudly. I don't remember specific use for telcos.  But I don't think that at least from those that I can, you know, expose publicly the negotiations we can talk or refer to in the telcos space. Okay, so I will add from the hyperledger side that we've got a telcom special interest group. So I will share a link in a second. So telco is definitely a grow area. So it would be very interesting to hear what are the trust challenges in the ecosystem and also show how this kind of technologies can potentially be applicable in these domains. I must admit that we also investigate various types of hybrid environments. The hybrid environment is an environment that may include multiple Orion servers, which may interact with each other at some point or the interaction between hyperledger, Orion, for example, a classical decentralized blockchain databases, potential is enough chain store to preserve the integrity through the entire life cycle. So these kind of scenarios can also be interesting for us. So if you see any ecosystems that the combination may make a lot of sense, we'll be glad to know and be involved. There is a question here from Angelina about technology at the heart of the replication component. And how does it relate to fabric, for example? So yes, many of the design decisions here are inspired by fabric and that's not by accident. Three of us are fabric developers. One of the team members is a fabric maintainer and we know fabric very well. And the component that we are using, the style of replication that we are using is inspired by fabric. It's not exactly like fabric, but it's similar. So we try not to invent the wheel. And we are using the same library, the same ATCD rough library for replication. I hope that answers the question. And there is a question from Hubert about is it possible to connect Orion with Ethereum? So I don't have a food developed answer to that, but as Dani said, one of the use cases we thought about is using Orion as a verifiable off-chain storage in order to speed up things that happen in slower blockchain platforms like Ethereum or Bitcoin or whatever, or fabric. It's kind of an alternative to the off-chain transactions. You can do transactions through Orion and then do a netting transaction once in a while into the public blockchain or the slower blockchain. I see another question about the... Do we aim to have Orion as a pay for service and so on? So first of all, as you can see, it's an open source project so everyone can go download it and use it in their environment and so on. We're considering various ways of taking this technology and exposing this to the users. And of course, one of the potential threads is to provide it as a service for clients. And of course, in cases where clients or potential users or partners would like to have also some additional support capabilities on top of just using an open source project. This is the areas where we can, as an IBM see a way for potential collaboration. So I hope that it answered your question. I can add also about the CBDC project and Hyperledger that we are involved in the many CBDC projects. So please check on our YouTube with a couple of videos about the CBDC and Hyperledger. Also, share now one of the link. So please feel free. Yeah, I can just relate. We have an ROI team generally involved in other activities beside Orion. One of them is around tokens and support for CBDC stage space. So token SDK is also a Hyperledger project that we as an IBM and our colleague from Zurich has a place there. And it is used today in various interactions, especially for those that requires decentralized approach. But we also considering various ways of integrating these capabilities to enable tokens support on whatever underlying blockchain technology you decide to use. It can be Hyperledger Fabric and Orion based on your client needs. So that's the wider answer for the CBDC space. And there's two more questions and let's make them the last two questions. There's a question about a question from Arsanti. Can we consider Orion as a distributed network like Fabric? Where can we use it as a permission blockchain? So the architecture of Orion is very similar to the ordering service in Fabric. It's a rough-based cluster and you interact with it. And the users are, of course, everything. The users are, of course, permission. They have to be onboarded with a certificate. The difference, however, is that Fabric comes ready to have the ordering service hosted by multiple organizations. It's built that way from the get-go. And Orion does not do that. The cluster is managed by an administrator, which typically belongs to a single organization. And the nodes are... We think that typically they will be hosted by a single organization. They will be full tolerant and highly available, of course. But still, it's a single organization. And we think that this organization can be trusted. And it does not take part in the business interaction that the users do via Orion. I hope that answers the question. Hi. This is Prashanti. I just posted this question. Thanks for answering my question. Ideally, this can be chosen in a high-level, which is useful for public. Maybe kind of a voting system for a government. So it can be most suitable for sub-scenarios, but not within the kind of organizations. Like, suppose we have something called reward exchange program. And we have built one ecosystem where the parties can participate in that... I mean, whoever wants to exchange their points, so they can participate in their blockchains. So we can consider Orion maybe kind of a public, in a government-wise kind of use cases. So as a permissioned, maybe... I mean, as a permissioned blockchain, maybe we can consider this approach. But in a high-level, same like public blockchain, we can consider this well with an authority and with an authority. So am I right? So more than the... Yes, yes. I mean, what you said is exactly true. When you have an authority that... I mean, users are naturally, by design, are required to trust or have to trust, like government or maybe a big company that provides a service. Then that could be the anchor for trust among users. So we trust the market, like the New York Stock Exchange. And that enables us to trade stocks, right? It's a centralized system, but you and me don't have to trust each other in order to trade stocks. So that's kind of the analogy. Okay, okay. So can I ask this question? So are there any... We are already live with anything or we are building it now? We are already live with any... in partner or... Or we are... Sorry, I... No, no, I'm just asking is this project... product got deployed to any client or we are developing this? I just wanted to understand if somebody is using already and how this is working on production? This is not yet officially released. It's not production ready yet. But we hope it's good enough right now. It's good enough for a group of concepts for initial ideation for testing. And we are right now working on productizing it, testing, making it robust. We hope to get there in a few months. Yeah, it's really a good idea. Many projects or many clients, they don't like to keep entire blockchain node on their private network, on their own laptop or on their own system. So having one centralized and keeping the trust on that particular server is really very good. Appreciate for your work. Yeah. Right. As we said, there are many use cases that may go with a centralized approach and this kind of technology looks like the best fit for them. And again, I'm just repeating that we are encouraged everyone who believes that they can contribute to this effort. You're welcome. And we'll be glad to get you on board to work with that. So we'll be very appreciative. And I think there is one more question. You have the last one. Which one? Thanks for answering. Okay. One more, please. That's the definition of a new JSON schema data model coincide with the deployment of a smart contract on the background. If yes. Is this the job of an administrator or all participants can achieve this via the SDK? Okay. So first of all, there are no smart contracts in Oreo. It's not a smart contract abstraction. It's a data abstraction. It's like a database. So in a sense, the code that runs this thing runs on agents which are outside of the database. So for example, in the car example and the car demo, the flow that the dealer does or the flow that the DMV does would be implemented by smart contracts in things like fabric or Ethereum, right? But here it will be implemented by client-side code maybe by the service that envelopes the database, like in the traditional free tier architecture approach. So the code that envelopes the database is actually plays the role of the smart contract. So with respect to permissions, the schema of the database and the creation of the database itself is controlled by an admin. So you prepare the database, you define an index because you expect the type of documents that will be in there and you grant users a privilege to read or write or create documents in a particular database and then the users do their own thing. I hope that answers the question. Thank you so much. Thank you so much, Danny. Thank you for all participants today. That was so great. Great session, great questions. Thank you so much. I hope we all know more about Hyperledger Orion who would like to be involved. You've got links on the chat. Also, you'll find a recording on our YouTube so send this recording to all, link to the recording to all our participants. So thank you so much. How we can stay connected with you, Danny and Joff? I can write my email and I think Joff can share. Yeah. And through the GitHub we are there and we'll soon open a chat and a messaging channel. Okay. Thank you so much. Thank you again. Have a nice day, evening, whenever you are now because it's a Hyperledger London meetup but we are around the world and so happy about that. Thank you again. Please find more nice events, meetups on our meetup profile as well check our website. Thank you again and see you soon. Thank you. Have a nice day. See you soon, everyone.


Hello everybody! E here. Welcome back to Thursday Thiers. Today we are talking about Under the Dome.  Also one of the worst endings of any of his books. But that's not what we're going to talk about today. Actually we're going to talk about the ending, but we're not going to talk about how bad it is. This book is terrific for about 800 pages I want to say. And then things take a turn for the worst. And then he rebooted the whole concept in Sleeping Duties. And then they got Lee Child, 7 words, the best yet from the best ever. No. Now in here, there's a thank you to Tabitha or somebody for really whittling down. Maybe it's in the acknowledgments. Yeah. Tabitha and Lenora LeGrand, his daughter-in-law who were both tough, humane and helpful. So this thing was actually longer than the almost 1,100 pages it is, 10-1,061 pages. I tried this book when it first came out and I got about 300 pages into it and I gave it up. Then it sat on my shelf forever and I went back to it. I think in 2000, I can't remember, 2000 or something, I came back to it and I was able to finish it and I liked it all right except for that ending. When I did my reread, I liked it, in 2015 I think it was, I liked it a lot more but that ending is still bad. But once again like Tommy Knockers, the parts that I don't like in this actually help tie my whole world together. So again we have, and I haven't gone into this much yet so I'm going to go into it now, I believe that the aliens in Stephen King's universe, I've talked about this before to an extent that they are from mid-world. But I have not mentioned that I consider them to be the old ones. Whenever you read through the Dark Tower series and they're talking about the old ones, kind of like Lovecraft's old gods, King has the old ones, I think, I theorize that any time we see the aliens, whether it be Pennywise, the aliens in Tommy Knockers, the aliens in Dreamcatcher, any of those things that we are dealing with the old ones. That's why they are so powerful. Another thing that of course you get to and the ending spoiler alert is aliens. But there's a connection in there that they have to convince these old ones that humans are worth saving. In mid-world there's a drastic disconnect between the gods or the old ones and the prim and all that stuff. In the Dark Tower series you never even get into the prim. They never even go into the prim. Things leak over, but you never actually get there. So my theory, that's how it all ties together is these old ones, they leak into our world but we've never been over there because they deal with the afterlife. And we'll get into more on that when we get to Revival. But what did you think about this one? I've seen some people say that it is their favorite Stephen King novel of all time and I don't understand. In fact, I would go as far as saying that if this is the best Stephen King novel for you, you haven't read much Stephen King. But what do I know? I'm just a Stephen King theorist. So let me know what you think down there in the comments below and until next time I have been Ian, you have been Ian, and this has been another Thursday. There is video. I'll talk to you guys later. Bye bye.